Thursday, 2015-08-06

*** jtriley has joined #kolla00:11
*** diogogmt has joined #kolla00:18
*** weiyu_ has joined #kolla00:20
*** shadower has quit IRC00:23
*** shadower has joined #kolla00:23
*** dolpher has joined #kolla00:25
*** weiyu_ has quit IRC00:25
*** weiyu has joined #kolla00:27
*** bmace has quit IRC00:39
*** weiyu has quit IRC00:46
*** bmace has joined #kolla00:53
*** jasonsb has joined #kolla01:01
openstackgerritSam Yaple proposed stackforge/kolla: Update Ansible docs to remove requirements  https://review.openstack.org/20971601:04
*** jasonsb has quit IRC01:04
*** jasonsb_ has joined #kolla01:04
*** echoingu_ has quit IRC01:06
*** dolpher1 has joined #kolla01:11
*** dolpher has quit IRC01:13
*** weiyu has joined #kolla01:15
*** dims_ has joined #kolla01:21
*** erkules_ has joined #kolla01:22
*** dims has quit IRC01:22
*** erkules has quit IRC01:24
*** sdake has joined #kolla01:27
*** sdake_ has joined #kolla01:30
openstackgerritSam Yaple proposed stackforge/kolla: Reduce dependencies on the dest nodes  https://review.openstack.org/20845101:32
*** sdake has quit IRC01:34
*** SourabhP has quit IRC01:39
*** echoingumesh has joined #kolla01:41
openstackgerritSam Yaple proposed stackforge/kolla: Updated some requirements about docker  https://review.openstack.org/20972201:43
*** unicell has quit IRC01:52
*** unicell has joined #kolla01:53
sdake_  samyaple did you see tripelo's plans01:55
sdake_pretty cool going to use puppet to configure kola containers using tripleo ;-)01:56
sdake_It hink using exclusvey config-external01:56
sdake_so we can possibly just drop config-internal entirely01:57
SamYaplesdake_: yea thats awesome01:57
SamYaplei say Slower and ryan talking about it in the channel a few weeks ago01:58
*** unicell has quit IRC01:58
SamYaplelooking forward to helping with that if possible01:58
SamYaplenot a big puppet guy though01:58
SamYaplesdake_: the containerized deps is ready to test01:58
*** achanda has joined #kolla02:00
*** dims has joined #kolla02:03
sdake_cool02:05
sdake_dinner time bbl02:05
*** dims_ has quit IRC02:05
*** dims_ has joined #kolla02:06
*** dims has quit IRC02:09
*** sdake_ has quit IRC02:09
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Add ansible support for Cinder  https://review.openstack.org/20886802:17
*** zhiwei has joined #kolla02:17
*** unicell has joined #kolla02:18
*** echoingumesh has quit IRC02:19
*** jtriley has quit IRC02:19
*** echoingumesh has joined #kolla02:20
*** unicell1 has joined #kolla02:22
*** dims_ has quit IRC02:22
*** unicell has quit IRC02:22
*** diogogmt has quit IRC02:22
*** echoingumesh has quit IRC02:24
*** achanda has quit IRC03:44
*** coolsvap|away is now known as coolsvap03:58
*** jasonsb_ has quit IRC04:01
*** jasonsb has joined #kolla04:03
*** weiyu has quit IRC04:24
*** achanda has joined #kolla04:50
*** achanda has quit IRC05:25
*** weiyu_ has joined #kolla05:28
*** achanda has joined #kolla05:31
*** SourabhP has joined #kolla05:50
*** dims has joined #kolla06:03
*** dims has quit IRC06:09
*** zhiwei has quit IRC07:03
*** juggler_ has joined #kolla07:14
*** juggler has quit IRC07:17
*** zhiwei has joined #kolla07:33
*** pbourke has quit IRC07:33
*** pbourke has joined #kolla07:33
*** jmccarthy has quit IRC07:36
*** jmccarthy has joined #kolla07:36
*** SourabhP has quit IRC07:47
*** sdake has joined #kolla07:54
sdakeevening folks07:54
*** weiyu_ has quit IRC07:58
*** weiyu_ has joined #kolla08:04
*** tfukushima has joined #kolla08:12
*** achanda has quit IRC08:14
*** tfukushima has quit IRC08:15
*** tfukushima has joined #kolla08:17
*** achanda has joined #kolla08:18
*** tfukushima has quit IRC08:22
*** athomas has joined #kolla08:26
*** achanda has quit IRC08:29
*** weiyu_ has quit IRC08:39
*** achanda has joined #kolla08:40
*** weiyu_ has joined #kolla08:43
*** achanda has quit IRC08:51
*** athomas has quit IRC09:08
*** inc0 has joined #kolla09:13
inc0good morning09:15
*** inc0 has quit IRC09:21
*** inc0 has joined #kolla09:21
*** athomas has joined #kolla09:26
*** inc0 has quit IRC09:27
*** inc0_ has joined #kolla09:27
openstackgerritweiyu proposed stackforge/kolla: Ceilometer config-ceilometer.sh file without backslash  https://review.openstack.org/20947309:30
*** inc0_ has quit IRC09:32
*** inc0 has joined #kolla09:38
coolsvappbourke, around09:49
*** dims has joined #kolla09:49
pbourkecoolsvap: hi09:49
coolsvappbourke, do you have steps to get the ansible env running, i am not able to run it from yesterday09:49
coolsvapi think its some config issue09:50
pbourkecoolsvap: im using harmw's vagrantfile env09:50
pbourkeworks very nicely09:50
*** gfidente has joined #kolla09:50
coolsvaplet me set it up09:57
*** inc0 has quit IRC10:00
*** dolpher1 has quit IRC10:01
*** inc0 has joined #kolla10:04
coolsvappbourke, i think similar issue will be there in https://review.openstack.org/#/c/205528/15/ansible/roles/heat/tasks/config.yml like you said for cinder10:07
pbourkelooks like it10:08
coolsvapi am not able to install hostmanager plugin for vagrant10:10
*** inc0 has quit IRC10:11
*** Haomeng has quit IRC10:19
*** Haomeng has joined #kolla10:19
*** weiyu_ has quit IRC10:28
*** weiyu_ has joined #kolla10:28
*** tfukushima has joined #kolla10:29
*** weiyu_ has quit IRC10:37
*** weiyu_ has joined #kolla10:44
*** inc0 has joined #kolla10:44
inc0hello10:44
*** zhiwei has quit IRC10:45
inc0anyone ran kolla with kilo openstack?10:45
pbourkeinc0: parts of it10:47
inc0pbourke, do you have dockerfiles with kilo maybe?10:50
inc0this should be as simple as changing repos, but never know10:50
pbourkeinc0: we just have buildconfs to pin to the 2015.1.0 tag10:50
inc0also, it will be Oracle linux right?10:50
inc0aaa...source install10:50
inc0even better10:50
pbourkeyup :)10:51
inc0I'll play with that, thanks:)10:51
*** dims_ has joined #kolla10:51
pbourkeinc0: added a reply on https://review.openstack.org/#/c/209430/10:53
*** dims has quit IRC10:53
pbourkedoes it make sense?10:53
inc0yeah, could you remove this file in separate patch tho? Or I can do it10:54
inc0anyway, I'll +1 this one10:56
pbourkeinc0: the patch is still needed though afaik10:56
pbourkeas it hasn't been merged in upstream horizon yet10:56
inc0I think its fix released status, so it was merged10:57
inc0but I'll check10:57
coolsvappbourke, are you using virtualbox with vagrant?11:00
pbourkecoolsvap: yes11:00
coolsvaphmm alright, i might need to tweak the vagrantfile a bit11:01
*** sdake has quit IRC11:07
pbourkehas anyone come across this problem with the horizon dashboard https://i.imgur.com/KcDSzRv.png11:10
pbourkecan't click anything, styling seems to be messed up11:10
pbourkeok found it, collectstatic is not being run11:19
*** rhallisey has joined #kolla11:21
*** rhallisey has quit IRC11:27
*** rhallisey has joined #kolla11:27
*** jtriley has joined #kolla11:29
*** jtriley has quit IRC11:33
inc0anyone had any problems with neutron l3 agent? it doesn't seem to add record to db11:48
inc0and server breaks11:48
rhalliseywhat's the error inc0 ?11:48
inc0neutron-l3-agent is running, but table neutron/agents is empty11:48
rhalliseycause I'm seeing something similar with cinder11:49
inc0and neutron-server breaks with "no l3 agent found"11:49
rhallisey ERROR cinder DBConnectionError: (OperationalError) (2002, "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)") None None11:49
inc0problem is, it looks like it connects to db11:49
rhalliseyya it's weird cause cinder creates user and stuff but says in never connects11:50
*** diogogmt has joined #kolla11:54
*** weiyu_ has quit IRC11:58
openstackgerritPaul Bourke proposed stackforge/kolla: Fix missing config in horizon source image  https://review.openstack.org/20941512:01
openstackgerritPaul Bourke proposed stackforge/kolla: Add horizon source for oraclelinux  https://review.openstack.org/20943012:03
openstackgerritPaul Bourke proposed stackforge/kolla: Add horizon source for oraclelinux  https://review.openstack.org/20943012:03
*** weiyu_ has joined #kolla12:06
*** jtriley has joined #kolla12:08
openstackgerritPaul Bourke proposed stackforge/kolla: Implement Murano source images  https://review.openstack.org/20990512:10
openstackgerritPaul Bourke proposed stackforge/kolla: Implement Murano source images  https://review.openstack.org/20990512:12
*** unicell has joined #kolla12:20
*** unicell1 has quit IRC12:21
*** weiyu_ has quit IRC12:23
*** dims has joined #kolla12:24
*** Haomeng|2 has joined #kolla12:25
*** weiyu has joined #kolla12:26
*** dims_ has quit IRC12:27
inc0SamYaple, ping12:27
*** weiyu has quit IRC12:27
SamYaplepong12:27
inc0did you have any problems with neutron setup on multinode?12:27
SamYapledefine problem12:27
inc0it dies without traceback, and only error I see is AgentsNotFound12:28
SamYapleyea its been doing that for the past few days12:28
inc0L3 agent is running but it never added anything to DB12:28
SamYaplesomething upstream changed12:28
*** Haomeng has quit IRC12:28
inc0meh12:28
inc0I hate this project12:29
rhalliseylols12:29
SamYaplei hate the binary deploy12:29
inc0been debugging this for last 4 hrs12:29
SamYaplei want the source to work but dont have time12:29
SamYaplefrom source would be so much more stable to test against12:29
inc0yeah, kilo12:30
inc0do they even have CI?12:30
*** diogogmt has quit IRC12:31
*** weiyu has joined #kolla12:36
SamYaplewe are the CI12:37
SamYaple!12:37
rhalliseyya haha12:37
*** dwalsh has joined #kolla12:44
*** jtriley has quit IRC12:46
*** vbel has joined #kolla12:59
vbelGood morning / evening everyone12:59
SamYaplemorning vbel12:59
vbelhttps://bugs.launchpad.net/kolla/+bug/1482214   I wonder if anyone could run keystone recently13:00
openstackLaunchpad bug 1482214 in kolla "ansible does not run bootstrap for keystone" [Undecided,New]13:00
vbelquite annoying because it should actually work - run_once is ignored as other flags13:00
vbelansible-playbook 1.9.213:01
SamYaplevbel: i have no problem running keystone13:01
vbelI have also found 'detach' does not work as13:01
SamYaplelet me doublecheck what its doing13:01
SamYaplevbel: there is a bug about detach13:02
SamYaplecheck bootstrap.yml13:02
SamYapleit should have a link13:02
vbelok, so we use docker wait instead13:02
*** athomas has quit IRC13:02
SamYapleyea docker module bug upstream13:02
SamYapleits been fixed13:02
vbelbootstrap.yml:13:03
vbel 23 - debug: msg="starting bootstrap container"13:03
vbel 24   run_once: True13:03
vbel 2513:03
vbel 26 - include: start.yml13:03
vbel 27   vars:13:03
vbel 28     run_me_once: True13:03
vbel 29   when: database|changed13:03
SamYaplevbel: "run_me_once" ?13:03
vbelit runs on all hosts and without bootstrapping flags - therefore no tables are inside of keystone13:03
vbelsorry, run_once, I am hacking a bit :)13:03
SamYapleoh13:04
SamYaple:/13:04
vbelwondered if keywords should not be vars13:04
SamYaplewell it works in the repo as ive just tested13:04
SamYapleyou can post your hacked playbooks but i make no promises13:04
vbelI used kolla latest13:04
vbelno modifications13:05
SamYaplerun_me_once isn't in the playbooks13:05
vbel- name: Creating database    runs on first node13:05
vbel- name: Creating database user and setting permissions   runs on first node13:06
vbelbut the above runs everywhere13:06
*** athomas has joined #kolla13:06
vbelsomething to do with multilevel includes?13:07
vbelTASK: [keystone | Copying over config(s)] *************************************13:08
vbelok: [ndb01]13:08
vbelok: [ndb02]13:08
vbelTASK: [keystone | Creating database] ******************************************13:08
vbelchanged: [ndb01]13:08
vbelTASK: [keystone | Creating database user and setting permissions] *************13:08
vbelchanged: [ndb01]13:08
vbelTASK: [keystone | Starting container(s)] **************************************13:08
vbelchanged: [ndb02]13:08
vbelchanged: [ndb01]13:08
vbelTASK: [keystone | Starting PID container(s)] **********************************13:08
SamYaplepastebin please13:08
vbelskipping: [ndb01]13:08
vbelskipping: [ndb02]13:08
vbel1 sec13:08
vbelyep13:08
vbelhttp://paste.openstack.org/show/411166/13:11
SamYaplewhich version of ansible13:12
vbel^ with clean checkout. ansible-playbook 1.9.213:12
vbelyou see that creating db and user does run once, but bootstrap run on both hosts. And more - the containers don't run bootstrapping (no db tables created)13:14
vbelthe same with -vvvvvv (after user/db cleanup): http://paste.openstack.org/show/411170/13:17
SamYapleyea i see the same thing, with mine bootstraping works, but i see it start on both nodes13:17
vbelI will try to debug this locally, with run_me_really_once :)13:19
*** jpeeler has quit IRC13:20
SamYaplevbel: can you file a bug?13:20
vbelyes -  https://bugs.launchpad.net/kolla/+bug/148221413:21
openstackLaunchpad bug 1482214 in kolla "ansible does not run bootstrap for keystone" [Undecided,New]13:21
SamYaplethanks13:21
*** thumpba has joined #kolla13:23
inc0also, it seems that nova bootstrap runs on compute nodes as well13:25
inc0isn't it?13:25
SamYapleits probably like that for everything inc013:26
SamYaplethis isn;t related to only keystone im sure13:26
*** thumpba_ has joined #kolla13:26
inc0it is, but I don't think that's good for this case, and no, not related to keystone13:26
inc0just random useless comment, you should get used to these after spending that much time in my presence13:26
SamYaplewell vbel i was going to remove this start.yml abstraction anyway. now is as good a time as any13:28
vbelthanks Sam, I will check if any workarounds are possible in the meantime13:29
*** thumpba has quit IRC13:30
SamYaplecool13:30
SamYapleyoure probably right about the calling multiple includes13:30
*** thumpba_ has quit IRC13:30
SamYaplewe could change this with pre/post tasks, but ive been trying to keep those out of the playbooks so they remain simple for people to read13:30
*** jpeeler has joined #kolla13:33
*** thumpba has joined #kolla13:36
*** jtriley has joined #kolla13:41
vbelInteresting, even if I remove run_once from start.yml and add it like below it still does not run once13:47
vbel 23 - include: start.yml13:47
vbel 24   run_once: True13:47
vbel 25   when: database|changed13:47
SamYapleyou cant run_once on includes13:49
vbelI see13:50
*** jtriley_ has joined #kolla13:55
*** sdake has joined #kolla13:55
sdakemorning13:57
*** jtriley has quit IRC13:57
SamYaplemorning sdake13:57
*** jtriley_ has quit IRC13:59
sdakehey sam14:00
coolsvapmorning14:02
sdakehey cool14:02
openstackgerritSam Yaple proposed stackforge/kolla: Updated some requirements about docker  https://review.openstack.org/20972214:04
SamYaplesdake: https://review.openstack.org/#/c/208451/14:04
SamYapleits ready to try14:04
vbelSamYaple: it is not only run_once, also when is ignored:14:09
vbel 23 - include: start.yml14:09
vbel 24   vars:14:09
vbel 25     run_once: True14:09
vbel 26   when: inventory_hostname == "xyz"14:09
coolsvapharmw, around?14:09
SamYaplevbel: no when works fine14:09
SamYapletheres probably something else going on there14:10
SamYaplei mean when works fine with includes in geeneral14:10
SamYapleit may be broken there14:10
vbelSamYaple: yes, ignore the sample above14:12
*** sdake has quit IRC14:14
SamYapleoh jeez14:14
SamYaplein openstack-meeting-4 they are tlaking abou splitting out glance into microservices14:14
SamYaple:/14:14
rhalliseyoh rlly14:19
*** Ti-mo- has quit IRC14:23
*** Ti-mo has joined #kolla14:24
*** dims has quit IRC14:25
*** dims has joined #kolla14:26
*** weiyu has quit IRC14:33
*** jtriley has joined #kolla14:36
*** diogogmt has joined #kolla14:38
*** weiyu has joined #kolla14:38
*** weiyu has quit IRC14:41
*** rhallisey has quit IRC14:42
SamYaplewell you know they just split out glance_store as a seperate library14:50
*** banix has joined #kolla14:55
*** achanda has joined #kolla14:59
*** inc0 has quit IRC15:06
*** achanda has quit IRC15:09
openstackgerritPaul Bourke proposed stackforge/kolla: Add a data vol image for the arista Neutron plugin  https://review.openstack.org/20754515:11
*** jtriley has quit IRC15:11
pbourkeanyone using horizon lately?15:12
pbourkehttps://bugs.launchpad.net/kolla/+bug/148219615:12
openstackLaunchpad bug 1482196 in kolla "Horizon dashboard not loading properly, can't click on anything" [Undecided,New]15:12
pbourkeif anyone knows even what horizon.auth is or does it would help15:13
SamYaplesounds like it provied auth for horizon15:14
* SamYaple is being helpful15:14
*** jtriley has joined #kolla15:15
pbourkeah, it was so simple!15:15
*** kevsi has joined #kolla15:16
*** diogogmt has quit IRC15:16
*** diogogmt has joined #kolla15:17
*** rhallisey has joined #kolla15:18
vbelSamYaple: http://paste.openstack.org/show/411194/  - this use case show that var is known but does not go into final run_once15:19
SamYapleyea vbel i think its because we are already running on an included playbook15:20
*** blahRus has joined #kolla15:24
vbelSamYaple: you know what is my workaround? put 'run_once: True' in service related bootstrap.yml :)15:26
vbelSamYaple: wait a sec, retry15:27
vbelSamYaple: sorry, wrong test15:31
*** sdake has joined #kolla15:31
*** daneyon has quit IRC15:32
*** daneyon has joined #kolla15:33
*** dwalsh has quit IRC15:33
SamYaplethe start.yml is going to continue to be a problem15:34
SamYaplei dont see any choice but to do it "right" and duplicate that docker module block15:34
SamYapleother than the duplicate code, is there any objections?15:34
SamYaplepbourke vbel ^15:35
vbelnope15:35
pbourkei haven't been following this issue closely enough15:35
SamYaplepbourke: just in geeneral15:35
SamYapleremove the abstraction layer around start.yml15:35
SamYaplebasically call the docker module without having the start.yml include15:35
vbelso at least we can have "starting keystone" instead of double "starting container(s)"15:36
SamYapleyea15:36
SamYaplethat i hated15:36
vbel+215:36
SamYaplei mean this was always the way it had to go, but i couldnt think of an easy way to abstract15:36
SamYapleim going to hit up #ansible for a minute to ask15:37
vbelyou can reference that paste from me15:37
pbourkeim looking at start.yml and can't see the difference between the two blocks15:37
vbelwith host pid and without15:37
vbel?15:38
SamYaplepbourke: dont worry about that15:38
SamYaplei just mean in geeneral15:38
SamYaplewe are doing wierd ansible things there15:38
sdakei really dislike the "starting container" skipoped thing15:38
pbourkelet me read the bug and scroll back15:39
SamYapleso we are agreeing to duplicate teh docker block?15:39
sdakei'm not familiar with the dockerblock in question15:39
pbourkeI understand about 25% of what you guys are talking about :p15:39
vbelsince we duplicate it anyway by passing quite some parameters15:39
SamYapleyea a little bit15:39
sdakeare you talking about container start duplicatd twice?15:40
SamYaplesdake: kinda, inderectly15:40
sdakethe reaosn is to get pid=host - unfortunately that is necessary15:40
SamYaplebasically instead of calling ../../start.yml im just going to switch it to the dockre module directly15:40
sdakeanother way to do it is specify container_pid in every module15:41
SamYapleso we duplicate 10 params each time15:41
sdakeright15:42
sdakeits pretty terrible, the biggest problem with it is it starts every container twice15:42
sdakeor says starting container skipped rather15:43
vbelif it is pid: "host" then we could combine blocks with   pid: "{{ 'host' if container_pid  else '' }}"15:49
pbourkevbel: can you explain the purpose of the two blocks in start.yml15:51
pbourkeim not seeing it15:51
*** dwalsh has joined #kolla15:52
vbelI think it is to run one if variable container_pid is set or run another if the variable is not set. Both differ in pid: 'host'15:52
pbourkeah yeah its for libvirt15:53
pbourkeand the two "starting containers" is one for bootstrap and one for the main container right?15:53
vbelI would try to combine it with      pid: "{{ 'host' if container_pid  else '' }}"15:54
vbelno, they run both but one is skipped :)15:54
pbourkeI see15:55
pbourkehow will moving this block into each role fix the issue15:55
SamYaplevbel: the issue is in the docker module15:56
SamYapleit doesnt accept '' as valid15:56
vbelif we provide pid: "{{ 'host' if container_pid  else var_that_is_None }}"15:59
vbelit is None by default, wonder how to tell ansible it15:59
pbourketrying to find the source for the ansible module16:04
pbourketry null?16:07
pbourkehttps://groups.google.com/forum/#!topic/ansible-project/pfaxQNPpst416:07
vbelanyway it does not help with run_once16:10
*** echoingumesh has joined #kolla16:13
*** sdake has quit IRC16:14
pbourkevbel: do we know why its ignoring run_once16:15
SamYaplevbel: you cant16:16
SamYapleansible wont eval it as a bool16:16
SamYapleor none16:16
SamYapleyou have to set it to None in the module16:16
SamYapleits fixed upstream16:16
SamYapleill just do the work or duplicating the docker module16:17
SamYaplethere really is no better solution16:17
SamYapleat least taht i can think of i mean16:17
*** SourabhP has joined #kolla16:18
*** unicell has quit IRC16:18
*** unicell has joined #kolla16:19
*** unicell has quit IRC16:20
vbelI have submitted a bug https://github.com/ansible/ansible/issues/11876  for run_once16:20
openstackgerritMerged stackforge/kolla: Update the documentation for Ansible  https://review.openstack.org/20947416:22
*** dwalsh has quit IRC16:22
harmwcoolsvap: you have 1 minute :)16:22
*** SourabhP_ has joined #kolla16:22
vbelI would put 'starting non-PID containters' and 'starting PID containers' to avoid further questions when running this double block :)16:23
SamYaplevbel: im ust removing all of that16:23
*** SourabhP has quit IRC16:24
*** SourabhP_ is now known as SourabhP16:24
vbelok16:24
*** dwalsh has joined #kolla16:24
*** echoingumesh has quit IRC16:25
SamYaplethe code would be alot cleaner if i removed the ability to specify a private registry per service, but rather do it on a global scale16:25
SamYaplewill anyone actually do that you think?16:25
SamYapleeh ill not be lazy and keep it16:27
pbourkeI can't ever see it being used16:27
openstackgerritRyan Hallisey proposed stackforge/kolla: Change build.py to match the release  https://review.openstack.org/21001516:27
vbelper service? yes, we had such use case, e.g. running some kollaglue containers with ours if something did not work :) But such hacks can be done locally anyway, so I would clean up too16:30
*** SourabhP has quit IRC16:30
SamYapleyou think? so youre saying if someone _really_ wants to do it they should tweak the playbooks?16:30
vbelyes16:31
SamYaplefair enough16:31
vbelthey would be 'developers'16:31
SamYaplei was thinking, business uses the kollaclue containers _except_ for the keystone contaienr where they do something different16:31
SamYaplebut i suppose at that point they should probably role thier own everything16:31
SamYapleroll*16:31
rhalliseySamYaple, would you say master==latest16:35
rhalliseyI'll just tag back to latest and move ansible to latest16:35
SamYapleyes, but having a latest tag is a bad thing for our project16:35
SamYaplewe discussed this a bit at the midcycle and everyone agreed latest caused confusion16:35
rhalliseywell technically when you're building locally it is latest16:35
SamYapleand was mostly broken16:35
rhalliseywell pushing latest16:36
SamYapleright, but the people who git clone will end up pulling from a broken image16:36
rhalliseyI say we just don't push the latest tag16:36
rhalliseygiven that discussion16:36
SamYapleif we untag latest in dockerhub im ok with that decision16:36
rhallisey'latest' would be defined as you just built it16:37
SamYapleagreed16:37
rhalliseypulls will be the 'latest' release16:37
rhalliseybut not tagged as latest16:37
rhalliseyok16:37
*** dwalsh has quit IRC16:37
SamYapleright i would think we would have a "liberty" tag that would be the latest liberty tested image16:37
SamYaplesame for the other branches16:38
rhalliseykk16:38
rhalliseywell the problem with defaulting ansible to latest is then it won't work outa the box16:41
rhalliseyehh..16:41
SamYapleit will on a tagged release16:41
rhalliseymay just need a doc16:41
SamYapleit _cant_ work out of the box for master16:41
SamYaplebut a tagged release will be fine16:42
SamYapleand so will stable branches16:42
rhalliseyok I'll leave it as is then16:42
SamYapleno it should be changed to latest again16:42
SamYaplethe liberty2 iamges cant work with teh master playbooks16:42
rhalliseyya that's true16:42
SamYaplebut you switch to the liberty2 tag and itll be fine16:42
SamYapletagged git == tagged specifed16:43
SamYaplemaster git == latest tag16:43
SamYapleso we switch the tags, release, then switch back16:43
*** unicell has joined #kolla16:43
rhalliseykk makes sense16:43
SamYaplestable will alway be pointed at a stable tag16:43
SamYaplealways*16:43
openstackgerritRyan Hallisey proposed stackforge/kolla: Change ansible to search for latest tag  https://review.openstack.org/21001516:45
SamYapleeh for readability and expected results lets just get rid of this abstractedness for the playbooks16:45
SamYaplei hate violating dry but idk16:46
SamYapleoverall i think it will just be a blemish on the playbooks to do the abstraction. everyone else just deals with the DRY violation and thats ansible "best practice"16:47
SamYapleI tried to do something here and i dont think its working out well. ill just do it the long way16:48
rhalliseySamYaple, don't understand your comment16:49
SamYaplerhallisey: just revert the commit that changed the tag in the first place16:49
SamYaplei also updated all the compose file tags as well16:50
SamYaplejust do `git revert f4d6fc6193b0d0a981433ad849c614130a13041a`16:50
SamYaplehttps://github.com/stackforge/kolla/commit/f4d6fc6193b0d0a981433ad849c614130a13041a16:50
rhalliseyoh16:51
openstackgerritRyan Hallisey proposed stackforge/kolla: Revert "Merge "Updated all tags for Liberty2""  https://review.openstack.org/21002716:57
rhalliseyok that patch will revert it16:58
openstackgerritSam Yaple proposed stackforge/kolla: Removed bootstrap.yml and start.yml abstraction  https://review.openstack.org/21004117:16
SamYaplepbourke: vbel rhallisey https://review.openstack.org/#/c/210041/17:17
SamYaplethats just for keystone, if everyone is ok with that change i will roll it out everywhere17:17
rhalliseyinteresting17:18
SamYapleI was just trying to avoid specifying those 10 docker options over and over again, but it is what it is17:19
SamYaplei mean they are variabled out, so the enduser won't have to specify it 30 times17:19
rhalliseysam can you review again https://review.openstack.org/#/c/210015/17:21
SamYaplewasnt that covered in the revert?17:22
SamYapleoh i suppose not17:22
*** achanda has joined #kolla17:30
*** sdake has joined #kolla17:33
*** tfukushima has quit IRC17:36
*** tfukushima has joined #kolla17:37
*** tfukushima has quit IRC17:39
rhalliseyjpeeler, can you ack https://review.openstack.org/#/c/210015/17:41
rhallisey1 lane change super easy17:41
jpeelerdone17:43
rhalliseythx17:43
sdakemorning again guys17:50
*** thumpba has quit IRC17:54
rhalliseymorning17:56
*** thumpba has joined #kolla17:57
*** echoingumesh has joined #kolla17:58
*** Haomeng has joined #kolla18:00
*** Haomeng|2 has quit IRC18:03
*** tfukushima has joined #kolla18:04
openstackgerritMerged stackforge/kolla: Change ansible to search for latest tag  https://review.openstack.org/21001518:06
*** thumpba_ has joined #kolla18:14
openstackgerritMerged stackforge/kolla: Revert "Merge "Updated all tags for Liberty2""  https://review.openstack.org/21002718:15
*** dwalsh has joined #kolla18:16
*** thumpba has quit IRC18:17
SamYaplehey guys, im goign to bed18:18
SamYaplewould really appreciate reviews on https://review.openstack.org/#/c/208451/ and https://review.openstack.org/#/c/210041/18:18
*** daneyon has quit IRC18:20
*** daneyon has joined #kolla18:20
*** jasonsb has quit IRC18:40
*** jasonsb has joined #kolla18:40
*** jasonsb has quit IRC18:45
openstackgerritMerged stackforge/kolla: Reduce dependencies on the dest nodes  https://review.openstack.org/20845118:45
*** dwalsh has quit IRC18:55
*** tfukushima has quit IRC19:04
*** achanda has quit IRC19:05
*** diga has quit IRC19:05
*** achanda has joined #kolla19:05
*** diga has joined #kolla19:06
*** dwalsh has joined #kolla19:10
jpeeleraccording to this blog post: https://labs.ctl.io/docker-hub-top-10/ , we're fourth in rank for number of repos (really should be images i guess) on docker hub19:18
sdakerockin ;-)19:20
rhalliseycool19:21
sdakethats pretty funny actually :)19:21
*** jasonsb has joined #kolla19:22
harmwyou see... this is why we should've named our repo "sdakeshouseofpleasure"19:22
rhalliseylol19:22
bmacelol19:23
jpeelerdoes anybody know if we actually need a network node for multi-node deployment?19:32
jpeelerthis makes me think yes, but i still know nothing about ansible: https://github.com/stackforge/kolla/blob/master/ansible/inventory/multinode#L1319:32
sdakenetwork node no19:33
sdakeeach node networks (with openvswitch)19:34
sdakefor linuxbridgey ou may nee a network node19:34
*** thumpba_ has quit IRC19:34
sdakei'd justrecommend using openvswitch if you dont have a strong preference - then it should just work multinode correctly19:34
*** thumpba has joined #kolla19:35
jpeeleransible seems to query it19:39
jpeelerand i'm still getting this eth0 error from yesterday19:39
harmwlol, $job is featured as a AWS case study with some video interview19:40
harmwcool stuff19:41
*** jruano has joined #kolla19:41
harmwjpeeler: ansible is just able to assign one node with the networking bits (server), it's not required19:41
harmwafaik19:41
harmwsdake: something interesting came out of yesterday's meeting?19:42
jpeelerharmw: i'm actually using your vagrant setup - the intention is to execute ansible from the operator node, right?19:42
harmwyep, just ssh into the operator node and run ansible19:42
jpeeleri'm getting this strange error: fatal: [network01] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_eth0'", 'failed': True}19:43
harmwhehe19:43
harmwyou do need to edit the Ansible config :)19:43
harmwyou're running Fedora in the Vagrant vms19:43
harmwwhich is not booted with a parameter to setup oldskool interface naming, so it uses enp0s3 or something similar19:44
harmwand you should configure that in etc/kolla/defaults.yml or general.yml19:44
jpeeleri thought your setup also booted centos, but i definitely switched it to centos19:44
jpeelerso eth0 is there19:44
harmwoh ok19:44
harmwfair enough19:44
harmware you setting the interface name correctly?19:45
jpeelerin the networking options?19:46
harmwyea19:46
jpeelerthey seemed sane, i haven't changed them19:46
jpeelerharmw: what does the net interfaces look like for your operator node?19:48
*** thumpba has quit IRC19:48
harmwoperator node isn't interesting, it's the compute and support nodes your interested in19:48
harmwthats where all the fun happens :)19:48
jpeelerwell they are all configured the same i thought19:48
*** thumpba has joined #kolla19:48
harmwenp0s8 and enp0s9 is what I have, on all nodes19:48
harmwyep19:49
jpeeleri have eth0, eth1, and eth219:50
jpeelereth2 the private interface19:50
harmwenp0s3 is there aswell, so that makes 319:51
jpeelerand eth0 and eth1 connected to the bridge. does that sound right? i'm doing this using the libvirt provider, hence the difference19:51
harmweth0 should be hostonly, so 10.something19:51
harmweth1 will be the private network shared with all vagrant virtual machines19:52
harmwand eth2 should be bridged to the public network19:52
harmw(I'm using virtualbox btw)19:52
jpeelernetworking is not my forte19:53
jpeeleri have the private address on eth2, know that for sure19:53
harmwah19:53
*** thumpba has quit IRC19:53
jpeeleri think eth0 and eth1 are both bridged in the same way19:53
harmwlets see19:54
harmwwhich address is assigned to each one of those interfaces?19:54
jpeelerhttp://paste.fedoraproject.org/252420/43889085/19:54
jpeeleri did that on the operator node, but the others are similar19:54
harmweth0 and eth1 are connected to the same network?19:54
harmwand the address on eth2, where'd that come from?19:55
*** thumpba has joined #kolla19:55
harmwor rather, those, since there are 2 addresses :)19:55
jpeelerharmw: yeah, not sure why there are two addresses... but it was manually assigned as i couldn't find any libvirt equivalent to dhcp there19:56
*** thumpba has quit IRC19:56
jpeelerharmw: want to see the Vagrantfile or diff?19:56
*** thumpba has joined #kolla19:57
harmwhm19:57
harmwthe point of one of those 3 interfaces it doesn't need an IP, it's just a bridge to get out to the (your) public net on which you can plant your floating ips19:57
harmwso all vagrant nodes are using static ips?19:58
harmwvagrant ssh operator19:58
harmwthats how you'd get in to the operator node, it should be able to tell you on which IP it's connected19:58
harmwso that way you can find out which interface is the hostonly one19:59
jpeelervagrant ssh operator actually uses eth019:59
harmwcool19:59
jpeeler192.168.121.23219:59
jpeeleris that right?19:59
harmwsure, probably :)19:59
harmwmine is using a different range, but thats dhcp19:59
harmwand mostly Virtualbox magic19:59
jpeelerwell the 192.168.121.232 is dhcp libvirt stuff20:00
harmwexcellent20:00
harmwso eth0 is getting an IP from dhcp?20:00
jpeeleryes, along with eth1 too20:00
harmwok20:00
harmweth2 is probably your bridged interface, not needing an address20:01
*** jruano has quit IRC20:01
jpeelerit's assigned directly though20:01
harmwhm20:01
jpeelerif this helps, http://paste.fedoraproject.org/252422/91038143/20:01
jpeeleri tried to replicate what you did20:01
* jpeeler thought this would be a simple image replacement20:02
jpeelernot the case20:02
jpeelerdiff if that's helpful http://paste.fedoraproject.org/252423/88910581/20:02
*** dwalsh has quit IRC20:04
harmwyour not building those network nodes properly, that looks like it won't achieve what you are after20:04
harmwam I missing the networking stuff for networks 2 and 3?20:04
jpeeleri thought only one node was needed? i only created it because the ansible multihost ping reported it missing20:05
harmwdepends, it's currently looking for it since it's specified in multihost inventory20:06
harmwbut you could change that20:06
harmwanyway, I only see one network created20:06
harmwand it's public20:06
jpeeleri know i'm network stupid, but i'm not seeing the difference from what you did20:08
harmwnp20:08
harmwyou posted that diff20:09
harmwL3820:09
harmwsets up a network20:09
harmwright20:09
harmwand L32+33 disable two networks, right?20:09
jpeeleri disabled the virtual box way20:10
jpeeleri tried to replicate the private ip assignment in each node config20:10
jpeelerfor example, line 9220:10
harmwI saw that, but is that creating networks in the way we want them?20:11
jpeelerprobably not...20:11
harmwI don't know Vagrant that much :) (and prefer building such a thing upfront)20:11
harmwyou don't happen to have access to virtualbox do you :p20:11
*** achanda_ has joined #kolla20:12
*** achanda has quit IRC20:12
jpeelerwell i mean, i was hoping to get this to work on libvirt. it's the fedora way20:12
*** thumpba_ has joined #kolla20:12
harmwyea well, libvirt can't bridge on wireless so I sadly choose vbox :(20:12
harmwbut can't you duplicate L38(+) to create those other 2 networks there?20:13
jpeeleri think i could, would that work?20:14
harmwgive it a go, it'll atleast match the virtualbox stuff :)20:15
jpeelerok thanks for looking at it. it'd really rock to get this going20:16
*** thumpba has quit IRC20:16
harmwsure np, let me know if I can be of any more help :)20:18
sdakesamyaple you around?20:19
jpeelerbleh private_network seems to require ip assignment. might have to shelve this for now20:22
harmwjpeeler: not if you configure it as dhcp, as is currently done20:22
harmwwould that work?20:22
jpeeleri don't think the libvirt provider plugin supports that option20:22
sdakehey jpeeler you ar estuck on ansible eth0?20:23
jpeelerwhich is the problem20:23
jpeelersdake: yes, but it's probably related to my vagrant networking setup20:23
sdakeThe reason that error would occur is becasue eth0 is not your interface name on your control node20:23
sdakeok cool20:23
*** dims_ has joined #kolla20:23
harmwah, yes, that was what got this started in the first place :p20:23
jpeelerharmw: https://github.com/pradels/vagrant-libvirt#networks20:24
*** dims_ has quit IRC20:24
openstackgerritRyan Hallisey proposed stackforge/kolla: Glance api and Glace registy shoudn't share tags  https://review.openstack.org/21010920:24
openstackgerritRyan Hallisey proposed stackforge/kolla: Glance api and Glance registry shouldn't share tags  https://review.openstack.org/21010920:24
rhalliseylol that spelling20:24
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Gnocchi  https://review.openstack.org/20879520:25
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Swift  https://review.openstack.org/20878920:25
openstackgerritMerged stackforge/kolla: Adds push to build script  https://review.openstack.org/20826620:25
*** dims_ has joined #kolla20:25
*** dims has quit IRC20:26
*** echoingumesh has quit IRC20:27
*** echoingumesh has joined #kolla20:28
*** echoingumesh has quit IRC20:32
openstackgerritMerged stackforge/kolla: Updated some requirements about docker  https://review.openstack.org/20972220:37
harmwrhallisey: is there even a docker_glance_registry_tag set?20:37
rhalliseyya20:37
rhalliseythe line above it20:38
harmwoh yes20:38
harmwyep20:38
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Designate  https://review.openstack.org/20933620:38
harmwjust noticed20:38
harmwdamn :P20:38
openstackgerritMerged stackforge/kolla: Ceilometer config-ceilometer.sh file without backslash  https://review.openstack.org/20947320:38
rhalliseyharmw, no worries20:38
rhalliseyI though the same thing when I saw it20:38
rhalliseyI was like maybe it's suppose to be that way20:38
harmwit's not broken because both got the same value, oh well20:39
harmwnice catch :)20:39
sdakebmace you around20:39
rhalliseyharmw, ya it works.  Thanks :)20:39
harmwbtw, what's you guys' oppinion about curling stuff and piping to bash?20:40
harmwre my comment in https://review.openstack.org/20972220:40
harmwsrw-rw---- 1 root root 0  6 aug 20:14 /var/run/docker.sock20:41
harmwwtf20:41
harmwdocker should be doing root:docker per default20:41
sdakeharmw tb fair those are docker instructions for intalling their packages20:41
sdakebut what we should do in that document is link to the upstream docker install directions20:41
harmwI know they are sdake20:41
bmacesdake here20:41
sdakebmace i've been thinking about ha of the deploy node forabout 45 minutes20:41
harmwI'm more about the general trend to do that more, or so it feels20:42
sdakeI wanted to run my thoughts by you20:42
bmacesdake sure20:42
sdakeso basically to do ha we need one storage environment for the configuration files20:42
sdakeand then when ansible runs it would pull the configuration files from some central store20:43
sdakeso kolla ansible would basically be stateless except for the database or etcd or whatever20:43
bmacewell, that or replicate the config data, sure20:43
sdakeyes the config files must be replicated, but I dont think we want to do that directly in kolla20:43
sdakewe want kolla to read from some third party data storage tool the config20:44
sdakeand offer an opportnity to load new config stuff in20:44
sdakedoing replication correctly is very hard, although in kolla's case it could be versioned so it could be easy20:45
bmaceit would be nice to allow for the properties to be read in a variety of ways, sure.20:45
harmwjpeeler: is your dockerd running with proper permissions on the .sock?20:46
*** echoingumesh has joined #kolla20:46
jpeelerharmw: where?20:46
bmacethere are varied degrees of complexity of ha.  simple active / passive can also do very simple file replication / sync, though it does end up being sort of an odd thing for kolla to worry about directly.20:46
harmwoperator20:46
harmwI didn't check the others yet20:47
sdakei'm thinking the anible modules instead of reading files could read from a replicated data store20:47
bmacelots of environments may be using etcd or some other replicated store and it would be great to take advantage of that.20:47
jpeelerharmw: i actually destroyed everything hoping i could recreate with a new private network config, but i didn't see a way to change from what i had20:48
bmacecould what they read from be configurable?  then if you want simple files, have at it, if you have some other mechanism, you can always write your own sort of interface between that service and how we do the file reads?20:48
jpeelerharmw: you think docker would be related to the ansible error i was getting?20:48
harmwbmace: that sort of thing does drag in several dependencies though, like having a zookeeper+etcd or something similar containers20:48
harmw(not that I don't like the idea of a key-value store containers to Kolla btw)20:48
harmwjpeeler: nah, it was ansible complaining20:49
bmacethat is why i'm suggesting, especially for the ansible management nodes, leave it variable / at the distro or users discretion.20:49
harmwI wanted to launch vagrant myself, now running into this20:49
harmwbmace: yea, sounds like how we'd want to do that (for now though, haven't given it much thought yet)20:49
sdakei dont think we want zookeeper20:50
harmwjpeeler: but docker is running?20:50
sdakebut etcd is dependency free20:50
harmwjpeeler: forget that, I meant is it accessible with the vagrant accuont :)20:51
bmacejust because there is a lot of different technology in different environments i think it is odd for us to pick one.  if we want to have sort of pre-built code to handle etcd and just flat files, that is probably good, as long as it isn't too onerous for people to contribute code to use other technologies.20:51
sdakeso the way the file merging works today is it reads from the filesysstem20:51
sdakethis code is a python module20:51
jpeelerharmw: i do believe it was, but i'll have to redeploy to further debug. do you think the networking options need changing or no? i couldn't change the private network to not be assigned by IP20:53
sdakebmace: merge-configs https://github.com/stackforge/kolla/blob/master/ansible/library/merge_configs.py20:53
*** dwalsh has joined #kolla20:53
harmwjpeeler: weird, tthough it feels like it's mostly libvirt related...20:53
harmwis there no libvirt-specific doc on Vagrant?20:53
jpeelerthe github repo i linked earlier are the only docs i could find20:54
harmwah, yes, Ill look into that20:54
bmacesdake: yup, i have looked at that code before.  so it seems possible to support some other file read mechanism.  I don't know where ConfigParser comes from.  it takes the file path so that would need to handle something else, or before the ConfigParser takes it, we could pull it out of some other storage medium and dump it into a normal file.20:55
sdakewell hte merging onto the local disk is fine20:56
sdakeits the reading that needs to come from a remote storage environment20:56
bmacethe comments in there seem off?  isn't if this is the config to be pulled into the container the destination should be the /opt/kolla/blah (or i hear that is being possibly changed to /var/lib/kolla/blah)20:58
sdakethis file merges a bunch of config files from /etc into /opt/kolla20:59
sdakethe container then loads that /opt/kollaconfig/file.ini into the container21:00
sdakeso instead of merging a bunch of config files on hard disk it could do it from etc or db21:00
sdakei'm not sure if this module could be parameterized to different backends21:00
sdakebut get the concern about wanting to support something besides just etcd21:00
bmaceright, which is why the docs are a bit off, for our environment21:00
harmwjpeeler: can you verify if docker is accessible on lets say the operator node?21:01
bmacewell, it isn't this file that does the real read, the file path / name of the source files is passed to the ConfigParser, which is why i suggest either ConfigParser would need to change, or we would need to have something in the middle, before the ConfigParser code, that pulls down the data from the alternate data source and drops it into files, in /tmp for example, and cleans them up after21:01
*** jtriley has quit IRC21:02
sdakewell lets say its path/file like /etc/kolla/nova.conf21:02
sdakeif your data store is configured for etcd, the merge config would go read nova.conf rom /etc/kolla/nova.conf21:03
*** britthou_ has quit IRC21:05
bmacewhich wouldn't work terribly well, since it needs to talk to etcd to read the data? :)21:05
sdakesorry read from etcd://etc/kolla/nova.conf21:05
openstackgerritHarm Weites proposed stackforge/kolla: Start docker without -H to make chgrp work on socket  https://review.openstack.org/21012221:06
*** rhallisey has quit IRC21:06
harmw^ Vagrant specific guys21:07
*** thumpba_ has quit IRC21:08
sdakebmace so think of the merge as haveing a file:// processor or etcd:// processor or mysqld:// processor21:11
sdakewhen the files get built the source data store is passed in21:12
sdakerather hwen merge gets called21:12
jpeelerharmw: redeploying, but i'm pretty sure the docker permissions were fine21:15
bmacesdake: that is fine, regardless of the path it still looks like it is config.read() that reads in the source files to merge them.. so either ConfigParser handles those protocols to find / read them or they need to be dumped into regular files before hand.21:18
sdakethat alone nearly gives us full ha21:20
sdakebecause we kick ha problem to the data storage mechanism21:20
sdakeand etcd and mysql both have solutiosn for that21:20
jpeelerharmw: so on support01, docker ps works fine and such21:20
bmaceyup, pick your own ha is nice.21:21
sdakethe only other thing we need to ensure is that multiple ansible deploys don't trigger at the same time21:21
bmacewhatever you are using in house?  either we have code for it already or just add a little yourself and poof21:21
sdakebmace I do think it means we need to possibly figure out how to containerize etcd and ansiblize deploy it in ha mode so its easy for users to use atleast 1 data store21:22
bmaceit would be nice.  "control" over who is doing the deploy could even be managed that way21:23
sdakeagree21:23
bmacesome sort of lock held in etcd21:23
sdakealthough there would need to be a reset the lock mode ;)21:24
bmaceyup, a command to say.. i know better than you, wipe the lock :)21:24
sdakefantastic we just designed ha in 1 hour that is easymode21:24
sdakeyou asked 2 months ago sorry it took me so long ;)21:24
bmaceteamwork! :)21:25
sdakeyou asked before i understood what the constraints were21:25
*** dwalsh has quit IRC21:27
harmwjpeeler: weird, my docker sock file didn't get chgrpd to docker grp21:29
jpeelerharmw: well, i am using a different image. had to for libvirt support21:29
harmwnonetheless, the service file would be the same21:29
harmwso: weird21:29
harmw:)21:29
harmw:libvirt__dhcp_enabled21:29
harmwcan't you use that?21:29
jpeelerwell it also is marked as true by default?21:34
harmwin that case, you only need something like 'private_network'21:34
jpeeleri've tried that, it reports that it requires usage of ip21:34
jpeeler"* An IP is required for a private network."21:38
harmwok21:39
harmwsucks21:39
harmwmaybe 0.0.0.0 works21:40
harmwhm, bootstrap_nova isn't progressing :21:40
harmw:|21:40
jpeelerharmw: i can try that i guess. but maybe i should do this on just one node...21:46
harmwhehe true21:47
harmwyou can just vagrant up compute01 afaik21:47
harmwthe operator is heavy on requirements, the others aren't21:47
harmwluckily :p21:47
jpeeleroh cool, didn't know that. still quite the beginner21:49
jpeelerwell it didn't accept 0.0.0.0 as the ip21:50
jpeeleri mean did21:50
harmwah21:50
harmwok21:50
jpeelerwill let you know how the interfaces look in a sec21:50
jpeelerwhy do you say only the operator is heavy though? it looks like they all execute the bootstrap script21:51
harmwthe operator is yum installing quite a lot21:51
harmwthe other don't have to since they won't be running anything difficult21:51
harmw(uhm, right? can't even remember, lol)21:52
harmwah great, ansible is done deploying OS :)21:52
harmw$ neutron agent-list21:53
harmwpublicURL endpoint for network service not found21:53
harmwwhoops21:53
*** banix has quit IRC21:57
sdakeharmw you get that with master?21:59
sdakei hope the images i pushed are not busted21:59
harmwno, my images are 13 days old :)22:00
harmwansible code is fresh pull though22:00
harmwbut things locked up when I first launched nova, it freezed/timedout whatever22:01
harmwI'm only starting services per tag, from ansible22:01
harmwwe need a nuke button on this btw :p22:01
harmwmultihost-nuke22:01
harmwjpeeler:22:06
harmwfatal: [support01] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_enp0s8'", 'failed': True}22:06
harmwfatal: [support01] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_enp0s8'", 'failed': True}22:07
harmwinteresting to see that all of a sudden22:07
harmwhaproxy22:07
jpeeleryeah that's what i saw!22:09
*** diga has quit IRC22:10
jpeelerexcept ansible_eth0 instead22:11
harmwjpeeler: you mind filing a bug on this?22:11
harmwlets see if I can fix this22:11
jpeelerwell no, but i don't understand what the problem is22:12
harmwundefined variable :)22:12
jpeelercan i file it in a few? i gotta go take care of something22:12
jpeelermaybe 10 min22:12
harmwyea totaly22:12
*** diga has joined #kolla22:14
*** diga has quit IRC22:15
*** diga has joined #kolla22:17
jpeelerharmw: the undefined variable has nothing to do with vagrant, right?22:23
harmwofcourse not :)22:23
jpeelerjust checking!22:23
harmw:) np22:23
harmwhm, looks like the haproxy is a little screwed22:25
jpeelerhttps://bugs.launchpad.net/kolla/+bug/148240622:26
openstackLaunchpad bug 1482406 in kolla "ansible deploy yielding undefined variable " [Undecided,New]22:26
harmwcould you make that specific to haproxy, if it's not already?22:26
jpeeleri hadn't22:27
jpeelerhow did you determine that was from haproxy?22:27
harmwansible told me :)22:27
harmwit says up front which play it's going to run22:27
harmwbut perhaps you need a -v for that22:27
harmw(most of the times I run with -vv)22:28
jpeelerright, just not used to reading ansible output22:28
harmwnp22:28
jpeelerit is in the haxproxy task22:28
jpeelerthis past hour has made me feel like i know nothing heh22:28
sdakefolks can you discuss https://blueprints.launchpad.net/kolla/+spec/deploy-ha plz22:28
harmwit tells you it'll be doing something with configuration stuff22:28
harmwfrom haproxy22:28
jpeeleryeah i see now22:28
harmwso just take a look into that task22:28
harmwthe task at hand (config.yml) will tell you it's mangling some template22:29
harmwand *that* fails22:29
harmwbecause that variable is missing22:29
sdakewhat is the variable22:29
jpeelerharmw: so now i have one interface with no IP, is that what we wanted?22:29
harmw-  server {{ hostvars[host]['ansible_hostname'] }} {{ hostvars[host]['ansible_' + api_interface]['ipv4']['address'] }}:{{ keystone_admin_port }} check inter 2000 rise 2 fall 522:30
harmw+  server {{ hostvars[ansible_hostname] }} {{ hostvars[inventory_hostname]['ansible_' + api_interface]['ipv4']['address'] }}:{{ keystone_admin_port }} check inter 2000 rise 2 fall 522:30
harmwthats times 100.000 sdake :)22:30
harmw(or maybe less)22:30
harmwbut after that it fails to boot, because the config file is broken22:30
sdakejpeeler yes that is whaty ou want22:30
harmwjpeeler: excellent, yes22:30
harmwsdake: you know if anything was added to keepalived container these last 2 weeks?22:33
harmwERROR: missing KEEPALIVED_HOST_PRIORITIES22:33
harmwcould be fixed already though22:33
sdakeharmw i hae not see that22:33
sdakeharmw which imaags are ou building22:33
sdakerather which images did you use22:33
harmw2 weeks old, self build22:33
sdakeuse git blame on that line22:34
sdakei think ansible wasn't done 2 weeks ago tbh for keepalived22:34
sdakethat error looks like a config-internal operation, so if your running ansible thatshould not be printing22:34
harmwyep, but it did :)22:35
sdakeharmw if your using master of kolla it pulls liberty2 images22:35
harmwanyway, I'll rebuild22:35
harmwansible is setup to pull from my own repo22:35
harmw(inside vagrant)22:35
harmwwhich is made up of self build images)22:35
*** Haomeng|2 has joined #kolla22:37
sdakei see, so if your using latest for your pull for vagrant that should be fine22:38
sdakemaster uses liberty222:38
sdakeso when people pull kolla from git they don't have to build images22:38
*** britthouser has joined #kolla22:38
*** Haomeng has quit IRC22:40
*** dims_ has quit IRC22:50
harmwright, well the fix is probably real simple but my devenv is giving me a hard time :p better luck tomorrow23:04
harmwnight guys23:04
harmw(what I just pasted isn't the proper fix btw)23:05
*** dims_ has joined #kolla23:10
*** blahRus has quit IRC23:24
*** echoingumesh has quit IRC23:28
*** echoingumesh has joined #kolla23:29
*** echoingumesh has quit IRC23:33
*** sdake has quit IRC23:38
*** weiyu has joined #kolla23:56
*** jasonsb has quit IRC23:58
*** achanda has joined #kolla23:59

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