settingsLogin | Registersettings

[openstack-dev] [openstack-ansible] network question and documentation

0 votes

Hi,

after a first test architecture of openstack (juno then upgrade to kilo), installed from scratch, and because we use Ansible in our organization, we decided to deploy our next openstack generation architecture from the project openstack-ansible.

I studied your documentation (very good work and very appreciate, http://docs.openstack.org/developer/openstack-ansible/[kilo|liberty]/install-guide/index.html) and i will need some more clarification compared to network architecture.

I'm not sure to be on the good mailing-list because it 's dev oriented here, for all that, i fear my request to be embedded in the openstack overall list, because it's very specific to the architecture proposed by your project (bond0 (br-mngt, br-storage), bond1 (br-vxlan, br-vlan)).

I'm sorry about that if that is the case...

So, i would like to know if i'm going in the right direction.
We want to use both, existing vlan from our existing physical architecture inside openstack (vlan provider) and "private tenant network" with IP floating offer (from a flat network).

My question is about switch configuration:

On Bond0:
the switch port connected to bond0 need to be configured as trunks with:
- the host management network (vlan untagged but can be tagged ?)
- container(mngt) network (vlan-container)
- storage network (vlan-storage)

On Bond1:
the switch port connected to bond1 need to be configured as trunks with:
- vxlan network (vlan-vxlan)
- vlan X (existing vlan in our existing network infra)
- vlan Y (existing vlan in our existing network infra)

Is that right ?

And do i have to define a new network (a new vlan, flat network) that offer floatting IP for private tenant (not using existing vlan X or Y)? Is that new vlan have to be connected to bond1 and/or bond0 ?
Is that host management network could play this role ?

Thank you to consider my request.
Regards

ps: otherwise, about the documentation, for great understanding and perhaps consistency
In Github (https://github.com/openstack/openstack-ansible), in the file openstack_interface.cfg.example, you point out that for br-vxlan and br-storage, "only compute node have an IP on this bridge. When used by infra nodes, IPs exist in the containers and inet should be set to manual".

I think it will be good (but i may be wrong ;-) ) that in chapter 3 of the "install guide: configuring the network on target host", you propose the /etc/network/interfaces for both controller node (br-vxlan, br-storage: manual without IP) and compute node (br-vxlan, br-storage: static with IP).

Fabrice GRELAUD
Université de Bordeaux


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked May 29, 2017 in openstack-dev by Fabrice_Grelaud (780 points)   4 5

8 Responses

0 votes

-----Original Message-----
From: Fabrice Grelaud fabrice.grelaud@u-bordeaux.fr
Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org
Date: February 17, 2016 at 09:02:49
To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org
Subject:  [openstack-dev] [openstack-ansible] network question and documentation

Hi,

after a first test architecture of openstack (juno then upgrade to kilo), installed
from scratch, and because we use Ansible in our organization, we decided to deploy our
next openstack generation architecture from the project openstack-ansible.

I studied your documentation (very good work and very appreciate, http://docs.openstack.org/developer/openstack-ansible/[kilo|liberty]/install-guide/index.html)
and i will need some more clarification compared to network architecture.

I'm not sure to be on the good mailing-list because it 's dev oriented here, for all that,
i fear my request to be embedded in the openstack overall list, because it's very specific
to the architecture proposed by your project (bond0 (br-mngt, br-storage), bond1 (br-vxlan,
br-vlan)).

I'm sorry about that if that is the case...

So, i would like to know if i'm going in the right direction.
We want to use both, existing vlan from our existing physical architecture inside openstack
(vlan provider) and "private tenant network" with IP floating offer (from a flat network).

My question is about switch configuration:

On Bond0:
the switch port connected to bond0 need to be configured as trunks with:
- the host management network (vlan untagged but can be tagged ?)
- container(mngt) network (vlan-container)
- storage network (vlan-storage)

On Bond1:
the switch port connected to bond1 need to be configured as trunks with:
- vxlan network (vlan-vxlan)
- vlan X (existing vlan in our existing network infra)
- vlan Y (existing vlan in our existing network infra)

Is that right ?

And do i have to define a new network (a new vlan, flat network) that offer floatting IP
for private tenant (not using existing vlan X or Y)? Is that new vlan have to be connected
to bond1 and/or bond0 ?
Is that host management network could play this role ?

Thank you to consider my request.
Regards

ps: otherwise, about the documentation, for great understanding and perhaps consistency
In Github (https://github.com/openstack/openstack-ansible), in the file openstack_interface.cfg.example,
you point out that for br-vxlan and br-storage, "only compute node have an IP on this bridge.
When used by infra nodes, IPs exist in the containers and inet should be set to manual".

I think it will be good (but i may be wrong ;-) ) that in chapter 3 of the "install guide: configuring
the network on target host", you propose the /etc/network/interfaces for both controller
node (br-vxlan, br-storage: manual without IP) and compute node (br-vxlan, br-storage:
static with IP).

Hi Fabrice,

Has anyone responded to your questions yet?

--
Ian Cordasco


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 18, 2016 by sigmavirus24_at_gmai (8,720 points)   1 2 3
0 votes

Le 19/02/2016 00:31, Ian Cordasco a écrit :

-----Original Message-----
From: Fabrice Grelaud fabrice.grelaud@u-bordeaux.fr
Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org
Date: February 17, 2016 at 09:02:49
To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org
Subject: [openstack-dev] [openstack-ansible] network question and documentation

Hi,

after a first test architecture of openstack (juno then upgrade to kilo), installed
from scratch, and because we use Ansible in our organization, we decided to deploy our
next openstack generation architecture from the project openstack-ansible.

I studied your documentation (very good work and very appreciate, http://docs.openstack.org/developer/openstack-ansible/[kilo|liberty]/install-guide/index.html)
and i will need some more clarification compared to network architecture.

I'm not sure to be on the good mailing-list because it 's dev oriented here, for all that,
i fear my request to be embedded in the openstack overall list, because it's very specific
to the architecture proposed by your project (bond0 (br-mngt, br-storage), bond1 (br-vxlan,
br-vlan)).

I'm sorry about that if that is the case...

So, i would like to know if i'm going in the right direction.
We want to use both, existing vlan from our existing physical architecture inside openstack
(vlan provider) and "private tenant network" with IP floating offer (from a flat network).

My question is about switch configuration:

On Bond0:
the switch port connected to bond0 need to be configured as trunks with:
- the host management network (vlan untagged but can be tagged ?)
- container(mngt) network (vlan-container)
- storage network (vlan-storage)

On Bond1:
the switch port connected to bond1 need to be configured as trunks with:
- vxlan network (vlan-vxlan)
- vlan X (existing vlan in our existing network infra)
- vlan Y (existing vlan in our existing network infra)

Is that right ?

And do i have to define a new network (a new vlan, flat network) that offer floatting IP
for private tenant (not using existing vlan X or Y)? Is that new vlan have to be connected
to bond1 and/or bond0 ?
Is that host management network could play this role ?

Thank you to consider my request.
Regards

ps: otherwise, about the documentation, for great understanding and perhaps consistency
In Github (https://github.com/openstack/openstack-ansible), in the file openstack_interface.cfg.example,
you point out that for br-vxlan and br-storage, "only compute node have an IP on this bridge.
When used by infra nodes, IPs exist in the containers and inet should be set to manual".

I think it will be good (but i may be wrong ;-) ) that in chapter 3 of the "install guide: configuring
the network on target host", you propose the /etc/network/interfaces for both controller
node (br-vxlan, br-storage: manual without IP) and compute node (br-vxlan, br-storage:
static with IP).
Hi Fabrice,

Has anyone responded to your questions yet?

--
Ian Cordasco

Hi Ian,

alas ! Not at the moment...

Thanks,

--
Fabrice Grelaud
Université de Bordeaux


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 19, 2016 by Fabrice_Grelaud (780 points)   4 5
0 votes

On 02/17/2016 09:00 AM, Fabrice Grelaud wrote:
So, i would like to know if i'm going in the right direction.
We want to use both, existing vlan from our existing physical architecture inside openstack (vlan provider) and "private tenant network" with IP floating offer (from a flat network).

My question is about switch configuration:

On Bond0:
the switch port connected to bond0 need to be configured as trunks with:
- the host management network (vlan untagged but can be tagged ?)
- container(mngt) network (vlan-container)
- storage network (vlan-storage)

On Bond1:
the switch port connected to bond1 need to be configured as trunks with:
- vxlan network (vlan-vxlan)
- vlan X (existing vlan in our existing network infra)
- vlan Y (existing vlan in our existing network infra)

Is that right ?

You have a good plan here, Fabrice. Although I don't have bonding configured in my own production environment, I'm doing much the same as you are with individual network interfaces.

And do i have to define a new network (a new vlan, flat network) that offer floatting IP for private tenant (not using existing vlan X or Y)? Is that new vlan have to be connected to bond1 and/or bond0 ?
Is that host management network could play this role ?

You could use the host management network as your floating IP pool network, but you'd need to create a flat network in OpenStack for that (unless your host management network is tagged). I prefer to use a specific VLAN for those public-facing, floating IP addresses. You'll need routers between your internal networks and that floating IP VLAN to make the floating IP addresses work (if I remember correctly).

ps: otherwise, about the documentation, for great understanding and perhaps consistency
In Github (https://github.com/openstack/openstack-ansible), in the file openstack_interface.cfg.example, you point out that for br-vxlan and br-storage, "only compute node have an IP on this bridge. When used by infra nodes, IPs exist in the containers and inet should be set to manual".

I think it will be good (but i may be wrong ;-) ) that in chapter 3 of the "install guide: configuring the network on target host", you propose the /etc/network/interfaces for both controller node (br-vxlan, br-storage: manual without IP) and compute node (br-vxlan, br-storage: static with IP).

That makes sense. Would you be able to open a bug for us? I'll be glad to help you write some documentation if you're interested in learning that process.

Our bug tracker is here in LaunchPad:

https://bugs.launchpad.net/openstack-ansible

--
Major Hayden


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 19, 2016 by Major_Hayden (3,560 points)   6 6
0 votes

Le 19 févr. 2016 à 14:20, Major Hayden major@mhtx.net a écrit :

On 02/17/2016 09:00 AM, Fabrice Grelaud wrote:

So, i would like to know if i'm going in the right direction.
We want to use both, existing vlan from our existing physical architecture inside openstack (vlan provider) and "private tenant network" with IP floating offer (from a flat network).

My question is about switch configuration:

On Bond0:
the switch port connected to bond0 need to be configured as trunks with:
- the host management network (vlan untagged but can be tagged ?)
- container(mngt) network (vlan-container)
- storage network (vlan-storage)

On Bond1:
the switch port connected to bond1 need to be configured as trunks with:
- vxlan network (vlan-vxlan)
- vlan X (existing vlan in our existing network infra)
- vlan Y (existing vlan in our existing network infra)

Is that right ?

You have a good plan here, Fabrice. Although I don't have bonding configured in my own production environment, I'm doing much the same as you are with individual network interfaces.

And do i have to define a new network (a new vlan, flat network) that offer floatting IP for private tenant (not using existing vlan X or Y)? Is that new vlan have to be connected to bond1 and/or bond0 ?
Is that host management network could play this role ?

You could use the host management network as your floating IP pool network, but you'd need to create a flat network in OpenStack for that (unless your host management network is tagged). I prefer to use a specific VLAN for those public-facing, floating IP addresses.

Thanks a lot for your answer.
I prefer to use a specific vlan too. Could you confirm to me that this new vlan has to be part of the trunk between the switch port and the bond1 interface (where we have the br-vlan) ?

You'll need routers between your internal networks and that floating IP VLAN to make the floating IP addresses work (if I remember correctly).

Absolutely.

ps: otherwise, about the documentation, for great understanding and perhaps consistency
In Github (https://github.com/openstack/openstack-ansible), in the file openstack_interface.cfg.example, you point out that for br-vxlan and br-storage, "only compute node have an IP on this bridge. When used by infra nodes, IPs exist in the containers and inet should be set to manual".

I think it will be good (but i may be wrong ;-) ) that in chapter 3 of the "install guide: configuring the network on target host", you propose the /etc/network/interfaces for both controller node (br-vxlan, br-storage: manual without IP) and compute node (br-vxlan, br-storage: static with IP).

That makes sense. Would you be able to open a bug for us? I'll be glad to help you write some documentation if you're interested in learning that process.

Our bug tracker is here in LaunchPad:

https://bugs.launchpad.net/openstack-ansible

I open a bug (https://bugs.launchpad.net/openstack-ansible/+bug/1547598 https://bugs.launchpad.net/openstack-ansible/+bug/1547598).

I’ll be delighted to contribute at the documentation, at my level. So, i’m interesting in learning that process.
We (my project team) plan to follow your guide then i’ll go back with pleasure that might be misunderstood to improve this guide.

Regards,

Fabrice Grelaud


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 19, 2016 by Fabrice_Grelaud (780 points)   4 5
0 votes

Hi osa team,

i have a multimode openstack-ansible deployed, ocata 15.1.3, with ceph as backend for cinder (with our own ceph infra).

After create an instance with root volume, i would like to mount a ceph block or cephfs directly to the vm (not a cinder volume). So i want to attach a new interface to the vm that is in the ceph vlan.
How can i do that ?

We have our ceph vlan propagated on bond0 interface (bond0.xxx and br-storage configured as documented) for openstack infrastructure.

Should i have to propagate this vlan on the bond1 interface where my br-vlan is attach ?
Should i have to use the existing br-storage where the ceph vlan is already propagated (bond0.xxx) ? And how i create the ceph vlan network in neutron (by neutron directly or by horizon) ?

Has anyone ever experienced this ?


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 24, 2017 by Fabrice_Grelaud (780 points)   4 5
0 votes

I doubt many people have tried this, because 1) cinder/nova/glance probably do the job well in a multi-tenant fashion 2) you’re poking holes into your ceph cluster security.

Anyway, if you still want it, you would need (I guess) have to create a provider network that will be allowed to access your ceph network.

You can either route it from your current public network, or create another network. It’s 100% up to you, and not osa specific.

Best regards,
JP

On 24/05/2017, 15:02, "fabrice grelaud" fabrice.grelaud@u-bordeaux.fr wrote:

Hi osa team,

i have a multimode openstack-ansible deployed, ocata 15.1.3, with ceph as backend for cinder (with our own ceph infra).

After create an instance with root volume, i would like to mount a ceph block or cephfs directly to the vm (not a cinder volume). So i want to attach a new interface to the vm that is in the ceph vlan.
How can i do that ?

We have our ceph vlan propagated on bond0 interface (bond0.xxx and br-storage configured as documented) for openstack infrastructure.

Should i have to propagate this vlan on the bond1 interface where my br-vlan is attach ?
Should i have to use the existing br-storage where the ceph vlan is already propagated (bond0.xxx) ? And how i create the ceph vlan network in neutron (by neutron directly or by horizon) ?

Has anyone ever experienced this ?

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse@rackspace.com and delete the original message. Your cooperation is appreciated.

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 25, 2017 by Jean-Philippe.Evrard (580 points)   1
0 votes

Thanks for the answer.

My use case is for a file-hosting software system like « Seafile » which can use a ceph backend (swift too but we don’t deploy swift on our infra).

Our network configuration of our infra is identical as your OSA documentation. So, on our compute node we have two bonding interface (bond0 and bond1).
The ceph vlan is actually propagate on bond0 (where is attach br-storage) to have ceph backend for our openstack.
And on bond1, among other, we have br-vlan for ours vlans providers.

If i understood correctly, the solution is to propagate too on our switch the ceph vlan on bond1, and create by neutron the provider network to be reachable in the tenant by our file-hosting software.

For security issues, using neutron rbac tool to share only this provider network to the tenant in question, could be sufficient ?

I’m all ears ;-) if you have another alternative.

Regards,
Fabrice

Le 25 mai 2017 à 14:01, Jean-Philippe Evrard Jean-Philippe.Evrard@rackspace.co.uk a écrit :

I doubt many people have tried this, because 1) cinder/nova/glance probably do the job well in a multi-tenant fashion 2) you’re poking holes into your ceph cluster security.

