lp:~rackspace-titan/nova/read-deleted-lp824008
- Get this branch:
- bzr branch lp:~rackspace-titan/nova/read-deleted-lp824008
Branch merges
- OpenStack release team: Pending requested
-
Diff: 32 lines (+4/-4)2 files modifiednova/api/ec2/cloud.py (+3/-1)
nova/tests/test_cloud.py (+1/-3)
- Brian Lamar (community): Approve
- Devin Carlen (community): Approve
- Alex Meade (community): Approve
-
Diff: 32 lines (+4/-4)2 files modifiednova/api/ec2/cloud.py (+3/-1)
nova/tests/test_cloud.py (+1/-3)
Related bugs
Related blueprints
Branch information
Recent revisions
- 1532. By dan wendlandt
-
This code contains contains a new NetworkManager class that can leverage Quantum + Melange.
Thierry suggested that I merge prop this to get feedback, even though it is too late to get a branch of this size in for D-4. Feedback will help determine whether we can get this code in during the Diablo time frame or not. This branch was developed stacked on top of the melange branch, which is still not merged, but I am merge-propping it without that branch so that the diff is correct.
The vast majority of the code is in nova/network/
quantum and is only invoked if the network manager is set to nova.network. quantum. QuantumManager In addition to implementing networks with Quantum instead of the linux bridge, the QuantumManager also provides a new, more flexible model of associating vNICs with networks. It supports the creation of networks that are specific to a project and networks that are "global". When a VM is created, it gets a vNIC for each project network, as well as each global network. For example, this could support giving a VM a "public" vNIC on a shared network and a "private" vNIC on a tenant-specific network.
The branch also implements Tushar's 'os-create-
server- ext' extension, so that the server create API call can indicate the set of networks the VM should be attached to (if this extension is used, it replaces the above mechanism for determining vNICs). QuantumManager can use either the traditional IPAM functionality in nova DB (i.e., the networks, fixed_ips tables) or melange. Similar to FlatManager, QuantumManager does not currently support DHCP, gateway/NAT, or floating IPs.
This branch requires additional testing before it is really ready for merge, but we thought it would be best to merge prop as soon as possible to identify any significant concerns people had.
- 1531. By Brian Lamar
-
Fixes a case where if a VIF is returned with a NULL network it might not be able to be deleted. Added test case for that fix.
- 1529. By Édouard Thuleau
-
An AMI image without ramdisk image should start.
It's possible with EC2 API but it fails with OS API.
This patch corrects that by returns 'None' value if AMI image doesn't contain 'ramdisk_id' metadata. - 1528. By Anthony Young
-
At present, the os servers.detail api does not return server.user_id or server.tenant_id. This is problematic, since the servers.detail api defaults to returning all servers for all users of a tenant, which makes it impossible to tell which user is associated with which server.
Similarly, when admin users access servers.list, all instances for all tenants are returned. Without a tenant_id field, administrators can't sift through the server list very easily.
This merge request does the following:
* add user_id and tenant_id to servers.detail
* makes it possible for admins to filter with the term 'tenant_id' (rather than project_id) - 1526. By Tushar Patil
-
Instance record is not inserted in db if the security group passed to the RunInstances API doesn't exists.
- 1525. By Tushar Patil
-
Added list of security groups to the newly added extension (Createserverext) for the Create Server and Get Server detail responses.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~hudson-openstack/nova/trunk