Open Stack

Hmm I am in two minds here.

I have an outage booked for Sat/Sun middle of the night.

Thing is its a tightish window and want to avoid additional reconfig if
possible. As I am replacing the network node at the same time.

I only have 7 or 8 networks I would have to change in the mysql. The only
place I can find any reference in the SQL side is ovs_network_bindings and
ovs_vlan_allocations both of which are pretty simple.Š

I think a bash one-liner should be safe enough.

One further question however is assuming my computes are connected like :

eth0
        } bond0.vlan40 -> br-int
eth1

Am I best to hand eth0/1 to ovs and let it do the LACP, or hand it the
bond0?

Also the other vlans on the compute nodes. How would they be presented to
the bare metal os ?

-- 
Geraint Jones

From:  Aaron Rosen <arosen at nicira.com>
Date:  Tuesday, 15 October 2013 1:43 pm
To:  Geraint Jones <geraint at koding.com>
Cc:  Rahul Sharma <rahulsharmaait at gmail.com>, openstack
<openstack at lists.openstack.org>
Subject:  Re: [Openstack] Migration from OVS-GRE to OVS-VLAN

Hi Geraint, 

Most plugins don't support updating the network_type unfortunately. You
could probably get away with updating the network_type in the database. That
said if you are switching from gre to vlans you'll end up having downtime so
it probably makes more sense to write a script that recreates the networks
using vlans instead with the same mac and port info rather than figuring out
how to change the db.

Aaron  


On Tue, Oct 15, 2013 at 10:15 AM, Geraint Jones <geraint at koding.com> wrote:
> Thanks for that, reading it makes me think I will need to update at least some
> stuff.
> 
> Okay so an example of one of my current networks looks like this :
> 
> +---------------------------+--------------------------------------+
> | Field                     | Value                                |
> +---------------------------+--------------------------------------+
> | admin_state_up            | True                                 |
> | id                        | 51efc95c-3791-4ca7-ad83-47a0e9b1d550 |
> | name                      | Application Servers                  |
> | provider:network_type     | gre                                  |
> | provider:physical_network |                                      |
> | provider:segmentation_id  | 7                                    |
> | router:external           | False                                |
> | shared                    | False                                |
> | status                    | ACTIVE                               |
> | subnets                   | 2caa6e3c-45ce-4021-9afa-19133c0d4b5e |
> | tenant_id                 | 59a2d92051fe417f90539622d61951d0     |
> +---------------------------+‹‹‹‹‹‹‹‹‹‹‹‹‹‹‹‹‹‹‹+
> 
> Clearly those will not come up post migration,
> 
> Do I just need to do quantum net-update 51efc95c-3791-4ca7-ad83-47a0e9b1d550
> ‹provider:network_type vlan ‹provider:physical_network physnet
> ‹provider:segmentation_id 107
> 
> ?
> -- 
> Geraint Jones
> Director of Systems & Infrastructure
> Koding 
> https://koding.com
> geraint at koding.com
> M (NZ) +64 22 123 4626 <tel:%2B64%2022%20123%204626>
> M (US) +1 415 316 8027 <tel:%2B1%20415%20316%208027>
> 
> From:  Rahul Sharma <rahulsharmaait at gmail.com>
> Date:  Monday, 14 October 2013 11:02 pm
> To:  Geraint Jones <geraint at koding.com>
> Cc:  openstack <openstack at lists.openstack.org>
> Subject:  Re: [Openstack] Migration from OVS-GRE to OVS-VLAN
> 
> Hi Geraint,
> 
> You missed one line which also needs to be added:-
> bridge_mappings = physnet:br-eth1
> 
> Here, br-eth1 does the similar kind of task which br-tun was doing in GRE
> mode, but with different  internal working. For more details, please refer to
> this guide:-
> http://docs.openstack.org/trunk/openstack-network/admin/content/under_the_hood
> _openvswitch.html
> 
> There is no need to change anything in MySql database.
> 
> Thanks and Regards
> Rahul Sharma
> 
> 
> 
> 
> On Tue, Oct 15, 2013 at 12:24 AM, Geraint Jones <geraint at koding.com> wrote:
>> Hi Guys
>> 
>> We are currently using OVS-GRE in our environment configured as below :
>> 
>> tenant_network_type = gre
>> tunnel_id_ranges = 1:1000
>> integration_bridge = br-int
>> tunnel_bridge = br-tun
>> local_ip = 192.168.52.12
>> enable_tunneling = True
>> 
>> 
>> If I change this to :
>> 
>> tenant_network_type = vlan
>> network_vlan_ranges = physnet:200:400
>> integration_bridge = br-int
>> 
>> 
>> If I then trunk vl 200 ­ 400 to the interfaces bound to br-int what else will
>> I need to change ? Anything in MySQL ?
>> 
>> Thanks
>> 
>> -- 
>> Geraint Jones
>> Director of Systems & Infrastructure
>> Koding 
>> https://koding.com
>> geraint at koding.com
>> M (NZ) +64 22 123 4626 <tel:%2B64%2022%20123%204626>
>> M (US) +1 415 316 8027 <tel:%2B1%20415%20316%208027>
>> 
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
> 
> 
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131015/77df7f28/attachment.html>