Wednesday, 2016-03-16

*** sdake has quit IRC00:01
*** vhosakot has joined #kolla00:05
*** dims has joined #kolla00:08
*** sdake_ has quit IRC00:08
*** sdake has joined #kolla00:11
*** Jeffrey4l has joined #kolla00:12
*** fthiagogv has joined #kolla00:19
openstackgerritMartin André proposed openstack/kolla: Fix host_manager plugin for vagrant virtualbox  https://review.openstack.org/29317900:21
openstackgerritMartin André proposed openstack/kolla: Fix genconfig on vagrant  https://review.openstack.org/29318000:22
*** openstack has joined #kolla00:24
*** tummy has joined #kolla00:24
*** vhosakot has quit IRC00:25
openstackgerritThiago Gomes proposed openstack/kolla: Add Manila deployment document  https://review.openstack.org/29258800:27
openstackgerritMerged openstack/kolla: Add missing tar command for oraclelinux binary  https://review.openstack.org/29302700:28
*** tummy has quit IRC00:28
*** ssurana1 has quit IRC00:28
sdakeasalkeld around?00:29
asalkeldhi00:29
sdakecan you get this fixed https://bugs.launchpad.net/python-heatclient/+bug/155781000:30
openstackLaunchpad bug 1557810 in python-heatclient "invalid json blocking kolla liberty gate" [Undecided,New]00:30
sdakei'm not sure we shoud be validating third party project json code but that is besides the point ;)00:30
asalkeldnot sure why that made it through the heatclient gate00:32
openstackgerritMerged openstack/kolla: Move sysctl out of haproxy container  https://review.openstack.org/29289200:32
sdakedo you know the problem?00:32
asalkeldno, i'll have a quick look00:33
asalkeldgot a clean python-heatclient and running pep800:33
sdakeyou don't run our validate json script in your gate im sure00:34
asalkeldo, why we doing that?00:34
sdaketo make sure the syntax is correct? :)00:34
openstackgerritMerged openstack/kolla: Switch to with items for sysctl  https://review.openstack.org/29289300:34
sdakedo you men why are we validating third party json and yaml files?00:35
sdakeno good reason i'm sure - I think master removed that00:35
asalkeldthis line failed: https://github.com/openstack/python-heatclient/blob/master/heatclient/tests/test_templates/adopt.json#L200:36
asalkeldcan't see the problem with that00:36
asalkeldadopt.json failed validation: Expecting property name: line 2 column 5 (char 6)00:37
sdakethat is master00:39
sdakei dont knwo what is in the gate00:39
sdakelooks like sbaker fixed hte invalid json00:39
sdakeprobably needs a new tag to get into the gate - i doubt the gate gates on master client packages00:40
asalkeldok00:41
SamYapleasalkeld: dont worry about that bug steven just posted, its already been fixed and merged upstream00:42
SamYaplehttps://review.openstack.org/#/c/289468/00:42
asalkeldk00:42
sdakeSamYaple ya that is pretty clear looking at the chanelog for the file00:42
sdakewhat is needed is a tag to introduce the new heatclient to the gate00:43
SamYaplesdake: also the comment in the kolla patchset00:43
sdakeand heatclient probably needs a validatejson00:43
SamYapleeh that json is valid for some parsers00:44
openstackgerritSam Yaple proposed openstack/kolla: heatclient has invalid json validation picks up  https://review.openstack.org/29318500:45
SamYapletheres the cherrypick from master00:45
*** dims has joined #kolla00:45
sdakethanks SamYaple00:46
sdakeok folks dinner time00:46
sdakeafter long hard day of physical labor00:46
sdakei think my remodel will be done about the time kolla remodel is done ;)00:46
sdakeasalkeld can you ack that cherrypick00:47
sdakethen we dont need a new tag00:47
SamYaplesdake: why did you increate teh gate timeout for centos00:49
SamYaplethat is not useful00:49
asalkelddone00:49
*** phuongnh has joined #kolla00:52
*** Jeffrey4l has quit IRC00:53
asalkeld /tmp/hudson4318013726486424771.sh: line 2: tools/setup_gate.sh: No such file or directory00:53
asalkeldSamYaple: ^00:53
asalkeldis that expected on stable?00:53
asalkeldhttp://logs.openstack.org/85/293185/1/check/gate-kolla-dsvm-build-centos-binary/b102915/console.html#_2016-03-16_00_49_21_34200:53
SamYapleasalkeld: we made some changes to that. let me look00:54
SamYapleasalkeld: stable is bust00:57
*** dave-mccowan has joined #kolla00:57
*** alisonh has left #kolla00:57
asalkeldok, i guess approving the above patch is ok tho'?00:57
asalkeldi.e. less bust00:57
*** Kennan has quit IRC00:58
SamYapleasalkeld: yes its fine00:58
SamYapleive got another patch to fix gate, please merge that one00:58
openstackgerritMerged openstack/kolla: heatclient has invalid json validation picks up  https://review.openstack.org/29318501:03
*** daneyon has quit IRC01:04
openstackgerritSam Yaple proposed openstack/kolla: Libvirt needs openvswitch to connect br-int  https://review.openstack.org/28807501:05
openstackgerritSam Yaple proposed openstack/kolla: Fix stable/liberty gate  https://review.openstack.org/29318901:05
*** dims has quit IRC01:07
*** Kennan has joined #kolla01:10
*** dims has joined #kolla01:12
openstackgerritSam Yaple proposed openstack/kolla: Libvirt needs openvswitch to connect br-int  https://review.openstack.org/28807501:12
rhallisey   SamYaple oh that's why it was failing01:13
rhalliseythanks for updating it01:13
openstackgerritSam Yaple proposed openstack/kolla: Fix stable/liberty gate  https://review.openstack.org/29318901:16
openstackgerritSam Yaple proposed openstack/kolla: Libvirt needs openvswitch to connect br-int  https://review.openstack.org/28807501:16
SamYaplerhallisey: yea im just trying to see it pass the gate01:16
*** dims has quit IRC01:29
*** dims has joined #kolla01:29
*** vhosakot has joined #kolla01:31
*** ccesario has quit IRC01:44
*** ccesario has joined #kolla01:45
*** dims has quit IRC01:52
*** mgoddard has quit IRC01:54
*** dims has joined #kolla01:56
*** tfukushima has joined #kolla01:57
*** tfukushima has quit IRC01:58
*** vhosakot has quit IRC02:02
*** dims has quit IRC02:03
*** dims has joined #kolla02:05
*** vhosakot has joined #kolla02:13
openstackgerritMerged openstack/kolla: Remove useless dependency on ifconfig  https://review.openstack.org/29318102:17
openstackgerritKuo-tung Kao proposed openstack/kolla: add unit tests for build script  https://review.openstack.org/29042302:37
*** unicell has quit IRC02:37
*** vhosakot has quit IRC02:39
*** vhosakot has joined #kolla02:43
*** rhallisey has quit IRC02:45
*** Jeffrey4l has joined #kolla02:57
*** tfukushima has joined #kolla03:02
*** tfukushima has quit IRC03:04
*** fthiagogv has quit IRC03:05
*** ssurana has joined #kolla03:06
*** dave-mccowan has quit IRC03:17
*** yuanying has quit IRC03:20
*** dims has quit IRC03:37
*** gbraad has joined #kolla03:38
openstackgerritGerard Braad proposed openstack/kolla: Changed commented default port for docker_registry  https://review.openstack.org/29324003:44
*** tfukushima has joined #kolla03:50
*** tfukushima has quit IRC03:52
openstackgerritMerged openstack/kolla: Fix genconfig on vagrant  https://review.openstack.org/29318004:00
*** ayoung is now known as ayoung_Zzz__04:01
*** yuanying has joined #kolla04:07
*** tfukushima has joined #kolla04:07
*** ayoung_Zzz__ has quit IRC04:12
openstackgerritGerard Braad proposed openstack/kolla: Changed port of docker_registry for consistency with documentation  https://review.openstack.org/29324004:19
*** vhosakot has quit IRC04:21
openstackgerritMD NADEEM proposed openstack/kolla: Fix race condition in haproxy  https://review.openstack.org/29278204:41
*** tfukushima has quit IRC04:43
*** alisonh has joined #kolla04:47
*** sdake has quit IRC04:50
*** ccesario has quit IRC04:59
*** ccesario has joined #kolla05:00
*** ssurana has quit IRC05:08
openstackgerritGerard Braad proposed openstack/kolla: Changed port of docker_registry in globals.yml  https://review.openstack.org/29324005:09
*** ssurana has joined #kolla05:13
*** SiRiuS_ has joined #kolla05:21
*** tfukushima has joined #kolla05:23
*** unicell has joined #kolla05:28
*** Jeffrey4l has quit IRC05:32
openstackgerritKuo-tung Kao proposed openstack/kolla: add unit tests for build script  https://review.openstack.org/29042305:37
*** alisonh has quit IRC05:42
*** alisonh has joined #kolla05:46
*** coolsvap has joined #kolla06:03
openstackgerritMartin André proposed openstack/kolla: Fix openstack-base for centos-source  https://review.openstack.org/29327606:40
*** ssurana has quit IRC06:44
gbraadinit-runonce needs python-neutronclient to be installed. currently not described in the quickstart06:57
*** Marga_ has quit IRC07:25
SiRiuS_Martin Andre07:27
SiRiuS_There is a bug in the Vagrantfile07:27
SiRiuS_`when "virtualbox_ubuntu"` and `when "virtualbox_centos"` .... should be replaced by just one line `when "virtualbox"`07:27
coolsvapSiRiuS_: i think there is a fix proposed for that today07:28
SiRiuS_Otherwise the host manager plugin won't function work07:28
SiRiuS_coolsvap: Oh, OK :)07:28
coolsvapSiRiuS_: https://review.openstack.org/#/c/293179/07:28
mandrehey SiRiuS_07:29
mandreI believe I submitted a fix for all the issues your reported07:30
coolsvapmandre: ^^07:30
mandreSiRiuS_: thanks for the reports by the way07:30
SiRiuS_manure: I saw, thanks :)07:31
mandreSiRiuS_: next time you find an issue you can report them directly in launchpad so that we don't lose track of them07:31
SiRiuS_mandre: Ok will do07:32
SiRiuS_mandre: There is also another issue, but it depends on the hypervisor I think07:33
SiRiuS_mandre: The problem is with VirtualBox and computers on wi-fi07:34
mandreSiRiuS_: it's good practice to come discuss the issues on IRC like you did, please keep doing it :)07:35
SiRiuS_mandre: The 3rd (neutron public) interface needs to have promiscuous activated07:35
mandreSiRiuS_: that's entirely depending on your environment07:36
SiRiuS_mandre: But according to the VirtualBox documentation (and tested by me), promiscuous mode on wi-fi does not work fully07:36
SiRiuS_mandre: I did a fix to make it work, but yes, I do understand it's environment dependent07:37
*** Marga_ has joined #kolla07:38
mandredid you make a change to the provision script?07:38
SiRiuS_mandre: no07:39
SiRiuS_mandre: Here is what I did -> http://pastebin.com/7jnixNrj07:39
SiRiuS_mandre: I also commented out this line : # config.vm.network "public_network", dev: get_default(:bridge_interface), mode: 'bridge', type: 'bridge'07:40
SiRiuS_mandre: The idea behind the fix is that in the VirtualBox + wi-fi combination the real physical wi-fi router can't be used, because VirtualBox changes the MAC address07:41
*** Marga_ has quit IRC07:41
*** Marga_ has joined #kolla07:41
SiRiuS_mandre: So we need to create a gateway on the host, and route all the traffic through it07:42
*** Marga_ has quit IRC07:42
SiRiuS_mandre: I used the VirtualBox NAT Network service07:42
mandreSiRiuS_: I'm afraid I can't be of much help here, I don't use virtualbox :/07:42
*** Marga_ has joined #kolla07:43
SiRiuS_mandre: Since vagrant does not provide a mechanism to do that, It has to be done at a low level. That's why I used vm.customize07:43
SiRiuS_mandre: Also it's mandatory that vm.customize be used for all the other virtual NICs, even if just t change something insignificant07:44
mandreSiRiuS_, you'll need to find a virtualbox user to test your changes07:45
mandremaybe pbourke?07:45
SiRiuS_mandre: I tested, and it works for me. The only inconvenience is that, now, the neutron public network, is actually a private network , and to connect to the VM's with the floating IPs we have to do a port forward07:47
SiRiuS_mandre: The host OS and the VM inside OpenStack with floating IPs, are not in the same network anymore, but this is the only way to get it working on wi-fi07:49
mandreSiRiuS_: oh, I'm sure you've tested and it worked for you, we just need to make sure it works for the general case07:50
SiRiuS_mandre: Oh yeah, sure :)07:51
mandresadly I'm not a virtualbox user and I can't confirm the bug07:51
mandreSiRiuS_: please log a bug and send a patch07:52
SiRiuS_mandre: Acording to VirtualBox documentation, promiscuous mode on wi-fi is a problem of the wi-fi interfaces07:52
mandreit will get reviewed07:52
SiRiuS_mandre: I never worked in launchpad, is there a quick-start documentation somewhere ?07:53
openstackgerritMartin André proposed openstack/kolla: Remove oslo-log patch  https://review.openstack.org/29329407:55
*** stvnoyes has quit IRC08:00
mandreSiRiuS_: no worries, we'll guide you08:01
*** stvnoyes has joined #kolla08:01
mandreyou'll need to create an account on launchpad.net if you haven't done it already08:03
SiRiuS_mandre: Ok, I'll first look around and get an idea08:04
*** jmccarthy has quit IRC08:04
mandrealso, have a look at http://docs.openstack.org/contributor-guide/first-timers-quickstart.html08:04
SiRiuS_mandre: Doing that right now :)08:04
*** jmccarthy has joined #kolla08:04
*** starmer has joined #kolla08:13
*** mikelk has joined #kolla08:21
*** kbyrne has joined #kolla08:22
openstackgerritMerged openstack/kolla: Fix host_manager plugin for vagrant virtualbox  https://review.openstack.org/29317908:28
*** starmer has quit IRC08:29
openstackgerritMD NADEEM proposed openstack/kolla: Manila ubuntu binary container  https://review.openstack.org/28637908:44
openstackgerritMD NADEEM proposed openstack/kolla: Manila ubuntu binary container  https://review.openstack.org/28637908:44
*** Serlex has joined #kolla08:46
openstackgerritGerard Braad proposed openstack/kolla: Trivial: changed port of docker_registry in globals.yml  https://review.openstack.org/29324008:48
*** kproskurin has joined #kolla08:55
*** starmer has joined #kolla08:55
openstackgerritMerged openstack/kolla-mesos: Add timestamp to logging and remove useless log string  https://review.openstack.org/29169209:03
*** kproskurin has quit IRC09:04
*** coolsvap has quit IRC09:07
*** mbound has joined #kolla09:10
*** salv-orlando has joined #kolla09:11
*** kproskurin has joined #kolla09:15
*** jmccarthy1 has joined #kolla09:25
*** tzn has joined #kolla09:31
*** v1k0d3n has quit IRC09:35
*** v1k0d3n has joined #kolla09:36
*** tfukushima has quit IRC09:39
*** ccesario has quit IRC09:45
*** ccesario has joined #kolla09:45
*** Serlex has quit IRC09:48
*** tfukushima has joined #kolla09:48
*** dims has joined #kolla09:51
*** Serlex has joined #kolla09:53
*** openstackgerrit has quit IRC09:53
*** openstackgerrit_ is now known as openstackgerrit09:53
*** openstackgerrit has quit IRC09:53
*** openstackgerrit_ has joined #kolla09:53
*** openstackgerrit_ is now known as openstackgerrit09:54
*** openstackgerrit_ has joined #kolla09:55
*** SiRiuS_ has quit IRC09:55
*** SiRiuS_ has joined #kolla09:55
*** openstackgerrit has quit IRC09:55
*** openstackgerrit has joined #kolla09:56
*** allen_gao has quit IRC10:01
*** kproskurin has quit IRC10:04
*** allen_gao has joined #kolla10:10
*** pbourke has quit IRC10:12
*** pbourke has joined #kolla10:13
*** gfidente has joined #kolla10:13
*** gfidente has joined #kolla10:13
*** starmer has quit IRC10:16
*** starmer has joined #kolla10:17
*** starmer has quit IRC10:22
*** AndChat|241401 has joined #kolla10:24
*** kproskurin has joined #kolla10:26
*** ccesario has quit IRC10:26
*** akwasnie has joined #kolla10:27
akwasnie morning10:28
*** rhallisey has joined #kolla10:31
*** AndChat|241401 has quit IRC10:39
*** vincent_vdk has quit IRC10:40
*** phuongnh has quit IRC10:42
*** kproskurin has quit IRC10:48
*** kproskurin has joined #kolla10:48
*** dims has quit IRC10:53
*** salv-orlando has quit IRC10:56
*** dims has joined #kolla10:59
*** alisonh has quit IRC10:59
openstackgerritPaul Bourke proposed openstack/kolla: Increase the docker parition for rht bases in gate  https://review.openstack.org/29303111:00
*** Jeffrey4l has joined #kolla11:06
*** iceyao has joined #kolla11:11
*** tfukushima has quit IRC11:12
*** tfukushima has joined #kolla11:13
*** tfukushima has quit IRC11:13
*** openstackgerrit has quit IRC11:18
*** openstackgerrit has joined #kolla11:18
*** alisonh has joined #kolla11:18
*** akwasnie has quit IRC11:30
*** iceyao has quit IRC11:32
*** alisonh has quit IRC11:34
mlimamorning guys11:40
*** alisonh has joined #kolla11:40
mlimathis bug can be closed? https://bugs.launchpad.net/kolla/+bug/155001111:40
openstackLaunchpad bug 1550011 in kolla " Add the default empty reconfigure.yml file to all roles" [Wishlist,Triaged] - Assigned to Jeffrey Zhang (jeffrey4l)11:40
*** dwalsh has joined #kolla11:47
*** allen_gao has quit IRC11:50
*** allen_gao has joined #kolla11:51
*** dave-mccowan has joined #kolla11:52
*** salv-orlando has joined #kolla11:57
ccesario_morning!12:00
openstackgerritMauricio Lima proposed openstack/kolla: Deploy fails with error in stable/liberty  https://review.openstack.org/29339012:05
*** asalkeld has quit IRC12:12
*** JoseMello has joined #kolla12:27
*** salv-orlando has quit IRC12:28
*** vincent_vdk has joined #kolla12:31
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Set --ipc option to "host" for kolla_docker  https://review.openstack.org/29340012:37
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Connect to mariadb with dnsname.  https://review.openstack.org/29017612:40
*** akwasnie has joined #kolla12:44
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Switch services to use mesos-dns names  https://review.openstack.org/29018112:46
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement commands list command  https://review.openstack.org/29308112:50
*** prithiv has joined #kolla12:52
*** inc0 has joined #kolla12:54
*** inc0_ has joined #kolla12:58
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement deployment commands  https://review.openstack.org/29274112:58
*** inc0 has quit IRC12:58
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Connect to mariadb with dnsname.  https://review.openstack.org/29017612:59
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Switch services to use mesos-dns names  https://review.openstack.org/29018112:59
*** Jeffrey4l has quit IRC13:02
openstackgerritThiago Gomes proposed openstack/kolla: Add Manila deployment document  https://review.openstack.org/29258813:11
*** fthiagogv has joined #kolla13:13
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Set --ipc option to "host" for kolla_docker  https://review.openstack.org/29340013:13
*** Jeffrey4l has joined #kolla13:14
openstackgerritSerguei Bezverkhi proposed openstack/kolla: [WIP] iscsi container with lvm2 support  https://review.openstack.org/29128513:15
openstackgerritSerguei Bezverkhi proposed openstack/kolla: [WIP] iscsi container with lvm2 support  https://review.openstack.org/29128513:16
*** iceyao has joined #kolla13:17
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement commands list command  https://review.openstack.org/29308113:24
*** Jeffrey4l has quit IRC13:27
*** salv-orlando has joined #kolla13:29
*** sdake has joined #kolla13:33
*** jtriley has joined #kolla13:38
*** salv-orlando has quit IRC13:40
*** shardy has joined #kolla13:42
*** tzn has quit IRC13:45
sdakehey shardy13:45
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Connect to mariadb with dnsname.  https://review.openstack.org/29017613:48
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Switch services to use mesos-dns names  https://review.openstack.org/29018113:48
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement deployment commands  https://review.openstack.org/29274113:50
*** fthiagogv has quit IRC13:50
SamYaplemorning13:51
*** fthiagogv has joined #kolla13:51
*** athomas has quit IRC13:51
SamYaplemlima: yes13:51
*** fthiagogv has quit IRC13:51
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Connect to mariadb with dnsname.  https://review.openstack.org/29017613:51
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Switch services to use mesos-dns names  https://review.openstack.org/29018113:51
*** fthiagogv has joined #kolla13:51
*** fthiagogv has quit IRC13:52
*** fthiagogv has joined #kolla13:52
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Connect to mariadb with dnsname.  https://review.openstack.org/29017613:53
openstackgerritArtur Zarzycki proposed openstack/kolla-mesos: Switch services to use mesos-dns names  https://review.openstack.org/29018113:53
*** fthiagogv has quit IRC13:54
*** fthiagogv has joined #kolla13:54
*** fthiagogv has quit IRC13:55
*** fthiagogv has joined #kolla13:55
*** athomas has joined #kolla13:56
sbezverkGood morning13:56
sbezverkSamYaple I removed those "sed" commands13:57
sbezverkit looks like --ipc=host did the magic..13:57
mlimaSamYaple, i was looking some bug in launchpad and i think that these bugs can be closed https://bugs.launchpad.net/kolla/+bug/154679813:57
openstackLaunchpad bug 1546798 in kolla "neutron failed to deploy in ubuntu binary" [Medium,Triaged] - Assigned to Sam Yaple (s8m)13:57
mlima https://bugs.launchpad.net/kolla/+bug/155243313:57
mlima https://bugs.launchpad.net/kolla/+bug/155478013:57
openstackLaunchpad bug 1552433 in kolla "init-runonce does not pull CirrOS image in fresh node deployment" [Low,Confirmed] - Assigned to Prithiv (prithiv)13:57
openstackLaunchpad bug 1554780 in kolla "Update the documentation about installation of curl, nova, neutron clients" [Low,Confirmed] - Assigned to Prithiv (prithiv)13:57
SamYaplesbezverk: oh right! i forgot to tell you abbout that one13:57
SamYaplesbezverk: yea when doing a super container there are a few shared namespaces you want13:58
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement deployment list command  https://review.openstack.org/29344413:58
SamYaplemlima: you have permission to close those bugs, but please close them with a link to the proper review that should have closed them (or mark them as dups of other bugs)13:58
SamYaplemlima: and adjust the owner and branch and what not please13:59
sbezverkSamYaple I submitted 1 line patch to make --ipc=host permanent in kolla_docker.py13:59
SamYaplelink?13:59
sbezverkSamYaple https://review.openstack.org/#/c/293400/14:00
sbezverkI tested it and it works14:01
SamYaplesbezverk: i left a review. please address teh comment and we can merge14:01
sbezverkSamYaple ok14:03
*** daneyon has joined #kolla14:03
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement deployment list command  https://review.openstack.org/29344414:06
ccesario_Hi guys... only to report - even with ansible - 1.9.5rc1 the problem related there https://bugs.launchpad.net/kolla/+bug/1520728 still happen14:06
openstackLaunchpad bug 1520728 in kolla "fatal: [openstack002] => One or more undefined variables: 'dict object' has no attribute 'stdout'" [Critical,In progress]14:06
SamYapleccesario_: yes its not going ot be fixed inthe 1.9.x branch14:08
SamYapleperiod, ansible has stated as much14:08
ccesario_:/14:09
*** absubram has joined #kolla14:11
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: CLI: implement commands list command  https://review.openstack.org/29308114:11
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Set --ipc option to "host" for kolla_docker  https://review.openstack.org/29340014:11
*** absubram_ has joined #kolla14:12
*** banix has joined #kolla14:12
*** tfukushima has joined #kolla14:14
*** daneyon has quit IRC14:15
*** salv-orlando has joined #kolla14:15
*** absubram has quit IRC14:15
*** absubram_ is now known as absubram14:15
sbezverkSamYaple your comment has been addressed.. could you please re-check? https://review.openstack.org/29340014:26
*** sdake has quit IRC14:27
*** ayoung has joined #kolla14:33
*** iceyao has quit IRC14:36
*** bugroger has joined #kolla14:37
*** absubram has quit IRC14:40
sbezverkSamYaple do we need to support ipc_mode change? if not then I do not need to compare current mode, just set it.14:41
SamYaplesbezverk: any container change should be registered, yes14:41
*** absubram has joined #kolla14:43
*** daneyon has joined #kolla14:46
inc0_akwasnie, ping14:47
sbezverkSamYaple, I tested and by default container has None "" ipc mode, which is the same if I do not specify ipc mode parameter, if I specify it it correctly sets ipc mode to host, see http://paste.openstack.org/show/490721/14:56
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Set --ipc option to "host" for kolla_docker  https://review.openstack.org/29340014:57
*** mlima has quit IRC15:02
*** mlima has joined #kolla15:05
*** inc0___ has joined #kolla15:08
*** inc0___ has quit IRC15:09
*** inc0 has joined #kolla15:09
akwasnieinc0_: hi15:10
*** inc0_ has quit IRC15:12
*** mbound has quit IRC15:22
*** sdake has joined #kolla15:25
*** vhosakot has joined #kolla15:29
sdakesbezverk did you manage to make a ipc model?15:33
sdakerather ipcMode in kolla docker module15:33
inc0akwasnie, do we have meeting today?15:36
inc0about prezentation?15:36
akwasnieinc0_: yes15:36
SamYapleinc0: yes 2300 UTC15:36
inc0SamYaple, not this meeting;)15:36
inc0but thanks;)15:36
SamYapleoh...15:37
inc022.30UTC akwasnie? on skype or hangouts or here?15:37
akwasnieinc0_: elemoine said that he would like to meet at 4:30 UTC, is it ok for you?15:37
inc0yeah15:37
SamYaplebtw i responded to everyones lightouts concern and have no intention of doing another patch with the comments provided, so please rereview and reiterate exactly what yo uare -1'ing on if you still are15:37
*** jasonsb has joined #kolla15:37
SamYaplehttps://review.openstack.org/#/c/293161/15:37
*** tfukushima has quit IRC15:38
elemoine_inc0: thanks 22:30 UTC is too late for me15:38
akwasnieinc0_: we can start on IRC15:38
inc0elemoine_, thats what I thought, hence my asking15:39
inc0so, about 1hr from now then15:39
inc0?15:39
elemoine_perfect15:39
akwasnieyes15:39
inc0cool, thanks guys15:39
sbezverksdake yes15:40
sbezverksdake I submitted patch and needs final reviev..15:40
*** blahRus has joined #kolla15:47
*** akwasnie has quit IRC15:48
openstackgerritSam Yaple proposed openstack/kolla: Mariadb upgrade  https://review.openstack.org/29316215:53
openstackgerritSam Yaple proposed openstack/kolla: MariaDB lights out recovery  https://review.openstack.org/29316115:53
openstackgerritMD NADEEM proposed openstack/kolla: Fix race condition in haproxy  https://review.openstack.org/29278215:56
inc0SamYaple, why you not do docs in patch?15:59
inc0that's where docs should be done15:59
SamYapleinc0: i disagree and tahts why docimpact flag exists15:59
SamYaplepeople like to nitpick docs and i dont want 30 patchsets with 25 being "two spaces after period please"16:00
pbourkeha16:01
SamYapledont get me wrong, i think docs _should_ be nitpicked16:01
SamYaplebut you know, not in a non-docs patchset16:02
inc0can you make next patch in dependency tree with docs?16:02
SamYaplenope that docimpact flag will trigger a bug _after_ merge16:02
SamYapleinc0: you ready to switch away from jinja2 else/if and move to includes?16:03
SamYaplei think its time!16:03
SamYaplein netwon that is16:03
inc0ready - yes, but this is lower priority than other stuff for me16:04
inc0also saltstack uses jinja?16:04
SamYapleit can use whatever you want, but im talking about the Dockerfile stuff16:04
pbourkeSamYaple: yes for includes please16:04
SamYaplethats not related to deploy tool16:05
pbourkethought that should've been done from the start tbh16:05
SamYaplei was the opposition there pbourke16:05
inc0+1 to pbourke16:05
inc0from the start16:05
SamYaplepeople didnt understand jinja216:05
SamYaplethere was like 3 people who understood jinja216:05
SamYapleand our dockerfiles were _not_ uniform16:05
inc0but not just includes, any feature jinja has to offer16:05
SamYaplenow they are and people understand jinja2 thanks to ansible16:05
inc0if it makes sense16:05
pbourkethere is something to be said for one dockerfile per service16:05
SamYapleyea i can get on board with that now inc016:06
pbourkebut ultimately they're too hard to read16:06
SamYaplewell pbourke now we have alot of shared code too16:06
pbourkeyeah16:06
SamYapleso there will still be the meat of the content in one file16:06
inc0but before we start this refactoring16:06
inc0funcional test plz16:06
SamYaplefunctional test of what?16:07
inc0in gates16:07
SamYapleyou mean voting gates?16:07
SamYaplebecause we do functional testing now16:07
inc01 vm spawn is kinda functional testing16:07
SamYapleit uploads to glance, creates networks, adds ssh keys16:07
inc0but maybe something more advanced would be in order16:07
SamYapleits more than just 1 vm boot16:07
inc0I know16:08
SamYaplebut i agree, it needs more16:08
SamYapleit does show core funcationlity is working though16:08
inc0and refactoring can hurt if you don't have good CI16:08
inc0if we start it from day one, that wouldn't be the case16:08
inc0now we make small bug in jinja and it can break stuff16:08
SamYaplewell that we have, since the refactor is all about the building16:08
SamYaplei agree with you inc016:08
inc0but if you forget to install one package16:08
inc0image will build16:08
SamYaplebut this is why we should do it _early_ in newton16:08
inc0app may even run16:09
inc0but it will break16:09
inc0I'd say first good CI, then refactoring16:09
inc0better CI at least16:09
SamYaplehonestly though, thats just presure on the reviewer16:09
inc0multinode and such16:09
SamYaplewe need to refactor to get more gates16:09
inc0my point is, we made a decision and what we have works16:09
SamYapleinfra will give us lots fo gates if we can show only a subset ever run together16:10
inc0if we change it, it may stop working16:10
SamYaplethats what the initial part of the cycle is for16:10
SamYaplemerge then stabilize16:10
SamYaplei dont want to refactor later16:10
SamYaplebecause what you say is still true16:10
SamYapleno matter the testing16:10
SamYaplethere is no 100% converage, it just doesnt exist16:11
SamYaplecoverage* rather16:11
inc0well, my point is16:11
inc0I'm +2 to refactor16:11
*** tzn has joined #kolla16:11
inc0but I'd calmer person if we have good gates before that16:11
SamYaplei dont disagree16:12
SamYaplei think we are of like mind16:12
sdakejust got out of meeting, reading scrollback16:12
*** allen_gao has quit IRC16:13
sdakeso folks re refactor of jinja2 dockerfiless, wfm, but we will come out of summit with a list of priorities and work em in the order we think is appropriate16:14
*** allen_gao has joined #kolla16:15
sdakei would prefer to take a holistic approach to it, rather then saying one feature is mandatory for mitaka-116:15
sdakefor exmaple, I think reno is #1 on the list16:15
inc0reno?16:15
sdakebut others may not, that is what the austin summit is all about - deciding priorities16:15
sdakereno is the release mangement  tool16:15
sdakeit lets us add release notes on the fly16:16
sdakeand creates sdocs automatically16:16
inc0a yeah we spoke about it16:16
sdakeits highly valuable and allows us to obtain the release:managed tag independently of whatever release model we use16:16
sdakeso we no longer have to take responsibility for taggin16:16
sdakeof course this depends on a proper ci - where everyone knows our gate is a bit leaky :)16:17
sdaketaggin/tagging16:17
SamYaplereno is a single commit. its not a problem16:18
sdakeagree, but every commit after requires reno releae notes, atleast blueprints do16:18
sdakeso it will be an alteration of our workflow that devs will have to familiarlize themselves with16:19
sdakefor example docimpact flag with release notes wont fly ;)16:20
*** allen_gao has quit IRC16:20
sdakethe tool uses commit dates to sort out the documentation creatoin on releases.openstack.org16:20
SamYapleyoure 100% wrong there sdake16:21
*** allen_gao has joined #kolla16:23
*** akwasnie has joined #kolla16:24
inc0shots fired;)16:25
sbezverkvhosakot Saw you comment, "" and NOne is it not the same in terms of python?16:27
sdakewrong on what16:27
vhosakotsbezverk: well, I see the other values for "default:" are Python datatypes, aren't they ?16:27
SamYaplesdake: how release notes work with docimpact16:27
sdakedhellmann and I had a 1 hour conversation on the topic16:27
SamYaplehttp://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2016-03-15.log.html#t2016-03-15T20:35:0016:27
SamYaplemind you Sam-I-Am is a docs core, and knows a thing or two16:28
sdakeSamYaple i am just speaking of usign docimplact with release notes, not other use cases16:31
sdakerelease otes have to hit with the commit - or the release notes could end up in the wrong release16:31
sdakeif for example someoen forgets to finish the job on the release notes16:31
SamYapledocimpact can still be used with releasenotes16:31
sdakeanyway all topics for discussion at summit16:31
SamYaplereleasenotes just have to be coupled with commit16:32
sdakei'm not sure reno is smart enough to figure out docimpact couples with the commit16:32
sdakebut i'll consult dhelllman about it16:32
SamYaplei dont think you understand the difference though16:32
SamYaplereleasenotes are not docs like that. they are yaml files16:32
SamYapledocs that go in our doc/* folder are what the docimpact flag is for16:33
sdakeright, ok soudns ike we are on same page16:33
SamYapleok cool16:33
sbezverkvhosakot have to disagree with you comment pid_mode is done the same way and changing ipc_mode would break consistency16:33
sdakethe yaml file needs to be part of the commit is all I'm saing :)16:33
SamYapleyes agree16:33
vhosakotsbezverk: ah ok, let me check something... give me 1 sec16:33
sdakeSamYaple can you mediate that problem with the None vs "" in ipc_mode16:34
sdakesince you are most familiar with the docker kolla module16:34
sdakerather kolla docker module16:34
sdakesbezverk hae a link review handy?16:34
SamYaplevhosakot: does passing None as the ipc mode break it?16:35
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Set --ipc option to "host" for kolla_docker  https://review.openstack.org/29340016:35
vhosakotSamYaple: no not about passing.... aren't default: values Python datatypes ?16:35
SamYapleyes16:36
sdakei thought they were yaml datatypes16:36
SamYapleand in this case the default is None16:36
sdakeSamYaple can you leave a comment in the review plz :)16:36
vhosakotSamYaple: so, if t he user does not pass ipc_mode, code thinks it is None ?16:36
sdakeirc reviews are hard to track ;)16:37
sbezverkSamYaple it does not break anything, but why one parameters is done one way and second similar by nature parameter by another way?!? No consistency!16:37
vhosakotsbezverk: yes, I agree about16:37
SamYaplesbezverk: thats dokcer-pys problem though16:37
SamYaplevhosakot: correct16:37
sdakeuse gerrit for reviews plz after sorting out the details so there is a record16:37
sdakesbezverk link this irc discussion in the review - check out the irc logs page16:38
sdakesbezverk nice job on triggering my thought processes around ipc_mode ;)16:39
sdakewould have never figured that out solo without you pointing out udev was stuck on a semtimedop16:39
sdakeudev/lvm16:39
vhosakotsbezverk: gave +1.... Agreed, this is consistent with the default type of pid_mode.16:40
sdakewell before we declare victory lets see what the gate has to say :)16:40
sbezverksdake really glad that there was a solution satisfying sheeps and wolves16:40
sdakebikeshed ftw ;)16:40
sdakethe lvm cat was like "that can't  be done"16:40
sdakeroflcoptersoysoy ;)16:41
vhosakotsdake: sbezverk: :) cool, ATM, the lvm2 ps is my fav :)  great storage iscsi/lvm2 backend for kolla containers16:41
SamYaplevhosakot: itll be a great feature for newton. its one of our oldest bugs16:44
sbezverksdake lvm folks think that container actually owns all lvm related aspects, where in fact it is just a fancy process wrapper and everything else is ownded by host16:44
SamYaplesbezverk: kernel*16:44
SamYaplelol lvm is just device-mapper wrapper16:45
vhosakotSamYaple: cool16:45
nihiliferwe have APAC timezone meering today?16:45
sdakeyup odd week16:45
sdakedate "+%V"16:45
sdakeif you ever need to know the even or odd weeks nihilifer16:46
sbezverkvhosakot few small left which needs to be addressed and then you could probably try this patch on top of master just to see if it works in your test bed..16:47
vhosakotsbezverk: I am planning to test your PS16:47
*** athomas has quit IRC16:47
vhosakotsbezverk: I have iscsi on my box.. I need to setup lvm216:47
vhosakotsbezverk: did you merge some docs about this into maater ? how to setup the host for iscsi/lvm2 ? what kernel modules are needed and blah blah ?16:48
vhosakotmaster*16:48
sbezverkvhosakot not yet, I still need to find out how to deal without "root" access in kolla_toolbox and cinder_volume..16:49
nihilifersdake: nice, thx ;)16:49
vhosakotsbezverk: so, is root access needed just to run few iscsi/lvm2 commands inside the container, or, should the container be _created_ with root user in its Dockerfile ?16:52
sdakethe lvm commands should be run as sudo16:52
sdakeand sudoers file approraitely modified16:53
*** athomas has joined #kolla16:53
vhosakotsdake: similar to neutron_rootwrap and neutron_sudoers ?16:53
sdakethisis the model our other containers follow and is the best we can do16:53
sdakenot similar to neutron_rootwrap but similar to our other sudo operations used throughout our containers16:54
vhosakotsdake: cool16:54
*** unicell has quit IRC16:56
SamYaplesbezverk: vhosakot im a bit confused, what is calling kolla-toolbox in the first place?16:56
SamYaplewhat task is even needing to use kolla_toolbox16:57
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Add hostname of a node as a lock name.  https://review.openstack.org/29287816:59
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: run_once commands locking rework  https://review.openstack.org/29169316:59
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Create separate ZK lock nodes  https://review.openstack.org/29287716:59
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: set_state now could use exact path as an arg  https://review.openstack.org/29287616:59
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Change mysql user from test to nobody  https://review.openstack.org/29357116:59
*** banix has quit IRC17:01
sdake94 people in channel17:02
sdakenew record ;-)17:02
*** banix has joined #kolla17:02
sdakespeaking of the 95 people in the channel, is it possible to get the openstack-kolla thing going?17:02
sdakei'd do the work myself but not certain how it should be done17:02
sdakeSamYaple you mentioned you might have time to take this one17:03
openstackgerritMerged openstack/kolla: Mariadb upgrade  https://review.openstack.org/29316217:08
openstackgerritMauricio Lima proposed openstack/kolla: Remove commented line  https://review.openstack.org/29358317:12
*** mikelk has quit IRC17:12
*** akwasnie has quit IRC17:15
*** rajathagasthya has joined #kolla17:16
*** inc0 has quit IRC17:16
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Add hostname of a node as a lock name.  https://review.openstack.org/29287817:16
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: run_once commands locking rework  https://review.openstack.org/29169317:16
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Create separate ZK lock nodes  https://review.openstack.org/29287717:16
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: set_state now could use exact path as an arg  https://review.openstack.org/29287617:16
*** kproskurin has quit IRC17:24
*** akwasnie has joined #kolla17:24
*** inc0 has joined #kolla17:25
*** unicell has joined #kolla17:27
*** tzn has quit IRC17:27
*** jasonsb has quit IRC17:29
*** akwasnie has quit IRC17:32
rajathagasthyaHello! Looking to contribute to diagnostics (EHK) in Kolla. sdake mentioned the need for integrating Kibana dashboard plugin with ES and I'd like to take up that task.17:33
rajathagasthyaWe've done something similar for Kibana 3. How do I go about doing that with Kibana 4? Maybe akwasnie and elemoine can comment?17:33
vhosakotSamYaple: I think sbezverk is planning to use kolla_toolbox for register / check to check disks, services, etc ?17:33
sdakerajathagasthya elemoine and akwasnie are probably asleep at present, but at our 23:00 UTC meeting would be a good time to sync up on this topic17:39
sdakeI think an integrated with OpenStack dashboard would be a fantastic improvement to the implementation - may I suggestyou edit the meeting wiki agenda listed in the topic with your topic?17:40
sdakerajathagasthya ^^17:40
sdakethe meeting is today17:40
inc0sdake, we just talked about that with akwasne and elemoine17:41
inc0personally I'd love it as post-deploy task17:41
sdakewell it sounds like there are more people wanting to join the party :)17:41
sdakeless is more more is not less? :)17:41
sdakeinc0 when didy ou discuss it - this morning?17:42
sdakein irc logs?17:42
inc0sdake, we had priv meeting regarding our presentation17:42
inc0this just came out17:42
inc0but I'll be happy to dicuss it in proper meeting17:42
sdakeinc0 i've been asking elemoine and ak* to look into it for a about a week17:42
*** rajathagasthya has quit IRC17:43
sdakeafter elemoine told me about it17:43
inc0hehe17:43
sdake(that it could be done)17:43
inc0it's a matter of a single curl17:43
sdakeyes I know17:43
inc0pretty long curl, but curl nonetheless17:43
sdakeits also a matter of making a rockin dashboard17:43
sdakejson from what I gather17:43
*** athomas has quit IRC17:52
*** rajathagasthya has joined #kolla17:54
*** salv-orl_ has joined #kolla17:54
*** salv-orlando has quit IRC17:56
*** akwasnie has joined #kolla18:01
rajathagasthyasdake - Having some trouble editing the meeting agenda.18:03
sdakegive me a topic and I'll put in for you18:04
rajathagasthya"Kibana dashboard integration"18:04
*** akwasnie has quit IRC18:08
fthiagogvsdake, could you look if is okay? https://review.openstack.org/#/c/29258818:14
*** Serlex has left #kolla18:17
*** vhosakot has quit IRC18:18
*** vhosakot_ has joined #kolla18:18
sdakefthiagogv enjoy thanks for the work :)18:29
*** rajathagasthya has quit IRC18:34
openstackgerritMerged openstack/kolla: Add Manila deployment document  https://review.openstack.org/29258818:34
sbezverkSamYaple sorry for delay with replay.. kolla_toolbox mounts volumes for swift, as a result it needs visibility in "/dev/{vg-group}/{lv}"18:34
sbezverkwhen it uses ansible as a user, I could not make it work so far..18:35
sdakerajath* done :)18:36
sdakesbezverk do as i suggested, put sudoers file in the container and use sudo18:36
*** jmccarthy1 has quit IRC18:37
sdakesbezverk https://github.com/openstack/kolla/blob/master/docker/nova/nova-base/nova_sudoers18:39
sdakesbezverk https://github.com/openstack/kolla/blob/master/docker/nova/nova-base/Dockerfile.j2#L55-L5718:39
*** Marga_ has quit IRC18:40
sbezverksdake thanks18:46
mlimaroot@kolla:~/kolla# neutron net-list19:01
mlima -> Unable to establish connection to http://172.24.56.16:9696/v2.0/networks.json19:01
vhosakot_Many gate failures not related to kolla today19:02
vhosakot_Error: Partition(s) on /dev/vdb are being used19:02
vhosakot_Crash dump was written to: erl_crash.dump19:02
vhosakot_mlima: Is neutron_server container up ?19:05
vhosakot_mlima:  "docker exec neutron_server netstat -pan | grep 9696"19:05
mlimanothing19:06
vhosakot_mlima: no output! ?19:06
mlimayes19:06
vhosakot_mlima: then, neutron is down19:06
mlimacontrol:4000/kollaglue/ubuntu-source-neutron-server:2.0.0              "kolla_start"            8 minutes ago       Up 8 minutes                                             neutron_server19:06
vhosakot_it is up19:07
vhosakot_not listening to TCP port 9696.. that is not good19:07
mlimabut, control:4000/kollaglue/ubuntu-source-neutron-openvswitch-agent:2.0.0   "kolla_start"            8 minutes ago       Restarting (1) 45 seconds ago                            neutron_openvswitch_agent19:07
mlimacontrol:4000/kollaglue/ubuntu-source-rabbitmq:2.0.0                    "kolla_start"            10 minutes ago      Restarting (1) 3 minutes ago                             rabbitmq19:07
vhosakot_mlima: restart all failed neutron services19:08
mlimai have three network interfaces19:08
mlimaeth0, eth1 and eth219:08
SamYaplesbezverk: kolla_toolbox doesnt mount swift volumes19:08
SamYaplebut what does that have to do with lvm19:08
vhosakot_mlima: multinode or AIO ?19:09
mlimaaio19:10
*** ayoung has quit IRC19:10
vhosakot_mlima: can you pastebin "/etc/kolla/globals.yml",  "ifconfig -a",  "ip a"  and  "ps aux | grep docker"19:11
mlimayes19:11
mlimaw819:12
mlimahttp://pastebin.com/7gKKyCiV vhosakot_19:14
*** salv-orl_ has quit IRC19:15
mlimahttp://pastebin.com/XJsxdNwR vhosakot_19:15
vhosakot_you can send all output in one pastebin :)19:16
mlimaok19:16
openstackgerritMerged openstack/kolla: Set --ipc option to "host" for kolla_docker  https://review.openstack.org/29340019:16
*** ssurana has joined #kolla19:17
mlimaenjoy http://pastebin.com/6zGh8fRG vhosakot_19:18
sbezverkSamYaple, you are right it does not mount them bu it discovers and prepares dis file which is used later for mounting.. The reason this topic came up, is my test bed is configured with swift and I always use lvm volumes for swift..19:19
*** ssurana has quit IRC19:22
*** fthiagogv has quit IRC19:22
*** prithiv has quit IRC19:22
SamYaplesbezverk: I dont think the permissions block viewing /dev/<vg-group> though do there?19:22
vhosakot_mlima: your kolla_internal_vip_address in globals.yml is not correct. It is the IP of eth0 which is not right.. please change it to an _unused_ IP address in the 172.24.56.16/24 subnet and rerun "kolla-ansible deploy"19:24
vhosakot_mlima: also, uncomment kolla_external_vip_address and have   kolla_external_vip_address: "{{ kolla_internal_vip_address }}"19:26
mlimauncomment?19:26
vhosakot_mlima: yes... it is commented19:27
mlimai know, but it is necessary?19:27
mlimaglobals just replace all.yml, right?19:28
vhosakot_no, not needed in gloabls... it defaults to kolla_internal_vip_address19:29
SamYaplemlima: globlaes doesnt _replace_ all.yml, it overrides it19:29
sdakemlima you dont need to uncomment kolla-extenral-vip19:30
mlimabut in all.yml file i have kolla_external_vip_address: "{{ kolla_internal_vip_address }}" and you said to uncomment it and set kolla_external_vip_address: "{{ kolla_internal_vip_address }}"19:30
sdakeif you dont hve an external vip, kolla will do the right hing19:30
mlimayes, yes override is the word19:30
mlimai don't know why i wrote replace19:31
SamYaplemlima: cool just checking19:31
mlimaThank you :)19:31
vhosakot_mlima: yep, have kolla_external_vip_address in globals if you want to override... so, everything looks goodf except that you are not using an unused IP for kolla_internal_vip_address19:32
vhosakot_SamYaple: sdake: shouldn't kolla-ansible find this (if the user reuses an existing IP on the box for kolla_internal_vip_address) and display and error and exit ? is this worth an enhacement ?19:33
sdakewould make a good precheck19:35
*** Marga_ has joined #kolla19:36
vhosakot_sdake: ok, let me submit something for that19:36
vhosakot_mlima: did you see any error from kolla-ansible when you used re-used IP ? I think neutron won't be happy if you start with an existing IP19:37
sdakemlima your external interface should hacve no configuration associated with it19:38
sdakerther your neutron interface19:38
vhosakot_yes, I saw mlima's pastebin.. neutron_external_interface is pure L2 with no ip no bridge19:39
mlimai have it now kolla_external_vip_address: "{{ kolla_internal_vip_address }}"19:39
mlima:)19:39
mlimadeploy is running19:40
vhosakot_mlima: can you send the error from last time ?19:40
mlimaroot@kolla:~/kolla# neutron net-list19:40
mlima Unable to establish connection to http://172.24.56.16:9696/v2.0/networks.json19:40
mlimathis error ^19:40
vhosakot_thanks19:41
sdakemlima you dont want kolla_external_vip_address uncommented unless you have an external vip19:42
mlimait is commented sdake19:42
sbezverkSamYaple I am reverting back to use normal users in container where I had to change to test sudoers to see if it does the job I need and I will show the issue in kolla_toolbox with discovering volumes..19:43
mlimathese files are a mess, i need to organize them19:43
*** ssurana has joined #kolla19:45
sdakemlima which files ?19:47
mlimathe globals, in my vm19:48
sdakeseem pretty straightforward to me ;)19:48
mlimayes sdake :)19:48
mlimasdake, i want use two network interfaces19:51
mlimait is possible?19:51
mlimaeth0,eth1 and eth219:51
mlimathree network interfaces*19:51
ccesario_mlima, bond?19:54
*** vhosakot_ has quit IRC19:54
sbezverksdake even with sudoers, lvcreate does not work http://paste.openstack.org/show/490786/19:59
*** vhosakot has joined #kolla19:59
*** mlima has quit IRC20:01
*** salv-orlando has joined #kolla20:01
vhosakotmlima: why do you want the third interface eth2 ? as a backup api/neutron interface in case eth1 goes down20:02
*** inc0 has quit IRC20:06
sbezverksdake if I read this bug right, only root not by design can manage lvm https://bugzilla.redhat.com/show_bug.cgi?id=62057120:08
openstackbugzilla.redhat.com bug 620571 in lvm2 "non root user can no longer view lvm devices" [Low,Closed: errata] - Assigned to agk20:08
sbezverksdake sorry what I meant only root now, which is by design can manage lvm devices20:09
*** ayoung has joined #kolla20:11
*** bugroger has quit IRC20:12
*** prithiv has joined #kolla20:18
*** ssurana has quit IRC20:19
elmikohi folks, i've got a question about redeploying kolla. i wanted to enable a few more services, so i modified the globals.yml, ran `tools/cleanup-containers`, then ran `tools/kolla-ansible deploy`20:20
elmikounfortunately, i ended up with this: http://paste.openstack.org/show/490789/20:20
elmikodo i need to run `tools/cleanup-host` as well?20:20
vhosakotelmiko: I have been able to enable services in globals.yml and rerun "kolla-ansible deploy" and it worked.. I did not have to cleanup to enable more services in globals.yml20:22
*** ssurana has joined #kolla20:22
elmikoah, maybe i should have skipped that20:22
elmikobut in general, shouldn't i be able to cleanup and rerun the deploy?20:23
elmiko(for example, when changing passwords)20:23
vhosakotelmiko: yep, no need to cleanup to enable more services.. this decreases ease of use I think... for me, enabling services in globals.yaml without cleanup and rerunning "kolla-ansible deploy" has worked fine20:24
vhosakotelmiko: I mean, running cleanup everytime a new service needs to be enabled, is a pain for the user20:24
elmikovhosakot: ok, great. what about if i want to change say the keystone conf and restart it, how would i do that?20:25
elmikoagreed20:25
vhosakotelmiko: reconfig*20:25
elmikoexcellent, tyvm vhosakot++20:25
vhosakotelmiko: wait.. searching a link20:25
*** sbezverk has quit IRC20:26
vhosakotelmiko: I suggest you refer this link to reconfigure keystone - https://etherpad.openstack.org/p/kolla-mitaka-testing-reconfigure20:27
*** dencaval has quit IRC20:27
elmikoexcellent!20:27
vhosakotelmiko: :)20:27
elmikothanks again =) time for more hacking!20:27
vhosakotnp20:28
*** prithiv has quit IRC20:29
*** diogogmt has joined #kolla20:33
elmikovhosakot: one more question, i tried enabling swift and reconfiguring, and i get this http://paste.openstack.org/show/490794/ look familiar?20:44
*** banix has quit IRC20:45
vhosakotelmiko: I haven;t this error20:47
elmikok, i'm reading through the swift-guide now. maybe i just missed something20:47
vhosakotelmiko: yep, setup all disks, partition tables, rings needed for swift properly20:48
elmikovhosakot: i'm guessing this is just a config error on my part, sorry for the bother20:48
vhosakotnp20:49
SamYaplesdake: back here for a moment since this is not infra related21:00
SamYapleI have been looking into automatic docker builds, and we _can_ do that21:00
SamYapleits is possible21:00
SamYaplerhallisey: jpeeler what are your thoughts on that? ^^21:02
jpeelerautomatic docker builds?21:03
SamYapleyes21:03
jpeeleri talked about doing that long ago so that we wouldn't have to worry about it doing it on the gate infrastructure21:03
SamYaplewe cant do them for master21:03
SamYaplebut we could do them for stable21:03
sdakeyou mean separate repositories per package for building?21:04
SamYapleyes and no, not a repo we commit to per packge for building21:04
jpeelerSamYaple: why would master be excluded?21:04
SamYaplejpeeler: the way im thinking of setting it up21:04
SamYapleremember automated builds mean we have no infrastrucutre21:04
SamYapleas in no build.py21:04
*** achanda has joined #kolla21:05
jpeelertrue21:05
SamYapleit has to be a non-jinja2 dockerfile with all tarballs in repo21:05
SamYaplewhich we could do in an automated fashion based on tags21:05
SamYaplebut it definetely exlcludes master21:05
jpeelerjust because of potential breakage?21:05
SamYapleit would never be up to date21:06
SamYaplei can setup a POC for this trigger/autobuilding process21:06
sdakeaustin summit disucssion imo ;)21:06
jpeelerheh it would be if people stopped committing for sometime21:06
SamYapleno it wouldnt because other proects21:06
SamYapleremember we pull master tarballs21:06
jpeeleryeah...21:07
jpeelerfair enough.21:07
jpeelerbut yes, automated builds for stable would be great in my opinion21:07
SamYaplei think we can do it fairly easily, it would put the load on github and dockerhub21:08
sdaketo use the docker infrastructure reuqires separate repositories21:08
SamYaplesdake: yes and no21:08
SamYapleyes it would require seperate repos, no we would never submit patches to them directly21:08
SamYapleor with infra resources21:08
jpeelerhow would those repos be synced21:09
SamYapleone of us can trigger it21:09
sdakei can see where your headed sam and i'm not one to stop you, but i'd like stable fixed first ;)21:09
SamYaplesdake: you are welcome to jump in at any time and do reviews (and even patchsets!) as i state everytime you say that21:11
sdakei was waiting for you to finish the job ;)21:11
sdakebut if you want reviews now I'm happy to provide them21:12
sdakeapril 1 is what we agreed for an rc21:12
SamYapleas i have stated everytime, yes please review21:12
sdakeok will do21:12
sdakeit is hard for more then one person to do the patches, but i'm willing to contribute to the backporting process as well21:13
sdakeif you need help all you have to do is ask :)21:13
SamYaplewell i ahve been asking for reviews, you seem to keep forgeting that because we have this conversation everytime21:14
sdakeack on reviews21:14
sdakei'll get the CR team on it21:14
SamYapletheres only 3 patches so far so should be no problem21:15
sdakeyes but we need sustained reviews for the life of the patchset21:15
sdakei'll escalate this to the core reviewer team21:15
*** sbezverk has joined #kolla21:15
sdakeso we can get a nice stable liberty by april 121:15
SamYaplejust remember, its green gate on final patch, not neccsarrily before21:16
SamYapleive blocked the initial patch so were safe to +2+121:16
sdakeyup i know that - that was discussed in the first comment21:16
*** ntpttr has joined #kolla21:20
ntpttrhey everyone, I'm running into an issue deploying kolla on multiple nodes. In the bootstrap.yml play of the neutron setup, the 'creating neutron database' step is getting skipped, causing 'read json from variable' to fail because the database variable doesn't exist21:21
SamYaplentpttr: can you post your inventory file21:21
ntpttris there a setting that I might be missing causing this to get skipped? the precheck all works and everything works up to that point21:21
ntpttrsure21:21
SamYapleccesario_: i think this is your problem as well ^^21:22
*** inc0 has joined #kolla21:22
ntpttrhere's the top of the file, the rest is unchanged from the default http://paste.openstack.org/show/490801/21:22
SamYaplentpttr: yea ok im going to point you to a file and i want you to make a change and see if it fixes it for you21:23
ntpttrSamYaple: sounds good21:23
SamYaplentpttr: https://github.com/openstack/kolla/blob/master/ansible/site.yml#L10721:23
SamYaplemove neutron-server above compute in that list21:23
SamYapleif that fixes this it is an ansible bug you are running into21:23
ntpttrso just put it up at the top of the hosts list?21:24
*** achanda has quit IRC21:24
ntpttrI feel like you're right, because in the create step, it's skipping over a host that I don't think should be a neutron-server host21:24
SamYaplentpttr: no in the site.yml file21:24
SamYaplethat list, just move neutron-server above compute21:25
ntpttryeah, that's what I meant sorry21:25
SamYapleyup21:25
SamYapleif that fixes it for you this is an ansible bug thats not fixed until 2.021:25
ntpttrSamYaple: okay, but kolla doesn't work with ansible 2 does it?21:26
*** achanda has joined #kolla21:28
*** shardy has quit IRC21:28
SamYaplentpttr: it will not for mitaka, no21:28
SamYaplentpttr: what ive described for you is the workaround21:28
ntpttrsounds good21:28
SamYapleif your inventory gets even fancier, you may run into a few more issues like that, all fixed in ansible 2.0 only21:29
SamYaplejust fyi21:29
ntpttrSamYaple: still failing at that same spot21:31
*** dwalsh has quit IRC21:31
ntpttrskipping: [172.16.2.6]21:32
ntpttrthat host should be 172.16.2.3 if it were using the neutron-server group21:32
SamYaplentpttr: did you pip install kolla?21:34
ntpttrSamYaple: ah do I need to redo that after making changes?21:34
SamYapleit sounds like youre still running with the old site.yml21:34
ntpttrSamYaple: I'll reinstall and try again21:34
SamYaple_if_ you pip install'd kolla then yes, youll need to reintall it after making git changes21:34
ntpttrunrelated, but is there no script to run the cleanup-containers and cleanup-hosts scrips on all the target hosts? sshing to each one and running them manually is a little slow21:35
SamYaplealternatively you could also make th changes directly to /usr/lib/python*21:35
inc0ntpttr, you have ansible:)21:35
SamYaplentpttr: there was some work to do that in the repo, but i havent seen it for a while21:35
*** achanda has quit IRC21:36
SamYapleinc0: did you see the conversation above about the automated docker builds21:36
inc0ansible -i inventory -m shell -a "tools/cleanup-containers"21:36
ntpttrinc0: I know, I could write my own ansible script, but it'd be cool if there was one built in to kolla21:36
inc0SamYaple, negative, I did not21:36
ntpttrcool thanks21:36
SamYaplentpttr: there will be, but proably not mitaka21:36
SamYaplentpttr: i could help you if you wanted to take on that work yourself21:36
sdake  /query inc021:37
ntpttrSamYaple: I might be interested in that for sure, I would need to talk to managers about work assignments and such if I were going to spend some time on kolla though21:37
SamYapleinc0: he is looking into you!21:37
ntpttrSamYaple: I'm definitely interested, so far it seems like a great tool21:37
SamYaplentpttr: cool just let me know if you want any guidance and ill point you the right way21:38
ntpttrSamYaple: thanks21:38
SamYapleinc0: i think i can get automated builds going in the dockerhub itself21:38
*** jtriley has quit IRC21:39
vhosakotsdake: read the first comment in https://bugs.launchpad.net/heat/+bug/147187021:44
openstackLaunchpad bug 1471870 in heat "Kilo Heat Authorization Failed" [Medium,Triaged]21:44
vhosakotsdake: I'm adding all the info I have into the heat DOA bug21:45
sdakeare you working on that bug vhosakot ?21:46
vhosakotsdake: no, I dug into a bit for a day and adding info for whoever is working on it21:47
*** achanda has joined #kolla21:47
openstackgerritSam Yaple proposed openstack/kolla: Add generate.py to generate passwords  https://review.openstack.org/29372821:47
sdakeya the heat domain keystone setup script is pretty much what we need but we need it to be broken out into a separate set of steps21:47
sdakei'll take care of that bug21:48
vhosakotsdake: cool21:48
*** absubram has quit IRC21:49
*** absubram has joined #kolla21:50
openstackgerritSam Yaple proposed openstack/kolla: update openrc file for keystone v3  https://review.openstack.org/29373221:54
*** asalkeld has joined #kolla21:55
SamYapleso good news everyone, it was a pita, but i successfully changed all of my passwords on a running openstack cluster21:59
SamYaplethere was downtime involved, but it is doable21:59
vhosakotmeeting ?22:01
SamYaplevhosakot: one hour22:01
SamYaple2300 UTC22:02
SamYaple(you forgot about DSL probably)22:02
vhosakotah ok22:02
vhosakot:)22:02
ntpttrSamYaple: success, the workaround worked22:03
ntpttrSamYaple: thanks!22:04
SamYaplentpttr: cool. sorry for the trouble. it really is an ansible bug22:04
ntpttrSamYaple: yeah that's definitely clear if changing the order of hosts is what fixed it22:05
sdakeSamYaple password change on running openstack is sweet22:06
sdakeneed a blueprint for that22:06
SamYaplentpttr: yea still its a bit annoying22:06
sdakesarbanes oxley requirees password changes every 3 months22:06
SamYaplehopefully that alone doesnt taint your kolla experince!22:06
SamYaplesdake: for that to happen we have to switch to shade modules entirely22:07
openstackgerritMerged openstack/kolla: Fix stable/liberty gate  https://review.openstack.org/29318922:07
SamYaplenot all shade modules exist for what we need yet22:07
sdakeSamYaple ya this is work for newton22:07
SamYaplei have several patches into shade and ansible to address this22:07
SamYaplebut mitaka and liberty will remain PITA to update passwords22:07
ntpttrSamYaple: so my deployment just finished, running kolla/tools/init-runonce is telling me "22:07
ntpttrneutron not installed. please install neutron before proceeding". Do I need to run that command on a network node?22:07
SamYaplentpttr: pip install neutron22:08
SamYapleits just expecting clients on your host22:08
*** vhosakot has quit IRC22:08
sdakeno22:08
SamYaplekolla will not touch your host22:08
sdakepip install python-neutronclient22:08
ntpttrSamYaple: oh makes sense!22:08
SamYapleyea thats right what sdake said ntpttr22:08
SamYapleit just needs the openstack clients is all22:08
ntpttrI already did the pip install python-openstackclient22:08
SamYapleclient(s022:08
ntpttrI need to do the individual service ones as well?22:08
sdakethat doesn't get em all22:08
sdakeosc doesn't yet have all the clients22:09
ntpttrcool22:09
SamYapleas in python-novaclient, python-neutronclient etc22:09
sdakeyou need nova and neutronclients to run init-runonce22:09
SamYaplesdake: it _does_ actually do everything our init script does22:09
sdakewe coud probably port it to osc, but have not done so yet22:09
SamYaplewe just have to update teh init script22:09
sdakeright22:09
sdakedefinately dont install python-keystoneclient22:09
sdakethat wont work at all ;)22:10
*** ccesario has joined #kolla22:10
SamYaplecorrect. we removed all v2 keystone bits in mitaka22:10
ntpttrcool, so now aftetr running it it runs, but after creating the glance image I get22:10
ntpttrConfiguring neutron.22:10
ntpttr<html><body><h1>503 Service Unavailable</h1>22:10
ntpttrNo server is available to handle this request.22:10
ntpttr</body></html>22:10
SamYaplentpttr: youll need to do some troubleshooting22:10
SamYapleneutron agents-list is where id start22:10
ntpttrall right, thanks for all the help!22:11
SamYaplentpttr: most commonly at this stage (right after initial deployment) there may have been a rabbitmq issue22:11
SamYapleso you might have to do some service restarting, but the logs and normal troubleshooting steps apply here22:11
ntpttryeah even issuing any neutron command is telling me no server is available22:11
ntpttrand nova service-list works, but says all my services are enabled but down22:12
inc0rabbit22:12
inc0definetly22:12
SamYaplesounds like rabbit yea22:12
SamYaplentpttr: check the logs for nova or neutron22:12
SamYaplealso the normal rabbitmq commands for debugging22:12
SamYapledocker exec -it rabbitmq rabbitmqctl cluster_status22:13
SamYapleI would recommend making an alias for commands like that, its what i do22:13
SamYaplealias rabbitmqctl="docker exec -it rabbitmq rabbitmqctl"22:13
SamYaplethat way you can do `rabbitmqctl cluster_status`22:13
inc0also docker exec -it rabbitmq bash  -> then navigate to /var/log/kolla22:13
inc0and look there22:13
ntpttrdo rabbit failures happen ofter after installation?22:13
SamYaplentpttr: only when networking on the backend is complicated22:14
SamYaplethey never happen for me, but its 2 switch setup22:14
*** SiRiuS_ has quit IRC22:14
ntpttryeah our networking is a little complicated, the networks are all vlan tagged and there's a lot of them22:14
SamYaplereally what we need to do is check rabbitmqs health before proceeding with the role to catch that early22:15
*** prithiv has joined #kolla22:15
SamYapleinc0: could you file a bug for that since you just did the rabbitmq work?22:15
SamYapleor implement that :P22:15
ntpttryep here's the rabbit cluster status22:15
ntpttrhttp://paste.openstack.org/show/490808/22:15
ntpttrconnection refused22:15
SamYapleinc0: i was thinking about recommending people look directly at /var/lib/docker/volume/kolla_logs/_data directly for logs22:15
inc0ntpttr, do you have all hostnames resolvable by hosts?22:16
SamYaplentpttr: right. so likely this is the hostname issue inc0 is resolving as we speak22:16
SamYaplewe are using ips because somepeople dont have resolveable hostnames thorught there cluster22:16
ntpttrinc0: I used IP addresses22:16
SamYaplentpttr: for now, you can update all your /etc/hosts files with all the hostnames and ip adresses22:16
*** dims_ has joined #kolla22:16
ntpttrand yeah they're all resolvable22:16
SamYaplentpttr: THIS specifically is a kolla thing22:16
*** prithiv has quit IRC22:16
*** prithiv has joined #kolla22:16
SamYaplentpttr: you can resolve 'jfz1r02h03' on all boxes?22:17
ntpttrnot sure why it tried to connect to that hostname22:17
inc0ntpttr, it uses hostname22:17
SamYaplentpttr: yea this is a kolla issue you see, inc0 should have a patch momemtarily22:17
inc0that's a bug in kolla, we're fixing it now so it will use ips instead22:17
ntpttrthere you have it then, I thought that'd be okay because I used IPs in my inventory file22:17
SamYapleyea thats on us ntpttr22:18
SamYapleworkaround is add all your hosts to /etc/hosts file22:18
ntpttrhaha no problem, there's always work to do22:18
*** dims has quit IRC22:18
ntpttrI'll add all the hosts to the files and reinstall22:18
inc0remember to run clear before22:18
ntpttrthe plus side is that installation is so quick that hardly matters ;)22:18
SamYapleyou shouldnt need to rerun anything ntpttr22:18
ntpttryep22:18
SamYapleit should recover22:18
ntpttroh nice!22:18
SamYapleyou may need to restart the containers but thats it22:18
SamYapleat this point its a 100% operational openstack cloud.... with a rabbitmq issue (so like most clouds)22:19
SamYaplebasic troubleshooting applies22:19
SamYaplentpttr: i am a bit worried your neutron database didnt truly get bootstrapped because of that issue22:22
SamYaplewould you mind doing a 'show tables;' on the database to confirm it is populated22:22
sdakebootstrapping isn't as robust as i'd like22:23
sdakeI hope upgrade migration is as robust as i'd like22:23
sdakesince bootstrap happens once, upgrade happens often22:23
SamYaplein this case the upgrade script is my recommendation to fix bootstrap22:24
SamYaplesince it will db_sync22:24
SamYaplethats only if tables are missing22:24
ntpttrsure, one moment almost done filling in /etc/hosts22:24
SamYaplentpttr: > not using ansible to populate all hosts22:24
SamYaplentpttr: > 201622:24
ntpttrSamYaple: :( you caught me, I'm still an ansible noob22:25
ntpttrI should do it with ansible for more practice for sure22:25
SamYaplehaha im just messing around22:25
SamYaplei wouldnt have either, i would have used tmux with a 9-way split22:25
ntpttrhah, it's true tho22:25
*** daneyon has quit IRC22:25
ntpttrSamYaple: so do I need to attach to a container to run that show tables command? how do I connect to the database22:27
SamYaplesame as before, docker exec -it mariadb mysql -h<kolla_internal_vip> -p<database_password>22:27
SamYapleyou can also use any mysql client from your host system22:27
SamYaplebut we dont install those22:27
SamYaplei personally use an alias there to as well22:28
SamYaplealias mysql='docker exec -it mariadb mysql'22:28
ntpttrkk, yeah I definitely should use those aliases22:28
SamYapleill post my list22:28
SamYaplentpttr: http://paste.openstack.org/show/490811/22:29
ntpttrSamYaple: thanks. Is this what you were looking for? http://paste.openstack.org/show/490812/22:30
SamYaplentpttr: hmm im not sure22:31
SamYaplei dont think so22:31
ntpttrI think I got the password wrong, what's the default22:31
SamYaplepassword :P22:31
SamYapledocker exec -it mariadb mysql -h<kolla_internal_vip> -p<database_password>  -e 'show tables;' neutron22:32
SamYaplethat should either return a list of tables, or nothign22:32
SamYapleif its nothing it hasnt been bootstrapped22:32
SamYapleas you can tell, kolla modifies your workflow a bit. but with aliases its largely unnoticable22:32
sdaketwo bags of chips = sdakes meal for the day22:32
ntpttryeah I bet it wouldn't be too much to get used to22:33
ntpttrmysql doesn't seem to like that command though22:34
ntpttrdocker exec -it mariadb mysql -h 172.16.2.203 -p password -e 'show tables;' neutron22:34
SamYapleno space between -p and password22:34
SamYaple docker exec -it mariadb mysql -h 172.16.2.203 -ppassword -e 'show tables;' neutron22:34
SamYapleits a mysql client thing, not a docker thing22:34
inc0no space after -h I think too22:35
ntpttrgotcha. access denied :( I didn't change the defaults22:35
SamYaplecheck /etc/kolla/passwords.yml on the deploy node22:35
sdakeya bootstrap = fragile22:35
inc0.203 is your floating22:35
inc0?22:35
SamYaplesdake: thats not whats going on22:35
ntpttryeah I had gotten rid of the space after h22:35
ntpttryeah that's it inc022:35
SamYaplerecommend checking passwords.yml to confirm password. if you ran the playbooks to neutron then you connected to the db with the password in passwords.yml22:36
ntpttrthe database password is indeed password22:36
SamYapleoh sorry ntpttr22:36
SamYapledocker exec -it mariadb mysql -h 172.16.2.203 -ppassword -u root -e 'show tables;' neutron22:36
SamYaplewe dropped the root user out so it was connecting with wrong user22:37
ntpttrthat did it! it's filled in22:37
SamYapleok cool22:37
SamYapleall that work to say "youre good dont worry about it" :P22:37
ntpttrrabbit cluster is still down though22:37
SamYapledid you restart the nodes?22:37
SamYaplerabbitmq containers*22:37
SamYapledocker restart rabbitmq22:37
inc0you need to redeploy rabbit22:37
inc0/etc/hosts didnt get copied22:38
SamYapleyou shouldnt need to redeploy rabbitmq22:38
SamYapleoh right yes inc0 is right22:38
SamYaple/etc/hosts in the container is wrong22:38
ntpttrto redeploy one service do i manually delete the containers22:38
inc0yeah22:38
SamYaplentpttr: `docker rm -f rabbitmq` on all your nodes running rabbitmq22:38
*** JoseMello has quit IRC22:39
SamYaplethen jsut rerun playbooks22:39
ntpttror can I pass something in to the cleanup containers22:39
ntpttrokay got it22:39
SamYaplesorry ntpttr we arent that fancy yet :)22:39
inc0then kolla-ansible deploy -t rabbitmq22:39
inc0it will just deploy rabbitmq22:39
SamYapleif you want to limit yes, you can tag just rabbitmq22:39
*** v1k0d3n has quit IRC22:39
*** v1k0d3n has joined #kolla22:39
*** spisarski has quit IRC22:40
ntpttrokay the playbook is off and running22:40
ntpttrhow long until the nodes should come up, it still says down after redeploying22:41
inc0nova nodes?22:41
sdakentpttr fwiw I had a demo fail because of  a wireless drop out - and i ceanup-containers and redeployed in under 4 minutes :)22:41
ntpttrsdake: I'm thinking of doing that haha. The speed is definitely a big plus22:42
sdakentpttr it is alot faster to use overlayfs backend storage driver too22:42
inc0aio for me take ~4 min for full deploy22:42
sdakedave-mccowan said 8x faster22:42
ntpttrsdake: where do I configure that?22:42
sdakeaio takes 4 minutes for me to deploy on overlay22:42
sdakentpttr its a docker option -s overlay22:43
sdakentpttr  depends what your distro is22:43
inc0you'd need to rebuild all of containers22:43
sdakebut you would have to reubild your images22:43
*** v1k0d3n_ has joined #kolla22:43
ntpttrsdake: ubuntu 14.0422:43
ntpttrI don't mind rebuilding22:43
SamYaplentpttr: if you want to redeploy i wont stop you22:43
sdakeunless your containers are in a docker registry22:43
inc0also for overlay I think you need to create overlay device22:43
sdakeinc0 you dont have to do naything for overlay22:43
SamYaplethough i assure you you _can_ recover what you have without much work22:43
sdakeinc0 it just uses the filesystem in place22:43
SamYaple*only ext422:43
inc0ok22:44
sdakeok didn't know that22:44
sdakei am on ext422:44
SamYapleyup22:44
SamYapleits the only one thats supports overlag in docker atm22:44
*** v1k0d3n has quit IRC22:44
inc0overlag doesn't sound promissing :P22:44
SamYapleWE REQUIRE MORE BANDWIDTH22:44
sdakeext4 works well enough ;-)22:44
sdake980 down 960gbit up ;)22:45
sdakeg/m22:45
SamYapleyou said you couldn't break 600mbit on your nodes22:45
sdake6000mbit22:46
sdakebut my switch isn't configured for jumbo frames22:46
sdakeor optimized at all22:46
sdakebut my internet connection is nearly gige22:47
sdakei only have 8 ports of 10gig22:47
SamYapleso where did you pull the 980 from?22:47
sdakethat is what speedtest shows22:47
sdakethat website thing22:47
sdakeon my workstation connected over gige22:48
sdakemaybe its kbit?22:48
sdakenot sure22:48
sdakedon't recall at present22:48
sdake980kbit would be gige right?22:48
sdakeif so, its 980kbit ;)22:48
SamYaple980mbit*22:48
inc0no...it would be meg;)22:48
sdakeright22:48
sdakewell thats whati've got22:48
sdakemy lab mahcines do 6000mbit between them22:49
sdakenot 600mbit22:49
inc0ntpttr, so, 4 minutes passed22:49
inc0should be deployed by now:22:49
inc0:P22:49
ntpttrinc0: but I'm deploying on 10 nodes not one22:49
sdakentpttr would love o have benchmarks on 10 node deploy22:49
sdakei dont have that much gear22:49
inc0ntpttr next time you can do kolla-ansible pull22:49
*** Jeffrey4l has joined #kolla22:49
inc0so it wont transfer images over net any more22:49
sdakeJeffrey4l sup dude22:49
SamYapledid you rebuild the images ntpttr or something?22:50
*** sbezverk has quit IRC22:50
ntpttrSamYaple: no they're in a registry22:50
sdakeaio takes 4 minutes - 10 node deploy takes ???? -> profit22:50
inc0yeah on second thought they should be pulled anyway22:50
inc0shouldn't be much more22:51
Jeffrey4lwhats ntpttr? sdake , do not get your point.22:51
sdakeJeffrey4l its a joke22:51
sdakefrom where I dont know22:51
sdakesomething about underpants gnomes22:51
sdakeits a US thing22:51
*** gfidente has quit IRC22:51
inc0right now I'm even afraid to ask22:51
Jeffrey4l:D. just wake up22:51
ntpttrayy it's done, and it seems to be working22:52
sdakeJeffrey4l https://en.wikipedia.org/wiki/Gnomes_(South_Park)22:52
sdakentpttr next time you do a 10 node deploy can you run time before the kolla-ansible command?22:52
sdaketime sudo kolla-ansible deploy22:52
sdakei'm curious how long it takes22:52
ntpttrsdake: for sure. I would say about 7-10 minutes22:52
sdakesuper super curios22:52
sdakecool thats fantastic info22:52
sdakethanks!22:52
SamYaplentpttr: awesomeness22:53
Jeffrey4lthat's cool ntpttr22:53
sdakehey guys - t-7 minute seto meeting, to not kill time can folks please update their blueprints status22:53
ntpttrtbh this is super refreshing, I literally strggled for a month getting OSA to work with all the networking preconfig stuff you have to do, this was up and running in one day with no previous kolla experience22:54
ntpttrthanks for the help guys22:54
ntpttrvery cool22:54
* sdake prints out a screenshot for the office cubicle22:54
ntpttri'm definitely interested in getting involved if i can22:55
SamYaplentpttr: I used to work at RAX. Kolla is the culmination of all my bad OSA experinces22:56
*** pbourke-mobile has joined #kolla22:56
sdakentpttr are you using master?22:57
ntpttrsdake: yes22:57
*** pbourke-pub has joined #kolla22:57
*** vhosakot has joined #kolla22:57
*** pbourke-mobile has quit IRC22:58
SamYaplemeeting time22:59
SamYaplejoin us in #openstack-meeting-4 ntpttr23:00
ntpttrSamYaple: thanks will do23:00
SamYaplei will make a contributor out of you yet ntpttr!23:01
SamYaplefeel free to ping me here to while the meetings going on if youre still working on your cluster23:01
*** akwasnie has joined #kolla23:01
*** v1k0d3n_ has quit IRC23:04
openstackgerritSerguei Bezverkhi proposed openstack/kolla: [WIP] iscsi container with lvm2 support  https://review.openstack.org/29128523:05
*** sbezverk has joined #kolla23:06
*** blahRus has quit IRC23:07
sbezverksdake SamYaple I cleaned up lvm-iscsi patch, there is no dependecy on "root" and other small things are addressed.23:07
sbezverkat least I hope23:07
sbezverkI was wondering if I could ask somebody to  test it?23:08
SamYaplesbezverk: now youll have to move all of the sockets to named volumes and stop all the host mounting stuff23:08
sbezverkSamYaple, I think it is done, I might have missed some23:09
sbezverkhopefully review will tell ;-)23:09
SamYaplesbezverk: ok i havent reviewed it yet :)23:09
SamYaplewe are in #openstack-meeting-4 sbezverk23:09
SamYapleplease join us23:10
vhosakotsbezverk: /join #openstack-meeting-423:13
sbezverkalready there, thank you and sorry for being late23:14
vhosakotcool, np23:16
SamYaplesbezverk: no problem at all!23:17
*** v1k0d3n has joined #kolla23:18
*** rajathagasthya has joined #kolla23:24
*** AndChat|241401 has joined #kolla23:25
*** ccesario has quit IRC23:25
*** nkorabli has joined #kolla23:27
*** pbourke-pub- has joined #kolla23:35
*** achanda has quit IRC23:36
*** pbourke-pub- has quit IRC23:36
*** pbourke-pub- has joined #kolla23:36
*** diogogmt has quit IRC23:38
*** pbourke-pub has quit IRC23:39
*** pbourke-pub- has quit IRC23:44
*** jtriley has joined #kolla23:45
*** jtriley has quit IRC23:52
openstackgerritSam Yaple proposed openstack/kolla: Add generate.py to generate passwords  https://review.openstack.org/29372823:52
*** salv-orl_ has joined #kolla23:54
*** salv-orlando has quit IRC23:57

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