<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" class="" style="word-wrap:break-word">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">There's two different pieces of software that exist that may handle the use case, depending on what you want to do.<br>
<br>
the neutron l2gw project:<br>
http://docs.openstack.org/developer/networking-l2gw/usage.html<br>
<br>
I believe it creates a gateway node to bridge between the tenant networks and phyiscal ones, so that you can attach non neutron devices to neutron networks.<br>
<br>
The second, is a script I wrote and have been using in production for a while that binds a neutron openvswitch agent supporting host directly to a tenant network. This eliminates any performance penalties with going through a gateway system. But can't really
be used with appliances.<br>
<br>
Its not the prettiest of scripts yet, but would be a good starting point if your interested. Code is here:<br>
https://review.openstack.org/#/c/158003/<br>
<br>
Thanks,<br>
Kevin<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF535213"><font color="#000000" face="Tahoma" size="2"><b>From:</b> Manuel Fernandes [manuelfernandes55@gmail.com]<br>
<b>Sent:</b> Friday, March 25, 2016 5:52 AM<br>
<b>To:</b> openstack-dev@lists.openstack.org<br>
<b>Subject:</b> [openstack-dev] [neutron] NaaS using Openstack Neutron<br>
</font><br>
</div>
<div></div>
<div>
<div class="">Hello to all,</div>
<div class=""><br class="">
</div>
<div class="">My name is Manuel, I'm a MsC student in Computing and Telematics engineering at the University of Aveiro in Portugal and I'm currently working on my MsC thesis, which the topic is "Network as a Service (NaaS) using Openstack - Neutron". My main
goal is to get a way to extend the virtual networks created in Openstack to the network outside of the datacenter (for example a campus network) to get external devices on the same L2 domain as the VMs on the virtual network, now this scenario is possible
using the extension "Provider Network", but the external network operator needs to configure all the devices manually one by one, so we have the goal to do this automatically. This scenario is thought to be accomplished by creating external ports, this ports
has to be created in an automatically way, to get that goal it must be created a set of overlay networks by configuring the devices in the way to the device that will be the host for the external port. This needs to be done, thinking that the devices on the
external network are mostly heterogeneous and they must be configured automatically in a transparent way regardless of their characteristics and functional patterns.</div>
<div class="">My main concern is to decide which is the better way to do this. Can I go with the ML2 plugin and create a type driver and a mechanism driver to implement this virtual network extension as a new virtual network segment, or it would be better to
implement it using the framework "Advanced Service Plugin" as a new type of service? In both possible solutions, we pretend to have an external agent to do the necessary configurations on the network devices.</div>
<div class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class=""><br class="">
</div>
<div class="">Manuel Fernandes.</div>
<div class="">
<div class="" style="color:rgb(0,0,0); font-family:Helvetica; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word-spacing:0px; word-wrap:break-word">
<div class=""><br class="">
</div>
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<div class=""><br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<br class="">
</div>
</div>
</div>
</body>
</html>