dbedbc776f
This introduces a new flag "quantum_use_dhcp=<boolean>" which indicates whether or not to enable dhcp for all of the networks. If it is set then we start dnsmasq (and provide it with the IP/MACs from Melange) similar to how this was done in linux_net before. Prior to this if you enabled dhcp then you would also get a gateway device.. some people may not want that so we now require that you specify the gateway when creating the network in order to end up with a device that will act as a gateway. If you're using Melange IPAM and you don't specify the gateway you still end up with one because it doesn't allow you to not have one. This lays the groundwork for the option of not having one in the future, at least :) Also, fix quantum/melange ipam interaction We now query for the subnets by net_id/vif_id instead of searching through all the blocks to find the right one. Both of the allocate and deallocate for instance calls are now using the vif_id -> network_id mapping instead of searching the quantum networks. get_port_by_attachment was also changed to take a net_id so that we don't have to search through all of the quantum networks to find the corresponding port. Change-Id: I6a84da35237b6c5f5cdee91ada92642103439a97
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 laugh at its PEP8 problems: http://jenkins.openstack.org/job/nova-pep8/ To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations