<div dir="ltr">Hi Marius,<div><br></div><div>I successfully managed to deploy overcloud with <a href="http://rdoproject.org/repos/openstack-liberty/rdo-release-liberty.rpm%60" rel="noreferrer" target="_blank" style="font-size:12.8px">http://rdoproject.org/repos/openstack-liberty/rdo-release-liberty.rpm</a> instead of delorean repos. I also built the images based on liberty. Thanks :)</div><div><br></div><div>A side note, is there a way to disable cinder when deploying? Because I get <span style="background-color:rgb(255,255,255)"><strong style="font-size:13px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:18.5714px"><font color="#000000">Error: </font></strong><span style="font-size:13px;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:18.5714px"><b><font color="#000000">Unable to retrieve volume limit information.</font></b><font color="#000000"> horizon errors. </font></span></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 21, 2015 at 6:41 PM, Marius Cornea <span dir="ltr"><<a href="mailto:marius@remote-lab.net" target="_blank">marius@remote-lab.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It's definitely a bug, the deployment shouldn't pass without<br>
completing keystone init. What's the content of your<br>
network-environment.yaml?<br>
<br>
I'm not sure if this relates but it's worth trying an installation<br>
with the GA bits, the docs are being updated to describe the steps.<br>
Some useful notes can be found here:<br>
<a href="https://etherpad.openstack.org/p/RDO-Manager_liberty" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/RDO-Manager_liberty</a><br>
<br>
trown ╡ mcornea: the important bit is to use `yum install -y<br>
<a href="http://rdoproject.org/repos/openstack-liberty/rdo-release-liberty.rpm`" rel="noreferrer" target="_blank">http://rdoproject.org/repos/openstack-liberty/rdo-release-liberty.rpm`</a><br>
for undercloud repos, and `export RDO_RELEASE='liberty'` for image<br>
build<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Oct 21, 2015 at 6:54 PM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>> wrote:<br>
> Yes, I've done that already, however it never runs keystone init. Is it<br>
> something wrong in my deployment command "openstack overcloud deploy" or do<br>
> you think it's a bug/conf issue?<br>
><br>
> Thanks<br>
><br>
> On Wed, Oct 21, 2015 at 5:50 PM, Marius Cornea <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>><br>
> wrote:<br>
>><br>
>> To delete the overcloud you need to run heat stack-delete overcloud<br>
>> and wait until it finishes(check heat stack-list)<br>
>><br>
>> On Wed, Oct 21, 2015 at 6:29 PM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>> wrote:<br>
>> > You're right, I didn't get that output, keystone init didn't run:<br>
>> ><br>
>> > $ openstack overcloud deploy --control-scale 3 --compute-scale 1<br>
>> > --libvirt-type kvm --ntp-server <a href="http://pool.ntp.org" rel="noreferrer" target="_blank">pool.ntp.org</a> --templates ~/the-cloud/ -e<br>
>> > ~/the-cloud/environments/puppet-pacemaker.yaml -e<br>
>> > ~/the-cloud/environments/network-isolation.yaml -e<br>
>> > ~/the-cloud/environments/net-single-nic-with-vlans.yaml -e<br>
>> > ~/the-cloud/environments/network-environment.yaml --control-flavor<br>
>> > controller --compute-flavor compute<br>
>> ><br>
>> > Deploying templates in the directory /home/stack/the-cloud<br>
>> > Overcloud Endpoint: <a href="http://192.168.174.35:5000/v2.0/" rel="noreferrer" target="_blank">http://192.168.174.35:5000/v2.0/</a><br>
>> > Overcloud Deployed<br>
>> ><br>
>> ><br>
>> > In fact I have some mysql errors in my controllers, see below. Is there<br>
>> > a<br>
>> > way to redeploy? Because I've run "openstack overcloud deploy" and<br>
>> > nothing<br>
>> > happens.<br>
>> ><br>
>> > Oct 21 14:21:51 overcloud-controller-0 os-collect-config[11715]:<br>
>> > [2015-10-21<br>
>> > 14:21:50,903] (heat-config) [INFO] Error: Could not prefetch mysql_user<br>
>> > provider 'mysql': Execution of '/usr/bin/mysql -NBe SELECT CONCAT(User,<br>
>> > '@',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't<br>
>> > connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'<br>
>> > (2)<br>
>> > Oct 21 14:21:51 overcloud-controller-0 os-collect-config[11715]: Error:<br>
>> > Could not prefetch mysql_database provider 'mysql': Execution of<br>
>> > '/usr/bin/mysql -NBe show databases' returned 1: ERROR 2002 (HY000):<br>
>> > Can't<br>
>> > connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'<br>
>> > (2)<br>
>> ><br>
>> > Thanks<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > On Wed, Oct 21, 2015 at 4:56 PM, Marius Cornea <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>><br>
>> > wrote:<br>
>> >><br>
>> >> I believe the keystone init failed. It is done in a postconfig step<br>
>> >> via ssh on the public VIP(see lines 3-13 in<br>
>> >> <a href="https://gist.github.com/remoteur/920109a31083942ba5e1" rel="noreferrer" target="_blank">https://gist.github.com/remoteur/920109a31083942ba5e1</a> ). Did you get<br>
>> >> that kind of output for the deploy command?<br>
>> >><br>
>> >> Try also journalctl -l -u os-collect-config | grep -i error on the<br>
>> >> controller nodes, it should indicate if something went wrong during<br>
>> >> deployment.<br>
>> >><br>
>> >> On Wed, Oct 21, 2015 at 5:05 PM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>> wrote:<br>
>> >> > Hi Marius,<br>
>> >> ><br>
>> >> > your tip worked fine thanks, bridges seems to be correctly created,<br>
>> >> > however<br>
>> >> > I still cannot login, seems some keystone problem:<br>
>> >> ><br>
>> >> > #keystone --debug tenant-list<br>
>> >> ><br>
>> >> > DEBUG:keystoneclient.auth.identity.v2:Making authentication request<br>
>> >> > to<br>
>> >> > <a href="http://192.168.174.35:5000/v2.0/tokens" rel="noreferrer" target="_blank">http://192.168.174.35:5000/v2.0/tokens</a><br>
>> >> > INFO:requests.packages.urllib3.connectionpool:Starting new HTTP<br>
>> >> > connection<br>
>> >> > (1): 192.168.174.35<br>
>> >> > DEBUG:requests.packages.urllib3.connectionpool:"POST /v2.0/tokens<br>
>> >> > HTTP/1.1"<br>
>> >> > 401 114<br>
>> >> > DEBUG:keystoneclient.session:Request returned failure status: 401<br>
>> >> > DEBUG:keystoneclient.v2_0.client:Authorization Failed.<br>
>> >> > The request you have made requires authentication. (HTTP 401)<br>
>> >> > (Request-ID:<br>
>> >> > req-accee3b3-b552-4c6b-ac39-d0791b5c1390)<br>
>> >> ><br>
>> >> > Did you had this issue when deployed on virtual?<br>
>> >> ><br>
>> >> > Regards<br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >> > On Wed, Oct 21, 2015 at 12:32 PM, Marius Cornea<br>
>> >> > <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>><br>
>> >> > wrote:<br>
>> >> >><br>
>> >> >> Here's an adjusted controller.yaml which disables DHCP on the first<br>
>> >> >> nic: enp1s0f0 so it doesn't get an IP address<br>
>> >> >> <a href="http://paste.openstack.org/show/476981/" rel="noreferrer" target="_blank">http://paste.openstack.org/show/476981/</a><br>
>> >> >><br>
>> >> >> Please note that this assumes that your overcloud nodes are PXE<br>
>> >> >> booting on the 2nd NIC(basically disabling the 1st nic)<br>
>> >> >><br>
>> >> >> Given your setup(I'm doing some assumptions here so I might be<br>
>> >> >> wrong)<br>
>> >> >> I would use the 1st nic for PXE booting and provisioning network and<br>
>> >> >> 2nd nic for running the isolated networks with this kind of<br>
>> >> >> template:<br>
>> >> >> <a href="http://paste.openstack.org/show/476986/" rel="noreferrer" target="_blank">http://paste.openstack.org/show/476986/</a><br>
>> >> >><br>
>> >> >> Let me know if it works for you.<br>
>> >> >><br>
>> >> >> Thanks,<br>
>> >> >> Marius<br>
>> >> >><br>
>> >> >> On Wed, Oct 21, 2015 at 1:16 PM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
>> >> >> wrote:<br>
>> >> >> > Hi,<br>
>> >> >> ><br>
>> >> >> > here you go.<br>
>> >> >> ><br>
>> >> >> > Regards,<br>
>> >> >> > Pedro Sousa<br>
>> >> >> ><br>
>> >> >> > On Wed, Oct 21, 2015 at 12:05 PM, Marius Cornea<br>
>> >> >> > <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>><br>
>> >> >> > wrote:<br>
>> >> >> >><br>
>> >> >> >> Hi Pedro,<br>
>> >> >> >><br>
>> >> >> >> One issue I can quickly see is that br-ex has assigned the same<br>
>> >> >> >> IP<br>
>> >> >> >> address as enp1s0f0. Can you post the nic templates you used for<br>
>> >> >> >> deployment?<br>
>> >> >> >><br>
>> >> >> >> 2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq<br>
>> >> >> >> state<br>
>> >> >> >> UP qlen 1000<br>
>> >> >> >> link/ether 7c:a2:3e:fb:25:55 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> inet <a href="http://192.168.21.60/24" rel="noreferrer" target="_blank">192.168.21.60/24</a> brd 192.168.21.255 scope global dynamic<br>
>> >> >> >> enp1s0f0<br>
>> >> >> >> 9: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> noqueue<br>
>> >> >> >> state<br>
>> >> >> >> UNKNOWN<br>
>> >> >> >> link/ether 7c:a2:3e:fb:25:56 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> inet <a href="http://192.168.21.60/24" rel="noreferrer" target="_blank">192.168.21.60/24</a> brd 192.168.21.255 scope global br-ex<br>
>> >> >> >><br>
>> >> >> >> Thanks,<br>
>> >> >> >> Marius<br>
>> >> >> >><br>
>> >> >> >> On Wed, Oct 21, 2015 at 12:39 PM, Pedro Sousa <<a href="mailto:pgsousa@gmail.com">pgsousa@gmail.com</a>><br>
>> >> >> >> wrote:<br>
>> >> >> >> > Hi Marius,<br>
>> >> >> >> ><br>
>> >> >> >> > I've followed your howto and managed to get overcloud deployed<br>
>> >> >> >> > in<br>
>> >> >> >> > HA,<br>
>> >> >> >> > thanks. However I cannot login to it (via CLI or Horizon) :<br>
>> >> >> >> ><br>
>> >> >> >> > ERROR (Unauthorized): The request you have made requires<br>
>> >> >> >> > authentication.<br>
>> >> >> >> > (HTTP 401) (Request-ID:<br>
>> >> >> >> > req-96310dfa-3d64-4f05-966f-f4d92702e2b1)<br>
>> >> >> >> ><br>
>> >> >> >> > So I rebooted the controllers and now I cannot login through<br>
>> >> >> >> > Provisioning<br>
>> >> >> >> > network, seems some openvswitch bridge conf problem, heres my<br>
>> >> >> >> > conf:<br>
>> >> >> >> ><br>
>> >> >> >> > # ip a<br>
>> >> >> >> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>
>> >> >> >> > inet <a href="http://127.0.0.1/8" rel="noreferrer" target="_blank">127.0.0.1/8</a> scope host lo<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 ::1/128 scope host<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > mq<br>
>> >> >> >> > state<br>
>> >> >> >> > UP<br>
>> >> >> >> > qlen 1000<br>
>> >> >> >> > link/ether 7c:a2:3e:fb:25:55 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://192.168.21.60/24" rel="noreferrer" target="_blank">192.168.21.60/24</a> brd 192.168.21.255 scope global<br>
>> >> >> >> > dynamic<br>
>> >> >> >> > enp1s0f0<br>
>> >> >> >> > valid_lft 84562sec preferred_lft 84562sec<br>
>> >> >> >> > inet6 fe80::7ea2:3eff:fefb:2555/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 3: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > mq<br>
>> >> >> >> > master<br>
>> >> >> >> > ovs-system state UP qlen 1000<br>
>> >> >> >> > link/ether 7c:a2:3e:fb:25:56 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet6 fe80::7ea2:3eff:fefb:2556/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state<br>
>> >> >> >> > DOWN<br>
>> >> >> >> > link/ether c2:15:45:c8:b3:04 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > 5: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN<br>
>> >> >> >> > link/ether e6:df:8e:fb:f0:42 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > 6: vlan20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > noqueue<br>
>> >> >> >> > state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/ether e6:79:56:5d:07:f2 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://192.168.100.12/24" rel="noreferrer" target="_blank">192.168.100.12/24</a> brd 192.168.100.255 scope global<br>
>> >> >> >> > vlan20<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet <a href="http://192.168.100.10/32" rel="noreferrer" target="_blank">192.168.100.10/32</a> brd 192.168.100.255 scope global<br>
>> >> >> >> > vlan20<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 fe80::e479:56ff:fe5d:7f2/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 7: vlan40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > noqueue<br>
>> >> >> >> > state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/ether ea:43:69:c3:bf:a2 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://192.168.102.11/24" rel="noreferrer" target="_blank">192.168.102.11/24</a> brd 192.168.102.255 scope global<br>
>> >> >> >> > vlan40<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 fe80::e843:69ff:fec3:bfa2/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 8: vlan174: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > noqueue<br>
>> >> >> >> > state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/ether 16:bf:9e:e0:9c:e0 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://192.168.174.36/24" rel="noreferrer" target="_blank">192.168.174.36/24</a> brd 192.168.174.255 scope global<br>
>> >> >> >> > vlan174<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet <a href="http://192.168.174.35/32" rel="noreferrer" target="_blank">192.168.174.35/32</a> brd 192.168.174.255 scope global<br>
>> >> >> >> > vlan174<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 fe80::14bf:9eff:fee0:9ce0/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 9: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > noqueue<br>
>> >> >> >> > state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/ether 7c:a2:3e:fb:25:56 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://192.168.21.60/24" rel="noreferrer" target="_blank">192.168.21.60/24</a> brd 192.168.21.255 scope global br-ex<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 fe80::7ea2:3eff:fefb:2556/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 10: vlan50: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > noqueue<br>
>> >> >> >> > state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/ether da:15:7f:b9:72:4b brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://10.0.20.10/24" rel="noreferrer" target="_blank">10.0.20.10/24</a> brd 10.0.20.255 scope global vlan50<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 fe80::d815:7fff:feb9:724b/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 11: vlan30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc<br>
>> >> >> >> > noqueue<br>
>> >> >> >> > state<br>
>> >> >> >> > UNKNOWN<br>
>> >> >> >> > link/ether 7a:b3:4d:ad:f1:72 brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> > inet <a href="http://192.168.101.11/24" rel="noreferrer" target="_blank">192.168.101.11/24</a> brd 192.168.101.255 scope global<br>
>> >> >> >> > vlan30<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet <a href="http://192.168.101.10/32" rel="noreferrer" target="_blank">192.168.101.10/32</a> brd 192.168.101.255 scope global<br>
>> >> >> >> > vlan30<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > inet6 fe80::78b3:4dff:fead:f172/64 scope link<br>
>> >> >> >> > valid_lft forever preferred_lft forever<br>
>> >> >> >> > 12: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state<br>
>> >> >> >> > DOWN<br>
>> >> >> >> > link/ether b6:88:6b:d7:3a:4c brd ff:ff:ff:ff:ff:ff<br>
>> >> >> >> ><br>
>> >> >> >> ><br>
>> >> >> >> > # ovs-vsctl show<br>
>> >> >> >> > 3ee4adeb-4a5a-49a6-a16e-1e5f6e22f101<br>
>> >> >> >> > Bridge br-ex<br>
>> >> >> >> > Port br-ex<br>
>> >> >> >> > Interface br-ex<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Port "enp1s0f1"<br>
>> >> >> >> > Interface "enp1s0f1"<br>
>> >> >> >> > Port "vlan40"<br>
>> >> >> >> > tag: 40<br>
>> >> >> >> > Interface "vlan40"<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Port "vlan20"<br>
>> >> >> >> > tag: 20<br>
>> >> >> >> > Interface "vlan20"<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Port phy-br-ex<br>
>> >> >> >> > Interface phy-br-ex<br>
>> >> >> >> > type: patch<br>
>> >> >> >> > options: {peer=int-br-ex}<br>
>> >> >> >> > Port "vlan50"<br>
>> >> >> >> > tag: 50<br>
>> >> >> >> > Interface "vlan50"<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Port "vlan30"<br>
>> >> >> >> > tag: 30<br>
>> >> >> >> > Interface "vlan30"<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Port "vlan174"<br>
>> >> >> >> > tag: 174<br>
>> >> >> >> > Interface "vlan174"<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Bridge br-int<br>
>> >> >> >> > fail_mode: secure<br>
>> >> >> >> > Port br-int<br>
>> >> >> >> > Interface br-int<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > Port patch-tun<br>
>> >> >> >> > Interface patch-tun<br>
>> >> >> >> > type: patch<br>
>> >> >> >> > options: {peer=patch-int}<br>
>> >> >> >> > Port int-br-ex<br>
>> >> >> >> > Interface int-br-ex<br>
>> >> >> >> > type: patch<br>
>> >> >> >> > options: {peer=phy-br-ex}<br>
>> >> >> >> > Bridge br-tun<br>
>> >> >> >> > fail_mode: secure<br>
>> >> >> >> > Port "gre-0a00140b"<br>
>> >> >> >> > Interface "gre-0a00140b"<br>
>> >> >> >> > type: gre<br>
>> >> >> >> > options: {df_default="true", in_key=flow,<br>
>> >> >> >> > local_ip="10.0.20.10",<br>
>> >> >> >> > out_key=flow, remote_ip="10.0.20.11"}<br>
>> >> >> >> > Port patch-int<br>
>> >> >> >> > Interface patch-int<br>
>> >> >> >> > type: patch<br>
>> >> >> >> > options: {peer=patch-tun}<br>
>> >> >> >> > Port "gre-0a00140d"<br>
>> >> >> >> > Interface "gre-0a00140d"<br>
>> >> >> >> > type: gre<br>
>> >> >> >> > options: {df_default="true", in_key=flow,<br>
>> >> >> >> > local_ip="10.0.20.10",<br>
>> >> >> >> > out_key=flow, remote_ip="10.0.20.13"}<br>
>> >> >> >> > Port "gre-0a00140c"<br>
>> >> >> >> > Interface "gre-0a00140c"<br>
>> >> >> >> > type: gre<br>
>> >> >> >> > options: {df_default="true", in_key=flow,<br>
>> >> >> >> > local_ip="10.0.20.10",<br>
>> >> >> >> > out_key=flow, remote_ip="10.0.20.12"}<br>
>> >> >> >> > Port br-tun<br>
>> >> >> >> > Interface br-tun<br>
>> >> >> >> > type: internal<br>
>> >> >> >> > ovs_version: "2.4.0"<br>
>> >> >> >> ><br>
>> >> >> >> > Regards,<br>
>> >> >> >> > Pedro Sousa<br>
>> >> >> >> ><br>
>> >> >> >> ><br>
>> >> >> >> > On Sun, Oct 18, 2015 at 11:13 AM, Marius Cornea<br>
>> >> >> >> > <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>><br>
>> >> >> >> > wrote:<br>
>> >> >> >> >><br>
>> >> >> >> >> Hi everyone,<br>
>> >> >> >> >><br>
>> >> >> >> >> I wrote a blog post about how to deploy a HA with network<br>
>> >> >> >> >> isolation<br>
>> >> >> >> >> overcloud on top of the virtual environment. I tried to<br>
>> >> >> >> >> provide<br>
>> >> >> >> >> some<br>
>> >> >> >> >> insights into what instack-virt-setup creates and how to use<br>
>> >> >> >> >> the<br>
>> >> >> >> >> network isolation templates in the virtual environment. I hope<br>
>> >> >> >> >> you<br>
>> >> >> >> >> find it useful.<br>
>> >> >> >> >><br>
>> >> >> >> >> <a href="https://remote-lab.net/rdo-manager-ha-openstack-deployment/" rel="noreferrer" target="_blank">https://remote-lab.net/rdo-manager-ha-openstack-deployment/</a><br>
>> >> >> >> >><br>
>> >> >> >> >> Thanks,<br>
>> >> >> >> >> Marius<br>
>> >> >> >> >><br>
>> >> >> >> >> _______________________________________________<br>
>> >> >> >> >> Rdo-list mailing list<br>
>> >> >> >> >> <a href="mailto:Rdo-list@redhat.com">Rdo-list@redhat.com</a><br>
>> >> >> >> >> <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
>> >> >> >> >><br>
>> >> >> >> >> To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
>> >> >> >> ><br>
>> >> >> >> ><br>
>> >> >> ><br>
>> >> >> ><br>
>> >> ><br>
>> >> ><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br></div>