dbc1e216e3
Change ISCSIDriver to set volume.provider_location during create_export. This records the location of the LUN, so that nova-compute does not need to run the iSCSI discovery code itself. As part of this, include the IP address of the target (--iscsi_ip_address) in the provider_location. This means that we don't use volume's host identifier (which could be an opaque ID) when trying to connect to the iSCSI target -- we use the admin-specified IP address instead. The string-join to set provider_location is shared with ZadaraBEDriver, which was doing something similar. I've brought that into a helper function. The docstring for the --host flag has been clarified. Change-Id: I8402da86345e786a46a4d222ad4d8a4449d2bd3f
The Choose Your Own Adventure README for Nova
You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://nova.openstack.org
To dissect it in detail: visit http://github.com/openstack/nova
To taunt it with its weaknesses: use http://bugs.launchpad.net/nova
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING
To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations