[Openstack-operators] Implement OS using existing network setup
Diego Parrilla Santamaría
diego.parrilla.santamaria at gmail.com
Tue Jul 30 15:44:04 UTC 2013
If you want to replicate your existing network configuration with 'Neutron'
(sorry, I'm not done yet to this name), you have to use the Neutron API to
do this. Don't try to do it directly using ovs commands, 'Neutron' won't
recognize it.
Keep in mind that the networks created with Neutron API work great inside
the Nova sandbox. If you want to connect to other existing networks, may be
you have add them as external networks. My experience trying to add an
existing subnetwork and the corresponding VLAN as a new (not-external)
network was not as smooth as expected. Still you can give a try.
Cheers,
Diego
--
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parrilla at stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*
*
On Tue, Jul 30, 2013 at 4:25 PM, Ronald J. Yacketta <yacketrj at potsdam.edu>wrote:
> Hello all!
>
> We have a rather complex network setup where our HP BL460c G8's have
> multiple VLAN's assigned and bridges already created per VLAN. Would like
> to setup a new HP BL460c G8 using OpenStack and mirror the network setup,
> looks like Quantum+OVS would be the logical choice but not sure how one
> would use OVS with existing bridges. All of the examples I have seen build
> up the bridge and assign the port which in the end executes the required OS
> commands to build out the network. How would one go about setting up
> OpenStack networking to utilizing existing network configuration?
>
> Regards,
>
> Ron
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130730/fee997ea/attachment.html>
More information about the OpenStack-operators
mailing list