9ed6cd4fc6
The mechanism for managing these rules is very similar to how security group rules are managed except there is only ever one instance of the provider rule table, as opposed to multiple security group tables. Each instance will simply jump into the provider firewall table as one of its first actions (before security groups, so these rules cannot be overridden on a per-user basis). Most of the changes are straightforward if you understand how security groups work. There are a few small logging and variable name changes as well. Right now this only exposes the creation of provider firewall rules. If we agree this is the best path forward I will quickly be adding a list and destroy method and updating nova-adminclient.
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