[openstack-dev] Building Openstack Trove Images
Debojyoti Das
debojyoti.das at indusnet.co.in
Mon Nov 13 14:22:57 UTC 2017
Hi All,
Please help us regarding the Openstack Issue, we are facing the following
error in our Openstack Environment, and we had tried almost every solution
found at internet but not able to resolve the issue.
we have added one compute node to our Openstack controller which is showing
in the openstack dashboard however the when we launch any VM, the VM goes
into error state. We have gone through most of the things available on the
internet but nothing sorts it out. Below are the logs for the error:
ERROR nova.compute.manager [instance: 054229be-3467-490d-b407-dc256a8747c8]
File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line
984, in _update_ports_for_instance
2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
054229be-3467-490d-b407-dc256a8747c8] port_client, instance, port_id,
port_req_body)
2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
054229be-3467-490d-b407-dc256a8747c8] File "/usr/lib/python2.7/site-
packages/nova/network/neutronv2/api.py", line 445, in _update_port
2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
054229be-3467-490d-b407-dc256a8747c8] _ensure_no_port_binding_
failure(port)
2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
054229be-3467-490d-b407-dc256a8747c8] File "/usr/lib/python2.7/site-
packages/nova/network/neutronv2/api.py", line 191, in
_ensure_no_port_binding_failure
2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
054229be-3467-490d-b407-dc256a8747c8] raise exception.PortBindingFailed(
port_id=port['id'])
2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
054229be-3467-490d-b407-dc256a8747c8] PortBindingFailed: Binding failed for
port 26b727dd-52b4-4b34-b484-6ea3fd571c8d, please check neutron logs for
more information.
Can you throw some light or give us some guidance on this as it has halted
the implementation of our Production Openstack Pike.
Your support and co-operation is highly appreciated.
FYI: Controller and compute node are running CentOS7.
On Mon, Nov 13, 2017 at 6:41 PM, Debojyoti Das <debojyoti.das at indusnet.co.in
> wrote:
> Hi Amrith,
>
> Please throw some light to the issue, we have stuck at a serious point of
> our Production migration from Cloudstack to Openstack. So Please help us,
> you co-operation is highly appreciated.
>
> On Mon, Nov 13, 2017 at 6:10 PM, Debojyoti Das <
> debojyoti.das at indusnet.co.in> wrote:
>
>> Hi Amrith,
>>
>> Please throw some light to the issue, we have stuck at a serious point of
>> our Production migration from Cloudstack to Openstack. So Please help us,
>> you co-operation is highly appreciated.
>>
>> On Mon, Nov 13, 2017 at 1:29 PM, Ritesh Vishwakarma <
>> ritesh.vishwakarma at indusnet.co.in> wrote:
>>
>>> Hi Amirth,
>>>
>>>
>>>
>>> Many thanks for your response coz of which I was able to build a MySQL
>>> image from Ubuntu Xenial.
>>>
>>> However, I am facing another obstacle now, we have added one compute
>>> node to our Openstack controller which is showing in the openstack
>>> dashboard however the when we launch any VM, the VM goes into error state.
>>> We have gone through most of the things available on the internet but
>>> nothing sorts it out. Below are the logs for the error:
>>>
>>>
>>>
>>> ERROR nova.compute.manager [instance: 054229be-3467-490d-b407-dc256a8747c8]
>>> File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py",
>>> line 984, in _update_ports_for_instance
>>>
>>> 2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
>>> 054229be-3467-490d-b407-dc256a8747c8] port_client, instance,
>>> port_id, port_req_body)
>>>
>>> 2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
>>> 054229be-3467-490d-b407-dc256a8747c8] File
>>> "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line
>>> 445, in _update_port
>>>
>>> 2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
>>> 054229be-3467-490d-b407-dc256a8747c8] _ensure_no_port_binding_failur
>>> e(port)
>>>
>>> 2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
>>> 054229be-3467-490d-b407-dc256a8747c8] File
>>> "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line
>>> 191, in _ensure_no_port_binding_failure
>>>
>>> 2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
>>> 054229be-3467-490d-b407-dc256a8747c8] raise
>>> exception.PortBindingFailed(port_id=port['id'])
>>>
>>> 2017-11-12 02:58:57.551 2372 ERROR nova.compute.manager [instance:
>>> 054229be-3467-490d-b407-dc256a8747c8] PortBindingFailed: Binding failed
>>> for port 26b727dd-52b4-4b34-b484-6ea3fd571c8d, please check neutron
>>> logs for more information.
>>>
>>>
>>>
>>>
>>>
>>> Can you throw some light or give us some guidance on this as it has
>>> halted the implementation of our Production Openstack Pike.
>>>
>>> Your support and co-operation is highly appreciated.
>>>
>>>
>>> FYI: Controller and compute node are running CentOS7.
>>>
>>>
>>>
>>> Thanks and Regards,
>>>
>>> Ritesh
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Nov 9, 2017 at 12:03 PM, Amrith Kumar <amrith.kumar at gmail.com>
>>> wrote:
>>>
>>>> Sorry, I should have been more clear.
>>>>
>>>> You shouldn't use redstack.
>>>>
>>>> And you should not be using trovestack with trusty.
>>>>
>>>> All of the gate moved to Xenial a while back and I don't know that
>>>> anyone is verifying trusty any longer. But, YMMV, set the force flag and
>>>> try again if you want. I am not able to verify with Trusty, don't have a
>>>> trusty env.
>>>>
>>>> Apologies for the back and forth. It has been a long week at summit.
>>>>
>>>>
>>>>
>>>> -amrith
>>>>
>>>>
>>>> On Thu, Nov 9, 2017 at 1:24 AM, Ritesh Vishwakarma <
>>>> ritesh.vishwakarma at indusnet.co.in> wrote:
>>>>
>>>>> Hi Amrith,
>>>>>
>>>>> This time I followed the https://github.com/opensta
>>>>> ck/trove/tree/master/integration/ however, it still throws me the
>>>>> same error. Please find the log file attached.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Ritesh
>>>>>
>>>>> On Wed, Nov 8, 2017 at 4:44 PM, Amrith Kumar <amrith.kumar at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Please see inline below.
>>>>>>
>>>>>> -amrith
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 8, 2017 at 9:52 PM, Ritesh Vishwakarma <
>>>>>> ritesh.vishwakarma at indusnet.co.in> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi Amrith,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Please find my response to your queries below:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 1. What (exact) version of OpenStack are you using? Is it
>>>>>>> from upstream or a vendor, if it is the latter, which vendor?
>>>>>>>
>>>>>>> We are using Openstack Pike installed on CentOS7.
>>>>>>>
>>>>>>> 2. What database (exact version) are you trying to create an
>>>>>>> image for?
>>>>>>>
>>>>>>> We want to build images for mysql5.7 as of now.
>>>>>>>
>>>>>>> 3. What operating system (exact version) are you attempting
>>>>>>> to perform this on?
>>>>>>>
>>>>>>> We have tried it from CentOS7 & Ubuntu 14.04.
>>>>>>>
>>>>>>> 4. What command(s) are you executing?
>>>>>>>
>>>>>>> I am step-by-step following the *https://github.com/openstack/trove-integration
>>>>>>> <https://github.com/openstack/trove-integration>* and the
>>>>>>> “./redstack install” command. Also, I want to confirm that as this code
>>>>>>> installs its own devstack cloud, will we be able to use the images
>>>>>>> created using it in our Openstack Pike trove environment.
>>>>>>>
>>>>>>
>>>>>>
>>>>>> The Trove Integration repository is dead and gone for a couple of
>>>>>> releases now and you should be using the stuff from the trove repository as
>>>>>> the documentation indicates.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 5. What exact error(s) are you receiving?
>>>>>>>
>>>>>>> I have attached the logs.
>>>>>>>
>>>>>>
>>>>>>
>>>>>> The end of your error log indicates
>>>>>>
>>>>>> +./stack.sh:main:225 echo 'WARNING: this
>>>>>> script has not been tested on trusty'
>>>>>> WARNING: this script has not been tested on trusty
>>>>>> +./stack.sh:main:226 [[ '' != \y\e\s ]]
>>>>>> +./stack.sh:main:227 die 227 'If you wish to
>>>>>> run this script anyway run with FORCE=yes'
>>>>>> +functions-common:die:187 local exitcode=0
>>>>>> +functions-common:die:188 set +o xtrace
>>>>>> [Call Trace]
>>>>>> ./stack.sh:227:die
>>>>>> [ERROR] ./stack.sh:227 If you wish to run this script anyway run with
>>>>>> FORCE=yes
>>>>>>
>>>>>>
>>>>>> That seems pretty clear to me. Don't do it, redstack is dead, gone,
>>>>>> bye-bye.
>>>>>>
>>>>>> Use the stuff in trove/integration/scripts
>>>>>>
>>>>>> The trove-integration repository should now have been deleted as
>>>>>> well.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Please guide us where are going wrong on this.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Ritesh
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Please guide us where are going wrong on this.
>>>>>>>
>>>>>>> On Wed, Nov 8, 2017 at 12:11 PM, Ritesh Vishwakarma <
>>>>>>> ritesh.vishwakarma at indusnet.co.in> wrote:
>>>>>>>
>>>>>>>> ++Looping my fellow engineer.
>>>>>>>>
>>>>>>>> On Wed, Nov 8, 2017 at 2:34 AM, Amrith Kumar <
>>>>>>>> amrith.kumar at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Ritesh,
>>>>>>>>>
>>>>>>>>> Your answers don't help me understand the problems you are having.
>>>>>>>>> So let's try this instead.
>>>>>>>>>
>>>>>>>>> 1. What (exact) version of OpenStack are you using? Is it from
>>>>>>>>> upstream or a vendor, if it is the latter, which vendor?
>>>>>>>>> 2. What database (exact version) are you trying to create an image
>>>>>>>>> for?
>>>>>>>>> 3. What operating system (exact version) are you attempting to
>>>>>>>>> perform this on?
>>>>>>>>> 4. What command(s) are you executing?
>>>>>>>>> 5. What exact error(s) are you receiving?
>>>>>>>>>
>>>>>>>>> For #4 and #5 it would be ideal if you just cut/pasted a terminal
>>>>>>>>> session into an etherpad or gist or pastebuffer or some such thing and
>>>>>>>>> shared that link via email. If you have passwords and other sensitive
>>>>>>>>> stuff, make sure you redact it.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> -amrith
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Nov 7, 2017 at 5:40 PM, Ritesh Vishwakarma <
>>>>>>>>> ritesh.vishwakarma at indusnet.co.in> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Amrith,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Many Thanks for your response. Hope you are doing well!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The confusing part here is that the OpenStack tutorial page
>>>>>>>>>> itself not seems to be updated https://docs.openstack.org/tro
>>>>>>>>>> ve/latest/admin/building_guest_images.html#build-guest-images
>>>>>>>>>>
>>>>>>>>>> as the *dib-lint* file is there instead of the mentioned *disk-image-create
>>>>>>>>>> *and when executed just verifies the other elements.
>>>>>>>>>>
>>>>>>>>>> I have also tried using https://github.com/denismakogo
>>>>>>>>>> n/trove-guest-image-elements but the error on which I got stuck
>>>>>>>>>> is “deltarpm not installed” (deltarpm is installed on the host machine).
>>>>>>>>>> Though yesterday, I came across the
>>>>>>>>>> https://github.com/openstack/trove-integration which I am going
>>>>>>>>>> to try out today, kindly let me know if it is the right one or please share
>>>>>>>>>> any relevant reference on which we can work.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Ritesh
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 7, 2017 at 8:16 AM, Amrith Kumar <
>>>>>>>>>> amrith.kumar at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Ha, it isn't often that I get called out by name in a mailing
>>>>>>>>>>> list thread.
>>>>>>>>>>>
>>>>>>>>>>> What are the issues that you are facing? Currently there are
>>>>>>>>>>> complete notes about how to build guest images but the issues you may be
>>>>>>>>>>> facing may not relate to the images you are building.
>>>>>>>>>>>
>>>>>>>>>>> So please provide some more details so I can give you a more
>>>>>>>>>>> accurate reply.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -amrith
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 6, 2017 at 6:09 PM, Ritesh Vishwakarma <
>>>>>>>>>>> ritesh.vishwakarma at indusnet.co.in> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Team,
>>>>>>>>>>>>
>>>>>>>>>>>> We have installed Openstack Pike in our campus but despite of
>>>>>>>>>>>> numerous attempts we are just unable to build trove images that we can use
>>>>>>>>>>>> to launch database instances.We also came across a mail thread where Mr.
>>>>>>>>>>>> Amrith updates that some review & update of the OpenStack Trove documents
>>>>>>>>>>>> was going on, kindly provide us some reference document or link which we
>>>>>>>>>>>> can follow.
>>>>>>>>>>>>
>>>>>>>>>>>> https://lists.gt.net/openstack/dev/58182
>>>>>>>>>>>>
>>>>>>>>>>>> We will be eagerly waiting for your response.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>> Ritesh Vishwakarma
>>>>>>>>>>>>
>>>>>>>>>>>> ____________________________________________________________
>>>>>>>>>>>> ______________
>>>>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>>>>> Unsubscribe: OpenStack-dev-request at lists.op
>>>>>>>>>>>> enstack.org?subject:unsubscribe
>>>>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
>>>>>>>>>>>> k-dev
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ____________________________________________________________
>>>>>>>>>>> ______________
>>>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>>>> Unsubscribe: OpenStack-dev-request at lists.op
>>>>>>>>>>> enstack.org?subject:unsubscribe
>>>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
>>>>>>>>>>> k-dev
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ____________________________________________________________
>>>>>>>>>> ______________
>>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>>> Unsubscribe: OpenStack-dev-request at lists.op
>>>>>>>>>> enstack.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 at lists.op
>>>>>>>>> enstack.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 at lists.op
>>>>>>> enstack.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 at lists.op
>>>>>> enstack.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 at lists.op
>>>>> enstack.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 at lists.op
>>>> enstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>
>>
>> --
>>
>>
>> *Thanks & Regards,Debojyoti Das - DevOps Engineer*
>>
>> *Cell: *+91-9933659954/8910001045 *| **Skype: *live:debojyoti.das
>> <debojyoti.das at indusnet.co.in>_4
>> *Hangout: *debojyoti.das at indusnet.co.in
>> *Email: *debojyoti.das at indusnet.co.in <debojyoti at optimizeitsystems.com>
>> *Website: *www.indusnet.co.in
>>
>>
>> *Indus Net Technologies Pvt Ltd*
>> * (CMMi Level 3 Appraised)*
>>
>> SDF Building, 4th Floor, Saltlake
>> Electronic Complex, GP Block, Sector V,
>> Salt Lake City, Bidhannagar, West Bengal-700091
>>
>>
>>
>> *E-Mail Disclaimer:*
>>
>> The views expressed by the author may not necessarily reflect the views
>> or policies of Indus Net Technologies Pvt Ltd. The foregoing is not
>> intended to be a legally binding or effective electronic signature.This
>> e-mail and any attachments transmitted with it, including replies and
>> forwarded copies subsequently transmitted (which may contain alterations),
>> contains information which may be confidential and which may also be
>> privileged. The content of this e-mail is for the exclusive use of the
>> intended recipient(s). If you are not the intended recipient(s), or the
>> person authorized as responsible for delivery to the intended recipient(s),
>> please note that any reading, printing, storage, disclosure, copying or any
>> other action taken in respect of this e-mail is strictly prohibited and may
>> be unlawful.Further, we make every effort to keep our network free from
>> viruses. However, you do need to validate this e-mail and any attachments
>> to it for viruses, as we can take no responsibility for any computer virus
>> that might be transferred by way of this e-mail.
>>
>
>
>
> --
>
>
> *Thanks & Regards,Debojyoti Das - DevOps Engineer*
>
> *Cell: *+91-9933659954/8910001045 *| **Skype: *live:debojyoti.das
> <debojyoti.das at indusnet.co.in>_4
> *Hangout: *debojyoti.das at indusnet.co.in
> *Email: *debojyoti.das at indusnet.co.in <debojyoti at optimizeitsystems.com>
> *Website: *www.indusnet.co.in
>
>
> *Indus Net Technologies Pvt Ltd*
> * (CMMi Level 3 Appraised)*
>
> SDF Building, 4th Floor, Saltlake
> Electronic Complex, GP Block, Sector V,
> Salt Lake City, Bidhannagar, West Bengal-700091
>
>
>
> *E-Mail Disclaimer:*
>
> The views expressed by the author may not necessarily reflect the views or
> policies of Indus Net Technologies Pvt Ltd. The foregoing is not intended
> to be a legally binding or effective electronic signature.This e-mail and
> any attachments transmitted with it, including replies and forwarded copies
> subsequently transmitted (which may contain alterations), contains
> information which may be confidential and which may also be privileged. The
> content of this e-mail is for the exclusive use of the intended
> recipient(s). If you are not the intended recipient(s), or the person
> authorized as responsible for delivery to the intended recipient(s), please
> note that any reading, printing, storage, disclosure, copying or any other
> action taken in respect of this e-mail is strictly prohibited and may be
> unlawful.Further, we make every effort to keep our network free from
> viruses. However, you do need to validate this e-mail and any attachments
> to it for viruses, as we can take no responsibility for any computer virus
> that might be transferred by way of this e-mail.
>
--
*Thanks & Regards,Debojyoti Das - DevOps Engineer*
*Cell: *+91-9933659954/8910001045 *| **Skype: *live:debojyoti.das
<debojyoti.das at indusnet.co.in>_4
*Hangout: *debojyoti.das at indusnet.co.in
*Email: *debojyoti.das at indusnet.co.in <debojyoti at optimizeitsystems.com>
*Website: *www.indusnet.co.in
*Indus Net Technologies Pvt Ltd*
* (CMMi Level 3 Appraised)*
SDF Building, 4th Floor, Saltlake
Electronic Complex, GP Block, Sector V,
Salt Lake City, Bidhannagar, West Bengal-700091
*E-Mail Disclaimer:*
The views expressed by the author may not necessarily reflect the views or
policies of Indus Net Technologies Pvt Ltd. The foregoing is not intended
to be a legally binding or effective electronic signature.This e-mail and
any attachments transmitted with it, including replies and forwarded copies
subsequently transmitted (which may contain alterations), contains
information which may be confidential and which may also be privileged. The
content of this e-mail is for the exclusive use of the intended
recipient(s). If you are not the intended recipient(s), or the person
authorized as responsible for delivery to the intended recipient(s), please
note that any reading, printing, storage, disclosure, copying or any other
action taken in respect of this e-mail is strictly prohibited and may be
unlawful.Further, we make every effort to keep our network free from
viruses. However, you do need to validate this e-mail and any attachments
to it for viruses, as we can take no responsibility for any computer virus
that might be transferred by way of this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171113/4a7b7d59/attachment.html>
More information about the OpenStack-dev
mailing list