|
|
| (8 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| = iscsi - SOP =
| | {{header|infra}} |
| | {{shortcut|ISOP:ISCSI}} |
|
| |
|
| == Contact Information ==
| |
| Owner: Fedora Infrastructure Team
| |
|
| |
|
| Contact: #fedora-admin, sysadmin-main
| |
|
| |
|
| Location: Phoenix
| | This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/iscsi.txt |
|
| |
|
| Servers: xen[1-15]
| | For changes, questions or comments, please contact anyone in the Fedora Infrastructure team. |
|
| |
|
| Purpose: Provides iscsi connectivity to our netapp.
| |
|
| |
|
| == Description ==
| | [[Category:Infrastructure SOPs]] |
| | |
| iscsi allows one to share and mount block devices using the scsi protocol over a network. Fedora currently connects to a netapp that has an iscsi export.
| |
| | |
| == Typical uses ==
| |
| | |
| The best uses for Fedora are for servers that are not part of a farm or live replicated. For example, we wouldn't put app1 on the iscsi share because we don't gain anything from it. Shutting down app1 to move it isn't an issue because app1 is part of our application server farm.
| |
| | |
| noc1, however, is not replicated. It's a stand alone box that, at best, would have a non-live failover. By placing this host on an iscsi share, we can make it more highly available as it allows us to move that box around our virtualization infrastructure without rebooting it or even taking it down.
| |
| | |
| == iscsi basics ==
| |
| | |
| === Terms ===
| |
| | |
| * initiator means client
| |
| * target means server
| |
| * swab means mop
| |
| * deck means floor
| |
| | |
| === iscsi's basic login / logout procedure is ===
| |
| | |
| 1. Notify your client that a new target is available (similar to editing /etc/fstab for a new nfs mount)
| |
| 1. Login to the iscsi target (similar to running "mount /my/nfs"
| |
| 1. Logout from the iscsi target (similar to running "umount /my/nfs"
| |
| 1. Delete the target from the client (similar to removing the nfs mount from /etc/fstab)
| |
| | |
| == Loggin in ==
| |
| | |
| Most mounts are covered by puppet so this should be automatic. In the event that something goes wrong though, the best way to fix this is:
| |
| | |
| {{{
| |
| # Notify the client of the target
| |
| iscsiadm --mode node --targetname iqn.1992-08.com.netapp:sn.101197194 --portal 10.8.34.17:3260 -o new
| |
| | |
| # Log in to the new target
| |
| iscsiadm --mode node --targetname iqn.1992-08.com.netapp:sn.101197194 --portal 10.8.34.17:3260 --login
| |
| | |
| # Scan and activate lvm
| |
| pvscan
| |
| vgscan
| |
| vgchange -ay xenGuests
| |
| }}}
| |
| | |
| Once this is done, one should be able to run "lvs" to see the logical volumes
| |
| | |
| == Logging out ==
| |
| | |
| Logging out isn't normally needed, for example rebooting a machine automatically logs the initiator out. Should a problem arise though here are the steps:
| |
| | |
| {{{
| |
| # Disable the logical volume:
| |
| vgchange -an xenGuests
| |
| | |
| # log out
| |
| iscsiadm --mode node --targetname iqn.1992-08.com.netapp:sn.101197194 --portal 10.8.34.17:3260 --logout
| |
| }}}
| |
