[Openstack] openstack-ansible aio error
Marcin Dulak
marcin.dulak at gmail.com
Mon Feb 5 08:34:13 UTC 2018
Please report a proper bug at https://bugs.launchpad.net/openstack-ansible/
- with the git hash you are using, and all steps to reproduce
Marcin
On Mon, Feb 5, 2018 at 5:53 AM, Satish Patel <satish.txt at gmail.com> wrote:
> Now i got this error when i am running following command, on my CentOS
> i do have "libselinux-python" installed but still ansible saying it is
> not installed. i have submit bug but lets see
>
> $openstack-ansible setup-hosts.yml
>
>
> TASK [openstack_hosts : include]
> ************************************************************
> ************************************************************
> ****************************
> Sunday 04 February 2018 23:49:29 -0500 (0:00:00.481) 0:00:31.439
> *******
> included: /etc/ansible/roles/openstack_hosts/tasks/openstack_update_
> hosts_file.yml
> for aio1
>
> TASK [openstack_hosts : Drop hosts file entries script locally]
> ************************************************************
> *********************************************************
> Sunday 04 February 2018 23:49:30 -0500 (0:00:00.074) 0:00:31.513
> *******
> fatal: [aio1 -> localhost]: FAILED! => {"changed": true, "failed":
> true, "msg": "Aborting, target uses selinux but python bindings
> (libselinux-python) aren't installed!"}
>
> NO MORE HOSTS LEFT
> ************************************************************
> ************************************************************
> ******************************************
>
> NO MORE HOSTS LEFT
> ************************************************************
> ************************************************************
> ******************************************
>
> PLAY RECAP ************************************************************
> ************************************************************
> **************************************************
> aio1 : ok=16 changed=7 unreachable=0 failed=1
>
> Sunday 04 February 2018 23:49:41 -0500 (0:00:11.051) 0:00:42.565
> *******
> ============================================================
> ===================
> openstack_hosts : Drop hosts file entries script locally ---------------
> 11.05s
> openstack_hosts : Install host packages --------------------------------
> 11.03s
> openstack_hosts : Install EPEL, and yum priorities plugin ---------------
> 6.41s
> Install Python2 ---------------------------------------------------------
> 5.87s
> openstack_hosts : Download RDO repository RPM ---------------------------
> 2.60s
> openstack_hosts : Enable and set repo priorities ------------------------
> 1.83s
> openstack_hosts : Install RDO repository and key ------------------------
> 0.80s
> openstack_hosts : Disable requiretty for root sudo on centos ------------
> 0.69s
> Gathering Facts ---------------------------------------------------------
> 0.59s
> openstack_hosts : Enable sysstat cron -----------------------------------
> 0.48s
> openstack_hosts : Allow the usage of local facts ------------------------
> 0.27s
> openstack_hosts : Disable yum fastestmirror plugin ----------------------
> 0.26s
> openstack_hosts : Add global_environment_variables to environment file ---
> 0.24s
> Check for a supported Operating System ----------------------------------
> 0.07s
> openstack_hosts : include -----------------------------------------------
> 0.07s
> openstack_hosts : include -----------------------------------------------
> 0.07s
> openstack_hosts : Gather variables for each operating system ------------
> 0.05s
> apt_package_pinning : Add apt pin preferences ---------------------------
> 0.03s
> openstack_hosts : Remove conflicting distro packages --------------------
> 0.02s
> openstack_hosts : Enable sysstat config ---------------------------------
> 0.01s
> [root at aio playbooks]# yum install libselinux-python
> Loaded plugins: priorities
> 243 packages excluded due to repository priority protections
> Package libselinux-python-2.5-11.el7.x86_64 already installed and latest
> version
> Nothing to do
> [root at aio playbooks]#
>
> On Sun, Feb 4, 2018 at 2:18 PM, <remo at italy1.com> wrote:
> > Not sure about that tripleo is very complicated and ready for production
> where ansible OpenStack is probably not.
> >
> > If you want to learn sure but let’s look at the facts production needs
> something more than what ansible OpenStack can now offer.
> >
> >> Il giorno 04 feb 2018, alle ore 11:14, Satish Patel <
> satish.txt at gmail.com> ha scritto:
> >>
> >> :)
> >>
> >> I am going to try openstack-ansible and and if i am lucky i will
> >> continue and plan to deploy on production but if it will take too much
> >> my time to debug then i would go with tripleO which seems less
> >> complicated so far.
> >>
> >> As you said openstack-ansible has good ubuntu community and we are
> >> 100% CentOS shop and i want something which we are comfortable and
> >> supported by deployment tool.
> >>
> >> My first production cluster is 20 node but it may slowly grow if all
> goes well.
> >>
> >>> On Sun, Feb 4, 2018 at 2:05 PM, <remo at italy1.com> wrote:
> >>> Tripleo = ha
> >>> Packstack = no ha
> >>>
> >>>> Il giorno 04 feb 2018, alle ore 11:00, Satish Patel <
> satish.txt at gmail.com> ha scritto:
> >>>>
> >>>> Just wondering why did you say we can't do HA with TripleO? I thought
> >>>> it does support HA. am i missing something here?
> >>>>
> >>>>> On Sun, Feb 4, 2018 at 11:21 AM, <remo at italy1.com> wrote:
> >>>>> What are you looking for ha? Etc. Tripleo is the way to go for that
> packstack if you want simple deployment but no ha of course.
> >>>>>
> >>>>>> Il giorno 04 feb 2018, alle ore 07:53, Satish Patel <
> satish.txt at gmail.com> ha scritto:
> >>>>>>
> >>>>>> Hi Marcin,
> >>>>>>
> >>>>>> Thank you, i will try other link, also i am using CentOS7 but anyway
> >>>>>> now question is does openstack-ansible ready for production
> deployment
> >>>>>> despite galera issues and bug?
> >>>>>>
> >>>>>> If i want to go on production should i wait or find other tools to
> >>>>>> deploy on production?
> >>>>>>
> >>>>>>> On Sun, Feb 4, 2018 at 5:29 AM, Marcin Dulak <
> marcin.dulak at gmail.com> wrote:
> >>>>>>> When playing with openstack-ansible do it in a virtual setup (e.g.
> nested
> >>>>>>> virtualization with libvirt) so you can reproducibly bring up your
> >>>>>>> environment from scratch.
> >>>>>>> You will have to do it multiple times.
> >>>>>>>
> >>>>>>> https://developer.rackspace.com/blog/life-without-
> devstack-openstack-development-with-osa/
> >>>>>>> is more than 2 years old.
> >>>>>>>
> >>>>>>> Try to follow
> >>>>>>> https://docs.openstack.org/openstack-ansible/latest/
> contributor/quickstart-aio.html
> >>>>>>> but git clone the latest state of the openstack-ansible repo.
> >>>>>>> The above page has a link that can be used to submit bugs directly
> to the
> >>>>>>> openstack-ansible project at launchpad.
> >>>>>>> In this way you may be able to cleanup/improve the documentation,
> >>>>>>> and since your setup is the simplest possible one your bug reports
> may get
> >>>>>>> noticed and reproduced by the developers.
> >>>>>>> What happens is that most people try openstack-ansible, don't
> report bugs,
> >>>>>>> or report the bugs without the information neccesary
> >>>>>>> to reproduce them, and abandon the whole idea.
> >>>>>>>
> >>>>>>> Try to search
> >>>>>>> https://bugs.launchpad.net/openstack-ansible/+bugs?field.
> searchtext=galera
> >>>>>>> for inspiration about what to do.
> >>>>>>> Currently the galera setup in openstack-ansible, especially on
> centos7 seems
> >>>>>>> to be undergoing some critical changes.
> >>>>>>> Enter the galera container:
> >>>>>>> lxc-attach -n aio1_galera_container-4f488f6a
> >>>>>>> look around it, check whether mysqld is running etc., try to
> identify which
> >>>>>>> ansible tasks failed and run them manually inside of the container.
> >>>>>>>
> >>>>>>> Marcin
> >>>>>>>
> >>>>>>>
> >>>>>>>> On Sun, Feb 4, 2018 at 3:41 AM, Satish Patel <
> satish.txt at gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> I have noticed in output "aio1_galera_container" is failed, how
> do i
> >>>>>>>> fixed this kind of issue?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> PLAY RECAP
> >>>>>>>> ************************************************************
> ************************************************************
> **************************************************
> >>>>>>>> aio1 : ok=41 changed=4 unreachable=0
> >>>>>>>> failed=0
> >>>>>>>> aio1_cinder_api_container-2af4dd01 : ok=0 changed=0
> >>>>>>>> unreachable=0 failed=0
> >>>>>>>> aio1_cinder_scheduler_container-454db1fb : ok=0 changed=0
> >>>>>>>> unreachable=0 failed=0
> >>>>>>>> aio1_designate_container-f7ea3f73 : ok=0 changed=0
> unreachable=0
> >>>>>>>> failed=0
> >>>>>>>> aio1_galera_container-4f488f6a : ok=32 changed=3
> unreachable=0
> >>>>>>>> failed=1
> >>>>>>>>
> >>>>>>>>> On Sat, Feb 3, 2018 at 9:26 PM, Satish Patel <
> satish.txt at gmail.com> wrote:
> >>>>>>>>> I have re-install centos7 and give it a try and got this error
> >>>>>>>>>
> >>>>>>>>> DEBUG MESSAGE RECAP
> >>>>>>>>> ************************************************************
> >>>>>>>>> DEBUG: [Load local packages]
> >>>>>>>>> ***************************************************
> >>>>>>>>> All items completed
> >>>>>>>>>
> >>>>>>>>> Saturday 03 February 2018 21:04:07 -0500 (0:00:04.175)
> >>>>>>>>> 0:16:17.204 *****
> >>>>>>>>>
> >>>>>>>>> ============================================================
> ===================
> >>>>>>>>> repo_build : Create OpenStack-Ansible requirement wheels
> --------------
> >>>>>>>>> 268.16s
> >>>>>>>>> repo_build : Wait for the venvs builds to complete
> --------------------
> >>>>>>>>> 110.30s
> >>>>>>>>> repo_build : Install packages ------------------------------
> ------------
> >>>>>>>>> 68.26s
> >>>>>>>>> repo_build : Clone git repositories asynchronously
> ---------------------
> >>>>>>>>> 59.85s
> >>>>>>>>> pip_install : Install distro packages
> ----------------------------------
> >>>>>>>>> 36.72s
> >>>>>>>>> galera_client : Install galera distro packages
> -------------------------
> >>>>>>>>> 33.21s
> >>>>>>>>> haproxy_server : Create haproxy service config files
> -------------------
> >>>>>>>>> 30.81s
> >>>>>>>>> repo_build : Execute the venv build scripts asynchonously
> --------------
> >>>>>>>>> 29.69s
> >>>>>>>>> pip_install : Install distro packages
> ----------------------------------
> >>>>>>>>> 23.56s
> >>>>>>>>> repo_server : Install repo server packages
> -----------------------------
> >>>>>>>>> 20.11s
> >>>>>>>>> memcached_server : Install distro packages
> -----------------------------
> >>>>>>>>> 16.35s
> >>>>>>>>> repo_build : Create venv build options files
> ---------------------------
> >>>>>>>>> 14.57s
> >>>>>>>>> haproxy_server : Install HAProxy Packages
> >>>>>>>>> ------------------------------- 8.35s
> >>>>>>>>> rsyslog_client : Install rsyslog packages
> >>>>>>>>> ------------------------------- 8.33s
> >>>>>>>>> rsyslog_client : Install rsyslog packages
> >>>>>>>>> ------------------------------- 7.64s
> >>>>>>>>> rsyslog_client : Install rsyslog packages
> >>>>>>>>> ------------------------------- 7.42s
> >>>>>>>>> repo_build : Wait for git clones to complete
> >>>>>>>>> ---------------------------- 7.25s
> >>>>>>>>> repo_server : Install repo caching server packages
> >>>>>>>>> ---------------------- 4.76s
> >>>>>>>>> galera_server : Check that WSREP is ready
> >>>>>>>>> ------------------------------- 4.18s
> >>>>>>>>> repo_server : Git service data folder setup
> >>>>>>>>> ----------------------------- 4.04s
> >>>>>>>>> ++ exit_fail 341 0
> >>>>>>>>> ++ set +x
> >>>>>>>>> ++ info_block 'Error Info - 341' 0
> >>>>>>>>> ++ echo
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>> ++ print_info 'Error Info - 341' 0
> >>>>>>>>> ++ PROC_NAME='- [ Error Info - 341 0 ] -'
> >>>>>>>>> ++ printf '\n%s%s\n' '- [ Error Info - 341 0 ] -'
> >>>>>>>>> --------------------------------------------
> >>>>>>>>>
> >>>>>>>>> - [ Error Info - 341 0 ] ------------------------------
> ---------------
> >>>>>>>>> ++ echo
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>> ++ exit_state 1
> >>>>>>>>> ++ set +x
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>>
> >>>>>>>>> - [ Run Time = 2030 seconds || 33 minutes ]
> --------------------------
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>>
> >>>>>>>>> - [ Status: Failure ] ------------------------------
> ------------------
> >>>>>>>>> ------------------------------------------------------------
> ----------
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> I don't know why it failed
> >>>>>>>>>
> >>>>>>>>> but i tried following:
> >>>>>>>>>
> >>>>>>>>> [root at aio ~]# lxc-ls -f
> >>>>>>>>> NAME STATE AUTOSTART
> GROUPS
> >>>>>>>>> IPV4 IPV6
> >>>>>>>>> aio1_cinder_api_container-2af4dd01 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.62, 172.29.238.210, 172.29.244.152 -
> >>>>>>>>> aio1_cinder_scheduler_container-454db1fb RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.117, 172.29.239.172 -
> >>>>>>>>> aio1_designate_container-f7ea3f73 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.235, 172.29.239.166 -
> >>>>>>>>> aio1_galera_container-4f488f6a RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.193, 172.29.236.69 -
> >>>>>>>>> aio1_glance_container-f8caa9e6 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.225, 172.29.239.52, 172.29.246.25 -
> >>>>>>>>> aio1_heat_api_container-8321a763 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.104, 172.29.236.186 -
> >>>>>>>>> aio1_heat_apis_container-3f70ad74 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.166, 172.29.239.13 -
> >>>>>>>>> aio1_heat_engine_container-a18e5a0a RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.118, 172.29.238.7 -
> >>>>>>>>> aio1_horizon_container-e493275c RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.98, 172.29.237.43 -
> >>>>>>>>> aio1_keystone_container-c0e23e14 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.60, 172.29.237.165 -
> >>>>>>>>> aio1_memcached_container-ef8fed4c RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.214, 172.29.238.211 -
> >>>>>>>>> aio1_neutron_agents_container-131e996e RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.153, 172.29.237.246, 172.29.243.227 -
> >>>>>>>>> aio1_neutron_server_container-ccd69394 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.27, 172.29.236.129 -
> >>>>>>>>> aio1_nova_api_container-73274024 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.42, 172.29.238.201 -
> >>>>>>>>> aio1_nova_api_metadata_container-a1d32282 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.218, 172.29.238.153 -
> >>>>>>>>> aio1_nova_api_os_compute_container-52725940 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.109, 172.29.236.126 -
> >>>>>>>>> aio1_nova_api_placement_container-058e8031 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.29, 172.29.236.157 -
> >>>>>>>>> aio1_nova_conductor_container-9b6b208c RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.18, 172.29.239.9 -
> >>>>>>>>> aio1_nova_console_container-0fb8995c RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.47, 172.29.237.129 -
> >>>>>>>>> aio1_nova_scheduler_container-8f7a657a RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.195, 172.29.238.113 -
> >>>>>>>>> aio1_rabbit_mq_container-c3450d66 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.111, 172.29.237.202 -
> >>>>>>>>> aio1_repo_container-8e07fdef RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.141, 172.29.239.79 -
> >>>>>>>>> aio1_rsyslog_container-b198fbe5 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.13, 172.29.236.195 -
> >>>>>>>>> aio1_swift_proxy_container-1a3536e1 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.108, 172.29.237.31, 172.29.244.248 -
> >>>>>>>>> aio1_utility_container-bd106f11 RUNNING 1
> onboot,
> >>>>>>>>> openstack 10.255.255.54, 172.29.239.124 -
> >>>>>>>>> [root at aio ~]# lxc-a
> >>>>>>>>> lxc-attach lxc-autostart
> >>>>>>>>> [root at aio ~]# lxc-attach -n aio1_utility_container-bd106f11
> >>>>>>>>> [root at aio1-utility-container-bd106f11 ~]#
> >>>>>>>>> [root at aio1-utility-container-bd106f11 ~]# source /root/openrc
> >>>>>>>>> [root at aio1-utility-container-bd106f11 ~]# openstack
> >>>>>>>>> openstack openstack-host-hostfile-setup.
> sh
> >>>>>>>>> [root at aio1-utility-container-bd106f11 ~]# openstack
> >>>>>>>>> openstack openstack-host-hostfile-setup.
> sh
> >>>>>>>>> [root at aio1-utility-container-bd106f11 ~]# openstack user list
> >>>>>>>>> Failed to discover available identity versions when contacting
> >>>>>>>>> http://172.29.236.100:5000/v3. Attempting to parse version from
> URL.
> >>>>>>>>> Service Unavailable (HTTP 503)
> >>>>>>>>> [root at aio1-utility-container-bd106f11 ~]#
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> not sure what is this error ?
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Sat, Feb 3, 2018 at 7:29 PM, Satish Patel <
> satish.txt at gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>>> I have tired everything but didn't able to find solution :(
> what i am
> >>>>>>>>>> doing wrong here, i am following this instruction and please
> let me
> >>>>>>>>>> know if i am wrong
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> https://developer.rackspace.com/blog/life-without-
> devstack-openstack-development-with-osa/
> >>>>>>>>>>
> >>>>>>>>>> I have CentOS7, with 8 CPU and 16GB memory with 100GB disk size.
> >>>>>>>>>>
> >>>>>>>>>> Error: http://paste.openstack.org/show/660497/
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I have tired gate-check-commit.sh but same error :(
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Sat, Feb 3, 2018 at 1:11 AM, Satish Patel <
> satish.txt at gmail.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>> I have started playing with openstack-ansible on CentOS7 and
> trying to
> >>>>>>>>>>> install All-in-one but got this error and not sure what cause
> that
> >>>>>>>>>>> error how do i troubleshoot it?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> TASK [bootstrap-host : Remove an existing private/public ssh
> keys if
> >>>>>>>>>>> one is missing]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> ************
> >>>>>>>>>>> skipping: [localhost] => (item=id_rsa)
> >>>>>>>>>>> skipping: [localhost] => (item=id_rsa.pub)
> >>>>>>>>>>>
> >>>>>>>>>>> TASK [bootstrap-host : Create ssh key pair for root]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> ********************************************
> >>>>>>>>>>> ok: [localhost]
> >>>>>>>>>>>
> >>>>>>>>>>> TASK [bootstrap-host : Fetch the generated public ssh key]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> **************************************
> >>>>>>>>>>> changed: [localhost]
> >>>>>>>>>>>
> >>>>>>>>>>> TASK [bootstrap-host : Ensure root's new public ssh key is in
> >>>>>>>>>>> authorized_keys]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> ******************
> >>>>>>>>>>> ok: [localhost]
> >>>>>>>>>>>
> >>>>>>>>>>> TASK [bootstrap-host : Create the required deployment
> directories]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> ******************************
> >>>>>>>>>>> changed: [localhost] => (item=/etc/openstack_deploy)
> >>>>>>>>>>> changed: [localhost] => (item=/etc/openstack_deploy/conf.d)
> >>>>>>>>>>> changed: [localhost] => (item=/etc/openstack_deploy/env.d)
> >>>>>>>>>>>
> >>>>>>>>>>> TASK [bootstrap-host : Deploy user conf.d configuration]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> ****************************************
> >>>>>>>>>>> fatal: [localhost]: FAILED! => {"msg": "{{
> >>>>>>>>>>> confd_overrides[bootstrap_host_scenario] }}: 'dict object'
> has no
> >>>>>>>>>>> attribute u'aio'"}
> >>>>>>>>>>>
> >>>>>>>>>>> RUNNING HANDLER [sshd : Reload the SSH service]
> >>>>>>>>>>>
> >>>>>>>>>>> ************************************************************
> *************************************************
> >>>>>>>>>>> to retry, use: --limit
> >>>>>>>>>>> @/opt/openstack-ansible/tests/bootstrap-aio.retry
> >>>>>>>>>>>
> >>>>>>>>>>> PLAY RECAP
> >>>>>>>>>>> ************************************************************
> ************************************************************
> **************************
> >>>>>>>>>>> localhost : ok=61 changed=36 unreachable=0
> >>>>>>>>>>> failed=2
> >>>>>>>>>>>
> >>>>>>>>>>> [root at aio openstack-ansible]#
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> 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/20180205/676ba0b1/attachment.html>
More information about the Openstack
mailing list