c2fb9485f9
1) Specify number and order of networks to the create server API. In the current implementation every instance you launch for a project having 3 networks assigned to it will always have 3 vnics. In this case it is not possible to have one instance with 2 vnics ,another with 1 vnic and so on. This is not flexible enough and the network resources are not used effectively. 2) Specify fixed IP address to the vnic at the boot time. When you launch a server, you can specify the fixed IP address you want to be assigned to the vnic from a particular network. If this fixed IP address is already in use, it will give exception. Example of Server Create API request XML: <?xml version="1.0" encoding="UTF-8"?> <server xmlns="http://docs.nttpflab.com/servers/api/v1.0" name="new-server-test" imageId="1" flavorId="1"> <metadata> <meta key="My Server Name">Apache1</meta> </metadata> <personality> <file path="/etc/banner.txt"> ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBp </file> </personality> <networks> <network uuid="6622436e-5289-460f-8479-e4dcc63f16c5" fixed_ip="10.0.0.3"> <network uuid="d97efefc-e071-4174-b6dd-b33af0a37706" fixed_ip="10.0.1.3"> </networks> </server> 3) Networks is an optional parameter, so if you don't provide any networks to the server Create API, it will behave exactly the same as of today. This feature is supported to all of the network models.
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