Monday, 2016-03-28

*** vhosakot has quit IRC00:01
*** achanda has quit IRC00:03
*** cfarquhar has joined #kolla00:07
*** cfarquhar has quit IRC00:07
*** cfarquhar has joined #kolla00:07
*** iceyao has joined #kolla00:18
*** iceyao has quit IRC00:22
*** vishwanathj has joined #kolla00:27
*** allen_gao has quit IRC00:31
*** allen_gao has joined #kolla00:37
*** allen_gao has quit IRC00:42
*** vhosakot has joined #kolla00:42
*** allen_gao has joined #kolla00:49
*** allen_gao has quit IRC00:54
*** allen_gao has joined #kolla01:01
*** achanda has joined #kolla01:01
*** vhosakot has quit IRC01:09
*** weiyu_ has joined #kolla01:18
*** achanda has quit IRC01:39
*** cfarquhar has quit IRC01:52
*** allen_gao has quit IRC02:07
*** sdake has joined #kolla02:11
*** allen_gao has joined #kolla02:17
*** sdake has quit IRC02:18
*** achanda has joined #kolla02:26
*** klint has joined #kolla02:43
*** vishwanathj has joined #kolla02:48
*** weiyu_ has quit IRC02:55
*** cfarquhar has joined #kolla02:55
*** cfarquhar has quit IRC02:55
*** cfarquhar has joined #kolla02:55
*** weiyu_ has joined #kolla03:02
openstackgerritAllen Gao proposed openstack/kolla-mesos: Fix the deprecated security_group_api and network_api_class  https://review.openstack.org/29045403:12
openstackgerritHui Kang proposed openstack/kolla: Add Kuryr Docker container  https://review.openstack.org/29800003:22
*** cbaesema has joined #kolla03:23
openstackgerritGerard Braad proposed openstack/kolla: Use packaged pip instead of easy_install  https://review.openstack.org/29752303:25
*** achanda has quit IRC03:44
*** yuanying has quit IRC03:53
*** allen_gao has quit IRC03:58
*** Jeffrey4l has joined #kolla04:02
openstackgerritJeffrey Zhang proposed openstack/kolla: Implement nova-ssh container  https://review.openstack.org/29796304:05
openstackgerritJeffrey Zhang proposed openstack/kolla: Restrict the rabbitmq only start on rabbitmq group  https://review.openstack.org/29792904:06
*** salv-orlando has joined #kolla04:06
*** allen_gao has joined #kolla04:06
*** salv-orlando has quit IRC04:06
*** salv-orlando has joined #kolla04:07
*** salv-orl_ has quit IRC04:09
*** salv-orlando has quit IRC04:12
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Fix gate to use world writeable docker socket  https://review.openstack.org/29809804:17
*** coolsvap has joined #kolla04:22
openstackgerritJeffrey Zhang proposed openstack/kolla: Only copy the necessary config files for Glance  https://review.openstack.org/29698204:28
openstackgerritJeffrey Zhang proposed openstack/kolla: Refactor the glance service group mapping  https://review.openstack.org/29810004:28
*** weiyu_ has quit IRC04:30
*** vishwanathj is now known as vishwanathj_zzz04:33
*** yuanying has joined #kolla04:56
openstackgerritMerged openstack/kolla: Use packaged pip instead of easy_install  https://review.openstack.org/29752305:00
openstackgerritMD NADEEM proposed openstack/kolla: Add optional services option in globals.yml  https://review.openstack.org/29810405:27
*** achanda has joined #kolla05:31
*** yuanying has quit IRC05:40
*** yuanying has joined #kolla05:48
*** allen_gao has quit IRC05:54
*** weiyu_ has joined #kolla05:59
*** allen_gao has joined #kolla06:04
*** allen_gao has quit IRC06:17
*** salv-orlando has joined #kolla06:21
*** kjejlly_ has joined #kolla06:24
*** kjelly has quit IRC06:25
*** Marga_ has quit IRC06:32
*** salv-orlando has quit IRC06:34
*** cristicalin has joined #kolla06:45
*** reddy has joined #kolla06:49
*** vishwanathj_zzz has quit IRC06:52
openstackgerritMerged openstack/kolla: Add reno support  https://review.openstack.org/29795906:56
*** Liuqing has joined #kolla06:59
*** allen_gao has joined #kolla07:01
*** smekel_ has joined #kolla07:06
*** allen_gao has quit IRC07:35
*** phuongnh has joined #kolla07:39
*** allen_gao has joined #kolla07:47
*** cristicalin has quit IRC07:47
*** salv-orlando has joined #kolla08:01
*** salv-orlando has quit IRC08:07
*** stvnoyes has quit IRC08:10
*** stvnoyes has joined #kolla08:11
*** nihilifer has quit IRC08:16
*** nihilifer has joined #kolla08:17
*** reddy has quit IRC08:25
*** yuanying has quit IRC08:31
*** yuanying has joined #kolla08:31
*** yuanying has quit IRC08:32
*** jmccarthy has quit IRC08:37
*** jmccarthy has joined #kolla08:38
*** yuanying has joined #kolla08:39
*** mikelk has joined #kolla08:53
*** mikelk has quit IRC08:55
*** achanda has quit IRC09:04
*** achanda has joined #kolla09:11
*** yuanying has quit IRC09:16
*** kproskurin has joined #kolla09:16
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Bump rabbitmq version in rabbitmq-env.conf  https://review.openstack.org/29816509:24
*** achanda has quit IRC09:28
openstackgerritMerged openstack/kolla-mesos: Fix the deprecated security_group_api and network_api_class  https://review.openstack.org/29045409:29
*** kproskurin_ has joined #kolla09:33
*** phuongnh has quit IRC09:34
*** kproskurin has quit IRC09:35
*** kproskurin_ is now known as kproskurin09:35
*** salv-orlando has joined #kolla09:36
*** weiyu__ has joined #kolla09:40
*** weiyu_ has quit IRC09:40
*** weiyu__ has quit IRC09:45
*** salv-orlando has quit IRC09:46
*** weiyu_ has joined #kolla09:57
*** allen_gao has quit IRC10:10
*** allen_gao has joined #kolla10:15
*** pbourke has quit IRC10:16
*** pbourke has joined #kolla10:16
*** Liuqing has quit IRC10:25
*** achanda has joined #kolla10:28
*** achanda has quit IRC10:33
*** mbound has joined #kolla10:35
*** achanda has joined #kolla10:36
*** Liuqing has joined #kolla10:51
*** coolsvap has quit IRC10:54
*** coolsvap has joined #kolla11:06
*** salv-orlando has joined #kolla11:11
*** achanda has quit IRC11:11
*** salv-orlando has quit IRC11:13
*** Liuqing_ has joined #kolla11:15
openstackgerritSerguei Bezverkhi proposed openstack/kolla: iscsi container with lvm2 support  https://review.openstack.org/29128511:16
*** Liuqing has quit IRC11:16
*** weiyu_ has quit IRC11:24
*** rhallisey has joined #kolla11:25
*** SiRiuS_ has joined #kolla11:35
openstackgerritCarlos Cesario proposed openstack/kolla: Change keystone log dir  https://review.openstack.org/29796711:52
*** mlima has joined #kolla11:53
*** Liuqing_ has quit IRC12:02
*** coolsvap has quit IRC12:08
*** achanda has joined #kolla12:12
*** kproskurin has quit IRC12:13
*** ccesario has joined #kolla12:14
*** kproskurin has joined #kolla12:14
kproskurinHello guys, I have a question about new keystone bootstrap12:14
kproskurinhttps://github.com/openstack/kolla/blob/master/docker/keystone/keystone_bootstrap.sh12:15
*** mbound has quit IRC12:15
kproskurinSo here we expect vars for admin-url + internal-url + public-url12:16
kproskurinBut at current keystone-manage(ver 9.0.0) there is no such parameters12:17
kproskurinSo I recive:  "keystone-manage: error: unrecognized arguments: --bootstrap-admin-url RegionOne --bootstrap-internal-url --bootstrap-public-url --bootstrap-service-name keystone --bootstrap-region-id"12:17
*** achanda has quit IRC12:17
*** mbound has joined #kolla12:36
*** salv-orlando has joined #kolla12:50
*** salv-orlando has quit IRC12:53
*** rhallisey has quit IRC12:53
*** rhallisey has joined #kolla12:53
*** mbound has quit IRC12:53
*** klint has quit IRC13:04
*** vhosakot has joined #kolla13:09
SamYaplekproskurin youre just using an old version of keystone-manage is all https://github.com/openstack/keystone/blob/9.0.0.0rc1/keystone/cmd/cli.py#L10313:12
kproskurinSamYaple, strange, it says version 9.0.013:13
SamYaplekproskurin: 9.0.0 hasnt been released yet13:13
SamYapleits a dev version for sure13:13
SamYaplelots of times these tools chop off the x.x.xdev34 type strings13:14
SamYapleso it looks like 9.0.0 buti ts not13:14
*** weiyu_ has joined #kolla13:14
*** achanda has joined #kolla13:15
kproskurinSamYaple, oh, ok. Ill check this13:15
*** achanda has quit IRC13:19
*** dwalsh has joined #kolla13:20
*** ayoung has joined #kolla13:22
*** vishwanathj_zzz has joined #kolla13:22
*** absubram has quit IRC13:24
*** vhosakot has quit IRC13:25
*** banix has joined #kolla13:26
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: Changing log levels in CLI  https://review.openstack.org/29823113:27
*** jtriley has joined #kolla13:31
*** pbourke-home has joined #kolla13:43
*** openstackgerrit has quit IRC13:48
*** openstackgerrit has joined #kolla13:48
*** mbound has joined #kolla13:54
*** mbound has quit IRC13:59
openstackgerritHui Kang proposed openstack/kolla: Add Kuryr Docker container  https://review.openstack.org/29800014:08
*** jtriley has quit IRC14:12
sbezverkGood morning14:20
sbezverkSamYaple I see failure of my patch on gate-kolla-docs, when I try to access logs it says file not found? Any ideas why this is happening?14:21
*** jtriley has joined #kolla14:22
SamYaplesbezverk: would need link14:22
sbezverkSamYaple here you go: https://review.openstack.org/#/c/291285/4414:23
patchbotsbezverk: patch 291285 - kolla - iscsi container with lvm2 support14:23
*** vishwana_ has joined #kolla14:26
*** vishwana_ has quit IRC14:26
ccesariosbezverk, I had the same problem yesterday ..... It seems a gate problem according vhosakot explained me...14:28
*** vishwanathj_zzz has quit IRC14:29
*** vishwanathj has joined #kolla14:29
sbezverkccesario thank you for letting me know, I was scratching my head trying to figure out how I managed to screw up docu :-)14:30
ccesariosbezverk, eheheheh, maybe SamYaple can confirm it :)14:31
openstackgerritHui Kang proposed openstack/kolla: Add Kuryr Docker container  https://review.openstack.org/29800014:31
*** sdake has joined #kolla14:42
*** rstarmer has quit IRC14:46
*** sdake has quit IRC14:46
*** sdake has joined #kolla14:47
*** JoseMello has joined #kolla15:01
*** pbourke-home has quit IRC15:03
*** inc0 has joined #kolla15:04
*** ph03n1x has joined #kolla15:08
*** weiyu_ has quit IRC15:09
*** Marga_ has joined #kolla15:12
*** Marga_ has quit IRC15:13
*** Marga_ has joined #kolla15:13
*** ssurana has joined #kolla15:14
*** achanda has joined #kolla15:17
inc0good morning15:18
-openstackstatus- NOTICE: Gerrit is restarting on review.openstack.org in an attempt to address an issue reading an object from the ec2-api repository15:20
*** achanda has quit IRC15:22
*** absubram has joined #kolla15:23
*** blahRus has joined #kolla15:28
*** salv-orlando has joined #kolla15:32
Marga_Hi!15:34
*** salv-orlando has quit IRC15:41
*** mdnadeem_home has joined #kolla15:48
*** vhosakot has joined #kolla15:49
*** ph03n1x has quit IRC15:53
*** Serlex has joined #kolla16:00
*** mdnadeem_home has quit IRC16:01
*** pbourke-home has joined #kolla16:03
*** pbourke-home has quit IRC16:05
mlimahelo guys, i have this error16:06
mlimaTASK: [mariadb | Running MariaDB bootstrap container16:06
mlimafull log -> http://pastebin.com/5428NGhx16:07
mlimaaio, enable_haproxy: "yes"16:07
inc0mlima, "address already in use"16:08
inc0do you have mysql running on host already?16:08
inc0netstat -nalp | grep 330616:09
inc0or if you are running haproxy16:09
inc0what kolla_external_addess do you have?16:09
inc0is it unused addr from your network?16:09
sdakemorning folks16:10
mlimahmm, i didn't change it16:10
mlimathank you inc016:10
inc0yeah, that's it, haproxy bound to 330616:11
inc0you can either turn it off for aio or give non-used address and keepalived will manage it16:11
inc0this way haproxy will bind to this addr:3306 and host-ip:3306 mariadb will take16:12
sdakekolla_external_address doesn't nee to be changed if you leave it commented out16:12
sdakekolla will dot he right thing, only kolla_internal_address really needs to be set16:12
inc0well it would be good to have addr from your network16:12
inc0otherwise multinode will not work16:13
sdakekolla_external_address = kolla_internal_address if fkolla_external-address is unchanged16:13
inc0ok, you need to set one of them, thats what I'm saying16:13
inc0but yeah, sdake is right, kolla_internal_addess is more important16:13
*** Marga_ has quit IRC16:13
mlima:)16:13
sdakeif yous set kolla external address and dont set kolla internal address  I think kolla wouldbust16:13
*** ph03n1x has joined #kolla16:14
inc0yeah, that's true, my mistake16:14
inc0but you get the idea mlima :)16:14
mlimayes, inc0 :)16:14
vhosakotccesario: I tested the patch set in https://review.openstack.org/#/c/297967/4 and see that it does not work.. I have provided my comments in the review... let me know if you ahve any questions16:15
patchbotvhosakot: patch 297967 - kolla - Change keystone log dir16:15
manjeetsi updated the kolla repo and it works with mariadb . older which version which pip gets does not works with mariadb16:20
manjeetswithout removing two patches in mariadb16:21
manjeetsand now I am getting failure at very end soon will get the logs and post currently a run is going on16:21
ccesariovhosakot, thaks by comments....... but the current code already create the correct directory.....  https://github.com/openstack/kolla/blob/master/docker/keystone/extend_start.sh#L15-L25      or  I 'm wrong ?16:22
inc0manjeets, what's the failure?16:22
manjeetsjust getting to that re ran the deploy16:22
inc0was that on neutron deploy?16:22
manjeetsno on cinder16:22
inc0oh, ok so something else16:23
vhosakotccesario: that should create.. but the code is not hitting that part in the shell script... let me update to master and re-try... could you test as well if you get a chanbc16:23
inc0keep in mind that cinder is fleaky in containers16:23
inc0that's why we suggest to use ceph underneath16:23
ccesariovhosakot, I have tested before ask review16:23
manjeetsit will take probably 10 mins to get that failure16:23
ccesariothe all logs are in /var/log/kolla/keystone/16:24
manjeetsI saw neutron containers and nova got done suucessfully but while doing cinde it was ending up in error16:24
vhosakotnice... give me around 20 mins16:24
ccesariovhosakot, sure.16:24
manjeetsinc0: ok I don't need cinder for my case if that did not work i will disable cinder16:24
manjeetsgo with nova and neutron16:24
sdakemanjeets my bro16:25
inc0manjeets, well it should deploy tho16:25
sdakemanjeets i need some benchmarks out of your 64 node cluster when you have an opportunity16:25
manjeetsokay it takes approax  23 minutes to finish run for those nodes16:26
sdaketo deploy 3 controlller nodes?16:26
manjeetstrying to get time on every run16:26
sdakeand the compute nodes16:26
manjeetsno all 64 nodes16:27
sdakeyou deployed controller on 64 nodes?16:27
manjeetsyes it was ending in issue for storage have not got that completely yet16:27
manjeetsanother run is in process16:27
manjeetswill post the issue16:28
sdakecontrollers should be 3 or max 516:28
sdakecompute andn storage shold e the remainder16:28
inc0well you dont need storage for cinder-less stiuff16:28
inc0what I do on this kind of hardware is I use every compute node as ceph osd16:29
inc0which translates to every compute node being storage node16:29
manjeetsso we can't have more than 5 control nodes ?16:31
sdakeyou can16:31
sdakei just dont recommend it ;)16:32
inc0manjeets, there is no need for 5 controllers16:32
sdakemanjeets i want benchmarks on upgrade and reconfigure16:32
inc0waste of resources16:32
sdakefor upgrade, I need to show you how to generate an upgrade evnrionment probably via google hangouts16:32
manjeetsinc0: ok16:32
sdakei'd like the results for 3 controller nodes, and the remainder compute or storage nodes as needed16:33
manjeetswhat is threshold for network nodes ?16:33
manjeetsall i care is scaling and performance of network nodes16:33
*** SiRiuS_ has quit IRC16:38
manjeetsinc0: i see two failure today16:39
manjeetshttp://paste.openstack.org/show/492106/16:39
manjeetshttp://paste.openstack.org/show/492107/16:40
sdakemanjeets i also need you to use the overlay graph driver for your deployment16:41
manjeetsoverlay graph driver ?16:41
sdake-s overlay flag to docker16:41
sdakerm -rf /var/lib/docker16:42
sdakesudo systemctl stop docker first16:42
sdakethe nrm16:42
sdakethe nstart it up again ater adding -s overlay flag16:42
sdakedont use it on your build nodes16:42
sdakeonly your deploy targets16:42
sdakeit should be faster16:42
sdakeso if you have 1-2 hours to go over what i want in terms of benchmarks today or osme otherday let me know16:43
SamYaple/msg/win 1116:43
SamYaplemorning16:43
sdakeyo SamYaple16:43
sdakeSamYaple manjeets ha a 64 node deployment - 23 minutes to deploy16:44
sdakeand he is deploying contorller nodes on 64 nodes lol16:44
inc0sdake, no, hes not16:44
inc0he's doing 7 controllers16:44
sdakeok16:44
inc0but still too much16:45
sdakehe said above he wa doing 64 controllers16:45
sdakebut when i looked at his environment previously he was doing 716:45
manjeetsinc0: will chqange it16:45
inc0you misunerstood each other16:45
manjeetsto 3 or 516:45
sdake5 gives you super ha16:45
sdake3 givees you ha ;)16:45
manjeetsokay16:45
inc0manjeets, yeah that should be enough...these are damn powerful machines16:45
inc0sdake, not really....it don't really matter that much 3v516:45
inc0doesn't16:46
manjeetscan i have more network nodes ?16:46
manjeetswhat is recommendation for network >16:46
inc0manjeets, 2 network nodes is enough, it's active-passive anyway16:46
manjeetsmy problem is to check the scale and network performance mainly16:46
inc0with dvr?16:46
inc0or without?16:46
manjeetswith dvr16:46
inc0so dvr's mostly reside on compute nodes16:47
inc0number of network nodes won't greatly increase network throughput16:47
inc0also...vlans or vxlans?16:47
sdakesbezverk irc dude ;)16:49
sdakesbezverk i'll eview that iscsi patch when i hit the reviw queue this morning16:49
manjeetsvxlans16:49
manjeetswith ovs and linuxbridge separately16:50
inc0try both;)16:50
inc0well, bottom line16:50
manjeetsso here is my new set of deployment16:50
manjeets3 control16:50
inc02-3 net nodes should be enough16:50
manjeets3 network16:50
manjeets50 computes16:50
manjeetsrest storage16:50
manjeets?16:50
sdakemanjeets can you do that with overlayfs16:50
manjeetssure16:51
inc0you don't need stor at all without cinder or swift16:51
inc0so I'd say put all the rest to compute16:51
sdakemanjeets lets setup a google hangout so i can make sure ou do it correctly plz :)16:51
sdakeits not documented really anywhere16:51
manjeetsinc0: ok just doing prechecks and cleanup16:52
manjeetssdake when you will be free ?16:52
*** unicell has quit IRC16:53
gmmahasdake: inc0: I and ntpttr were just trying a deploy and were wondering how you guys feel about making pre-check as the first step of deploy always?16:54
gmmahaso that if somethign is off, we dont even try to deploy but fix the hosts before the deploy actually happens16:54
sdakewhisky tango foxtrot http://logs.openstack.org/98/298098/1/check/gate-kolla-dsvm-deploy-centos-binary/4f8dc1a/console.html#_2016-03-28_07_10_43_38116:54
sdakegmmaha it takes too long imo16:55
inc0gmmaha, we do something like this in rabbitmq hosts16:55
inc0I'm actually good with that16:55
inc0but not as first step, but nova prechecks before nova deploy and such16:55
gmmahasdake: true.. we add some overhead, but thought its better than half deploy to find something is wrong, then clean the containers & hosts, run cehck, fix and then start again!16:56
gmmaha :)16:56
inc0also I started to make post-deploy tests so it will stop deployment if for example rabbit doesn't work after deploy16:56
gmmahainc0: just stop when that piece fails?16:56
inc0gmmaha, yeah, pretty much16:56
gmmahainc0: hmm.. so lets say it happens and fails.. whats the next steps?16:57
sdakeoh nm that i the stable branch16:57
gmmahaFix that piece and restart the play just from that spot?16:57
inc0if you fail on preckeck, you will get clear message what's wrong16:57
inc0go and debug;)16:57
gmmahainc0: absolutely16:57
gmmahabut what if i didnt run pre-check and deploy fails somehow16:57
gmmahafor obvious reasons16:57
gmmahajust thtought that pre-emptively assujming that the deployer has a non-perfect state of hosts to deploy and running pre-check would be good for us16:58
inc0I agree with you16:58
inc0I'm ok with adding minute or two more to deploy16:58
inc0it is rocket fast anyway;)16:58
inc0and we can optimize16:59
inc0bottom line, this is good place to do some refactoring16:59
inc0because we do some precheck-style stuff in deploy as well16:59
sdakecan we finish mitaka first please ;)16:59
gmmahainc0: nice.. yeah agree with you on that16:59
manjeetsinc0: for me prechecks all green not error16:59
gmmahasdake: sorry didnt mean to digress a current plan.. Just thought it will be a great wish-list item16:59
inc0good for N17:00
inc0we need to do some refactoring anyway17:00
manjeetsi am starting a run 3 control  3 networks and rest compute17:00
inc0as we move to ansible 2.017:00
sdakemanjeets with overlayfs?17:00
openstackgerritMauricio Lima proposed openstack/kolla: Remove bootstrap_mariadb with cleanup-containers  https://review.openstack.org/29832817:00
manjeetsyes i am doing that change as well17:00
sdakeremember to stop the daemon17:01
sdakerm -rf /var/lib/kolla17:01
sdakesystemctl daemon-reload17:01
sdakerather /var/lib/docker17:01
*** salv-orlando has joined #kolla17:02
*** Marga_ has joined #kolla17:02
sdakebugs need fixing:17:03
sdakehttps://launchpad.net/kolla/+milestone/mitaka-rc317:03
manjeetssdake service docker restart -s ?17:03
manjeetsstart**17:03
sdakei dont know what -s flag does to restart17:03
manjeetsno start17:03
sdakethe way you can tell if overlay is being used is via p -ef | grep docker17:03
sdakeyou have to stop docker daemon17:03
sdakeyou have to rm -r /var/lib/docker17:03
sdakethen you have to start docker daemon17:04
sdake*ONLY ON YOUR DEPLOY TARGETS*17:04
sdakeinbetween the stop and start you need to add -s overlay to the start options17:04
sdakein docker17:04
sdakei am not quite sure hwo to do this on debuntian17:04
*** cbaesema has quit IRC17:05
*** ssurana has quit IRC17:07
manjeetsi ran docker daemon -storage-driver=overlay17:09
*** ssurana has joined #kolla17:10
sdake-s overlay17:11
sdakeno equal sign i think17:12
manjeetssadake docker daemon --storage-driver=overlay17:12
manjeetsis taking time17:12
sdakei think you dont need the equal sign17:12
manjeetsshowing something like http://paste.openstack.org/show/492116/17:13
sdakeoh your on ubuntu17:13
* sdake groans17:13
manjeetshow long it takes ?17:13
sdakeinc0 SamYaple do either off you knwo which ubuntu kernel is required to run with overlay?17:14
inc0well we suggest to run wily kernel anyway17:14
manjeetsI have wily17:14
manjeetswhich did on all nodes17:14
sdakedoes that support overlay?17:14
inc0if it's newer that wily (I doubt that) than I suggest to not run it17:14
manjeetsi don't think so it is17:14
inc0you may need to install different packages tho17:14
sdakeuese the flag -s overlay17:14
manjeetsis overlay fs is must or can i go without it ?17:15
sdakei have also heard your filesystem must be ext417:15
sdakemanjeets i want to see if fit prodcues a speed delta17:15
inc0manjeets, it's completely optional17:15
sdakepeople are speed freaks around deployment17:15
inc0may make build and deploy quicker17:15
*** salv-orlando has quit IRC17:16
manjeetsinc0 what packages are required for this ?17:16
sdakeinc0 i asked him to see what the delta is for deploy17:16
inc0manjeets, not sure...I use aufs;)17:16
manjeetsits heading no where just stuck saying that old message17:16
inc0old habits die hard;)17:16
sdakemanjeets pleae use -s overlay17:16
sdakenot --storage-ddriver=overlay17:16
manjeetsok17:16
sdakealso paste your /etc/fstab17:17
manjeetsi saw --storage-driver = overlay on docker doc17:17
manjeetssdake same thing happens i don't see any difference17:17
manjeetsdocker daemon -s overlay17:17
sdakehttp://askubuntu.com/questions/109413/how-do-i-use-overlayfs17:18
*** unicell has joined #kolla17:19
daneyonAny known issues running Kolla on Ubuntu 14.04.3 LTS (GNU/Linux 3.16.0-30-generic x86_64)17:19
sdakehttps://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/17:19
*** unicell has quit IRC17:19
*** unicell1 has joined #kolla17:19
inc0daneyon, for once we suggest in docs to upgrade kernel to wily17:20
vhosakotdaneyon: share /run.... mount --make-shared /run     in    http://docs.openstack.org/developer/kolla/quickstart.html17:20
inc0stuff break without new kernel17:20
daneyonShould I follw http://docs.openstack.org/developer/kolla/quickstart.html instead of https://github.com/openstack/kolla/blob/master/doc/quickstart.rst17:21
inc0follow one on master17:22
manjeetsinc0: any way to check which storage driver is currenlt being run ?17:22
*** achanda has joined #kolla17:22
inc0not sure if theyre not the same17:22
inc0manjeets, so if you didn't change anything default is devicemapper I think17:22
inc0which isn't pretty17:22
inc0if you change to aufs, which is just an option change, deploy should speed up considerably17:23
manjeetsI am trying docker daemon -s AUFS17:23
vhosakotdaneyon: I think both are same17:24
vhosakotyep, refer master17:24
inc0overlay or btrfs is even better performance-wise, but it's not as dramatic change17:24
vhosakotccesario: I am rebuilding heka now17:24
manjeetshow to switch to that ?17:25
manjeetsi tried using docker daemon -s but now its freezing whenever i use docker command17:26
inc0vim /etc/default/docker17:26
manjeetsthat just has DOCKER_OPTS17:27
*** achanda has quit IRC17:27
daneyonvvhosakot: OK, thx.17:27
vhosakotcool17:27
inc0it's a docker_opts entry:)17:27
inc0add -s aufs17:27
*** SamYaple has left #kolla17:27
inc0and service docker restart17:27
manjeetsokay17:27
vhosakotmanjeets: "docker info | grep Storage"   shows what storage driver the daemon is currently running17:28
manjeetsI already have aufs17:30
sdakewe want -s overlay ;)17:30
manjeetssdake let me have one run17:32
manjeetsi will do overlay later17:32
sdakemanjeets ok as long as you getme data - i'll love you long time ;)17:33
manjeetslol17:33
*** mark-casey has joined #kolla17:36
ntpttrhey kolla people, gmmaha and I are having some trouble with libvirt. we cleaned up our hosts and made sure libvirt was stopped, passed prechecks, but on deployment libvirt doesn't start17:39
ntpttrwe get these logs http://paste.openstack.org/show/492120/17:39
ntpttranyone know what might be the issue?17:40
mark-caseyhello. I was wondering if the image build process builds any secrets into the images such that the internal docker registry could become an attractive attack target, or if that kind of thing (perhaps credentials for inter-service interactions) passed at runtime?17:41
inc0ntpttr, looks like libvirtd is broken...logs plz17:41
*** SiRiuS_ has joined #kolla17:42
ntpttrinc0: here's libvirtd.log http://paste.openstack.org/show/492121/17:43
ntpttrpower management can't be found?17:43
inc0strange17:43
ntpttrpm-is-supported17:43
inc0sudo apt-get -y install pm-utils try to do it in container17:44
ntpttrthe internet says "install pm-utils will slove the problem."17:44
inc0and restart17:44
ntpttrah yep17:44
*** Marga_ has quit IRC17:44
ntpttrinc0: in nova_libvirt container? or host?17:45
gmmahainc0: since the container is on a constant restart path, how can we install it inside the container?17:45
inc0nova_libvirt17:46
*** Marga_ has joined #kolla17:46
inc0try to add this line to dockerfile and rebuild then17:46
*** achanda has joined #kolla17:46
inc0if it fixes the issue, publish a patch plz:)17:46
ntpttrinc0: where do the dockerfiles live?17:46
sdakentpttr the docker dir17:47
sdakeunder nova17:47
sdakeunder libvirt17:47
ntpttrah just in the kolla repo kk17:47
inc0then kolla build and deploy17:47
ntpttrthere's already a line in that dockerfile to install pm-utils17:48
sdakelibvirtd has a connection refused17:48
*** ph03n1x has quit IRC17:48
sdakeis libvirtd in a restart loop?17:48
ntpttrsdake: don't think so17:49
sdakedocker ps -a |  grep libvirt17:50
sdake2016-03-28 17:37:37.207 1 ERROR nova.virt.libvirt.host libvirtError: unable to connect to server at '172.16.2.6:16509': Connection refused17:50
ntpttrsdake: oh the container, all of the nova containers are in a restart loop17:50
ntpttrsorry, yes17:50
sdakedocker logs nova_libvirt -> paste17:50
ntpttrsdake: here it is, looks like a permissions issue http://paste.openstack.org/show/492125/17:52
mlimasdake, i did a script to clean fstab17:52
mlima:)17:52
mlimaI clean all references to ceph17:53
ntpttrsdake: I'm running everything as root though17:53
*** ph03n1x has joined #kolla17:54
inc0ntpttr, you might have to, or at least allow libvirt to do stuff17:54
inc0remember that it plays with kernel17:54
ntpttrinc0: I already am17:54
inc0ahh17:54
inc0drop-root gone bad sdake?17:54
sdakemlima nice17:55
*** mark-casey1 has joined #kolla17:59
*** mark-casey has quit IRC18:01
*** Jeffrey4l has quit IRC18:04
*** unicell1 has quit IRC18:07
*** unicell has joined #kolla18:07
vhosakotI see nova_libvirt is run as root.. I see all nova containers except nova_libvirt are run as nova user, and nova_libvirt is run as root.... "docker exec nova_libvirt whoami"   shows root..18:09
ntpttrvhosakot: think I should change that setting to fix my permissions error?18:11
manjeetssdake, inc0 success on kolla http://paste.openstack.org/show/492129/18:11
manjeetsthis is with all images already built18:11
vhosakotntpttr: kolla already runs nova_libvirt as root18:11
inc011min - 64 nodes?18:11
sdakemanjeets were your nodes cleaned up of images?18:11
manjeetsinc0: this is with all the images already on it18:11
manjeetsno18:11
manjeetsi did not cleanup images to save time18:11
sdakecan you do that18:11
vhosakotntpttr: can you paste the output of   grep USER /usr/local/share/kolla/docker/nova/nova-libvirt/Dockerfile.j218:11
inc0well build images is ok18:11
ntpttrvhosakot: no output from that command18:12
vhosakotntpttr: that means, no nova USER for nova_libvirt... can you paste the output from other nova container like nova_compute ?      grep USER /home/kolla/kolla/docker/nova/nova-compute/Dockerfile.j218:13
manjeetswhat is domain in horizon saw it for first time18:14
manjeets?18:14
ntpttrvhosakot: that one has user nova18:14
manjeetswhile logging horizon dashboard18:14
openstackgerritMauricio Lima proposed openstack/kolla: Add a step to clean all ceph references in fstab  https://review.openstack.org/29836318:14
vhosakotntpttr: I dont think it is user issue in nova_libvirt container..18:15
ntpttrvhosakot: hmm no clue what's causing it now, this was working just last week18:16
*** salv-orlando has joined #kolla18:18
manjeetsinc0: what is domain on horizon board ?18:18
manjeetsnever saw it before18:18
inc0default18:18
manjeetsasking me to put domain, usename and password18:18
inc0this is new in KS18:18
inc0I think18:18
inc0just type in "default"18:18
manjeetscool18:18
manjeetsthansk18:19
*** JoseMello has quit IRC18:19
sdakedomain is default18:20
ccesariovhosakot, got success!?18:20
vhosakotccesario: will keep you posted18:24
*** salv-orlando has quit IRC18:25
ccesarioright...18:26
*** sdake_ has joined #kolla18:34
*** sdake_ has quit IRC18:35
*** sdake has quit IRC18:37
*** SiRiuS_ has quit IRC18:37
*** sdake has joined #kolla18:39
vhosakotntpttr: don't know... would be a good check to see the permissions of libvirt-admin.so  in  /var/lib/docker....18:39
vhosakotntpttr: I meant checking the permission of each file that shows up in the output of      sudo find /var/lib/docker | grep 'libvirt-admin.so$'18:39
*** banix_ has joined #kolla18:42
vhosakotccesario: tested, works, gave +1, nice work!18:43
*** banix has quit IRC18:43
*** banix_ is now known as banix18:43
*** sdake has quit IRC18:44
gmmahavhosakot: inc0: should this still be there? https://github.com/openstack/kolla/blob/master/ansible/roles/horizon/templates/local_settings.j2#L15818:44
gmmahait seems that the altest keystone donesnt need it and this is causing the issue where we cannot create new roles/projects without creating the _member_ role18:45
vhosakotgmmaha: if you need _member_, you'll need that18:45
gmmahavhosakot: right, but any reason we should enable it by default?18:46
vhosakotgmmaha: are you using the   "openstack project/user/role create"   command ?18:46
gmmahavhosakot: have tried both the commadn line and the horizon dashboard18:47
gmmahai think both failed with the same error18:47
* gmmaha isnt sure about the command line18:47
gmmahai am 100% sure that the horizon dashboard failed18:47
manjeetswhat password is used when you try to do something as sudo on container18:48
*** sdake has joined #kolla18:48
manjeetsi am trying to into namespace inside neutron_l3_agent container18:48
manjeetsit is asking password for neutron18:48
vhosakotgmmaha: hmmm... ok... I can successfully create a user without _member_ and  "openstack role create test"  works fine for me18:48
gmmahavhosakot: aaah18:48
gmmahathen its just horizon that will crap out!18:48
manjeetstried host and neutron_keystone password from password,yml18:48
gmmahaand thats bad isnt it?18:48
sdakeinc0 what do you have on your plate atm that needs reallocation now that your taking over the 1.1.0 backports18:49
vhosakotgmmaha: well, horizon will see the user _not_ with _member_ role.. yes....18:49
gmmahavhosakot: right and it will deny creating of any new user/project until i get the _member_ role inclued/added18:50
vhosakotmanjeets: docker exec -tu root <container name>    works for me18:50
inc0sdake, I was pretty free after rabbitmq stuff, wanted to fix this bug: https://bugs.launchpad.net/kolla/+bug/154678918:50
openstackLaunchpad bug 1546789 in kolla "neutron failed to deploy in a multi-node deployment" [High,Triaged]18:50
gmmahavhosakot: how do you feel about a patch that will comment out that line?18:50
* gmmaha was going to ask that 18:50
inc0I'll be happy if someone takes care about it18:50
inc0this one is painful18:50
ccesariovhosakot, thanks ;)18:51
vhosakotgmmaha: yes, but I think creating user/role/project is operator task after kolla is dpeloyed.. so, I'm thinking should kolla do it... would be a good Q to the entire team18:51
vhosakotccesario: no, nice work18:51
*** achanda has quit IRC18:51
vhosakotno=np18:51
gmmahavhosakot: absolutely.. but expecting the operator to create _member_ when there is no need for it.. thats what i was curious about.. cause keystone doesnt expect you to need that role to anything18:52
gmmahavhosakot: thanks for the comments.. will wait for others' comments on it..18:53
*** SiRiuS_ has joined #kolla18:53
sdakeinc0 the workaround in #7 no bueno?18:53
* manjeets created a instance that got two ip from local network 18:53
vhosakotgmmaha: yep... I will dig the code a bit and get back to you... cool18:54
inc0sdake, I wanted to have this workaround in master18:54
inc0it will make things better18:54
*** achanda has joined #kolla18:54
sdakeinc0 how many nodes it require to duplicate?18:54
gmmahavhosakot: thanks a lot18:54
inc0so it happened on 7 for me18:54
sdakenobody in the comunity has this many nodes18:55
sdakewould it happen with 3 nodes?18:55
inc0can't say, if you make separated controller from compute it might18:55
vhosakotgmmaha: the gate uses the default user/role/domain/project and it works fine.. I have been able to boot VMs fine with the default user/role/domain/project...18:55
inc0I suspect it's because of enable_manila | bool18:55
vhosakotgmmaha: so, I will dig the code a bit and see if kolla must create the _member_ role for the operator18:56
gmmahavhosakot: i am guessing both the gate and your tests are using command line tools?18:56
vhosakotyep..18:56
vhosakotopenstack CLI18:56
gmmahavhosakot: per the folks at keystone we dont need it anymore..18:56
sdakeinc0 looks like an esy workaround - not sur how much work in testing18:56
gmmahawhich is why the command line works (I guess)18:56
gmmahaso horizon setting tht as the default role is throwing a monkey wrench when you try creating users/projects using GUI18:57
gmmahaso unless horizon needs it, i think its fair to throw it out18:57
inc0sdake, yeah, but it did break for me and it's hard to pinpoint if you're not know what to look at18:57
sdakeinc0 that workaorund broke?18:57
sdakein comment #7?18:57
inc0no, workaround worked18:57
inc0for me18:57
sdakeok well git review it and lets moce on ;)18:57
inc0but since it's not invasive18:58
inc0I was thinking about putting it in master18:58
inc0I dont have code now;)18:58
sdakeit needs t obe backported too18:58
inc0yeah18:58
inc0or no18:58
inc0actually, it might not18:58
inc0because we don't have manila in Lib18:58
vhosakotgmmaha: kolla-toolbox setups KS  https://github.com/openstack/kolla/blob/master/docker/kolla-toolbox/kolla_keystone_user.py#L62-L7818:58
sdakei mean backported to mitaka18:58
inc0yeah, that's correct18:59
gmmahavhosakot: hmmm..19:00
gmmahait definitely doesnt setup _member_ in my deploys..19:00
gmmahacan you check if that role exists in your setup?19:00
sdakeinc0 since its such a simple fix and you expressed interest in fixing it, i dont think we need to clear it for you doing 1.1.0 backports19:00
vhosakotgmmaha: but the backend KS code that runs is the same for all clients - CLI, python client, horizon19:00
sdakeso I assigned it toyou sa a result :)19:00
vhosakotgmmaha: let me check.. 1 min19:00
inc0sdake, yeah19:01
inc0I'll just do it19:01
gmmahavhosakot: right the keystone is the same19:01
*** mark-casey has joined #kolla19:03
*** dwalsh has quit IRC19:03
gmmahavhosakot: https://github.com/openstack/horizon/blob/711f88dd4785fdb3cd26bb0d7b8ddf38037f5b8d/openstack_dashboard/dashboards/identity/projects/workflows.py#L200-L21619:03
*** dwalsh has joined #kolla19:04
*** mark-casey1 has quit IRC19:04
gmmahaand with that we are getting poushed out by horizon from creating others even though keystone doesnt care/need you to have it19:04
vhosakotgmmaha: aha :)19:04
*** cbaesema has joined #kolla19:06
gmmahainc0: sdake: same error with re-build of the images and re-deploy http://paste.openstack.org/show/492140/19:06
gmmaha:(19:06
vhosakotgmmaha: as you pointed we alread have OPENSTACK_KEYSTONE_DEFAULT_ROLE=_member_  in    https://github.com/openstack/kolla/blob/master/ansible/roles/horizon/templates/local_settings.j2#L158... but KS is not pikcing it up19:06
sdakeinc0 sdake is the same person apparently ;)19:07
gmmahasdake: :)19:07
sdakegmmaha are you on ubutu or centos19:07
gmmahasdake: Ubuntu19:08
sdakegmmaha do following19:09
sdakesudo -i19:09
sdakecd /var/lib/kolla19:09
sdakefind . -name libvirt-admin.so.0 -ls19:09
sdakerather cd /var/lib/docker19:09
gmmahasdake: guessing this is in the container?19:09
sdakewhen you find the file19:09
sdakels -l it to see its permissions19:09
gmmahasdake: http://paste.openstack.org/show/492142/19:10
*** dwalsh has quit IRC19:11
sdakels -l the file its linked to plz19:11
*** dwalsh has joined #kolla19:11
gmmahasdake: http://paste.openstack.org/show/492144/19:12
sdakedocker exec nova_libvirt id19:12
gmmahasdake: Error response from daemon: Container nova_libvirt is restarting, wait until the container is running19:13
vhosakotgmmaha: does the horizon error say "OPENSTACK_KEYSTONE_DEFAULT_ROLE" is missing ?19:13
sdakeoh is this horizon?19:13
gmmahavhosakot: right.. it will say we cannot cerate the user19:13
sdakeI thought wew ereon libvirt19:13
gmmahasdake: two parallel things :)19:13
gmmahavhosakot has been helping me with an interesting issue with horizon and keystone roles19:14
sdakegmmaha ok lets stay focused on libvirt for the moment19:14
gmmahasdake: you got it19:14
vhosakotgmmaha: sdake: wont mix things.. you guys carry on.. I want to check something in KS users in kolla19:14
vhosakotgo shead19:14
sdakecd /var/lib/docker19:15
sdakefind . -name libvirtd.log19:15
sdakepaste the contents of that file19:15
gmmahasdake: nothing.. no file with that name exists19:15
sdakemoment let me read the code19:16
sdaketry libvirt.log19:16
gmmahasdake: is that in /var/lib/docker or /var/log/libvirt(local host)19:16
sdake /var/lib/docker19:17
gmmahasdake: no file exists with name libvirt*log19:17
sdakedocker logs nov_libvirt19:18
sdakepaste19:18
sdakeplz19:18
sbezverksdake lately I noticed permission denied when accessing libvirtd.log19:18
sbezverksdake it is probably runs as root and heka used does not have access there..19:18
gmmahasdake: http://paste.openstack.org/show/492146/19:19
sdakegmmaha run docker --version19:20
gmmahasdake: Docker version 1.10.3, build 20f81dd19:20
sdakegmmaha run ps -ef | grep docker19:20
gmmahasdake: root       2231      1  0 16:23 ?        00:00:48 /usr/bin/docker daemon --insecure-registry 172.16.2.2:400019:21
sdakewas it working prior and stopped working?19:21
sdakethis looks like some kind of  wierd docker bug to me19:21
gmmahasdake: yeah it used to work all last week19:22
sdakeand youd id what to braek it? :)19:22
gmmahawe did a fresh deploy on friday to switch from OVS to linuxbridge and noticed that we no longer see compute hosts on horizon dashboard19:22
sdakeby fresh deploy did you cleanup-images?19:24
sdakeand cleanup-containers?19:24
sdakeand rebuild19:24
sdakeor what19:24
sdakedefine "fresh deploy" plz :)19:25
gmmahasdake: full remove of imges, re-buld and redeploy19:25
gmmahawith cleanup of containers and hosts19:25
sdakehow old were your previous images?19:26
gmmahabarely a week old19:26
sdakerun docker images | grep libvirt19:26
gmmaha172.16.2.2:4000/kollaglue/ubuntu-source-nova-libvirt                2.0.0               3cd0d481d32b        11 days ago         630.7 MB19:27
sdakedid you run cleanup-images?19:27
gmmahahm m19:27
gmmahai thought we did19:27
gmmahantpttr: ^^19:27
sdakei dont know what is causing the problem19:27
ntpttrgmmaha: sdake: yeah we ran cleanup-images19:27
sdakei dont know if the linuxbride container was tested19:28
sdakewhen it was made into a thin container19:28
sdakehere is what I recommend19:28
sdakerun cleanup-containers and cleanup-images on every host19:28
sdakereboot every hot19:28
sdakerevert your ovs to linuxbrige config optoin change19:28
sdakeand try a fresh deploy with your images in your registry19:28
sdakein the meantime i am going to try a linuxbridge deployment on my side19:34
sdakebecause my environment definately works ;)19:34
*** vhosakot has quit IRC19:34
*** vhosakot has joined #kolla19:35
*** sdake_ has joined #kolla19:36
*** sdake has quit IRC19:38
*** salv-orlando has joined #kolla19:42
sdake_ntpttr  in the midst of deploying linuxbridge, i'll let you know how that goes19:46
sdake_manjeets around?19:47
ntpttrsdake_: thanks, we're rebuilding images now19:47
sdake_ntpttr i didn't really want you to rebuild images but ok ;)19:48
ntpttrsdake_: oh you just wanted us to clean them up on all the target hosts?19:48
ntpttrthough that was implied with the cleanup-images19:48
sdake_yup19:48
sdake_cleanup-images removes the images from the docker image cache19:49
sdake_but not from the registry19:49
ntpttrsdake_: oh so building them again is creating duplicates in the registry? or does it just overwrite?19:50
*** salv-orlando has quit IRC19:52
sdake_it overwrites if you use the same tag number19:54
sdake_i change my tag number for every build i do19:54
sdake_so i can go back in time and change things around ;)19:54
sdake_(2)No such file or directory: AH02291: Cannot access directory '/var/log/kolla/horizon/' for error log of vhost defined at /etc/httpd/conf.d/horizon.conf:319:54
sdake_vhosakot horizon not working19:54
sdake_did you do the horizon container log change?19:54
sdake_ntpttr i can't get a vm to boot in nova for some reason with or without linuxbridge, but linuxbridge doesnt' caue libvirtd to restart loop19:56
sbezverkvhosakot there were two patches for horizon, both must be present for horizon logging to work..19:56
ntpttrsdake_: weird we were able to boot instances before this issue stopped libvirt from working19:56
sdake_ntpttr it may just be a problem on centos19:57
sdake_i am not certain yet19:57
manjeetssdake yes19:57
sdake_manjeets did you get overlayfs working with docker?19:58
manjeetsnot yet having rabbit mq issues19:58
manjeetsi get 2 ip's when i spin a instance19:58
manjeetswhen i do docker exec -tu root rabbitmq bash19:59
*** Serlex1 has joined #kolla19:59
manjeetsand it just freezes19:59
manjeetsi need to watch logs which needs sudo access19:59
manjeetsand password for rabbitmq in password.yml is not working19:59
manjeetsvhosakot: here ?20:01
sdake_docker exec heka tail -f /var/log/rabbitmq/rabbitmq.log20:01
manjeetsok20:01
sdake_rather /var/log/kolla/rabitmq/rabbitmq.log20:01
*** Serlex has quit IRC20:02
*** vhosakot has quit IRC20:02
*** sdake has joined #kolla20:03
sdakesbezverk where is the other patch for horizon -> link plz20:05
*** sdake_ has quit IRC20:06
*** pbourke-home has joined #kolla20:08
sbezverksdake_ https://bugs.launchpad.net/kolla/+bug/156107320:08
openstackLaunchpad bug 1561073 in kolla "incomplete horizon logging fix" [Undecided,Fix released] - Assigned to Serguei Bezverkhi (sbezverk)20:08
*** vhosakot has joined #kolla20:09
*** mark-casey1 has joined #kolla20:09
vhosakotsdake: yes.. saw the IRC logs.. file bug for horizon20:09
openstackgerritSteven Dake proposed openstack/kolla: Add creation of new log folder for Horizon  https://review.openstack.org/29841820:09
*** pbourke-home has quit IRC20:09
sdake^^needs cr approvals20:09
vhosakotah you submitted the patch.. cool20:10
*** akscram has quit IRC20:11
*** mark-casey has quit IRC20:11
*** akscram has joined #kolla20:11
*** mark-casey1 has left #kolla20:12
sdakei just ued the cherrypick button20:14
sdakeit was already in master20:14
sdakei have stable/mitaka checked out20:14
sdakemanjeets after you finish the job on overlay benchmarking i'd like to know what a  tls enabled  registry produces in terms of performance deficits ;)20:15
sdakeand then upgrade and then reconfigure20:15
sdakeand i'll be done with my benchmark requets :)20:16
vhosakotmanjeets: I just checked.... rabbitmq in passwords/yml works fine for me in lastet master20:34
*** vhosakot has quit IRC20:34
*** vhosakot has joined #kolla20:36
manjeetsok latest master ?20:36
sdakemanjeets if your using master you have to use samyaple's generate-password.py tool20:36
vhosakotmanjeets: yes...20:36
vhosakotyes, kolla-genpwd...20:36
sdakethis will filll out the password file20:36
sdaketools/generate-password.py is the link20:36
sdakethen go look in the password file for the passwords ;)20:36
ntpttrsdake: we finished the reinstall and still libvirt is broken20:37
sdakedid you rebuild images?20:37
ntpttrsdake: yeah20:37
sdakeare you using master?20:37
ntpttrsdake: I havent done a pip install on master20:38
ntpttrwe're using the same version that worked last week20:38
sdakeso you haven't updated your repos?20:38
ntpttrI think we did, but didn't pip install kolla20:38
sdakeyou dont want to pip install kolla20:38
ntpttrright gmmaha, you did update the repo?20:38
sdakethat needs to go from the docs20:38
sdakeperhaps a recent change broke libvirt20:39
sdakelet me try master in my environment moment20:39
gmmahantpttr: yes i updated the code base to the latest master20:39
vhosakotgmmaha: which same error ? permission issue on libvirt-admin.so ? or, pm-is-supported  not found error ?20:43
*** sdake_ has joined #kolla20:43
ntpttrsdake_: we've got to go and do some other stuff for now, but will be back to this later20:43
*** sdake has quit IRC20:43
sdake_ntpttr it takes me about 15 mins to buidl and 5 mins to deploy i'll leave a note if master is working20:43
ntpttrsdake_: awesome, thank you20:44
gmmahavhosakot: yeah.. think the same error..20:45
gmmahai am stuck with soemthing for a bit20:45
gmmahai will update it asap20:45
gmmahawhen i am out of there20:45
gmmahahere*20:45
vhosakotgmmaha: also, which of the two error ? :)20:45
vhosakotor both20:45
sdake_how do folks feel about the ansible offices is nc for the next midcycle?20:47
sdake_or maybe its sc ;)20:47
vhosakotdid you mean RH offices ? :)20:47
sdake_ansible has their own office20:47
sdake_but ya, its a red hat facility20:48
vhosakotah ok20:48
vhosakotcool20:48
gmmahavhosakot: http://paste.openstack.org/show/492160/20:49
*** banix has quit IRC20:49
vhosakothmm.. same permission issue for libvirt-admin.so.. ok20:51
*** achanda has quit IRC20:52
vhosakotgmmaha: can you paste the output of   "ps aux | grep libvirtd"...20:53
gmmahavhosakot: on the host i presume?20:56
vhosakotyes.. compute host20:56
gmmahavhosakot: nothing but the grep command itself20:56
vhosakotah... ok.. 1 sec20:56
vhosakotgmmaha: your nova_libvirt container is not up as well, right ?21:01
gmmahavhosakot: thats the one thats going on restarting21:01
gmmahavhosakot: yes its not up and running21:01
*** jtriley_ has joined #kolla21:01
*** achanda has joined #kolla21:04
*** jtriley has quit IRC21:04
*** Marga_ has quit IRC21:06
*** jtriley_ has quit IRC21:06
*** Marga_ has joined #kolla21:06
vhosakotgmmaha: your permissions match mine for libvirt in http://paste.openstack.org/show/492142/21:10
vhosakotgmmaha: can you paste the output of  "sudo find /var/lib/docker -name libvirt-admin.so.0.1003.1 | xargs sudo ls -l"21:10
vhosakotI have it   -rw-r--r--21:11
gmmahavhosakot: i have the smae21:11
gmmahasme*21:11
gmmahasame*21:11
vhosakot-rw-r--r--  ?21:11
gmmaha-rw-r--r-- 1 root root 30680 Mar  2 04:20 /var/lib/docker/aufs/diff/1c9abd1375465d1015865015e8cb8c09f0b4a4caafe4826d4261b92336162fb4/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0.1003.121:11
gmmaha-rw-r--r-- 1 root root 30680 Mar  2 04:20 /var/lib/docker/aufs/diff/48c7f01c7d48558ff82b836c4c1534b5917d1c6978e717ffe07de4feb5f67c28/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0.1003.121:11
gmmahavhosakot: yeah21:12
sdake_gmmaha my libvirt on masater with linuxbridge doens't enter a recycle loop21:15
gmmahasdake_: aaah21:15
gmmahathen definitely somethign wrong with the hosti guess..21:15
gmmaha:(21:15
gmmahai can try and redeploy the base OS on the compute hosts and start all over again!21:15
sdake_do you know how to turn off that thing that is ike selinux in ubuntu21:15
sdake_apparmor21:16
sdake_gmmaha ls -l the symlinks again plz21:16
gmmahasdake_: hmm.. you think selinux persmissions are mucking with this?21:16
gmmahasdake_: sure21:16
sdake_ubuntu doesn't have selinux21:16
gmmaha-rw-r--r-- 1 root root 30680 Mar  2 04:20 ./aufs/diff/1c9abd1375465d1015865015e8cb8c09f0b4a4caafe4826d4261b92336162fb4/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0.1003.121:17
gmmaha-rw-r--r-- 1 root root 30680 Mar  2 04:20 ./aufs/diff/48c7f01c7d48558ff82b836c4c1534b5917d1c6978e717ffe07de4feb5f67c28/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0.1003.121:17
vhosakotgmmaha's symlinks' permission match with my env in which I have a booted a working vm fine21:17
sdake_no, the symlinks21:17
sdake_not what they link to21:17
gmmahavhosakot: sdake_: the same env worked last week21:17
gmmahaits starting today that its acting up21:17
gmmahasdake_: aaah21:17
vhosakotsdake_: I see gmmaha already sent that.. is this what you're looking for ?   http://paste.openstack.org/show/492142/21:18
gmmahalrwxrwxrwx 1 root root 25 Mar  2 04:20 ./aufs/diff/1c9abd1375465d1015865015e8cb8c09f0b4a4caafe4826d4261b92336162fb4/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0 -> libvirt-admin.so.0.1003.121:18
gmmahalrwxrwxrwx 1 root root 25 Mar  2 04:20 ./aufs/diff/48c7f01c7d48558ff82b836c4c1534b5917d1c6978e717ffe07de4feb5f67c28/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0 -> libvirt-admin.so.0.1003.121:18
vhosakotgmmaha: there is a way to start libvirtd in debug mode.. 1 sec21:19
sdake_i have no libvirt-admin in centos21:20
sdake_ /var/lib/docker/overlay/fbc95f417506830845bd6921820d26fdf5e6e38dd7d4eb3ee2a894b3e6512636/root/usr/lib64/libvirt-admin.so.021:21
sdake_ok i have idea21:22
sdake_find the libvort .so 1003 file21:22
sdake_and do the following to it21:22
sdake_chmod 755 the file21:22
gmmahasdake_: clean containers after that and redeploy?21:22
sdake_-rwxr-xr-x. 3 root root 28144 Feb 16 12:09 /var/lib/docker/overlay/fdf4439f1831cccbdd1e051fa1a5c3b58d4760d6a1b2062f41628785d13c8903/root/usr/lib64/libvirt-admin.so.0.1002.1721:23
sdake_no21:23
sdake_just change the permissions21:23
gmmahasdake_: done21:23
sdake_still looping?21:23
vhosakotsdake_: gmmaha already has -rw-r--r--   for     libvirt-admin.so.0.1003.121:23
sdake_ya my file for that has execute bit set21:23
gmmahasdake_: let me set it21:24
vhosakotsdake_: ah... change it to 755.... ah21:24
vhosakotI have -rw-r--r-- ... only read bits set21:24
sdake_and it works on your gear hosakot?21:24
vhosakotyep, both OVS and LinuxBrdige... AIO.. I just told gmmaha that21:25
*** sdake_ is now known as sdake21:27
vhosakotgmmaha: let us know what happens after you retest with 755... I just found out the way to start libvirtd in debug mode21:27
gmmahavhosakot: sure21:27
*** salv-orlando has joined #kolla21:27
gmmahavhosakot: sdake: didnt work.. the perms change21:29
vhosakotgmmaha: ok... do this21:29
sdakejpeeler rhallisey ping21:30
vhosakotgmmaha: in   https://github.com/openstack/kolla/blob/master/ansible/roles/nova/templates/nova-libvirt.json.j2#L2     change        "command": "/usr/sbin/libvirtd --listen",           to         "command": "/usr/sbin/libvirtd -v --listen",      and redeploy nova_libvirt21:30
rhalliseysdake, yo21:31
sdakeyou will hae to remove the contanier not just redeploy because a restarting container isn't redeployed by our software atm unfortunately21:31
vhosakotgmmaha: add -v21:31
gmmahavhosakot: aah21:31
vhosakotgmmaha:   there is more.. 1 sec21:31
gmmahavhosakot: sue21:31
gmmahasure*21:31
vhosakotgmmaha: you need to do the change in     /usr/local/share/kolla/ansible/roles/nova/templates/nova-libvirt.json.j2    and re-deploy nova_libvirt21:33
sdakecleanup-containers nova -f21:33
sdakeor nova_libirt21:34
sdakenot sure exact syntax21:34
sdakeyou dont want that livirt container looping while you redeploy21:34
vhosakotgmmaha: and then pastebin the output  of   "docker exec -u root heka cat /var/log/kolla/libvirt/libvirtd.log"21:34
*** dwalsh has quit IRC21:35
vhosakotgmmaha: yep, dont re-deploy a broken looping container... stop it, remove it, make the changes in nova-libvirt.json.j2, redeploy21:35
*** salv-orlando has quit IRC21:35
vhosakotkolla-ansible deploy -t nova21:35
gmmahavhosakot: sdake: will do it soon.. off to some meetings.. :(21:37
* gmmaha hates mondays filled with meetings21:37
sdakewe hae meeting free monday at cisco21:37
sdakeexcept as my dirctor informs me, it doesn't apply to principals ;)21:37
* gmmaha is jealous21:37
*** achanda has quit IRC21:37
vhosakothaha21:37
gmmahasdake: :)21:37
gmmahasdake: i have to rebuild the docker images?21:40
gmmahaor just destroy and deploy is god?21:41
gmmahagood*21:41
*** Serlex1 has quit IRC21:44
*** salv-orlando has joined #kolla21:45
*** cfarquhar has quit IRC21:45
sdakejust redpeloy gmmaha21:45
gmmahavhosakot: the file doesnt exist in the heka container21:46
gmmahacat: /var/log/kolla/libvirt/libvirtd.log: No such file or directory21:46
vhosakotit should.... the code latest ?21:47
gmmahavhosakot: as of this afternoon..21:47
gmmahai did a 'git pull' in the kolla project and re-built them all21:47
vhosakotgmmaha: can you do         docker exec -u root heka find / -name libvirtd.log21:47
*** cfarquhar has joined #kolla21:48
*** cfarquhar has quit IRC21:48
*** cfarquhar has joined #kolla21:48
gmmahavhosakot: empty21:48
gmmahano files found21:48
vhosakotgmmaha: did you add -v and re-deploy ?21:48
gmmahavhosakot: yeah21:48
gmmahavhosakot: the file in /usr/local/share/kolla right?21:49
vhosakotyep... /usr/local/share/kolla/ansible/roles/nova/templates/nova-libvirt.json.j221:49
vhosakotgmmaha: did you stop, remove, make changes, saved file and re-deployd ?21:49
gmmahavhosakot: yeah.. stop, dump containers, make cahnge to file, kolla-ansible... deploy21:50
gmmahaverified that the containers also got created again21:50
* gmmaha runs to his stupid meeting21:50
gmmahavhosakot: sdake: thanks for all the help debugging21:50
vhosakotdid it work now ?21:51
gmmahahave half a mind to blow out all the hosts and redeploy them21:51
gmmahavhosakot: no.. but have a feeling i have to do that tonight21:51
gmmahawipe the hosts and start fresh21:51
gmmaha:(21:51
sdakewait a minute21:51
sdakedid adding -v fix the problem?21:51
gmmahasdake: nope did not..21:51
sdakeok good that is not an outcome i woudl hvae expected21:52
gmmahasdake: :D21:52
vhosakotgmmaha: did nova_libvirt start fine ?21:52
gmmahathat would have been a bizzare one21:52
gmmahavhosakot: no, it did not..21:52
vhosakotsdake: -v should _not_ resolve the issue.. :)21:52
gmmahastil on the reboot cycle21:52
vhosakotgmmaha: ah ok21:52
sdakeso lets get some more logs this time21:52
gmmahasdake: just thanking you guys for sitting with me through all this21:52
sdakenow that we have debug enabled21:52
vhosakotbut gmmaha is not even seeing th libvirtd.log in heka21:53
sdakevhosakot can you tell me where that libvirt-admin file is in your environment?21:53
sdakelibvirtd.log wont be created becaue libvirtnever starts21:53
sdakebecaues his envirionment is busted21:53
vhosakotsdake: but, he pastebinned the output of libvirtd.log from heka this morning right ?21:54
vhosakotgmmaha: how did you see the contents of this pastebin ?   http://paste.openstack.org/show/492125/21:54
sdakethose wer old olgs21:54
vhosakotah ok21:54
sdakeold dogs21:55
gmmahavhosakot: just dokcer logs21:55
gmmahai guess21:55
* gmmaha isnt sure what he is talking about though21:55
vhosakotok... send "docker logs nova_libvirt"... let us see if there is any debug message21:56
manjeetssdake: on cleaned up targets http://paste.openstack.org/show/492168/22:03
sdake25 minutes to build with aufs22:04
sdakerrather deploy22:04
manjeetsits aufs already22:04
*** achanda has joined #kolla22:04
manjeetsyes deploy takes around 21 to 25 mins with aufs22:05
sdakewhat about reconfigure?22:05
sdaketime sudo ./kolla-ansible reconfigure22:05
openstackgerritHui Kang proposed openstack/kolla: Add etcd Docker container  https://review.openstack.org/29845122:12
*** Marga_ has quit IRC22:19
*** Marga_ has joined #kolla22:19
sdakeinc0 jpeeler rhallisey review - stablemitaka broken22:21
sdakehttps://review.openstack.org/#/c/298418/22:21
patchbotsdake: patch 298418 - kolla (stable/mitaka) - Add creation of new log folder for Horizon22:21
*** ccesario_ has joined #kolla22:22
inc0jpeeler, we ran into race condition;)22:23
jpeelerthat's gotta be some type of gerrit bug22:24
jpeelerit shows now me as having +1, when I never set that22:24
inc0well whatever, I hit +222:24
jpeelerer, maybe i did it by mistake22:24
inc0+w22:24
jpeeleryeah i'm dumb, nevermind22:25
openstackgerritMerged openstack/kolla: Add creation of new log folder for Horizon  https://review.openstack.org/29841822:27
sdakeinc0 or rhallisey either of ou want to be backup release liasons for kolla22:30
*** ccesario_ has quit IRC22:30
sdakethe job involves learning how the releases repoistory works and doing the job if - iI for example hae a deadly root canal infection again ;)22:31
inc0yeah count me in22:31
rhalliseysure22:31
sdakewell it only needs to be one person22:31
sdakeso sort it out guys :)22:32
inc0heads or tails rhallisey ?;)22:32
rhalliseytails22:32
sdakehaha22:32
vhosakotI can help with whatever is needed... have some release/versioning/branching experience... not specific to kolla but22:32
sdakeinc0 holds all the quarters!22:32
rhalliseysomeone filp a coin22:32
inc0so if tail is oposite to side than one with president, than tails22:33
sdakevhosakot go find  a quarter and flip it and let it lland on teh ground22:33
inc0and from north dakota nonetheless!22:33
rhalliseyya that's tails22:33
rhalliseylol22:33
sdakeand tell us the results22:33
inc0one with buffalos22:33
vhosakotwhat if it lands vertically and both (neither) heads and tails22:33
sdakegold coins ftw22:33
inc0vhosakot, then you do the job22:33
sdakelet gravity do its thing ;-)22:34
vhosakothahaha22:34
inc0so tails it is, congrats Ryan;)22:34
*** mbound has joined #kolla22:35
inc0I can be backup to your backup;)22:35
rhalliseylol woo :)22:35
sdakevhosakot was supposed to flip the coin :)22:35
* sdake thinks inc0 just got out of oding work ;)22:35
inc0ok, waiting for him then22:35
vhosakotstill flipping... gravity is slow today22:35
inc0sdake, I could well...not volounteer if I wouldnt want it;)22:35
sdakeinc0 i joke ;)22:36
inc0sorry, my sense of humor is post-soviet22:36
sdakein soviet russia coin flips own you22:36
inc0nah, you don't have coins at all;)22:37
inc0and that is actually true in Belarus22:37
sdakei thin i foxtrot echo delta'ed that joke ;)22:37
sdakecomon vhosakot i gotta do stuf f- get on twith the flipping22:37
vhosakotyou guys serios..22:38
vhosakotok let me flip...22:38
rhallisey:D22:38
vhosakotgot some quaters on my desk22:38
inc0vhosakot, what made you think we're not serious?22:38
sdakeall games are started with a coin flip ;-)22:38
vhosakotI first though it was a joke to flip coiin to decide release eng for kolla :)22:39
vhosakotok, I'm flipping now...22:39
vhosakotshould I start telling the rules... or assume the participants know it ?22:39
rhalliseyhe's heads im tails22:39
*** mbound has quit IRC22:39
inc0some of them starts with spin of revolver barrel, but these usually ends with it as well22:39
vhosakotok.. got it...22:39
*** banix has joined #kolla22:40
vhosakotcoin is thrown once in air... in a free space... let is land on ground.. there is no carpet.. I'm on level 0... so gravity is good.... if coin stands vertically, I will redo it22:40
rhalliseyperfect22:40
inc0what's your current atmospheric pressure?22:41
sdakejust flip a coin22:41
vhosakot322:41
vhosakot222:41
vhosakot122:41
sdakeits not rocket surgery22:41
rhalliseyinc0, dude this is so official22:41
vhosakottails22:41
vhosakotI got tails22:41
rhallisey:D22:41
inc0congrats rhallisey22:41
rhalliseyI win22:41
rhalliseylol22:41
sdaketwo tails22:41
sdakeit was meant to be ;-)22:41
rhalliseyor did I lose22:41
vhosakotno.. just one tails22:41
vhosakotI typed twice22:41
inc0vhosakot, I also rollet tails22:41
sdakeinc0 got tails eaerlier22:41
rhalliseyXD22:41
inc0rolled22:41
inc0and tails from ND22:42
sdakewhat are the odds of that ;-)22:42
rhallisey1/422:42
inc01:4 sdake22:42
inc0unless you're asking to include state of origin of a quarter, then we need to get statistics of how many coins got emitted by each state22:43
inc0or at least what percentage of total coins got emitted in ND22:43
sdakethis is where the lecture of the gambler's fallacy comes in :)22:43
inc0rhallisey, you're from ND or SD?22:43
rhalliseywhat's ND/SD22:44
inc0north dakota or south dakota22:44
rhalliseyI'm from Connecticut22:44
inc0lol22:44
rhalliseywhat made you think I was from there O.o22:44
inc0I thought you live in one of Dakotas22:44
inc0no idea22:44
rhalliseyhaha22:44
rhalliseythat's funny :)22:45
inc0then it's not nearly as cool as I thought it is...picking a quarted and rolled a tails from your home state22:45
inc0I'll keep saying that you live in North Dakota because it makes this story better22:45
rhalliseyya that would've been cool22:45
inc0sorry man22:45
rhalliseyno problem at all22:45
inc0you need to move now22:45
rhallisey:)22:46
sdakein case rhallisey and sdake have, yu know, a deadly root canal at the asm etime22:46
rhalliseyI live in Massachusetts currently22:46
sdakeboth of you read the docs in openstack/releases22:46
sdakerhallisey inc0 read this review https://review.openstack.org/#/c/297976/22:47
patchbotsdake: patch 297976 - releases - Add kolla releases already in Mitaka22:47
vhosakothaha.. gambler's fallacy...22:48
vhosakotrhallisey: I'm in MA as well.. :)22:48
rhalliseyvhosakot, neat!22:48
inc0there you go, we have location of our next midcycle22:48
rhalliseycould do Red Hat westford22:49
rhalliseynice in the summer22:49
sdakeor red hat ansible offices22:49
* sdake can hook that one up22:49
rhalliseyoh cool22:49
rhalliseyeither way works22:49
rhalliseywe can flip another coin22:49
rhallisey!22:49
inc0rh ansible would allow us to meet ansible community as well22:49
inc0and express how much we....like... them22:50
inc0I'll go with like22:50
inc0on a recorded chat at least22:50
vhosakotsomeone in a casino once told me and my wife about gambler's fallacy.... "Just because you and your wife fought 5 times this week does not mean you guys will fight less than 5 times next week".. or something like that... it's got something to do with the frequncy of occurence of an event in a period of time22:53
inc0in this particular scenerio that might actually be true22:54
inc0if you fight everyday for 10 years, it may affect your fighting 2 years from then22:54
inc0also name on house ownership docs22:55
inc0marriage is like a handgrenade - remove a ring and house is gone22:55
*** blahRus has quit IRC23:02
*** kproskurin has quit IRC23:07
openstackgerritSteven Dake proposed openstack/kolla: Revert "Fix consistently failing CentOS gate"  https://review.openstack.org/29708423:07
openstackgerritSteven Dake proposed openstack/kolla: [WIP] Test to see if this fixes the gate  https://review.openstack.org/29846023:07
sdakelet see what the gate does with that23:08
inc0sdake, so rsyslog is broken in Liberty code with docker 1.123:08
inc01.1023:08
inc0we may need to backport heka23:08
sdakelets make 1.1.0 work - hell or highwater23:08
inc0will look at heka backport23:09
inc0tomorrow, when elemoine and akwasne will wake up23:09
inc0reason is docker introduced /dev/shm stuff in 1.1023:09
inc0and if we bind /dev/ for rsyslog to create /dev/log23:09
inc0we have issues23:09
inc0I'll try other stuff23:10
*** yuanying has joined #kolla23:11
sdakeinc0 we may be going about this wrong23:13
sdakeone option which wasn't super discussed rather then trying to backport a bunch of things23:13
inc0what's on your mind?23:13
sdakeis to take mitaka as it is, and make kolla that23:13
sdakeliberty that23:13
sdakeand then fix the repos up and whatnot'23:14
inc0well I was thinking about that23:14
sdakethat is probably the fastest way to a working iberty tree23:14
sdakeits not something we would ever do again23:14
inc0we need to test it tho23:14
inc0things may go bad, but not sure23:14
sdakebut at this point w eare backporting a bunch of things23:15
inc0let's try both ways, maybe someone can explore changing repos23:15
sdakei think where we need to be careful with that approach is the defaults files23:15
*** absubram has quit IRC23:15
inc0at this point we're backporting half of mitaka anyway23:15
sdakeits more like a backport + rewrite23:15
sdakewhy not just rewrite the damn thing23:15
sdakemake it stable23:15
sdakeand long term forget liberty ever happpened after operators have migrated off of it23:16
inc0so best case scenerio - we just change repos and versions in our build scripts23:16
sdakeand keep the default the same in ansible23:17
sdakethe keystone migratoin might be a pain23:17
inc0worst case scenerio - something changed so much that our code doesn't work any more23:17
sdakemaybe we should fix the defaults file too23:17
sdakemost of the defult changes have been around authentication23:18
inc0might actually be more stable as we tested mitaka stuff much more than we will test liberty with mitaka backport23:18
sdakeI think a careful one by one diff can sort those out23:18
sdakeyes the testing here is critical23:18
inc0sdake, I'll keep working on backport just in case, can you find someone trustworthy to try out changing repos and defaults?23:18
sdakebecause the way your goingboutit inc0 we lose allt he testing we di on liberty23:19
sdakeand gain none that we did with mitaka23:19
sdakeinc0 i'll take that onn as soon as i fix the gate23:19
sdakeif it looks promising i'll look for help finishing the job23:19
inc0I agree and acutally I like your plan better, I was thinking about it but I guess it got lost by "let's not backport features, only absolute minimum"23:19
sdakepossibly you ;)23:19
inc0but then backport of thin containers, upgrades23:19
sdakeand now heka23:20
inc0well, heka wasn't planned23:20
sdakei want backports in the future to be critical bugs only23:20
inc0and I'm not positive that I can't get around it with rsyslog23:21
sdakebut we do need to fix the state of liberty23:21
inc0I just see it will be pain23:21
sdakeliberty already has cves which we don't deploy23:21
*** salv-orlando has quit IRC23:21
inc0we may actually look at supporting current master => lastest stable release23:22
inc0so mitaka kolla will support liberty, newton will support mitaka23:22
inc0most of deployment tools does that23:22
inc0but that's discussion for later23:22
sdakeyou mean support n and n-123:22
inc0or just n-123:22
inc0we may try to support both23:23
sdakei want our mitaka release to implement mitaka not liberty ;-)23:23
inc0ok23:23
inc0well23:23
sdakejust becaue every other deploymeent tool is behind23:23
sdakedoesnt mean we should be23:23
inc0there are good reasons for it, but again, discussion for later23:23
inc0sdake, try to change repos23:24
inc0I'll try to do it with ubuntu tomorrow23:24
inc0hopefully any of our infra won't be "too new for liberty"23:24
sdakeatm i am using build rom source23:24
sdakebecause ccentos is busted23:24
inc0I only use build from source;)23:24
sdakerathe rdo is busted23:24
inc0ok I'm off for today, I'm exhausted23:25
inc0cya all tomorrow23:25
*** inc0 has quit IRC23:26
*** shakamunyi has joined #kolla23:30
*** barra204 has quit IRC23:32
*** asalkeld_ has joined #kolla23:34
sdakeasalkeld you about23:38
*** achanda has quit IRC23:41
*** weiyu_ has joined #kolla23:44
*** jtriley has joined #kolla23:44
*** weiyu_ has quit IRC23:45
manjeetssdake question ??23:46
sdakemanjeets shoot23:46
manjeetssuppose i change some params in /etc/neutron/neutron.conf23:46
manjeetsshould i just restart container ?23:46
sdakedepends on setting o fcoy once or copy always23:46
vhosakotsdake: all,  I am working on moving mysql logs from /var/log/ in the mariadb container to /var/log/kolla/mariadb/... can any one check if they see mysql logs in  /var/log/23:47
sdakeif copy always you can just restart the container23:47
vhosakot"docker exec mariadb ls /var/log/ | grep mysql"     I see myql logs in  /var/log/23:47
manjeetssuppose i want to change some setting in conf file how do i get those reflected to actual neutron23:48
*** weiyu_ has joined #kolla23:48
vhosakotthe person who commented at the end of this bug   https://bugs.launchpad.net/kolla/+bug/1562231   says  mysql logs are not found in  /var/log/...23:48
openstackLaunchpad bug 1562231 in kolla mitaka "lights out recovery patches may have caused problems with mariadb" [Critical,Confirmed]23:48
manjeetsin devstack i just restart the neuton service23:48
sdakecreate config entries in /etc/kolla/config/neutron.conf23:48
manjeetsok23:48
sdakeand run kolla-an sible reconfigure23:48
*** diogogmt has joined #kolla23:48
manjeetscool23:48
vhosakotsdake: can you send your output of      "docker exec mariadb ls /var/log/ | grep mysql"23:49
sdakethose will be merged or override tthe defaults23:49
sdakehttp://paste.fedoraproject.org/346554/59208964/ -> http://paste.fedoraproject.org/346554/5920896423:49
*** jtriley has quit IRC23:50
manjeetssdake i assume i don't need to stop or clean-up container before i do kolla-ansible reconfigure ?23:50
vhosakotsdake: you don't see it..... ok.. why do i see it... http://paste.openstack.org/show/492178/   let me dig the cotnainer23:51
vhosakotsdake: ah, you are on CentOS right23:52
vhosakotthey are seen in Ubuntu23:52
sdakevhosakot need to be seen on both equally ;-)23:54
vhosakotsdake: It looks like I see them on ubuntu and you dont on CentOS... http://paste.openstack.org/show/492178/23:55
vhosakotyep, I will check this23:55

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