Anyway, if you still want it, you would need (I guess) have to create a provider network that will be allowed to access your ceph network.

You can either route it from your current public network, or create another network. It’s 100% up to you, and not osa specific.

Best regards,
JP

On 24/05/2017, 15:02, "fabrice grelaud" fabrice.grelaud@u-bordeaux.fr wrote:

Hi osa team,

i have a multimode openstack-ansible deployed, ocata 15.1.3, with ceph as backend for cinder (with our own ceph infra).

After create an instance with root volume, i would like to mount a ceph block or cephfs directly to the vm (not a cinder volume). So i want to attach a new interface to the vm that is in the ceph vlan.
How can i do that ?

We have our ceph vlan propagated on bond0 interface (bond0.xxx and br-storage configured as documented) for openstack infrastructure.

Should i have to propagate this vlan on the bond1 interface where my br-vlan is attach ?
Should i have to use the existing br-storage where the ceph vlan is already propagated (bond0.xxx) ? And how i create the ceph vlan network in neutron (by neutron directly or by horizon) ?

Has anyone ever experienced this ?


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse@rackspace.com and delete the original message. Your cooperation is appreciated.

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 29, 2017 by Fabrice_Grelaud (780 points)   4 5
0 votes

Hello,

That was indeed my suggestion.
The alternative would be to make sure your ceph can be routed through your public network. But it’s not my infrastructure, I don’t know what you store as data, etc…

In either case, you’re making possible for your tenants to access a part of your infra (the ceph cluster that’s used for openstack too), so you should think of the implications twice (bad neighbours, security intrusions…).

Best regards,
JP

On 29/05/2017, 10:27, "fabrice grelaud" fabrice.grelaud@u-bordeaux.fr wrote:

Thanks for the answer.

My use case is for a file-hosting software system like « Seafile »  which can use a ceph backend (swift too but we don’t deploy swift on our infra).

Our network configuration of our infra is identical as your OSA documentation. So, on our compute node we have two bonding interface (bond0 and bond1).
The ceph vlan is actually propagate on bond0 (where is attach br-storage) to have ceph backend for our openstack.
And on bond1, among other, we have br-vlan for ours vlans providers.

If i understood correctly, the solution is to propagate too on our switch the ceph vlan on bond1, and create by neutron the provider network to be reachable in the tenant by our file-hosting software.

For security issues, using neutron rbac tool to share only this provider network to the tenant in question, could be sufficient ?

I’m all ears ;-) if you have another alternative.

Regards,
Fabrice
> Le 25 mai 2017 à 14:01, Jean-Philippe Evrard <Jean-Philippe.Evrard@rackspace.co.uk> a écrit :
> 
> I doubt many people have tried this, because 1) cinder/nova/glance probably do the job well in a multi-tenant fashion 2) you’re poking holes into your ceph cluster security.
> 
> Anyway, if you still want it, you would need (I guess) have to create a provider network that will be allowed to access your ceph network.
> 
> You can either route it from your current public network, or create another network. It’s 100% up to you, and not osa specific.
> 
> Best regards,
> JP
> 
> On 24/05/2017, 15:02, "fabrice grelaud" <fabrice.grelaud@u-bordeaux.fr> wrote:
> 
>    Hi osa team,
> 
>    i have a multimode openstack-ansible deployed, ocata 15.1.3, with ceph as backend for cinder (with our own ceph infra).
> 
>    After create an instance with root volume, i would like to mount a ceph block or cephfs directly to the vm (not a cinder volume). So i want to attach a new interface to the vm that is in the ceph vlan.
>    How can i do that ?
> 
>    We have our ceph vlan propagated on bond0 interface (bond0.xxx and br-storage configured as documented) for openstack infrastructure.
> 
>    Should i have to propagate this vlan on the bond1 interface where my br-vlan is attach ?
>    Should i have to use the existing br-storage where the ceph vlan is already propagated (bond0.xxx) ? And how i create the ceph vlan network in neutron (by neutron directly or by horizon) ?
> 
>    Has anyone ever experienced this ?
> 
>    __________________________________________________________________________
>    OpenStack Development Mailing List (not for usage questions)
>    Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
>    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> ________________________________
> Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse@rackspace.com and delete the original message. Your cooperation is appreciated.
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 31, 2017 by Jean-Philippe.Evrard (580 points)   1
...