Good point. Certainly depends on the type of reseller we're dealing with. If it's a company, each instance will likely share the network. If it's a university (let's say), each student may be on their own network.
This may fall into the Distributed Scheduler camp ... don't allocate new instances in Zones running low on available networks? -S ________________________________________ From: Vishvananda Ishaya [vishvana...@gmail.com] Sent: Tuesday, April 05, 2011 4:31 PM To: Sandy Walsh Cc: Eric Day; openstack@lists.launchpad.net Subject: Re: [Openstack] Federated Identity Management (bursting and zones) Just thought of something else to consider. There is a further issue with setting the owner to resource_group: Networking. In Vlan mode, each owner gets its own vlan and communication between the instances is easy. If users start dividing up instances into a bunch of sub-groups we will run out of vlans very quickly. Network communication between the subgroups will probably be much more complicated as well. Perhaps some of this can be solved with the multinic / network refactor. If we can specify at launch which network we want the instance created in instead of keying it off of the owner's network, we might have everything we need. Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
