On Apr 14, 2011, at 12:49 PM, Rick Clark wrote: > As many of you know there are a few Network as a Service proposals > floating around. All of the authors are working to combine them into > something we all want to move forward with. Hopefully by the summit we > will have one blueprint to rule them all. > > I would like to make a couple suggestions publicly that I have been > mentioning to everyone I talk to about NaaS. > > 1. NaaS should be optional > nova's existing hypervisor only flat and vlan network functionality > should stay in nova. You should not need to bring up a separate service > to bring up a simple test instance. This will also help us not break > nova as we are making rapid code changes.
We have arrived at a similar conclusion. We are thinking that NaaS could initially be implemented as a 3rd network manager option (a peer to the current flat or vlan) that receives messages through the current queue. > > 2. all communication should be via API. > NaaS should not write or read directly from Novadb. I have seen many > diagrams that have the NaaS writing data directly to novadb. Agree here as well. As we've been working on some prototyping efforts, we are discovering a number of places where networking communicates to the compute through the DB. Cleaning this up so that Network is properly isolated is probably one of the first things that would need to be done. In talking with Vish, that probably warrants a separate blueprint that will come out of the NaaS discussion. The one exception I can see around the API notion is that given our approach to #1 - initial nova communication might be through the existing network manager queue vs. converting all calls to the external REST API. That would merely be a way to introduce NaaS with minimal disruption. In either case, there should be no data passed through a shared DB. > > 3. NaaS should be generic enough that other things can consume it. I > would love to see Opennebula and Eucalyptus be able to use the Openstack > NaaS. I know of a few sites that have both Eucalyptus and Openstack > deployed. It would be nice if they could share a NaaS. i would also > like to support application calling NaaS to create their own shared > network containers. Agreed. Our early focus may be around getting NaaS to work well in an Openstack environment. But, we should be building this project in a way that it can be a more generally accessible service that can facilitate hybrid interactions between implementations as well. > > Cheers, > > Rick > > Principal Engineer, Cisco Systems > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp 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 [email protected], and delete the original message. Your cooperation is appreciated. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
