[Rdo-list] Deploying RDO using Foreman
Arash Kaffamanesh
ak at cloudssky.com
Wed Mar 19 17:21:51 UTC 2014
Hi again,
"ovs-vsctl show " works now :-)
I started openvswitch over the horizon console, created the br-ex interface
and plugged it into eth0.
What I don't understand is, why I can't login through the br-ex interface
into the controller node from outside, but I can login from the compute
node through the eth1 network (management network). If I reboot the
controller and watch it during reboot, I can see the famous issue with the
metadata request error (no route to host).
I guess I've to adjust the routing table (?):
[root at controller ~]# ovs-vsctl show
8e8a6f2f-1b41-4bfc-a95e-dee5039be55b
Bridge br-ex
Port "eth0"
Interface "eth0"
Port br-ex
Interface br-ex
type: internal
ovs_version: "1.11.0"
[root at controller ~]# cat /etc/sysconfig/network-scripts/ifcfg-br-ex
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.0.0.6
NETMASK=255.255.255.0
GATEWAY=10.0.0.1
#DOMAIN=mydomain.com
DNS1=8.8.8.8
#DNS2=192.168.10.111
ONBOOT=yes
DEFROUTE=yes
[root at controller ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes
#PROMISC=yes
[root at controller ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
br-ex
10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
10.0.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1004 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0
br-ex
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0
br-ex
On Wed, Mar 19, 2014 at 5:20 PM, Arash Kaffamanesh <ak at cloudssky.com> wrote:
> Hi again,
>
> openvswitch was not running:
>
> [root at controller ~]# /etc/init.d/openvswitch status
> ovsdb-server is not running
> ovs-vswitchd is not running
>
> but if I start it, then I can't access the VM anymore:
>
> [root at controller ~]# /etc/init.d/openvswitch start
> Starting ovsdb-server [ OK ]
> Configuring Open vSwitch system IDs [ OK ]
> Inserting openvswitch module [ OK ]
> Starting ovs-vswitchd [ OK ]
> Enabling remote OVSDB managers [ OK ]
> [root at controller ~]#
>
> Any ideas?
>
> Thanks!
>
> On Wed, Mar 19, 2014 at 3:24 PM, Arash Kaffamanesh <ak at cloudssky.com>wrote:
>
>> Hello together,
>>
>> I'm proceeding with this installation and I'm facing a strange problem
>> with openvswitch on the controller node which has been reported here too:
>>
>>
>> https://ask.openstack.org/en/question/10228/neutron-ovs-error-on-controller/
>>
>> If I do a ovs-vsctl show, I'm getting:
>>
>> [root at controller ~]# ovs-vsctl show
>> 2014-03-16T04:40:26Z|00001|reconnect|WARN|unix:/var/run/openvswitch/db.sock:
>> connection attempt failed (No such file or directory)
>> ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed
>> (No such file or directory)
>>
>> And in /var/log/neutron/openvswitch-agent.log I can see:
>>
>> 2014-03-15 23:22:37.296 3084 INFO neutron.common.config [-] Logging
>> enabled!
>> 2014-03-15 23:22:37.296 3084 ERROR
>> neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Tunneling cannot be
>> enabled without a valid local_ip. Agent terminated!
>>
>> It seems that on the controller the ovs neutron agent doesn't like my
>> "local_ip".
>> But on the compute and network node ovs-vsctl show works:
>>
>> [root at neutron ~]# ovs-vsctl show
>> 6093f101-4bac-4e30-afc6-545f8f3dc6a1
>> Bridge br-int
>> Port br-int
>> Interface br-int
>> type: internal
>> Bridge br-tun
>> Port br-tun
>> Interface br-tun
>> type: internal
>> ovs_version: "1.11.0"
>>
>>
>> And here is my ifconfig on the controller node:
>>
>> [root at controller ~]# ifconfig
>> eth0 Link encap:Ethernet HWaddr FA:16:3E:80:BC:FB
>> inet addr:10.0.0.6 Bcast:10.0.0.255 Mask:255.255.255.0
>> inet6 addr: fe80::f816:3eff:fe80:bcfb/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:6523 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:4982 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:1317111 (1.2 MiB) TX bytes:849191 (829.2 KiB)
>>
>> eth1 Link encap:Ethernet HWaddr FA:16:3E:0B:AF:9A
>> inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0
>> inet6 addr: fe80::f816:3eff:fe0b:af9a/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:336 (336.0 b) TX bytes:546 (546.0 b)
>>
>> eth2 Link encap:Ethernet HWaddr FA:16:3E:45:8E:FD
>> inet addr:10.0.2.5 Bcast:10.0.2.255 Mask:255.255.255.0
>> inet6 addr: fe80::f816:3eff:fe45:8efd/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:336 (336.0 b) TX bytes:566 (566.0 b)
>>
>>
>> Any ideas?
>>
>> Thanks!
>> Arash
>>
>> Mit freundlichen Grüßen,
>> Arash Kaffamanesh
>>
>> Like <https://www.facebook.com/cloudssky> | Follow<https://twitter.com/CLOUDSSKYONE>
>> | Build your CloudSite with OpenCms OCCX on ProfitBricks<http://cloudssky.com/en/cloud_services/cloudsite.html>
>>
>> *________________**____________*
>>
>> *Arash Kaffamanesh*
>>
>> * Clouds Sky GmbH*
>>
>> *Im Mediapark 4C*
>>
>>
>> *50760 Köln*
>> T.: +49 221 379 90 680
>> M.: +49 177 880 77 34
>> www.cloudssky.com
>> * _________________**___________*
>>
>>
>>
>> On Tue, Mar 11, 2014 at 2:07 PM, Hugh O. Brock <hbrock at redhat.com> wrote:
>>
>>> On Tue, Mar 11, 2014 at 09:53:35AM +0530, Kashyap Chamarthy wrote:
>>> > On Mon, Mar 10, 2014 at 08:46:45PM +0100, Arash Kaffamanesh wrote:
>>> > > Hi,
>>> > >
>>> > > I posted a question regarding "Deploying RDO using Foreman" to
>>> > > ask.openstack.org and thanks to Keshyap and Rich which engaged me to
>>> > > proceed further, I updated the thread here:
>>> > >
>>> > >
>>> https://ask.openstack.org/en/question/12104/deploying-rdo-using-foreman/
>>> > >
>>> > > The post might be too long, here some more information about the
>>> reason
>>> > > behind my question and some more questions:
>>> > >
>>> > > I'm trying to learn Foreman for installing OpenStack and use it to
>>> deploy
>>> > > RDO on top of RDO to provide some kind of OpenStack training /
>>> webinars and
>>> > > later to run the whole thing on 6-8 bare metal machines and use it to
>>> > > deploy OpenShift and write a tutorial about the whole thing and post
>>> it on
>>> > > the RDO site, LinkedIn, etc.
>>> > >
>>> > > About our BASE RDO environment:
>>> > > Our RDO based 3 node environment is thanks to the latest update very
>>> stable
>>> > > and very fast now and I've to thank all of you smart guys for doing
>>> such a
>>> > > great work!
>>> > >
>>> > > Our environment uses VLAN and the Foreman RDO installation shall use
>>> GRE
>>> > > and Qemu (or LXC / Docker) to let us play with the whole thing and
>>> write a
>>> > > tutorial about the whole thing.
>>> > >
>>> > > So my questions:
>>> > > Does the Foreman installation on top of a virtualized environment
>>> work at
>>> > > all? (I guess yes)
>>> >
>>> > Yes, technically, it should work. Refer to my previous email on
>>> > this list[1] for some URLs on Foreman.
>>> >
>>> > > Could a VLAN based BASE-Install be a problem to succeed with this
>>> scenario
>>> > > (to have GRE on top of VLAN)? (I guess no)
>>> >
>>> > Only way to know with certainity - to try it.
>>> >
>>> > > Has someone tried such a scenario before? (I guess yes)
>>> > > Could I use LXC / Docker instead Qemu?
>>> >
>>> > There's active work on upstream for Docker support, so you ought to
>>> > experiment and carefully note down observations, filing bugs along the
>>> > way.
>>> >
>>> > And, it depends on _what_ you want to do with the LXC/Docker setup. If
>>> > it's just to try it out, there's decent resources on the inter-webs.
>>> >
>>>
>>> Hi there. It's also worth mentioning that we are actively working on
>>> improving the OpenStack installation process with Foreman, including
>>> adding a better UI and some workflow components to stage
>>> deployments. Watch this list for details as they emerge.
>>>
>>> --Hugh
>>>
>>>
>>> --
>>> == Hugh Brock, hbrock at redhat.com ==
>>> == Senior Engineering Manager, Cloud Engineering ==
>>> == Tuskar: Elastic Scaling for OpenStack ==
>>> == http://github.com/tuskar ==
>>>
>>> "I know that you believe you understand what you think I said, but I’m
>>> not sure you realize that what you heard is not what I meant."
>>> --Robert McCloskey
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20140319/2ae0bd99/attachment.html>
More information about the dev
mailing list