segregating neutron [closed]

asked 2017-12-11 13:37:59 -0600

Bindas gravatar image

hi

currently we are trying to deploy a openstack architecture where there is two different networking architecture. one is with native neutron with OVS and other is cplane networking where only neutron api is running but all the other neutron components are turned off i.e neutron-ovs-agent neutron-metadata-agent etc. we are planning to install openstack mikata version of openstack using juju on ubuntu 14.04LTS.

what i am looking for is recommendations to achieve this architecture , should i segregate openstack controllers using regions or its ok with using cells, or availability zones. also it would be very helpful if you can provide any resources where i can read up on this type of deployment a bit more. I found a similar question regarding this type of deployment but unfortunately there was no answer provided. any guidance or help would be appreciated :)

thanks

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Bindas
close date 2017-12-17 22:47:14.344388

Comments

What do you want to achieve? On one server, you want to run the Neutron API only. On the "native Neutron" server, you want to run what - all the other Neutron components or a second Neutron API with the other components?

In the former case, there is nothing special to do. Just deploy everything.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-12 01:58:40 -0600 )edit

Configure the "native Neutron" server with the message queue and DB details, and off you go.

In the latter case, I don't understand what a Neutron API without any other component is supposed to do.

In any case, a cloud can only have one Neutron API. If you need more, use regions.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-12 02:00:43 -0600 )edit

Or do you want to have High Availability? In this case, deploy all Neutron components two or three times behind a load balancer. docs.openstack.org has an HA guide that should give you many hints.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-12 02:03:18 -0600 )edit

Hi Bernd , thanks for the reply but actually we achieve the configuration by segregating using regions. the reason behind this architecture was so we can have two separate SDN controller , openvswitch and cplane

Bindas gravatar imageBindas ( 2017-12-17 22:46:26 -0600 )edit

Although you have a solution, let me comment that the Neutron ML2 plugin allows deploying several mechanism drivers in the same cloud. Now, I don't know if there is a cplane mech driver, and whether that would address your requirement.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-18 17:55:54 -0600 )edit