Ask Your Question
0

OpenStack Liberty dedicated network node (neutron)

asked 2016-03-17 03:09:47 -0600

JeroenH gravatar image

Hi,

I am assigned a project to create a proof of concept with OpenStack. All the provided lecture in the OpenStack docs section is very educational. Just now, iam setting up this proof of concept with the guidance of the OpenStack liberty Ubuntu 14.04 guide. At some points of the proof of concept it has to resemble a (sort of) production cloud. One point is the network node. I just want a dedicated network node (neutron) in my proof of concept. The Liberty Ubuntu 14.04 guide says:

This example architecture differs from a minimal production architecture as follows: Networking agents reside on the controller node instead of one or more dedicated network nodes. Overlay (tunnel) traffic for private networks traverses the management network instead of a dedicated network.

But what do i have to do to create a dedicated network node when following this guide? I don't want the tunnel traffic to travel over the management network. I just want the connection between the VM's (compute node) and the network node. Also, the hardware that is provisioned for this project isn't that high in performance. This is the leading reason that I don't want (almost) every service to run on the controller node, just seperate some services from the controller.

Can somebody help me with this?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2016-03-18 07:24:29 -0600

pjb gravatar image

updated 2016-03-18 07:25:14 -0600

Hi, try the following configuration changes to have a dedicated Network node:

1) Install and run the following services on network node rather than on controller: a.openstack-neutron b.openstack-neutron-ml2 c.openstack-neutron-linuxbridge d.openstack-neutron-openvswitch e.python-neutronclient f.ebtables g.ipset

2) Let the netron-server run on controller. Make necessary changes to the above services' configuration file on the network node.

3) Now to have a different tunnel-network set the following configuration options on Network and Compute nodes: file: /etc/neutron/plugins/ml2/ml2_conf.ini

[ovs]
local_ip = $THISHOST_TUNNEL_IP
enable_tunneling = True
[agent]
tunnel_types = gre

Please feel free to ask any question. I have written installation scripts for Liberty on CentOS 7.1. In case you plan on using them let me know.

edit flag offensive delete link more

Comments

Allright pjb, I will try this solution. Thanks for your answer!

JeroenH gravatar imageJeroenH ( 2016-03-18 10:18:57 -0600 )edit

thanks PJB. can you share the script pls

rajkumar2507 gravatar imagerajkumar2507 ( 2017-05-04 02:03:27 -0600 )edit
0

answered 2016-03-18 08:35:08 -0600

dbaxps gravatar image

You wrote "Just now, iam setting up this proof of concept with the guidance of the OpenStack liberty Ubuntu 14.04 guide" There is another Openstack flavor CentOS 7 and RDO Liberty having puppet technology employed for about 3-4 years
See RDO Liberty Set up for three Nodes (Controller+Network+Compute) ML2&OVS&VXLAN on CentOS 7.2
http://dbaxps.blogspot.com/2015/10/rd...
As of now view count shows 1714 since 10/22/2016
Setup described above on OS already installed nodes takes about 20-30 min. It works on bare metal exactly same way as on VMs @KVM Hypervisor on Fedora 22/23

image description

edit flag offensive delete link more

Comments

Thanks for your answer dbaxps! That would be a nice alternative. In my project there exists a requirement that I have to use Ubuntu 14.04 LTS. So unfortunately I can't use CentOS.

JeroenH gravatar imageJeroenH ( 2016-03-18 10:18:08 -0600 )edit

Ok. So much attractive Triple0 approach does have Controller/Network Node to be hosted on one box. Because 3 Node Controllers cluster ( overcloud ) is forced to use MariadbGalera MultiMaster Replication running. Setting up Network Node as separate box (VM) is supposed to be left in past.

dbaxps gravatar imagedbaxps ( 2016-03-18 10:55:46 -0600 )edit

Painful Ubuntu 14.04 exercises look for me as a bad syndrome even as POC. Because Concept itself won't be required by Enterprise in about year or so.

dbaxps gravatar imagedbaxps ( 2016-03-18 11:02:35 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-03-17 03:09:47 -0600

Seen: 377 times

Last updated: Mar 18 '16