Go to file
Vishvananda Ishaya 69050622d9 Add initiator to initialize_connection
Some volumes need to know the name of the initiator that will be
connecting to the iscsi volume.  This adds a call down to the hypervisor
driver to get the ip and the initiator name for the vm before calling
initialize connection. This connection is passed down to the volume
driver so that it can be used to authenticate when the hypervisor
tries to connect to the volume.

 * Adds initiator initialize_connection
 * Makes a call to driver to get initiator name and ip address
 * Gets initiator from openiscsi for libvirt
 * Gets initiator from config for xenapi
 * Add tests for the driver calls
 * Fixes bug 924461

Change-Id: I5b6a2dd84560c7f7b447571e0abf0993e5512ca0
2012-02-04 11:35:16 -08:00
2012-02-03 19:21:54 +00:00
2012-01-20 12:33:38 +00:00
2011-12-08 15:17:51 -08:00
2012-01-05 10:21:57 -06:00
2010-05-27 23:05:26 -07:00
2011-11-20 18:54:08 -05:00

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

Description
RETIRED, Client code for the common scheduler for OpenStack
Readme 18 MiB