Go to file
Jason Koelker 6acc317297 Fix for bug #798298
* Removes restriction of have to have an IPv4 network to create and use an IPv6 network
* Modifies nova-manage network to require either an IPv4 or IPv6 network be passed
* Modifies nova-manage network to ignore FLAGS.use_ipv6 (what is passed on the command line is what you get)
* Modifies nova-manage network to list IPv4 and IPv6 on list, no longer lists IPv4 netmask as it is implied by the cidr for the network
* Modifies network/manage.py to allow for empty IPv4 assignments.
2011-08-02 23:07:42 +00:00
2011-08-02 15:13:33 -05:00
2011-08-02 23:07:42 +00:00
2011-08-02 10:09:58 -04:00
2011-07-26 09:50:05 +04:00
2010-07-15 01:28:51 -04:00
2011-03-29 11:15:16 -07:00
2010-05-27 23:05:26 -07:00
2010-12-20 14:54:27 -06: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 @novacc on twitter

To tame it for use in your own cloud: read http://nova.openstack.org/getting.started.html

To study its anatomy: read http://nova.openstack.org/architecture.html

To dissect it in detail: visit http://code.launchpad.net/nova

To taunt it with its weaknesses: use http://bugs.launchpad.net/nova

To watch it: http://hudson.openstack.org

To hack at it: read HACKING

To laugh at its PEP8 problems: http://hudson.openstack.org/job/nova-pep8/violations

To cry over its pylint problems: http://hudson.openstack.org/job/nova-pylint/violations

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