Re: [Openstack-operators] [openstack-operators][openstack-ansible]

2016-12-19 Thread Wade Holler
en all of that is done, I think we could have lots of fun with the ssl libs > issue :D > > Best regards, > JP > > On 17/12/2016, 00:36, "Wade Holler" <wade.hol...@gmail.com> wrote: > > Hi All, > > I am trying to upgrade a multinode cluster that

[Openstack-operators] [openstack-operators][openstack-ansible]

2016-12-16 Thread Wade Holler
Hi All, I am trying to upgrade a multinode cluster that has been very valuable in our environment. The idea was to start at trusty/mitaka and get to xenial/newton. Step1 mitaka -> newton on a trusty environment went fine. Step2 trusty to xenial is not going well and I could use some help. So

Re: [openstack-dev] [openstack-ansible] When to purge the DB, and when not to purge the DB?

2016-07-02 Thread Wade Holler
+1 "As part of the normal execution of the service playbooks" w/ user_variable to turn it on/off of course; whether it defaults to on or off is really designers choice. Some production clouds will have the playbooks ran against them frequently, others not so much. On Sat, Jul 2, 2016 at 7:43

[Openstack-operators] [OpenStack-Ansible] Mitaka Upgrade

2016-04-28 Thread Wade Holler
Hi All, If this is RTFM please point me there and I apologize. If not: We are testing the Liberty to Mitaka transition with OSAD. Could someone please advise if these were the correct general steps. osad multinode (VMs/instances inside a osad cloud) built with latest 12.X liberty osad 1. save

[openstack-dev] [Openstack-operators] [OpenStack-Ansible] Mitaka Upgrade

2016-04-28 Thread Wade Holler
Hi All, If this is RTFM please point me there and I apologize. If not: We are testing the Liberty to Mitaka transition with OSAD. Could someone please advise if these were the correct general steps. osad multinode (VMs/instances inside a osad cloud) built with latest 12.X liberty osad 1. save

Re: [openstack-dev] [kolla]

2016-02-22 Thread Wade Holler
removed multiple python packages via yum and pip uninstall. that made it past it. now hitting a mariadb error early in the deploy If anyone can help I would really appreciate it. Im on #kolla @ wadeholler http://pastebin.com/83jL0ege On Sat, Feb 20, 2016 at 9:45 AM Wade Holler <wade.

Re: [openstack-dev] [kolla]

2016-02-20 Thread Wade Holler
talled via both pip and RPM and they are > different versions. If you want help, join us on irc on #freenode, and we > can get you going. Its much faster then debugging over a mailing list. > > Regards > -steve > > > From: Wade Holler <wade.hol...@gmail.com> &g

[openstack-dev] [kolla]

2016-02-20 Thread Wade Holler
Just a little help probably. On CentOS 7.2 I tried to follow the quickstart very closely. [root@cpn00012 kolla]# python --version Python 2.7.5 [root@cpn00012 kolla]# pip --version pip 8.0.2 from /usr/lib/python2.7/site-packages (python 2.7) tools/build.py fails like this: tools/build.py

Re: [Openstack-operators] [openstack-ansible]

2016-02-17 Thread Wade Holler
really appreciate the help. Wade On Wed, Feb 17, 2016 at 2:33 PM Major Hayden <ma...@mhtx.net> wrote: > On 02/17/2016 01:23 PM, Wade Holler wrote: > > Going to ask this question without much data or background as I hope > someone very familiar with openstack-ansible will be abl

[Openstack-operators] [openstack-ansible]

2016-02-17 Thread Wade Holler
Hi All, Going to ask this question without much data or background as I hope someone very familiar with openstack-ansible will be able to easily answer it. I tried to follow the install guide and network config pretty closely. All is well except my physical compute nodes don't have an eth12.

Re: [Openstack-operators] OpenStack node redundancy

2015-12-18 Thread Wade Holler
Yes and, I prefer mode=4 MLAG bond/team. On Cent we had to use xmit_hash_policy layer2+3 because layer3+4 caused kernel panics @ Cent 7.1.1503 Cheers Wade On Fri, Dec 18, 2015 at 12:17 PM Serguei Bezverkhi (sbezverk) < sbezv...@cisco.com> wrote: > Hello team, > > > > I would appreciate if you

Re: [openstack-dev] [ansible] One or more undefined variables: 'dict object' has no attribute 'bridge'

2015-12-12 Thread Wade Holler
Hi Mark, I haven't reviewed your configs yet but if "bridge" is a valid ansible inventory attribute , then this error is usually caused by trying to reference a host that ansible didn't check in on yet / gather facts on. At least this is what is has been in my brief experience. For example if I

[Openstack-operators] openstack-ansible virt_type=lxc

2015-11-18 Thread Wade Holler
Just a little help needed. on trusty using openstack-ansible ( allinone ) changed user_variables nova_virt_type to lxc re-run os-nova-install Something else I need to do? When launching an instance I get the no hosts found. And in nova-conductor log I get the CPU model error 2015-11-18