openstack team mailing list archive

[Erik Carlin <erik.carlin@xxxxxxxxxxxxx>]

Rick -

Agree with everything below. IMO, #3 should apply in general to all OS services (core network, block storage, load balancing, etc.)  We want things to work as a suite of services but each service should be independent and deployable by itself.  There will obviously by interface standards that will need to be adhered to, but totally doable.  The more we can make each OS service the canonical API and automation engine for each IaaS piece, the better.  And part of that is making it usable with non-OS services.

Erik

Sent from my iPhone

On Apr 14, 2011, at 1:08 PM, "Rick Clark" <rick@xxxxxxxxxxxxx> 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.
> 
> 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.
> 
> 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.
> 
> Cheers,
> 
> Rick
> 
> Principal Engineer, Cisco Systems
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> 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 abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.