Thursday, 2016-07-21

*** zhurong has quit IRC00:01
*** david-lyle has joined #openstack-kolla00:02
*** jascott1_tmp has joined #openstack-kolla00:02
*** mewald has quit IRC00:03
openstackgerritPrithiv proposed openstack/kolla: Support Networking-SFC Container  https://review.openstack.org/34493000:15
v1k0d3nis anyone having issues with docker v1.11?00:16
v1k0d3nprechecks are failing with docker v1.11.2 / API 1.2300:17
*** david-lyle has quit IRC00:18
v1k0d3nah, i see a bug already out there for it :( crap. https://bugs.launchpad.net/kolla/+bug/160271200:19
openstackLaunchpad bug 1602712 in kolla "Docker Version Check fails in error" [Undecided,New]00:19
*** jascott1_tmp has quit IRC00:31
*** diogogmt has quit IRC00:33
*** banix has joined #openstack-kolla00:36
*** mbound has joined #openstack-kolla00:38
*** mbound has quit IRC00:43
*** Liuqing has joined #openstack-kolla00:45
*** rhallisey has quit IRC00:54
*** zhurong has joined #openstack-kolla01:11
*** banix has quit IRC01:11
*** Jeffrey4l has joined #openstack-kolla01:16
*** inc0 has quit IRC01:30
*** diogogmt has joined #openstack-kolla01:32
*** harlowja has joined #openstack-kolla01:35
*** harlowja has quit IRC01:35
*** harlowja has joined #openstack-kolla01:36
*** daneyon has joined #openstack-kolla01:39
*** csj has joined #openstack-kolla01:42
*** daneyon has quit IRC01:43
*** salv-orl_ has joined #openstack-kolla02:02
*** salv-orl_ has quit IRC02:02
*** salv-orl_ has joined #openstack-kolla02:03
*** salv-orlando has quit IRC02:05
*** salv-orl_ has quit IRC02:11
*** unicell has quit IRC02:14
*** csj has quit IRC02:21
*** david-lyle has joined #openstack-kolla02:24
*** david-lyle has quit IRC02:29
*** signed8bit_Zzz is now known as signed8bit02:29
*** signed8b_ has joined #openstack-kolla02:32
*** signed8bit has quit IRC02:32
*** Jeffrey4l has quit IRC02:38
*** Jeffrey4l_ has joined #openstack-kolla02:38
*** harlowja has quit IRC02:46
*** yuanying has quit IRC02:46
*** signed8b_ has quit IRC03:07
*** salv-orlando has joined #openstack-kolla03:09
*** salv-orlando has quit IRC03:19
*** aernhart has quit IRC03:19
*** inc0 has joined #openstack-kolla03:19
*** inc0 has quit IRC03:25
*** dave-mccowan has quit IRC03:27
*** mark-casey has joined #openstack-kolla03:32
*** yuanying has joined #openstack-kolla03:48
*** yuanying_ has joined #openstack-kolla04:03
*** yuanying has quit IRC04:06
*** diga has joined #openstack-kolla04:09
*** salv-orlando has joined #openstack-kolla04:18
*** bdaca has joined #openstack-kolla04:23
*** salv-orlando has quit IRC04:28
*** diga has quit IRC04:29
*** Liuqing has quit IRC04:36
*** Liuqing has joined #openstack-kolla04:36
*** salv-orlando has joined #openstack-kolla04:59
*** yuanying has joined #openstack-kolla05:03
*** michauds has joined #openstack-kolla05:05
*** yuanying_ has quit IRC05:06
*** kfox1111 has quit IRC05:06
*** michauds has quit IRC05:10
*** kfox1111 has joined #openstack-kolla05:15
*** salman has joined #openstack-kolla05:17
*** unicell has joined #openstack-kolla05:24
openstackgerritrahul sharma proposed openstack/kolla: updates default registry tag to latest version  https://review.openstack.org/34516605:30
*** unicell has quit IRC05:31
*** unicell has joined #openstack-kolla05:31
*** harlowja has joined #openstack-kolla05:39
*** dmueller-evoila has joined #openstack-kolla05:43
*** mark-casey has quit IRC05:58
*** unicell has quit IRC05:59
*** unicell has joined #openstack-kolla06:02
*** harlowja has quit IRC06:04
*** daneyon has joined #openstack-kolla06:09
*** daneyon has quit IRC06:14
*** bjolo has joined #openstack-kolla06:21
*** bjolo has quit IRC06:25
*** bjolo has joined #openstack-kolla06:25
bjolomorning06:25
*** mewald has joined #openstack-kolla06:28
bdacahi06:33
*** mewald1 has joined #openstack-kolla06:37
*** mewald has quit IRC06:39
openstackgerritDennis Mueller proposed openstack/kolla: Added neutron-metering-agent  https://review.openstack.org/34480806:41
mewald1moirning06:43
mewald1morning06:43
*** BernhardW has joined #openstack-kolla06:48
*** BernhardW is now known as bwe_06:48
*** lulei has joined #openstack-kolla06:50
*** mfalatic has quit IRC06:51
luleihi, all. I'm new here. Any suggestion for me to start? Thanks.06:52
*** salv-orlando has quit IRC06:52
*** cfarquhar has quit IRC06:55
*** jascott1_tmp has joined #openstack-kolla06:56
*** cfarquhar has joined #openstack-kolla06:58
*** cfarquhar has quit IRC06:58
*** cfarquhar has joined #openstack-kolla06:58
*** salman has quit IRC06:59
*** bootsha has joined #openstack-kolla07:00
mewald1What do you guys think about limiting cpu and memory for each container?07:02
*** cfarquhar has quit IRC07:03
*** athomas has joined #openstack-kolla07:05
*** Serlex has joined #openstack-kolla07:10
*** Serlex has quit IRC07:13
*** Serlex has joined #openstack-kolla07:17
*** b_bezak has joined #openstack-kolla07:18
*** Serlex has quit IRC07:18
bjolohmmm horizon and plugins?07:19
bjololulei, what do you want to try?07:20
bjolofor example, containers tab is not showing up.07:20
*** cfarquhar has joined #openstack-kolla07:20
*** cfarquhar has quit IRC07:20
*** cfarquhar has joined #openstack-kolla07:20
bjolomewald1, when i enable rgw/swift i was kinda expecting that tab to show up in horizon. i guess i have to enable that manually in horizon or?07:21
bjolomewald1, limiting... anything in particular your are thinking of?07:22
mewald1I have never tried that in Kolla but typically Horizon discovers the plugins to load by looking at the service endpoints registered in Keystone07:22
mewald1I would check if everything is set up correctly there first07:22
mewald1then try using them via CLI, if all of this works but the tab in Horizon is still not showing we should continue looking at horizon07:23
mewald1any reviewers for https://review.openstack.org/#/c/344705/ ?07:27
patchbotmewald1: patch 344705 - kolla - External Ceph - Implementation Nova07:27
bjolomewald1, would love to give +1 but i dont know the code base well enough to approve yet.07:37
bjolomewald1, i can only have opinions on the structure07:37
mewald1no worries, it was primarily addressing core reviewers :)07:38
bjolobut i do feel globals.conf is getting kinda messy and hard to understand07:38
bjoloto continue the discusssion we had yesterday....07:39
mewald1can you go into details? maybe we can work on that without losing the option to enable / disable ceph per individual service07:39
bjoloenable_ceph means today that kolla should deploy ceph right?07:39
mewald1correct07:39
bjoloi think we should make that a seperate type of playbook. i.e. break that out07:40
mewald1it already is07:40
bjoloand name it something like kolla_ceph_deploy07:40
mewald1https://github.com/openstack/kolla/tree/master/ansible/roles/ceph07:40
mewald1but that makes in inconsistent with all the other enable_* options07:40
mewald1https://github.com/openstack/kolla/blob/master/etc/kolla/globals.yml#L10807:41
bjoloyes it is a seperate code tree, but i mean logically07:41
bjolofrom an operator and workflow perspective07:42
mewald1I dont get it07:42
bjolohold, let me check something07:42
mewald1The only thing that is inconsistent atm is https://github.com/openstack/kolla/blob/master/etc/kolla/globals.yml#L130 but I'll fix that in a later patch when my Nova patch is through07:43
bjolokolla ceph deploy options are scattererd out in globals07:44
mewald1I think the structure is as follows: enable_* parameters are flags for Kolla, "Ceph options" are those options that configure the _deployment_ of Ceph, the "Cinder options" section configures Cinder when _using_ Ceph. It makes sense to me, but if you feel it is messed up propose a patch :)07:47
*** Serlex has joined #openstack-kolla07:47
*** salv-orlando has joined #openstack-kolla07:53
bjolohttp://paste.openstack.org/show/538933/07:54
bjolokolla means glue07:54
bjolokolla depoying ceph is an exception i believe for real use cases07:55
bjoloso i would like to see all kolla ceph options grouped together in globals.conf07:55
bjolobut... if we do that. what does enable_ceph mean in the opstack options section?07:56
bjoloopenstack options section07:57
mewald1I dont know man, I am indifferent to this. My suggestion is: Put together a patch and submit it for review and we'll see what people thing07:58
mewald1-g +k07:58
*** daneyon has joined #openstack-kolla07:58
*** shardy has joined #openstack-kolla07:59
bjolohttp://paste.openstack.org/show/538935/08:01
*** daneyon has quit IRC08:02
bjolokolla deploy ceph or not? doesn't that need a new flag?08:03
*** salv-orlando has quit IRC08:05
*** jascott1_tmp has quit IRC08:06
*** tyrola has joined #openstack-kolla08:12
*** Serlex has quit IRC08:12
bjolomewald1, when using your external ceph, where do you feed kolla the ceph info that it needs?08:15
bjolofor cinder_backend_ceph etc08:16
mewald1bjolo: https://github.com/openstack/kolla/blob/master/doc/external-ceph-guide.rst should explain it in great depth :)08:16
mewald1its not the most recent version. check my proposed patch for updated version08:17
bjolook i see08:27
bjolowhen kolla deploys ceph, where does it keep the keys etc?08:30
mewald1same location: /etc/ceph/08:30
bjoloi mean on the deployer node08:31
mewald1not at all I think08:31
mewald1ansible creates the cephx credentials and installs keyring files in the containers08:31
bjolohmm i just added one more node to my kolla ceph and kolla-ansible deploy worked08:32
*** jascott1_tmp has joined #openstack-kolla08:33
mewald1wouldnt you expect that?08:33
*** gfidente|afk has joined #openstack-kolla08:34
bjoloyes, but doesnt kolla deployer need to know some stuff to be able to do that?08:34
bjolo(need to review my ceph deploy knowledge :) )08:34
mewald1All you need are bootstrap keys for OSDs I think. If you are interested in finding out how it works: My best guess is to start looking at https://github.com/openstack/kolla/blob/master/ansible/roles/ceph/tasks/distribute_keyrings.yml08:36
bjoloand when kolla deploys new / upgrade a compute node, it needs to know the keys08:44
bjolook from what i can see in the code, it fetches the keys from the mons08:44
bjolocorrect?08:44
mewald1looks like it, yes08:44
bjoloso loosing all my mons, means loosing my ceph?08:45
bjolowell it usually does that anyway right but...08:45
mewald1correct, but thats always the case08:45
bjolobut i mean i cannot deploy new ones with kolla08:45
mewald1hmm not so sure, because at some point Kolla deploys the first mon without any others available08:46
bjololets say big maintenance, i through away my mons containers to deploy new ones08:46
mewald1to that must work somehow08:46
bjolowhoopsi ceph gone08:47
mewald1If you loose all mons Ceph is gone by definition. I dont think it makes any different whether you are able to build new mons with the same config or not. Recovering will always be pain in the ass :D08:49
bjolonaw ceph will be offline if i loose my mons08:49
bjolobut if i deploy a new one with right keys, ceph is back08:50
mewald1you might be right, I have no idea how Kolla handles it. As said: have never tried it :) If you try, please report back :)08:50
*** jascott1_tmp has quit IRC08:54
bjolohave no nodes to play with right now, handed off to testing yesterday08:54
*** Serlex has joined #openstack-kolla09:01
*** gfidente|afk is now known as gfidente09:03
*** bootsha has quit IRC09:03
*** salv-orlando has joined #openstack-kolla09:03
bjoloenable_ceph_rgw does not seem to create an object store API endpoint09:05
bjolokolla 2.0.209:05
*** ntpttr has quit IRC09:08
*** ntpttr has joined #openstack-kolla09:08
*** bjolo has quit IRC09:08
*** bjolo has joined #openstack-kolla09:08
mewald1I dont think it should09:11
mewald1swift should, though09:11
bjolo?09:11
bjolorgw is to me a replacement for swift09:12
mewald1ah sorry, got confused :D09:12
mewald1too much multitasking09:12
*** salv-orlando has quit IRC09:13
bdacabjolo: to do this, rgw should connect with keystone I think09:20
*** wznoinsk_ has joined #openstack-kolla09:20
*** sean-k-m1 has joined #openstack-kolla09:20
bdacaand it is not implemented i think09:20
*** wznoinsk- has joined #openstack-kolla09:22
*** wznoinsk has quit IRC09:22
*** sean-k-mooney has quit IRC09:22
*** wznoinsk has joined #openstack-kolla09:22
*** wznoinsk| has joined #openstack-kolla09:23
*** wznoinsk- has quit IRC09:24
*** wznoinsk has quit IRC09:25
*** wznoinsk_ has quit IRC09:25
*** wznoinsk has joined #openstack-kolla09:30
*** tyrola has quit IRC09:31
*** tyrola has joined #openstack-kolla09:31
*** wznoinsk| has quit IRC09:32
openstackgerritMerged openstack/kolla: Configurable policy.json for keystone  https://review.openstack.org/34427309:41
*** salv-orlando has joined #openstack-kolla09:43
*** salv-orl_ has joined #openstack-kolla09:56
bdacabjolo, mewald1: inspired by your ceph-related discussion i tested your scenario with all ceph_mon removals09:57
bdacaand it breaks everything :D09:58
*** bootsha has joined #openstack-kolla09:58
mewald1nice! :D09:59
*** salv-orlando has quit IRC10:00
bjolobdaca, not implemented in kolla or not in general?10:00
bjolohave to check, but our fuel based clouds are runing rados_gw and is intergrated with keystone10:01
bjolobdaca, cool! (or not)10:01
*** zhurong has quit IRC10:02
*** salv-orlando has joined #openstack-kolla10:04
bjolobdaca, mewald1 and i continued seperatly on that. if you want to read more, you can read it here10:05
bjolohttp://paste.openstack.org/show/538959/10:05
bjolotime for proteins, fat and carbs.10:06
*** dwalsh_ has joined #openstack-kolla10:06
*** dwalsh has joined #openstack-kolla10:07
*** salv-orl_ has quit IRC10:08
*** Liuqing has quit IRC10:08
*** salv-orlando has quit IRC10:08
*** Liuqing has joined #openstack-kolla10:09
bdacabjolo: not implemented in kolla, on the ceph rgw guide there is a description what to do to connect rgw with keystone10:12
bjoloaha ok missed that. tnx for pointing out10:13
*** wznoinsk_ has joined #openstack-kolla10:15
*** wznoinsk has quit IRC10:17
*** mbound has joined #openstack-kolla10:26
*** mewald1 has quit IRC10:35
*** rhallisey has joined #openstack-kolla10:50
openstackgerritPrithiv proposed openstack/kolla: Support Networking-SFC Container  https://review.openstack.org/34493010:54
*** chopmann has joined #openstack-kolla10:56
*** bootsha has quit IRC10:58
*** bootsha has joined #openstack-kolla11:04
openstackgerritDennis Mueller proposed openstack/kolla: Added neutron-metering-agent  https://review.openstack.org/34480811:16
*** Liuqing has quit IRC11:19
*** dave-mccowan has joined #openstack-kolla11:23
*** dwalsh has quit IRC11:25
bjolohttps://github.com/ceph/ceph-docker11:25
*** dwalsh_ has quit IRC11:25
bjolosebastian haan is a contributer. says a lot11:25
bjolooops sorry wrong channel :)11:26
*** zhubingbing has joined #openstack-kolla11:30
*** aernhart has joined #openstack-kolla11:36
*** zhurong has joined #openstack-kolla11:37
*** zhurong has quit IRC11:42
*** aernhart_ has joined #openstack-kolla11:43
*** zhurong has joined #openstack-kolla11:44
*** Serlex has quit IRC11:44
*** aernhart has quit IRC11:46
*** Serlex has joined #openstack-kolla11:51
*** bdaca has quit IRC11:58
v1k0d3ndoes anyone know if there's anything special i need to do for haproxy with multinode vs aio? i am getting an error on play "Waiting for virtual IP to appear" because there's a timeout. do i need to have separate ip addresses for haproxy on different hosts or am i missing a keepalive flag maybe?12:10
*** mewald has joined #openstack-kolla12:18
bjolov1k0d3n, you need to have an UNUSED ip for haproxy. i.e. that ip cannot be configure on any of the nodes12:19
bjolov1k0d3n, sometimes if you do repeated deployments. i.e. deploy, tear down. the IP is still configured on one of the haproxy nodes12:20
bjolodo an ip addr | grep <VIP> on all nodes to see if it is ther12:20
bjoloalternatively run: kolla-ansible -i <inventory file> prechecks12:21
openstackgerritMathias proposed openstack/kolla: External Ceph - Implementation Nova  https://review.openstack.org/34470512:23
*** athomas has quit IRC12:27
*** banix has joined #openstack-kolla12:28
*** banix has quit IRC12:33
*** banix has joined #openstack-kolla12:34
*** athomas has joined #openstack-kolla12:34
*** diogogmt has quit IRC12:36
*** banix has quit IRC12:37
*** diogogmt has joined #openstack-kolla12:38
*** zhubingbing has quit IRC12:41
*** salv-orlando has joined #openstack-kolla12:45
*** lyncos has joined #openstack-kolla12:46
*** diogogmt has quit IRC12:46
*** zhubingbing has joined #openstack-kolla12:47
v1k0d3nbjolo: it's an unused ip, but i am running all roles on all nodes in this deployment, so haproxy is trying to install on each node using the same ip address.12:48
v1k0d3nso it passes on the first, fails on the rest.12:49
v1k0d3nprechecks succeed each time though.12:49
mewaldv1k0d3n: I dont think that's what's happening. Its not haproxy who sets the IP but keepalived12:51
*** salv-orlando has quit IRC12:51
v1k0d3n^^ right...sorry.12:51
mewaldv1k0d3n: if you connect to each node and do ip addr show in each: Do you see the VIP on each node or multiple times?12:52
v1k0d3ni wrote the wrong thing...mind was thinking one, hands were typing the other (confusing sorry about that).12:52
mewaldI've seen it a couple of times that when you redeploy everything the VIP is not removed from the interface12:53
mewaldas a result the next run of prechecks fails as the IP responds to ping12:53
v1k0d3nok, so...i the VIP get's placed on one...node04...but it is not being placed on the others.12:53
v1k0d3nshould vip be the same on each?12:53
mewaldno, the VIP should only be carried by a single node!12:54
v1k0d3nright, that makes sense...12:55
mewaldat the moment of running the prechecks playbook, NOBODY should carry the IP12:55
mewaldotherwise the check will fail12:55
v1k0d3nso that happened...let me explain again....starting from scratch.12:55
v1k0d3nip is 10.254.254.25/32 > prechecks succeed.12:55
v1k0d3nthen run...playbook try to apply...get's applied to node04 >> success.12:56
v1k0d3nnow it tries to apple to the OTHERS...12:56
v1k0d3nbad12:56
v1k0d3nthat fails...12:56
v1k0d3nthen memcache/mariadb fails...bombs out.12:56
v1k0d3none sec...let me paste playbook progression for you...12:56
mewaldwas going to ask for that :)12:57
v1k0d3nmewald: https://gist.github.com/v1k0d3n/28fbeb16f291aa236139f4bf30e5fcd612:58
v1k0d3nsee what i mean now?12:59
v1k0d3nso my assumption is that keepalive is either acting wonky / the same ip is being applied to all nodes and that there's a configuration limitation i am missing  (my guess here)13:00
*** mewald1 has joined #openstack-kolla13:02
mewald1well that theory is something you can validate within 30 sec13:02
mewald1another idea would be: The database nodes dont come up for some reason and therefore Haproxy doesnt see them as UP.13:03
mewald1https://github.com/openstack/kolla/blob/6f17a71d7fe30422ee96c9e159b45ebd72b7d563/ansible/roles/mariadb/tasks/check.yml13:03
mewald1see what happens here? The play runs mysql client in the mariadb container against the kolla_internal_fqdn which points to the VIP13:04
mewald1but you can easily troubleshoot all that13:04
*** mewald has quit IRC13:05
openstackgerritDave Walker proposed openstack/kolla: Add Watcher ansible roles and templates  https://review.openstack.org/33755613:06
*** JianqingJiang has joined #openstack-kolla13:12
*** jtriley has joined #openstack-kolla13:13
*** godleon has joined #openstack-kolla13:16
*** neouf has quit IRC13:19
*** rmart04 has joined #openstack-kolla13:20
*** neouf has joined #openstack-kolla13:21
*** neouf has quit IRC13:39
*** Liuqing has joined #openstack-kolla13:40
*** neouf has joined #openstack-kolla13:40
*** Liuqing has quit IRC13:41
bjolomewald1, ok so now i have configure swift and as you said, it now shows up in horizon13:45
bjolomewald1, however, i have also built murano and magnum and deployed, but those does not show in horizon. Should they or do i need to do that manually? or not implemented in kolla?13:47
bjoloendpoints are there13:47
*** lyncos_ has joined #openstack-kolla13:52
*** haplo37_ has joined #openstack-kolla13:57
*** salv-orlando has joined #openstack-kolla14:01
*** mgoddard_ has joined #openstack-kolla14:02
*** salv-orl_ has joined #openstack-kolla14:02
openstackgerritJeffrey Zhang proposed openstack/kolla: Bind the ceilometer-api process to the api_interface only  https://review.openstack.org/34545114:04
*** zhurong has quit IRC14:04
*** mgoddard has quit IRC14:05
*** salv-orlando has quit IRC14:07
*** salv-orlando has joined #openstack-kolla14:09
*** bjolo has quit IRC14:11
mewald1bjolo: I believe they need horizon plugins which are not shipped by default14:11
*** salv-orl_ has quit IRC14:14
*** neouf has quit IRC14:17
*** bootsha has quit IRC14:18
v1k0d3nmewald1: interesting. ok. so i may have to rerun with a different vip. i used the same as with an AIO, which at first was a 169.254.0.2514:18
v1k0d3nand even on that node, i am getting connection refused :(14:19
v1k0d3nERROR 2003 (HY000): Can't connect to MySQL server on '169.254.0.25' (111 "Connection refused")14:19
*** neouf has joined #openstack-kolla14:19
v1k0d3ni think the deployment is stuck in some halfway state...which really sucks14:20
v1k0d3nmewald1: so when i try to access the container, the mariadb command doesn't exist14:23
mewald1the sql client command should be "mysql"14:24
mewald1or are you looking for the server binary?14:24
*** Mr_Broken has joined #openstack-kolla14:24
v1k0d3nsorry...having issues thinking apparently this morning.14:24
v1k0d3nusing mysql, no databases returned.14:25
v1k0d3n(working on little sleep).14:25
v1k0d3nso within the container on localhost...14:26
v1k0d3nERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111 "Connection refused")14:26
*** aernhart__ has joined #openstack-kolla14:26
v1k0d3n(mariadb)[mysql@os-node04 /]$ mysql -h localhost -P 3306 -u haproxy -e show databases;14:26
mewald1try with -u root -h 127.0.0.1 -p<PW>14:26
mewald1ah14:26
mewald1well it never got to the point where any databases could be created14:26
mewald1can you verify the galera cluster works?14:27
mewald1SHOW STATUS LIKE 'wsrep_cluster%'14:27
*** aernhart_ has quit IRC14:27
v1k0d3ni know this sounds bad...but i am really new to galera clusters.14:29
v1k0d3nlearning still.14:29
v1k0d3nso that's a direct command?14:30
mewald1mysql -h localhost -P 3306 -u haproxy -e "SHOW STATUS LIKE 'wsrep_cluster%';"14:30
mewald1that should work14:30
v1k0d3ncan't connect to socket14:31
v1k0d3n2.0.1 is a good build version for kolla, right?14:31
mewald1ah shit, sorry. use root user14:31
mewald1yes14:31
*** Mr_Broken has quit IRC14:31
mewald1mysql -h 127.0.0.1 -u root -p -e "SHOW STATUS LIKE 'wsrep_cluster%';"14:31
mewald1does that do?14:31
v1k0d3nlooking for a mysql password in the passwords.yml file....14:33
v1k0d3ndb got it14:33
v1k0d3nstill connection refused.14:34
v1k0d3nmaybe i need to rebuild the containers again or something?14:34
*** huikang has joined #openstack-kolla14:34
*** ljjjustin has quit IRC14:40
*** bwe_ has quit IRC14:42
*** ljjjustin has joined #openstack-kolla14:43
*** michauds has joined #openstack-kolla14:44
*** aernhart_ has joined #openstack-kolla14:47
*** JianqingJiang has quit IRC14:48
*** bdaca has joined #openstack-kolla14:48
*** Jeffrey4l_ has quit IRC14:48
*** zhubingbing has quit IRC14:49
*** zhubingbing has joined #openstack-kolla14:49
*** aernhart__ has quit IRC14:50
*** dmueller-evoila has quit IRC14:52
*** Jeffrey4l_ has joined #openstack-kolla14:53
mewald1v1k0d3n: just found out mariadb is not listening on 127.0.0.114:53
mewald1you have to use the IP of your controller host14:54
*** inc0 has joined #openstack-kolla14:55
inc0good morning14:55
mewald1hi14:56
*** michauds has quit IRC14:57
*** inc0_ has joined #openstack-kolla14:57
*** diogogmt has joined #openstack-kolla14:59
*** pece has joined #openstack-kolla15:01
*** b_bezak has quit IRC15:01
*** inc0 has quit IRC15:01
*** b_bezak has joined #openstack-kolla15:01
*** mgoddard_ has quit IRC15:02
*** haplo37_ has quit IRC15:02
*** david-lyle has joined #openstack-kolla15:04
*** b_bezak has quit IRC15:06
*** mgoddard has joined #openstack-kolla15:08
*** daneyon has joined #openstack-kolla15:11
openstackgerritMerged openstack/kolla: Change rgw frontend interface  https://review.openstack.org/34441015:13
*** sdake has joined #openstack-kolla15:13
inc0_hey sdake, you15:14
inc0_you've pinged me yesterday'\15:14
*** haplo37_ has joined #openstack-kolla15:14
sdakemorning15:14
sdakeya15:14
sdakeneed an email t the l related to osic cluster15:14
sdakekey points should be dates, link to testing, and contributors so you can get them set up15:14
sdakesince that starts friday iirc15:15
sdakeor monday15:15
inc0_on that note, we'll move 1 week forward, got info from osic operators15:15
inc0_but will get more time in return15:15
inc0_they had some problems with setup15:15
inc0_I'll send over details as soon as I get them myself:)15:15
*** daneyon has quit IRC15:16
*** salv-orlando has quit IRC15:16
*** sdake_ has joined #openstack-kolla15:17
sdake_rhallisey its best practice to put a 1 week window on voting and tell how many votes are needed to pass a vote and place [vote] in the tag15:19
*** sdake has quit IRC15:19
sdake_that way people don't forget to vote - know its a vote -and whether they need to care enough to vote15:19
rhalliseyk15:20
rhalliseyI can update it15:22
inc0_sdake_, did you review customizations prototype?15:24
openstackgerritMerged openstack/kolla: Change rgw frontend interface  https://review.openstack.org/34441115:24
sdake_man i can't believe kolla has 4365 commits15:27
inc0_well we did have Sam in our team15:27
inc0_he had his way to push these numbers to unrealistic levels15:27
*** unicell1 has joined #openstack-kolla15:29
*** bootsha has joined #openstack-kolla15:30
*** unicell has quit IRC15:30
*** mliima has quit IRC15:32
*** michauds has joined #openstack-kolla15:35
*** bootsha has quit IRC15:35
*** michauds has quit IRC15:40
*** salv-orlando has joined #openstack-kolla15:43
pecehi, any tips how to tcpdump MySQL traffic from single container in Kolla?15:43
*** slagle has quit IRC15:45
inc0_pece you can't do this on a single container per se15:45
inc0_but you can do this for all of them, and you can filter out using tcpdump15:45
inc0_like you normally would15:46
inc0_also you can run tcpdump on host and it won't affect anything15:46
*** slagle has joined #openstack-kolla15:47
*** rmart04 has quit IRC15:49
*** zhubingbing has quit IRC15:50
*** zhubingbing has joined #openstack-kolla15:51
sdake_inc0_ kolla has same number of commits in its lifecycle that heat did16:12
*** jascott1_tmp has joined #openstack-kolla16:19
*** godleon has quit IRC16:19
inc0_gerrit is down?16:22
*** ayoung has joined #openstack-kolla16:24
*** ayoung has quit IRC16:25
*** ayoung has joined #openstack-kolla16:25
*** derekjhyang has joined #openstack-kolla16:29
derekjhyangHey folks, I have a question: when I built nova-libvirt container image with tools/build.py , I met an error in libvirt-bin installation(I used ubuntu-based image)16:36
Mech422Morning16:36
*** lyncos has quit IRC16:39
*** zhubingbing has quit IRC16:41
*** david-lyle has quit IRC16:41
*** mewald1 has quit IRC16:43
Mech422sdake_, inc0_: I think the recent 'external ceph' discussions really are more about pluggability then ceph...16:44
Mech422sdake_, inc0_: so many of the openstack components have multiple drivers/options/etc now that as sdake mentioned, it will be impossible to cater to them all in kolla core16:45
inc0_yeah, I agree16:46
inc0_but I think it's summit-worthy topic16:46
*** sdake_ has quit IRC16:46
Mech422inc0_: yeah - above my pay grade...16:46
inc0_nah16:46
inc0_just we need lots of eyes/brains on this one16:47
Mech422inc0_: but I don't think we should be 'all or nothing' on stuff like this (eg 'ceph is enabled so everything uses ceph' )16:47
Mech422inc0_: _deploying_ stuff should be orthogonal to _using_ it16:47
inc0_yeah, I agree, we always planned to do this plugabbility16:47
Mech422inc0_: btw, my boss is wanting to know about the upgrade process with kolla...16:48
inc0_what does he want to know?16:49
*** sdake has joined #openstack-kolla16:49
Mech422inc0_: do we have compelling upgrade/maintenance stories yet ?16:49
*** mark-casey has joined #openstack-kolla16:49
Mech422inc0_: oh just the usual - can we use kolla to stay on 'current' os (eg will kolla/netwon be able to in-place upgrade to kolla/o)16:50
Mech422inc0_: can we add nodes with kolla, can we delete nodes with kolla, etc etc16:50
inc0_so, stories are hard, we need production deployments to hear the stories;) but featureset is there16:55
inc0_we support orchiestrated upgrades between major and minor releases16:55
inc0_kolla-ansible upgrade will take tyou from L->M and M->N16:55
Mech422inc0_: I'll be doing rolling upgrades of our small cluster starting a week from friday16:55
inc0_kolla tries to do rolling whenever it's possible16:55
Mech422inc0_: oh nice!16:55
inc0_but I still suggest to call a maintenance window16:56
inc0_as neutron for example is crap to do rolling upgrade16:56
inc0_still, 60 nodes took 10mins so that's not that bad16:56
inc0_as for adding/deleting ndoes16:56
inc0_compute nodes are super easy16:56
inc0_controller nodes are a bit harder as galera and rabbitmq doesn't like chanign of cluster size that much16:57
inc0_but apart from that, to add node just add it into inventory and rerun the deployment16:57
inc0_delete node - just remove containers and volumes16:57
*** unicell has joined #openstack-kolla16:57
*** unicell1 has quit IRC16:58
Mech422inc0_: cool ...This should also give us some feedback as to how kolla/Newton is working overall, as our dev/qa group is supposed to start using it16:58
Mech422inc0_: very small, and not mission critical - but live users nonetheless :-)16:59
inc0_yeah, make sure to tell us any painpoints you encounter16:59
inc0_brb, changing vpns17:00
*** inc0_ has quit IRC17:00
*** inc0 has joined #openstack-kolla17:00
inc0back17:01
rahulssdake: should I update the version to 2.0.3 in stable/mitaka?17:03
rahulsI missed the commit in ansible/groups_vars/all.yml17:04
rahulshttps://review.openstack.org/#/c/345166/17:04
patchbotrahuls: patch 345166 - kolla (stable/mitaka) - updates default registry tag to latest version17:04
rahulsI hope its  ok if I update it to 2.0.3?17:04
rahulswhen I built my images yesterday, they were built with tag 2.0.3 and then deployment failed at it was looking for 2.0.217:04
*** jascott1_tmp has quit IRC17:05
*** chopmann has quit IRC17:08
Mech422inc0: I have a patch to fix the ceph-in-partition stuff that was just merged - should I open a new bug/gerrit or can we just use the existing one ?17:10
Mech422inc0: its literally like 2 lines of code17:10
openstackgerritDavid Wang proposed openstack/kolla-kubernetes: WIP(do not merge) Add status command for Workflow Engine  https://review.openstack.org/34510217:13
inc0TrivialFix17:13
inc0just use this17:13
*** inc0 has quit IRC17:13
*** inc0 has joined #openstack-kolla17:14
*** wrouesnel1 has quit IRC17:17
*** athomas has quit IRC17:19
*** Jeffrey4l_ has quit IRC17:19
openstackgerritrahul sharma proposed openstack/kolla: updates default registry tag to latest version  https://review.openstack.org/34516617:23
*** athomas has joined #openstack-kolla17:30
*** harlowja has joined #openstack-kolla17:44
*** bjolo has joined #openstack-kolla17:45
inc0wirehead_, rhallisey I might have to cancel next weeks meeting17:54
*** mewald has joined #openstack-kolla17:54
rhalliseyinc0, move it later?17:57
*** Serlex has quit IRC17:57
ccesariohi guys... does someone is having problem on kolla-build with the current git code ? http://paste.openstack.org/show/539099/17:58
*** jascott1_tmp has joined #openstack-kolla17:58
*** mliima has joined #openstack-kolla17:58
Mech422ccesario: looks like your missing the 'https' driver for apt17:59
ccesarioMech422, maybe any code did this..... because before I update my local rep the build it was working :)18:01
Mech422ccesario: something might have switched to using a https repo?18:01
Mech422ccesario: I'm building now - give me 20 minutes and I can see if I get errors18:01
*** inc0 has quit IRC18:02
Mech422ccesario: you could try install apt-transport-https and rebuilding if you don't want to wait18:02
ccesarioMech422, sure... sure18:02
ccesariolet me check with apt-transport-https installed18:03
*** david-lyle has joined #openstack-kolla18:04
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Adds ansible support to deploy skydns service  https://review.openstack.org/33567718:04
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Adds ansible support to deploy skydns service  https://review.openstack.org/33567718:05
*** david-lyle_ has joined #openstack-kolla18:05
*** david-lyle has quit IRC18:05
*** jascott1_tmp has quit IRC18:07
ccesarioMech422, the hosts already has apt-transport-https pack ... let try include it in base  container18:07
Mech422ccesario: sorry boss grabbed me - I'll take a look in a bit...18:13
ccesarioMech422, no problem  :)18:14
*** david-lyle_ has quit IRC18:22
ccesarioMech422, only to notify you.... the same error happen even with apt-transport-https pack into docker/base/Dockerfile.j2 file18:27
*** salv-orlando has quit IRC18:28
*** salv-orlando has joined #openstack-kolla18:30
*** bjolo_ has joined #openstack-kolla18:32
*** salv-orlando has quit IRC18:34
*** harlowja has quit IRC18:35
*** harlowja has joined #openstack-kolla18:38
bjologood evening18:40
*** daneyon has joined #openstack-kolla18:47
*** bjolo has quit IRC18:50
*** michauds has joined #openstack-kolla18:51
*** derekjhyang has quit IRC18:52
*** daneyon has quit IRC18:53
Mech422ccesario: I get the same error18:57
ccesarioMech422, O_o18:57
ccesariothanks to let me know :)18:58
ccesariobut does not exists https:// entry to apt configs18:59
*** harlowja has quit IRC18:59
*** banix has joined #openstack-kolla19:06
*** banix has quit IRC19:07
Mech422ccesario: I'm getting weird xml responses from elasticsearch.co : https://packages.elastic.co/elasticsearch/2.x/debian19:12
Mech422sdake: Is the wifey re-arranging repos ?19:13
Mech422sdake: spring cleaning maybe ? :-D19:14
*** bjolo has joined #openstack-kolla19:14
openstackgerritDavid Wang proposed openstack/kolla-kubernetes: WIP(do not merge) Add status command for Workflow Engine  https://review.openstack.org/34510219:21
*** jascott1_tmp has joined #openstack-kolla19:30
v1k0d3nhey all. having issues with a multi-node deployment, and i can't seem to get over them.19:35
bjolowhats the error?19:35
v1k0d3nit always passes prechecks, but fails at  haproxy | Waiting for virtual IP to appear19:35
v1k0d3ni have all nodes be both compute and controller19:36
v1k0d3n5 node cluster.19:36
bjolocan you paste your multinode and globals.conf?19:36
v1k0d3nit works on the first node that ansible grabs, applies the ip address for the keepalive, and bombs out on all the rest.19:36
bjolowhat version of kolla?19:36
bjolopip list | grep kolla19:36
*** ByPasS has joined #openstack-kolla19:37
v1k0d3nhttps://gist.github.com/v1k0d3n/3fe9f71129bc52d82c038dbdc9e0094a19:38
v1k0d3nhttps://gist.github.com/v1k0d3n/06033dbeece0ab61dfd956c8efee1bd319:39
*** sdake_ has joined #openstack-kolla19:39
v1k0d3nkolla is 2.0.119:39
*** sdake has quit IRC19:40
v1k0d3nanything glaring there?19:42
bjolonot the error, but fyi. when building your own images, it is recommended to add a 4 digit to openstack_release. i.e 2.0.1.1 for ex19:42
v1k0d3noh, interesting...i thought that had to be the same as kolla...didn't realize that.19:42
v1k0d3nso anything on the error though?19:43
v1k0d3nbeen stuck on this, and really want to find a way through it.19:44
*** shardy has quit IRC19:45
bjolonope *should* work19:45
bjolobut since it is not working, i would simplify19:45
bjolodisable TLS for now19:45
bjoloonly deploy 1 controler, 1 network, 1 compute19:45
bjoloyou only have IP configured on eth0 right?19:46
bjolodo you have kolla tools on each node so you can clean them properly?19:47
v1k0d3ndo kolla tools need to be install on each node?19:48
v1k0d3nlol19:48
bjolonope19:48
v1k0d3nok...but just for the cleanup, is that right?19:48
bjolobut the kolla repo does have a tools folder that ...19:48
bjoloexactly19:48
bjoloi assume you have a couple of failed installs by now right?19:48
v1k0d3ntis true...definitely.19:49
bjoloeasiest is just to clone the kolla repo on each node19:49
bjoloclean up each host. cleanup-containers; cleanup-host; cleanup-images -f19:51
bjolomake sure VIP is not lingering on any node19:51
bjolosimply the deployment as suggested above19:51
bjolothere is a 2.0.2 tag out now as well19:52
bjolobut i dont think there are any 2.0.2 images on docker hub, so you need to do another build if you wanna try that19:52
bjolopersonally i pip install stable-mitaka latest branch19:58
bjolowhat version of ansible and docker are you running?20:03
*** bdaca has quit IRC20:04
*** lyncos_ has quit IRC20:04
rahulsbjolo: stable/mitaka do has 2.0.2 tag. I guess the new images get built with 2.0.3 tag20:05
rahulsmy bad, I read half line.20:05
rahulsis there any build issue going on with ubuntu based images?20:06
bjoloi run centos images, but i have done quite a few ubuntu builds lately and not seen any issues20:07
*** inc0 has joined #openstack-kolla20:07
rahulsI am seeing them today20:07
bjolorahuls, on mitaka branch?20:08
rahulsyes20:08
rahulsI guess earlier today, ccesario pointed out the same20:09
bjolohmm20:09
rahulshttp://logs.openstack.org/66/345166/2/check/gate-kolla-dsvm-build-ubuntu-binary/fd13ed5/console.html#_2016-07-21_19_33_37_62378120:09
openstackgerritMathias proposed openstack/kolla: External Ceph - Implementation Nova  https://review.openstack.org/34470520:09
rahulsThis is the output of jenkins autobuild for one of my patches20:09
rahulsit passes everything except ubuntu20:09
*** inc0 has quit IRC20:09
rahulsit looks like there is some issue going on with ubuntu based images20:10
*** mewald has left #openstack-kolla20:10
*** gfidente is now known as gfidente|afk20:11
*** inc0 has joined #openstack-kolla20:11
*** shardy has joined #openstack-kolla20:12
*** salv-orlando has joined #openstack-kolla20:14
bjoloim having kolla swift access issues20:14
bjolodid a small setup of swift and it works for admin, but a normal users have no access20:16
bjoloanyone experienced this?20:18
*** tyrola has quit IRC20:24
*** huikang has quit IRC20:31
*** mliima has quit IRC20:34
*** jtriley has quit IRC20:36
openstackgerritIldar proposed openstack/kolla: Fixing typo in the documentation  https://review.openstack.org/34565920:37
Mech422rahuls: Can you access the elastic.co repos?  I think thats the issue biting ccesario and I20:37
Mech422anyone else having issues with the elastic.co repos ? http://packages.elastic.co/kibana/4.4/debian shows an xml error20:38
bjolohmm admin also has issues when going through the public apis20:38
bjolowhats going on here20:39
Mech422bjolo: are you using different public/admin endpoints?20:39
*** harlowja has joined #openstack-kolla20:39
bjoloyes, using TLS so public is not the same as admin/internal20:40
Mech422bjolo: I have to export OS_INTERFACE=admin and OS_ENDPOINT=admin20:40
Mech422bjolo: it default to trying to hit the public endpoint IIRC20:40
*** lyncos has joined #openstack-kolla20:40
bjolook20:42
Mech422bjolo: you can just add that to your admin-openrc.sh20:42
bjoloadmin-openrc.sh works fine using os client20:44
bjolohorizon works fine when using admin tenant20:44
inc0anyone seen issue with apt-transport-https missing?20:44
Mech422anyone else having issues with the elastic.co repos ? http://packages.elastic.co/kibana/4.4/debian shows an xml error20:45
bjoloadding admin to a the sandbox tenant as _member_20:45
bjoloswift not working20:45
*** tyrola has joined #openstack-kolla20:45
Mech422inc0: check scrollback20:45
inc0Mech422, I just tried to build and it failed on elastic20:45
Mech422inc0: yeah - repo is fubar20:45
Mech422inc0: I tried asking here and in #elasticsearch but not getting any answer20:46
Mech422inc0: I figured sdake_ could let his wife know20:46
inc0shes working with Ansible, not elasti20:46
inc0c20:46
Mech422inc0: oh - my bad20:47
Mech422inc0: anyway - if you hit the url directly, it spits out an xml error saying key 'kibana/4.4/debian' not found20:48
*** ccesario has quit IRC20:49
inc0for me it failed on build20:49
Mech422inc0: same for me and ccesario20:49
inc0that https method not found20:49
*** tyrola has quit IRC20:49
Mech422inc0: I think that's a red-herring20:49
inc0and here I was, doing demo how cool is kolla...;)20:49
Mech422inc0: oh - I see you met Mr. Murphy20:50
Mech422:-)20:50
Mech422inc0: we should probaby update /etc/kolla/admin-openrc.sh at some point to specify the admin endpoint...20:53
Mech422inc0: we're starting to see people install with seperate public/admin endpoints, and everything seems to default to hitting the 'public' endpoint20:53
inc0yeah, good call20:54
Mech422I export OS_INTERFACE and OS_ENDPOINT='admin' ...I think that covers nova, and neutron?  there was one I couldn't find the override for ? cinder maybe ?20:55
*** salv-orlando has quit IRC20:56
bjoloMech422, yes +1 on that20:56
bjoloTLS is a must for production20:56
bjoloimplies seperate admin and public endpoints afa understand it20:57
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: POC - Ansible support for Mariadb  https://review.openstack.org/33425520:57
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Adds ansible support to deploy skydns service  https://review.openstack.org/33567720:57
*** haplo37_ has quit IRC21:00
*** tyrola has joined #openstack-kolla21:03
bjolohas anyone attempted to make a docker image of kolla deployer node?21:04
bjolodocker run kolla-master:2.0.221:04
bjolowith all deps sorted out of course21:06
openstackgerritDavid Wang proposed openstack/kolla-kubernetes: WIP(do not merge) Add status command for Workflow Engine  https://review.openstack.org/34510221:06
Mech422inc0:  <warkolm> just tested with LS and it works ok?21:08
Mech422inc0: maybe its not the elastic.co repos (warkolm says they're not supposed to be browseable)21:09
inc0Mech422, what hepled me is to install apt-get -y install apt-transport-https  in container21:10
Mech422inc0: ccessario mentioned trying that and not having any luck...21:11
Mech422inc0: I'll try that when I get back - I gotta take the GF to look at some houses21:11
Mech422inc0: did you put that in base image ? or just elasticsearch container ?21:12
Mech422inc0: oh - elastic.co is in the base image sources.list, so needs to be there I guess21:12
*** banix has joined #openstack-kolla21:20
bjolov1k0d3n, hows it going? any improvements?21:24
v1k0d3nbjolo: had a really long call with a big wig on our side....21:27
bjolook you gotta take care of that first :)21:28
v1k0d3ngetting back to it. while doing that i noticed that pip installing kolla failed on one of the other nodes21:28
bjolooh you dont have to do pip install to run the tools21:28
bjolojust git clone ...; cd kolla/tools; ./cleanup-containers21:28
v1k0d3nthe clean that you're talking about...21:29
v1k0d3njust the cleanup stull in /kolla, right21:29
v1k0d3n?21:29
v1k0d3ncontainers/host/etc21:29
bjoloyes21:29
bjoloresets the target node21:29
v1k0d3nah! on the pip...should've really thought about that!21:30
*** daneyon has joined #openstack-kolla21:30
bjoloonly master node needs pip install21:32
v1k0d3nassuming if i do that i need to redeploy passwords, certs etc...21:32
v1k0d3nbtw...thanks for the help and staying around/asking again21:32
*** tyrola has quit IRC21:33
bjolothat will be done automatically when you do your next kolla-ansible -i <inventory file> deploy21:33
bjolono worries :)21:33
*** tyrola has joined #openstack-kolla21:33
mark-caseybjolo: v1k0d3n: you may not have to clone on nodes.  ansible -i /usr/local/share/kolla/ansible/inventory/ -m script -a '/kolla/tools/cleanup-containers' all21:33
v1k0d3neven the certs? i thought certs needed to be done manually...21:33
mark-caseythat'll push the script from the deployer and run it21:34
mark-caseyout of $tmpdir21:34
*** daneyon has quit IRC21:35
bjolomark-casey, cool.21:35
v1k0d3n \o/ mark-casey! awesome trick21:36
mark-casey:)21:37
*** dave-mccowan has quit IRC21:37
*** inc0 has quit IRC21:37
bjoloso i still have this swift issue when accessing it as a normal _member_ user for sandbox tenant21:39
bjoloForbidden 40321:39
*** shardy has quit IRC21:39
bjolois there like a quota or permission that needs to be enabled?21:39
bjolokeystone policy.json?21:40
*** harlowja has quit IRC21:41
v1k0d3nshoot now complaining that /etc/kolla/certificates/haproxy.pem doesn't exist (which is doesnt)21:43
bjolodid you comment out the TLS stuff in globals.conf?21:43
bjolooh did you run ./cleanup-host on the deployer node?21:44
v1k0d3nyes21:44
bjolosorry if i was vague. only do the cleanup on the target nodes21:45
bjoloi meant21:45
*** pece has quit IRC21:45
v1k0d3nwell, they're all target nodes in this case...21:45
v1k0d3nall doing everything, if that's ok?21:45
v1k0d3nwas told it should be though...21:45
bjolo?21:45
bjoloplease go over your setup21:45
bjoloyou have a seperate master node and 5 target nodes?21:46
v1k0d3n5 hosts. all controller, compute and network. it's for a test environment.21:46
bjoloyes, but since you have issues, i would recommend to scale down and simplify till you get it working21:47
bjoloi.e. basic basic default deployment21:47
bjolono TLS21:47
*** harlowja has joined #openstack-kolla21:48
bjolo1 node as the master node. git clone ...; pip install; tox -e genconfig; cp etc /etc/kolla; etc etc21:48
*** harlowja has quit IRC21:48
bjoloedit inventory file and specify one node for controller, one for network and one for compute21:49
v1k0d3ni just noticed something......21:49
v1k0d3nnever mind...can't be in use.21:50
v1k0d3nbut when i make changes and then pip install....i have my git kolla repo in /opt/kolla, but realized that what mark-casey sent works which uses an inventory file of /usr/local/share/kolla/ansible/inventory/multinode and not /opt/kolla....21:51
v1k0d3nthe two are throwing me off...now i'm wondering if there are two globals or someting too?21:51
*** jascott1_tmp has quit IRC21:52
bjolochannel please correct me if im wrong, but default location it looks in should be /etc/kolla21:53
bjoloin my /etc/kolla i have globals.conf passwords.yml and kolla-build.conf21:53
bjoloi have also copied the default inventory file /etc/kolla21:54
bjoloso when i run anything, i do: kolla-ansible -i /etc/kolla/multinode deploy21:54
bjoloyou only do the pip install once on the master node21:55
v1k0d3nis the globals config correct? when i limited to three nodes it started complaining about ceph now...21:56
bjolodisable ceph as well21:56
v1k0d3nthis is starting to get strange.21:56
bjolonot needed for basic deploy21:56
v1k0d3nso most of the stuff below isn't required right? ironic etc...?21:56
bjolono21:57
openstackgerritDavid Wang proposed openstack/kolla-kubernetes: Add resource status command for Workflow Engine  https://review.openstack.org/34510221:57
*** banix has quit IRC21:57
bjolov1k0d3n, the globals.conf you pasted has all you need. Just disable TLS in that one21:59
*** jascott1_tmp has joined #openstack-kolla21:59
v1k0d3nok22:01
v1k0d3nthanks22:01
v1k0d3nrunning again. simple...one compute, one network, one controller. easy.22:02
v1k0d3nno TLS22:02
v1k0d3ngoing to be frustrated if this works and don't understand why wouldn't work with multi :(22:02
bjoloyou are still runing multi22:03
v1k0d3nso true. sorry...with all i mean.22:03
bjoloit will still deploy haproxy etc, but only one of each type22:03
v1k0d3nthink i may still get hung up on the mariadb issue.22:03
bjolobut here is the cool thing with kolla22:03
bjoloif this works22:03
bjolothen you can edit your inventory file and add one more controller etc22:04
bjoloand run the deploy again22:04
v1k0d3nyeah, so i think this is back to where i was at one point with mariadb...22:05
v1k0d3nthink it's going to fail at: Waiting for MariaDB service to be ready through VIP22:05
v1k0d3nwhere mysql command should be issued to the container.22:05
v1k0d3ni think this container may be faulty during build.22:05
v1k0d3nand 2.0.1 is known to be good?22:06
bjoloyes, centos binary worked for me22:06
v1k0d3ni know for sure 2.0.0 works...wrote a blog about that. and i seem to recall the container being built at one point via 2.0.122:06
v1k0d3nah, you're using centos binaries. i was using ubuntu source.22:07
bjoloi was. now i run centos source22:07
v1k0d3nand centos source containers work well for you?22:07
bjoloso far...im also pretty much starting out and just testing things22:08
*** salv-orlando has joined #openstack-kolla22:08
v1k0d3ni wonder if there some cruft from running a previous registry on the same build host...does removing a registry container also blow away the storage it was using previously?22:08
*** tyrola has quit IRC22:09
*** jascott1_tmp has quit IRC22:10
bjoloif you do a docker rm registry i believe so22:11
bjolodocker inspect registry22:11
*** salv-orl_ has joined #openstack-kolla22:14
bjolobut bump up your openstack_version in kolla-build.conf and globals.conf and do a new build22:17
*** salv-orlando has quit IRC22:17
bjoloi.e. change from 2.0.1.1 to 2.0.1.222:18
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Adds ansible support to deploy skydns service  https://review.openstack.org/33567722:19
*** sdake_ has quit IRC22:24
*** tyrola has joined #openstack-kolla22:25
*** tyrola has quit IRC22:27
v1k0d3nso that just tells kolla what to build and fetch from the repository?22:32
bjolona it is just a version number22:33
bjolofurther down in kolla-build.conf it actually specifies what sources to fetch22:33
*** jascott1_tmp has joined #openstack-kolla22:34
bjolosearch for "location"22:34
bjolokolla hardcodes a specific version for each project22:35
v1k0d3ngetting worried...hanging again at the mariadb command again, and this is with a centos source deployment.22:35
v1k0d3ni don't think it's going to work again...wait and see though.22:36
bjoloin my kolla-build.conf i have changed most of them to <project>-stable-mitaka.tar.gz22:36
*** gfidente|afk has quit IRC22:38
*** salv-orl_ has quit IRC22:41
*** salv-orlando has joined #openstack-kolla22:43
*** lyncos has quit IRC22:43
v1k0d3nyeah, so failed...same spot22:44
bjologeee whats going on22:44
bjololets take this from the top22:44
bjoloon your deployer node, what version of ansible and docker is installed22:45
v1k0d3none sec. let me load something on git. gonna be around for another 15-20 minutes. this will answer a lot of questions.22:45
bjolomaybe... im in sweden so its alrady 1AM here22:47
v1k0d3noh damn22:48
v1k0d3nwell, you'll be around here tomorrow?22:48
v1k0d3n1am...haha...that's like my sort of night!22:48
bjolodo your thing, if im still here i help22:48
*** salv-orlando has quit IRC22:48
*** sdake has joined #openstack-kolla22:49
v1k0d3nwell, let me just answer the questions...22:49
v1k0d3nhad issues with ansible 2.2, then 2.1. then noticed 2.0 tried that...nope...1.9.422:49
v1k0d3nso i'm on 1.9.4 right now22:49
v1k0d3ni have started building a repo that builds out hosts from scratch, loads prerequisites for kolla, and deploys the project. have drifted from that for troubleshooting obviously, but would want to eventually pin the right versions of packages once i figure out what is causing this issue.22:50
v1k0d3nin an AIO, it just worked. my blog http://www.jinkit.com/openstack-dockerized/22:51
v1k0d3nneeded to clean it up, and i want to have a repo i can refer to and just say "here...load, run, run kolla...done".22:51
v1k0d3none thing that has drifted...i didn't do the wily kernel upgrade because i noticed the kernel is already 4.2 on these hosts.22:52
*** banix has joined #openstack-kolla22:52
*** jascott1_tmp has quit IRC23:12
*** daneyon has joined #openstack-kolla23:18
*** daneyon has quit IRC23:23
*** chopmann has joined #openstack-kolla23:25
*** tyrola has joined #openstack-kolla23:39
*** tyrola has quit IRC23:43
*** jascott1_tmp has joined #openstack-kolla23:54
*** aernhart_ has quit IRC23:57

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!