I would also like to chime in on this. Our customers routinely make use of bridging vlans out into dedicated infrastructure, and a way to automate this with SDN deployments would be welcome. I might even be able to get some dev resources to assist with the development.
Thanks, -Nate On Thu, Mar 13, 2014 at 9:19 AM, Ian Rae <i...@cloudops.com> wrote: > Hugo, > > This is a common request from our SP customers but most have balked at the > cost of developing a custom solution. It is an important feature for hybrid > architectures, let us know how we can help. Certainly we will give feedback > on the functional spec. > > Ian > > Ian Rae > CEO, CloudOps Inc. > 514-944-4008 > @ianrae | www.linkedin.com/in/ianrae > www.cloudops.com > > > On Tue, Mar 11, 2014 at 10:12 AM, Hugo Trippaers <h...@trippaers.nl> > wrote: > > > Hey all, > > > > I've been working on adding Bridge support to CloudStack. The use case is > > that with the introduction of SDN there is a need for us to link logical > > networks to physical hosts or physical networks. A typical use case would > > be to connect legacy infrastructure to cloud infrastructure, or to > support > > cloud bursting from an existing infrastructure to a network in the cloud. > > > > Routing can sometimes be used to accomplish the same effect (for example > > the private gateway option in a VPC), but in some cases a L2 connection > is > > preferred. > > > > The functionality would a central bridge manager in CloudStack. The > bridge > > manager would have a number of admin only commands that link a number of > > networks to a specified domain or account. The user commands would allow > an > > account to link a logical network to an external physical network. This > > separation is done to ensure users are never able to configure a bridge > to > > a network they shouldn't have access to. Admins will have to make an > > external network available as a bridge destination and a user can select > it. > > > > The network implementation will consists of a BridgeProvider element > > extension which elements can implement. It's up to the elements to > > configure the particulars of their bridge implementation. > > > > Initial implementation will cover the admin commands, user commands and > an > > implementation in the VMware NSX plugin. UI is out of scope for the > first > > implementation. > > > > Any feedback is welcome :D > > > > Cheers, > > > > Hugo > -- *Nate Gordon*Director of Technology | Appcore - the business of cloud computing® Office +1.800.735.7104 | Direct +1.515.612.7787 nate.gor...@appcore.com | www.appcore.com ---------------------------------------------------------------------- The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
