lp:~termie/nova/nearly_direct_api
- Get this branch:
- bzr branch lp:~termie/nova/nearly_direct_api
Branch merges
- Paul Voccio (community): Approve
- Vish Ishaya (community): Approve
- Todd Willey (community): Approve
- Jesse Andrews: Pending requested
-
Diff: 349 lines (+137/-23)7 files modifiedbin/nova-direct-api (+33/-2)
bin/stack (+12/-2)
nova/api/direct.py (+47/-3)
nova/api/ec2/cloud.py (+13/-9)
nova/compute/api.py (+5/-4)
nova/tests/test_direct.py (+25/-2)
nova/volume/api.py (+2/-1)
Branch information
Recent revisions
- 874. By Sandy Walsh
-
In this branch we are forwarding incoming requests to child zones when the requested resource is not found in the current zone.
For example: If 'nova pause 123' is issued against Zone 1, but instance 123 does not live in Zone 1, the call will be forwarded to all child zones hoping someone can deal with it.
NOTE: This currently only works with OpenStack API requests and routing checks are only being done against Compute/instance_id checks.
Specifically:
* servers.get/pause/ unpause/ diagnostics/ suspend/ resume/ rescue/ unrescue/ delete
* servers.create is pending for distributed scheduler
* servers.get_all will get added early in Diablo.What I've been doing for testing:
1. Set up a Nova deployment in a VM (Zone0)
2. Clone the VM and set --zone_name=zone1 (and change all the IP addresses to the new address in nova.conf, glance.conf and novarc)
3. Set --enable_zone_routing= true on all zones
4. use the --connection_type=fake driver for compute to keep things easy
5. Add Zone1 as a child of Zone0 (nova zone-add)(make sure the instance id's are different in each zone)
Example of calls being sent to child zones:
http://paste.openstack .org/show/ 964/
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