diff options
author | Vishvananda Ishaya <vishvananda@yahoo.com> | 2010-10-13 16:28:46 +0000 |
---|---|---|
committer | Tarmac <> | 2010-10-13 16:28:46 +0000 |
commit | e5c89b94c1b4b06b2e64fb1c1e3481aca4d06a64 (patch) | |
tree | 0624f65037003073cdf4eac43045844af7885635 /nova/context.py | |
parent | d0a55238fdf64a8da51ea1fe328a1a3dc3d17dc7 (diff) | |
parent | d533d6414041437e642f2bbfbc7a86daa2527a65 (diff) | |
download | nova-e5c89b94c1b4b06b2e64fb1c1e3481aca4d06a64.tar.gz nova-e5c89b94c1b4b06b2e64fb1c1e3481aca4d06a64.tar.xz nova-e5c89b94c1b4b06b2e64fb1c1e3481aca4d06a64.zip |
This patch removes the ugly network_index that is used by VlanManager and turns network itself into a pool. It adds support for creating the networks through an api command:
nova-manage network create # creates all of the networks defined by flags
or
nova-manage network create 5 # create the first five networks
This moves the network out of project.create, associating a network to a project lazily in project_get_network. This allows for a bit greater control over networks. There are a couple outstanding issues:
1) Where do networks get disassociated? Right now I'm not disassociating at all. We're sharing ldap users across different deploys, whereas sql db is unique per deploy. Perhaps the solution is to have a flag like disassociate_on_project_destroy and make it optional?
2) How do we handle creation of networks for tests? It is really slow to create a pool of networks and fixed_ips for each test case. Right now I'm taking advantage of the fact that the db isn't cleaned between tests, and creating them if they don't exist in BaseTestCase.SetUp() and disassociating in TearDown(). Ideally this should be replaced with fixtures of some sort.
Comments on these two issues are welcome.
Diffstat (limited to 'nova/context.py')
0 files changed, 0 insertions, 0 deletions