Hi George,

in the guide you are using nova-network service is deployed on the compute node, so you need br100 only on it (and every compute node)
so forget what i wrote about controller and compute
as a guide to setup br100 try this link (http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/compute-configuring-guest-network.html) but be careful with the interface you use, in your case (as described in the guide you follow) eth1 is the right one

for the deployment i would suggest you try using a deployment tool like RDO, following the guide found under the link below
  http://openstack.redhat.com/Quickstart
then there are configuration option on setting all-in-one or multi-node deployments
as well as using neutron or nova-network or adding compute nodes

for the networking part i suggest try using neutron, but this might not be an easy solution as you will need to study and understand some things about it.

in any case, keep updating and i will help
Thanassis

Thanassis Parathyras
StackMasters - The European OpenStack Integration Company
www.stackmasters.eu

On 9/1/2014 12:11 μμ, Georgios Dimitrakakis wrote:
Hello again!

No the br100 was not created automatically unfortunately! There is also this bug report: https://bugs.launchpad.net/openstack-manuals/+bug/1241331

Since it wasn't created automatically I am asking if it has to be on both nodes (controller + compute) in order for the network to work correctly? Furthermore, I would like to know how should it be bridged in order to achieve floating (public) IPs?

If it's easier for you or there is a guide that you can point me to I would be happy to try with neutron instead of nova-network.

Best,

G.

On Thu, 09 Jan 2014 11:54:18 +0200, Thanassis Parathyras wrote:
Hi George,

Personally i have not dealt with this setup, but i can follow and
assist you further.
According to the related bug report
(https://bugs.launchpad.net/ubuntu/+bug/1243588)
"br100 is automatically set up by nova-network, you do not need to
manually create it"
is that the case on your setup?

Best,
Thanassis

Thanassis Parathyras
StackMasters - The European OpenStack Integration Company
www.stackmasters.eu

On 9/1/2014 3:15 πμ, Georgios Dimitrakakis wrote:
Dear Thanassi,

thank you very much for your interest! First of all let me inform you that you are right and I am going with the first (a) approach (nova-network). The guide I was following and the place on which the specific problem arises is this one: http://docs.openstack.org/havana/install-guide/install/yum/content/nova-network.html

As you can see by yourself many people on the comment session below are trying to understand how to move on with the br100 interface.

In my case the interface wasn't created automatically (although in a previous bug that I 've found the say that this was fixed but apparently it hasn't been in my case). So I 've tried to move on and created the br100 on the compute node without success. If I understand correctly, according to your suggestion the br100 has to exist on the controller node as well. Am I right? Should I create the br100 on both nodes?? Do you have any further suggestions on how to assign floating (public) IPs to the VMs? Currently I am having two nodes (controller + compute) with two NIC interfaces each! One of them is used in order to connect directly each to node to the other, while the other is used to connect to the public LAN with a static IP. Any help and configuration schema much appreciated!

All the best,

G.

On Tue, 07 Jan 2014 11:06:42 +0200, Thanassis Parathyras wrote:
Hi George,

It would be a pleasure to help you on this, do you still have
problems with the deployment?
In OpenStack there are two types of networking that can be used
a)nova-network and b)neutron.
Given your specified question i assume you are going with option a),
then in that case the br100 bridge should be present (manually created
- if you follow a manual deployment) on the controller node.
May be you can provide the link of the guide you are following so
that we check if there is a need for correction on this.
One more thing, since you are using Centos you can consider using
RedHat RDO ( http://openstack.redhat.com ) for the deployment.

Feel free to contact me with regard to any issues you have.
Best regards,
Thanassis

Thanassis Parathyras
Virtual Trip Ltd.

e [email protected]
w www.vtrip.net
t +30 2106756112
f +30 2106756527
skype-id: aparathyras

--------------------------------
This transmission (including any attachments) from the Virtual Trip
Group of companies is exclusively addressed to the above named
recipients and is bound to contain privileged and confidential
information. Disclosure, distribution, copying or any other use of
this message is strictly prohibited and may breach intellectual
property provisions. In case of fault transmission please delete
e-mail message and notify us by reply immediately.

On 27/12/2013 8:12 μμ, Georgios Dimitrakakis wrote:
Hi people!

I am following the exact steps of the "Openstack Installation Guide" for Havana on a CentOS 6.5

The problem is that when I try create the network on the controller node using this :

nova --debug network-create vmnet --fixed-range-v4=x.x.x.x/32 --bridge-interface=br100 --multi-host=T

I get an error that the br100 interface cannot be found.

So, my question is the following: should this interface appear on the controller node , on the compute node or on both nodes?

What do I have to do to set it up properly since it doesn't appear on any of them??

I have found this bug for CentOS 6.4 and I am not sure that has been corrected for 6.5.


Could someone help me a bit with this??


Best,

G.

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack





_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to