Friday, 2016-02-19

*** Allen_Gao has joined #kolla00:02
*** vhosakot has quit IRC00:03
*** vhosakot has joined #kolla00:04
vhosakotback!00:04
* vhosakot is reading all the replies!00:04
*** tobe has quit IRC00:06
openstackgerritAllen Gao proposed openstack/kolla: Keep consistent with others for ironic containers name  https://review.openstack.org/28055700:06
*** aginwala has quit IRC00:06
vhosakotok, I will delete all the containers and build with less number of threads then.. cool00:08
*** aginwala has joined #kolla00:08
*** kproskurin has quit IRC00:10
vhosakot"sudo docker rm -f `docker ps -aq`"   deletes all the containers at once00:10
*** Allen_Gao has quit IRC00:18
*** Allen_Gao has joined #kolla00:18
vhosakotSamYaple: are you there ?00:20
vhosakotSamYaple: here is my "docker info "00:20
vhosakothttp://paste.openstack.org/show/487515/00:20
vhosakotI'm using aufs graph driver....00:20
*** diogogmt has quit IRC00:21
vhosakotshould we use btrfs for kolla ?  Doesn't kolla support aufs ?00:21
*** mbound has quit IRC00:26
*** tzn has joined #kolla00:28
Allen_Gaovhosakot: I think no limit, FYI I'm using overlayfs00:29
*** salv-orlando has quit IRC00:32
vhosakotAllen_Gao: cool, thanks!00:34
*** tzn has quit IRC00:39
*** iceyao has joined #kolla00:58
SamYaplevhosakot: this isnt a kolla issue00:59
SamYapleits a docker and your storage backend issue00:59
SamYaplewith slower storage docker trips over itself trying to do multiple things00:59
SamYapleits a single threa daemon00:59
vhosakotSamYaple: aufs issue on my Ubuntu ?00:59
SamYaplejust lower the number of threads you use to build to like 2 or 401:00
SamYapleshould help01:00
SamYapleno01:00
vhosakotSamYaple: is the number of thread configurable in globals.yml ?01:00
SamYapleaufs is slow, btrfs would probably work better01:00
SamYaplevhosakot: this is a buildtime issue not a deploy time issue01:00
SamYapleall that cruft is from building01:00
*** iceyao has quit IRC01:00
vhosakotkolla-buid's number of threads.. is this something I can configure in globals ?01:01
SamYapleno globals is for deploying, kolla-ansible01:01
SamYaplekolla-build.conf is for building01:01
vhosakotah01:01
vhosakotwhere is kolla-build.conf ?01:02
SamYaplehave you generated it?01:03
vhosakotI see kolla/etc/oslo-config-generator/kolla-build.conf01:03
SamYapleyea thats the generated location01:03
vhosakothow can I generate it ?01:03
SamYaplethats it01:03
vhosakotoh ok01:03
vhosakotI see two.. which one ?01:04
vhosakot/home/kolla/kolla/etc/oslo-config-generator/kolla-build.conf01:04
vhosakot/usr/local/share/kolla/etc_examples/oslo-config-generator/kolla-build.conf01:04
*** tobe has joined #kolla01:04
vhosakotwhich of these two ?01:05
*** JoseMello has joined #kolla01:06
*** iceyao has joined #kolla01:08
vhosakothow can I set conf.threads ?01:10
SamYaplevhosakot: either config. also from the cli01:11
vhosakothow can I lower the number of threads ?01:11
vhosakotwhat is the command ? :)01:11
vhosakotI'm three days old in kolla :)01:12
*** jtriley has joined #kolla01:12
vhosakotI see it!01:12
vhosakot  --threads THREADS, -T THREADS, --kolla-build-threads THREADS01:12
vhosakot:)01:12
vhosakothow many should I use ?01:12
vhosakotlike 10 ?01:12
*** Allen_Gao has quit IRC01:15
*** Allen_Gao has joined #kolla01:15
*** Allen_Gao has quit IRC01:16
*** allen has joined #kolla01:16
*** allen has quit IRC01:17
*** diogogmt has joined #kolla01:18
SamYaplethe default is 801:20
SamYapleyou should use 2 or 401:20
*** iceyao has quit IRC01:20
*** iceyao has joined #kolla01:21
*** vhosakot has quit IRC01:24
*** vhosakot has joined #kolla01:25
*** vhosakot has quit IRC01:29
openstackgerritMerged openstack/kolla: Refined documentation regarding registry  https://review.openstack.org/28208401:32
*** sdake_ has joined #kolla01:34
*** iceyao has quit IRC01:35
*** sdake has quit IRC01:36
*** iceyao has joined #kolla01:36
*** ssurana has quit IRC01:38
*** sdake has joined #kolla01:38
*** Serlex has left #kolla01:39
*** sdake_ has quit IRC01:41
claytonSamYaple: have you thought about how to handle keepalived for HA routers now that you can run neutron l3 agent inside its own container?01:41
*** Allen_Gao has joined #kolla01:41
claytonseems like it would be bad to run them inside the l3-agent container, since restarting that container would probably cause gateway failovers01:42
*** Allen_Gao has quit IRC01:42
*** Allen_Gao has joined #kolla01:42
SamYapleclayton: not neccesarily01:43
SamYaplekeepalived can keep the vip on the same host even if the process dies01:43
SamYaplelook at the -V option01:43
*** Liuqing has joined #kolla01:44
*** tfukushima has joined #kolla01:44
claytonyeah, but if it's the primary and stops heartbeating then the backup is going to take over01:44
claytonseems like you'd want to avoid those sort of spurious failovers if you can01:45
SamYapleits a configurable failover, and its like 10 seconds I think. but you can always stop the other ones or increase the time out01:45
SamYaplehavent really looked into it to be honest01:45
claytonnod.  I've been thinking about it.  my thought was to work out a way to run the keepalived processes in another container that I'd almost never restart01:46
claytonnot sure how gross I think that is compared to the other options01:46
*** allen has joined #kolla01:47
claytonbut honestly I don't know enough about how l3 agent manages keepalived to know how practical that is01:47
claytonhoping to get some time in the next few weeks to look into it01:47
SamYaplemy best guess right now (10 seconds in to thinking about it) is jacking up the heartbeat timeout to like 60 seconds01:48
claytonideally I'd like my failover to be faster than that :)01:49
*** allen has quit IRC01:49
*** allen has joined #kolla01:49
SamYaplei agree. but again, havent really thought about it :)01:50
*** allen has quit IRC01:50
claytonfair enough, I'll let you know if I come up with anything clever01:50
SamYaplesounds good01:50
*** vhosakot has joined #kolla01:53
*** aginwala has quit IRC01:54
vhosakotSamYaple: ok, will use 4 threads then... thanks!01:55
vhosakotwill file a bug for this01:55
SamYaplevhosakot: that is not a bug01:56
SamYapleplease dont file one for it01:56
SamYapleor if you do, do it in docker01:56
*** tobe has quit IRC01:56
*** aginwala has joined #kolla01:56
vhosakotSamYaple: don't you think kolla-build must find if images are leaked due to aufs issue.. if, reduce the number of threads and build ?01:57
vhosakotSamYaple: like build throttling01:57
SamYaplevhosakot: it doesnt happen to me01:57
SamYapleor the gate01:57
SamYaplei use AUFS01:57
vhosakotI saw it :)01:58
SamYapleits a docker daemon bug01:58
SamYapleif you want to provide a 'FAQ' type doc, thats fine, but its not a kolla bug01:58
vhosakotso, the images in "docker ps -a" in http://paste.openstack.org/show/487514/... aren't they built by kolla ?01:58
vhosakottiny_babbage, hopeful_sinoussi, stupefied_golick, cocky_kare, etc etc01:59
SamYaplevhosakot: kolla-build tells docker to build it. after that its in docker engines control01:59
SamYapledocker engine is failing here01:59
sdakeSamYaple isn't there a case where partial builds end with a container that is left for debug purpose?01:59
SamYaplesdake: yea but this isnt it01:59
vhosakotah, so those funny names are genertaed by docker then ? not kolla ?01:59
SamYaplevhosakot: correct01:59
vhosakotah02:00
sdakevhosakot yes generated by docker02:00
sdakei was thinking it was an intermediate build leak but i'm not certain02:00
sdakelk4d4 (docker guy) says the threading in docker is maddening :)02:00
SamYaplemore like it dosnt exist02:00
sdakeall kinds of races02:00
SamYapleits very single threaded02:00
sdakego has all kinds of multithreading02:01
sean-k-mooneysdake: esplically if you try to delete images concurrently02:01
sdakei'm not a gopher dude02:01
SamYaplemultithreading is very much non-existant in the docker engine02:01
sdakebut its got goroutinees built in02:01
vhosakot"docker images built simultaneuosuly in multi-threaded manner cause leaked images with aufs graph driver"  is this the right way to write the bug against docker ?02:01
SamYapleits psuedo multithreading02:01
sdakeand docker uses that heavily02:01
sean-k-mooneycorrect me if im wrong but are goroutines like isolate or greenthreads?02:02
sdakethey are no coroutines no02:02
vhosakotSamYaple, sdake is the wording right ?02:02
sdakethey are full linux threads02:03
vhosakot" docker images built simultaneuosuly in multi-threaded manner cause leaked images with aufs graph driver"02:03
vhosakoti will file a bug against docker02:03
vhosakotI need to know what to write :)02:03
sdakevhosakot that sounds good02:03
vhosakotcool02:03
sean-k-mooneysdake: ah good to know, thanks.02:03
sdakemake sure to show all the leaked stuff02:03
sdakedocker inspects on each one woud lbe helpful for them as well i suspect02:04
vhosakotsdake, SamYaple how about this... if kolla-build sees this leaked image issue I'm seeing, kolla-build should throw and error and exit02:04
sdakeno we don't want exits02:04
vhosakotbecause, other images may pass ?02:04
sdakeyes02:04
sdakeand we have retry02:04
openstackgerritMerged openstack/kolla-mesos: Make Mesos resources configurable  https://review.openstack.org/28014402:05
vhosakothttp://paste.openstack.org/show/487514/    if you look at this, none passed for me :)02:05
SamYaplevhosakot: no see thats the point. its docker failing. you can have those leaking containers and build images correctly02:05
SamYaplekolla has no idea02:05
SamYapleit just has what docker tells it02:05
openstackgerritMerged openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510902:05
rhalliseywe should put that in the docs02:05
rhalliseykolla has no idea02:05
vhosakotI will update the docs, sure02:05
SamYaplerhallisey: ive honestly never seen it outside of the gate02:06
SamYapleand i fixed that in the gate02:06
sdakei've only seen in in vms myself on my laptop02:06
sdakewith overlayfs02:06
SamYapleyea its a "your stuff is too slow" problem02:06
rhalliseyI was joking02:06
rhalliseyI was taking about 'kolla has no idea'02:06
SamYapleWhat would 'kolla' look like?02:07
vhosakotSamYaple: doesn't kolla need "let me slow down then" mechanism ? :)02:07
SamYaplewe need a graphic02:07
rhalliseysdake, has a sticker02:07
SamYaplevhosakot: it has one! threads02:07
rhalliseygolden ticket right02:07
rhallisey?02:07
SamYapleoh jeez that golden ticket stuff02:07
sdakeyup golden ticket02:07
*** allen has joined #kolla02:07
sdakebut too late to use that02:07
SamYapleok dinner02:08
vhosakotdoes kolla-buidl check the output for "docker ps -a" after building each image to check if the image was built fine ?02:08
SamYaplenope02:08
vhosakotSamYaple: shouldn;t it check ?02:09
SamYapleits goign to trust docker for that02:09
SamYaplenope02:09
vhosakotwell, we know what docker is doing for me in aufs02:09
SamYapleagain, that stuff can stick around and have perfect images02:09
vhosakotok cool02:09
vhosakotI was thinking, if the built image if missing in "docker ps -a", print a message.. does it make sense02:10
sean-k-mooneyyou could just use the regex suppot in tools/cleanup-containers to delete the leaked conteiners aferwards  and we could document the issue?02:10
*** Marga__ has joined #kolla02:10
*** sdake_ has joined #kolla02:11
sean-k-mooneyvhosakot: out of interest what kernel are you using?02:11
vhosakotubuntu 14.04 4.2.0-27-generic02:12
*** sdake has quit IRC02:12
sean-k-mooneyoh ok i recent ly upgreaded to that too. i was noticing some aufs errors in dmesg02:12
vhosakotI'm talking about kolla-build finding built containers that are missing in "docker ps -a" and retry building them02:12
vhosakotif a built image is missing in "docker ps -a", shouldn't it be retried ?02:12
sean-k-mooneyvhosakot: after the image is built why would docker keep the conteiner in docker ps -a if it was not running?02:14
*** Marga_ has quit IRC02:14
*** Allen_Gao has quit IRC02:14
vhosakotsorry, I did not say correctly, if funny names are found in "docker ps -a" :)02:15
*** allen is now known as Allen_Gao02:15
sean-k-mooneyvhosakot: if you have other container on you plathform that could cause issues though02:15
vhosakotright right02:16
vhosakotok, I was getting my questions answered! :)02:16
vhosakotcool, I will retry with lesser number of threads! :)02:16
vhosakotthanks!02:16
sean-k-mooneySamYaple: are you still around? i was going to respond to https://review.openstack.org/#/c/275932/ but it could be quicker if you were here?02:17
sean-k-mooneySamYaple: ill take that as a no :) TLDR if source infra containers are not desired for binary disto i can work with that and ill drop the review02:20
sean-k-mooneySamYaple: i did want to get your and everyones input on an intermediate solution until packages of ovs with dpdk are available02:21
sdake_sean-k-mooney have to say i am not keen on building infra packages from source02:22
sdake_they are far too complex and hard to get correct02:22
sean-k-mooneyyes i know02:23
sdake_if we permit openvswitch we end up permitting all infra services to be built from source02:23
sean-k-mooneyi have been maintain devstack support for ovs with dpdk since icehouse so i was hopeing to enable ovs with dpdk in kolla next cycle02:23
sdake_is dpdk some type of plugin?02:24
sean-k-mooneybinary packages should be available in ubuntu 16.04. it is an optional compile time libary02:24
sdake_if so we have made a decision that we want plugin support already02:24
sean-k-mooneyso its basically a different build target when building ovs02:25
sean-k-mooneyit does not use the kenel module and does all forwarding in userspace02:25
sdake_dpdk is a replacement for the kernel mdoule?02:26
sdake_i know i could google to find out02:26
sdake_but been rolling since 5am02:26
sdake_8pm now02:27
sean-k-mooneyyes kindof. ovs has a netdev datapath. dpdk is an optional extention to that datapath02:27
sdake_want to understand what use case your after02:27
sean-k-mooneybasically dpdk is an opensouce toolkit for developing high performace packet processing applicaitons02:28
sean-k-mooneyit was started by intel and 6wind and has beeen integreated with upstream openvswitch02:28
*** dims has joined #kolla02:28
sdake_which language02:28
sdake_c?02:28
sean-k-mooneyits in c yes02:28
sdake_cool i like c02:28
sdake_however being a C master, I understand the complexity of building from source vs doing so for python packages02:29
*** dims_ has quit IRC02:29
sean-k-mooneyso basically how dpdk works is it uses a userspace driver to poll the nic instead of being interupt driven.02:29
sean-k-mooneyyes the build chain add some challanges but it is relativly stable02:30
sdake_will you be in austin?02:30
*** aginwala has quit IRC02:30
sean-k-mooneyyes probably. i should find out in the next week or 2. so what i wanted to ask was as packages are not yet availabel and since02:30
sean-k-mooneykolla would prefer not to do source build of infra contianers02:31
sdake_i dont think we ha ereally made a deicision on that point sean-k-mooney02:31
sdake_we have made a decision to build python from source02:32
sdake_other things no decision has been made02:32
sdake_probably worth a design session at summit02:32
sean-k-mooneyoh ok . i would the comunity be ok if i added source deployment support for ovs form souce to another repo i maintian for the mitika cycle02:33
sdake_mitaka is over capacity at the moment02:33
sdake_we have apprxoimately 100 unsolved bugs02:33
sean-k-mooneyoh yes i know02:33
sdake_and 40 unimplemented blueprints02:33
sdake_i dont want to add any more stuff to mitaka :)02:34
sdake_its not a "I dont like your idea thing" it a "holy shit we have too much risk" thing :)02:34
sean-k-mooneysure02:34
sean-k-mooneyi was actully going to suggest not doing anything upstream until newton02:35
sdake_yes you mentioned both above is why I point that out :)02:35
sdake_[19:33:03]  <sean-k-mooney>oh ok . i would the comunity be ok if i added source deployment support for ovs form souce to another repo i maintian for the mitika cycle02:35
sean-k-mooneyyes i miss phrase as i started reading your message while typeing, i mainting dpdk support of openstack in https://github.com/openstack/networking-ovs-dpdk02:36
sean-k-mooneywould you be ok if i added a kolla sub folder to keep some experamental support for this cycle?02:37
sdake_sub folder to kolla repository?02:37
*** sdake_ is now known as sdake02:37
sdakewe have not made a deicision on a /contrib directory02:38
sdakei think the cores are in favor02:38
sean-k-mooneyi would like to submit a blueprint/spec to dicuss for next cycle to see if this is someting that alings with kolla goals. no sub folder to networking-ovs-dpdk02:38
sdakei am not in favor prior during mitaka cycle02:38
sdakepeople are free to do with their repositories as they please :)02:38
sean-k-mooneywell so i just dont want it to be percived as a fork or anything like that as i want to work upstream as much as i can02:39
sdakethere was discussion of farming out kolla for the various projects like how devstack and horizon has done (plugins)02:39
sean-k-mooneyya that was something i was hoping would be added to kola at some point02:40
sdakeI dont know if plugins are viable in our architecture02:40
sdakenot saying they aren't02:40
sdakenot saying they are02:40
sdakebut its an open question to me at this point02:40
sean-k-mooneyi dont think the ansible code as writted is easily plugable currently but it could be if desired02:41
sdakethe bottom line is mitaka is overloaded with deliveries for kolla - our bug tracker and feature tracker are off the hook02:41
sdakeour review queue is super long02:41
sdakethe community was pretty clear that upgrades are mandatory for this cycle02:42
sdakehere is our priority discussion from idcycle:02:42
sdakehttps://etherpad.openstack.org/p/kolla-mitaka-midcycle-priorities02:42
*** Allen_Gao has quit IRC02:43
sdakeupgrades scored a 9.202:43
sean-k-mooneyok yes so ill close the review and i will submit a blueprint/ spech for dpdk support when the review backlog is less overloaded02:43
sdakethere were 9 people in the room02:43
sean-k-mooneyyes i would really like to see upgrades done too02:43
sdakediags came in second02:44
sdakestability (mostly of liberty) came in third02:44
sean-k-mooneyyes i dont know if i can help much but i would like to get more involved in kolla in general.02:45
sdakeif you want to get involed in kolla  Ican help you there ;)02:45
sdakeadding more to the plate isn't ideal in the 3 weeks we have left before mitaka-302:46
sdakelets eat the food we have first :)02:46
sean-k-mooneyyes sorry02:46
sdakeno reason to apologize02:46
sean-k-mooneyi had actuly hoped to do more this cycle on the kolla side but got tied up in neutron/nova. but if there are some low02:47
sean-k-mooneyhaging fruit bug i might see if i can fix one or two02:47
sdakedocs are low hagning fruit02:47
sdakeif you want big impact work, fix bugs that are critical/high ;)02:48
*** Allen_Gao has joined #kolla02:48
sdakeeven just 1 bug would do :)02:48
sdakeI could solve all the low hanging  fruit in a day (the docs)02:48
sdakethings like upgrades take longer02:49
sdakeone area where you could immediately help is in drop-root blueprint02:49
sdakeits not quite finished yet02:49
sdakethe work is easy02:49
sdakeand mostly done02:49
sean-k-mooneycool ill take a look. i belive the libvirt container is still not resolved for the drop-root change02:50
sean-k-mooneythat was waiting on docker 1.10 right02:50
sdakehttps://blueprints.launchpad.net/kolla/+spec/drop-root02:50
sdakeonly a few TODOs left02:51
sdakeit is waiting on contributors not docker 1.1002:51
sean-k-mooneyok cool weel ill put that to the top of my list. but yes ill look at the docs and take a look at the other open bugs too02:51
sdakesean-k-mooney should be pretty easy to copy the patterns used by other ocntainers02:52
sdakeif you ahve neutron experience, drop root would e helpful02:52
sdakehae you deployed kolla?02:52
sean-k-mooneyyes i have it running at home02:52
sean-k-mooneyim also trying to get our team to adopt it02:53
sdakesweet top 3 pain points in order please?02:53
sean-k-mooneyour corparte proxies but that is fixed with the inject file. am let me think02:54
sdakepretty sure kolla already works with corporate proxies, although its undocumented02:54
sean-k-mooneyoh it does yes02:55
sdakedave-mccowan got it rolling today behind his corporate proxy02:55
sean-k-mooneyour corparte proxies is just usally my main pain point02:55
sdakei know the last week has been a charlie foxtrot02:56
sean-k-mooneyits fairly simple to do with the kolla-build header and futter02:56
sdakebut that is atypical of our development :)02:56
sdakeyup that is why the header and footer are there - for proxies02:56
sdakeI would document it myself but I have no idea what to document ;)02:56
sdakeif you want to document the proxy thing that would be helpful02:57
sean-k-mooneyi guess right now for our team to adopt is just the ramp on ansible and docker. i have worked with docker before but ansible was new. overall the experince of using kolla has been good02:57
dave-mccowansean-k-mooney sdake documented: https://review.openstack.org/28205702:58
dave-mccowani didn't get the header/footer to work02:58
sean-k-mooneyone sec i can share mine if i sanities them02:59
*** jasonsb has joined #kolla02:59
openstackgerritDave McCowan proposed openstack/kolla: Update Instructions for Building Behind HTTP Proxy  https://review.openstack.org/28205703:01
*** Marga__ has quit IRC03:04
*** Marga_ has joined #kolla03:05
vhosakotSamYaple, sdake:  done, filed docker bug! :)   https://github.com/docker/docker/issues/2047703:06
sean-k-mooneydave-mccowan: the following is what i use https://etherpad.openstack.org/p/kolla-proxy-header-footer03:06
sean-k-mooneydave-mccowan: the pip and apt mirror are obviously optional but i like to run them locally to speed up the image build03:07
*** vhosakot has quit IRC03:08
*** JoseMello has quit IRC03:08
*** salv-orlando has joined #kolla03:09
*** Jeffrey4l__ has joined #kolla03:11
*** salv-orlando has quit IRC03:11
sdakeok folks i've hit the wall03:13
sdaketime to PT FO03:13
sdakenight night all :)03:13
sean-k-mooneyoh just realised its 3 am... i should  go to sleep too night03:14
*** tzn has joined #kolla03:17
*** vhosakot has joined #kolla03:18
*** sdake has quit IRC03:21
*** rhallisey has quit IRC03:22
*** tzn has quit IRC03:22
vhosakotother funny docker names :)03:23
vhosakothttps://github.com/docker/docker/blob/630a5a23c73276faefaedd0b639ce1525c2bdc24/pkg/namesgenerator/names-generator.go#L3003:23
*** dims has quit IRC03:32
SamYaplesean-k-mooney: if you build the package and host it _outside_ kolla in a repo then kolla can install it whith the current code. I don't see why it would need to be compiled as such by Kolla03:32
*** dims has joined #kolla03:34
*** dims has quit IRC03:37
*** vhosakot has quit IRC03:37
*** unicell has quit IRC03:41
*** Marga_ has quit IRC03:42
*** Allen_Gao has quit IRC03:48
*** tfukushima has quit IRC03:50
*** tfukushima has joined #kolla04:02
*** Marga_ has joined #kolla04:05
*** Marga_ has quit IRC04:06
*** Marga_ has joined #kolla04:06
openstackgerritLingfeng Xiong proposed openstack/kolla: Allow cinder-volume to be configured to use nfs  https://review.openstack.org/27991304:09
*** yuanying_ has quit IRC04:10
openstackgerritLingfeng Xiong proposed openstack/kolla: Add backward compatibility for liberty (ubuntu binary)  https://review.openstack.org/27989204:11
*** rstarmer has joined #kolla04:19
*** Allen_Gao has joined #kolla04:19
*** Allen_Gao has quit IRC04:24
*** Allen_Gao has joined #kolla04:29
*** Allen_Gao has quit IRC04:33
*** Liuqing has quit IRC04:47
*** Allen_Gao has joined #kolla04:48
*** yuanying has joined #kolla04:50
*** salv-orlando has joined #kolla04:51
*** Allen_Gao has quit IRC04:53
*** Liuqing has joined #kolla04:56
*** salv-orlando has quit IRC05:07
*** tzn has joined #kolla05:07
*** tzn has quit IRC05:12
*** daneyon_ has quit IRC05:17
*** daneyon has joined #kolla05:17
*** salv-orlando has joined #kolla05:22
mandreSamYaple, awesome! let's get your VM in the gate patch merged05:26
*** salv-orlando has quit IRC05:28
*** dave-mccowan has quit IRC05:28
SamYaplemandre: i think it only works on ovh gates....05:28
mandre"only worked" or "only works"?05:28
SamYapleonly worked05:30
SamYaplerax gates it "no valid hosts"'s on me05:30
SamYaplemandre: running it through some rechecks05:31
mandreSamYaple: hmmm, se we will never be completely good with a fixed setting for the hypervisor then?05:33
mandrewe need to make it dependent on whre is running the CI node?05:33
*** Allen_Gao has joined #kolla05:36
*** Allen_Gao has quit IRC05:41
*** yuanying has quit IRC05:43
SamYaplemandre: no thats not it05:54
SamYapleits just an issue i cant pinpoint yet05:55
*** Marga_ has quit IRC06:01
*** Marga_ has joined #kolla06:11
*** rstarmer has quit IRC06:12
*** Liuqing has quit IRC06:22
*** Liuqing has joined #kolla06:24
*** salv-orlando has joined #kolla06:34
*** kjelly has quit IRC06:36
*** salv-orlando has quit IRC06:37
*** Allen_Gao has joined #kolla06:41
*** Allen_Gao has quit IRC06:46
*** jasonsb has quit IRC06:52
*** tzn has joined #kolla06:56
*** tzn has quit IRC07:01
*** chandankumar has joined #kolla07:21
*** yuanying has joined #kolla07:28
*** unicell has joined #kolla07:30
*** aginwala has joined #kolla07:40
*** unicell has quit IRC07:43
*** unicell has joined #kolla07:44
*** alisonh has quit IRC07:48
*** Liuqing has quit IRC07:53
*** iceyao has quit IRC07:54
*** fgimenez has joined #kolla07:58
*** alisonh has joined #kolla08:06
*** Serlex has joined #kolla08:09
*** shardy has joined #kolla08:10
*** alisonh has quit IRC08:12
*** alisonh has joined #kolla08:15
*** asalkeld has quit IRC08:17
*** salv-orlando has joined #kolla08:22
*** mbound has joined #kolla08:30
*** salv-orlando has quit IRC08:31
-openstackstatus- NOTICE: Gerrit is going to be restarted due to performance problems08:32
*** athomas has quit IRC08:35
*** jmccarthy has joined #kolla08:43
*** liyi has joined #kolla08:43
*** mikelk has joined #kolla08:48
*** yuanying has quit IRC08:49
*** kproskurin has joined #kolla08:52
*** salv-orlando has joined #kolla09:03
*** achanda has quit IRC09:07
*** gfidente has joined #kolla09:09
*** achanda has joined #kolla09:12
*** aginwala has quit IRC09:29
*** achanda has quit IRC09:30
*** macsz has joined #kolla09:39
*** pbourke has joined #kolla09:40
*** akwasnie has joined #kolla09:42
elemoine_sdake, I created a Launchpad bug for the extend_start code duplication issue: https://bugs.launchpad.net/kolla/+bug/1546944.  We can probably find a solution to that general problem.09:44
openstackLaunchpad bug 1546944 in kolla "Tech-Debt: Duplicate code in extend_start.sh" [Wishlist,Triaged]09:44
*** pbourke has quit IRC09:45
*** tzn has joined #kolla09:50
*** fgimenez_ has joined #kolla09:50
*** fgimenez has quit IRC09:50
*** tzn has quit IRC09:51
*** tzn has joined #kolla09:51
*** pbourke has joined #kolla09:58
*** liyi has quit IRC10:01
*** pbourke_ has joined #kolla10:02
*** salv-orl_ has joined #kolla10:03
*** pbourke has quit IRC10:05
*** salv-orlando has quit IRC10:06
*** Liuqing has joined #kolla10:12
*** Liuqing has quit IRC10:14
*** tpot has quit IRC10:14
Serlexwhy are some docker images showing as none?10:18
Serlexafter kolla-build10:18
*** chandankumar has quit IRC10:19
*** tfukushima has quit IRC10:20
*** mbound has quit IRC10:20
*** fgimenez_ has left #kolla10:21
*** yuanying has joined #kolla10:25
*** shardy has quit IRC10:34
pbourke_Serlex: Im guessing you're doing 'docker images -a'10:39
pbourke_the None are just intermediate layers afaik10:39
pbourke_you shouldnt see them without the -a10:40
Serlexhmm ok10:40
SerlexI see them with docker images10:41
SerlexI failed couple failed kolla-builds, last one finished successfully10:41
SerlexI was hoping to see a clean list of docker images, but some of them still showing as none. So i'm not sure whether to deploy10:41
pbourke_http://www.projectatomic.io/blog/2015/07/what-are-docker-none-none-images/10:44
Serlexbrilliant thank you!10:47
*** tzn has quit IRC10:48
nihiliferguys using ovs - are you sure that ovs-vsctl should point to the /run/openvswitch/db.sock everytime everywhere on every distro?10:48
nihiliferi'm trying to run ovs on centos-source containers right now10:48
*** salv-orl_ has quit IRC10:48
nihiliferand i'm always getting10:48
nihiliferovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)10:48
*** Serlex has left #kolla10:48
nihiliferfor every ovs-vsctl command (no matter if that's kolla_ensure_openvswitch_configured or anything else)10:49
nihiliferwhen i specify the --db argument and provide a full path, it's working fine10:49
*** pbourke_ has quit IRC10:50
*** yuanying has quit IRC10:51
*** pbourke has joined #kolla10:52
*** chandankumar has joined #kolla10:55
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Provide ovs-db socket path directly  https://review.openstack.org/27562110:59
*** achanda has joined #kolla11:01
*** chandankumar has quit IRC11:02
*** achanda has quit IRC11:06
*** rmart04 has joined #kolla11:14
*** mikelk has quit IRC11:22
*** mikelk has joined #kolla11:22
*** salv-orlando has joined #kolla11:29
*** JoseMello has joined #kolla11:29
*** shardy has joined #kolla11:31
*** Allen_Gao has joined #kolla11:31
*** akwasnie has quit IRC11:31
*** mbound has joined #kolla11:37
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Fix Mesos-managed volumes  https://review.openstack.org/28229311:39
*** Allen_Ga_ has joined #kolla11:40
*** Allen_Gao has quit IRC11:40
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Fix Mesos-managed volumes  https://review.openstack.org/28229311:42
*** Allen_Gao has joined #kolla11:44
*** tzn has joined #kolla11:44
*** Allen_Ga_ has quit IRC11:46
*** tzn has quit IRC11:48
*** tzn has joined #kolla11:48
*** dave-mccowan has joined #kolla11:49
*** akwasnie has joined #kolla11:50
*** chandankumar has joined #kolla11:50
*** Allen_Gao has quit IRC11:56
*** bmace has quit IRC11:56
*** bmace has joined #kolla11:57
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Fix Mesos-managed volumes  https://review.openstack.org/28229311:58
*** Allen_Gao has joined #kolla12:00
*** Allen_Gao has quit IRC12:01
*** Allen_Gao has joined #kolla12:02
*** tzn has quit IRC12:05
*** rmart04 has quit IRC12:18
*** rhallisey has joined #kolla12:19
*** tzn has joined #kolla12:26
*** shardy has quit IRC12:29
*** dims_ has joined #kolla12:29
openstackgerritAllen Gao proposed openstack/kolla: Keep consistent with others for ironic containers  https://review.openstack.org/28055712:32
*** stvnoyes has quit IRC12:33
*** stvnoyes has joined #kolla12:34
*** sdake has joined #kolla12:43
sdakemorning12:45
*** iceyao has joined #kolla12:48
akwasnie hi sdake12:49
sdakehey akwasnie12:49
sdakedid you sync up with elemoine on the merge plan for diags?12:49
akwasnieyes, he prepared a good plan, I just added one point about making sure Kibana is working correctly witk Heka and Elasticsearch12:50
sdakeok, fwiw normally we process patches in order submitted and yours was first, so this is a bit unfair to you12:50
sdakeapologies for that, but sometimes technical reasons make a different ordering more appropriate12:51
*** tzn has quit IRC12:51
sdakei think the current ordering plan is the right order12:51
sdakebuttom up12:51
akwasniesdake, np:)12:51
akwasnieI think it is a right order too12:52
*** pbourke has quit IRC13:01
elemoine_sdake: I hope my comment regarding file_match was clear enough13:01
elemoine_otherwise I'm happy to discuss this more13:01
sdakeelemoine i didn't see it13:01
sdakecan you give me the tldr13:02
sdakeelemoine note I dindnt -1 your patch :)13:02
elemoine_https://review.openstack.org/#/c/279489/13:02
sdakeelemoine yes but why is not swift and cinder and heat in there13:03
elemoine_I have separate patches/commits for cinder and heat13:04
sdakeyes but its the same file13:04
elemoine_and these patches come after that of Neutron13:04
sdakeshouldn't that file_match have swift|cinder|heat|glance|neutron?13:04
elemoine_this is the patch for cinder : https://review.openstack.org/#/c/281259/8/ansible/roles/common/templates/heka-openstack.toml.j213:04
sdakewhat do you expect file_match should be at he conclusion of hte merging13:05
*** pbourke has joined #kolla13:05
elemoine_the last openstack service patch is magnum: https://review.openstack.org/#/c/28132913:06
elemoine_so https://review.openstack.org/#/c/281329/7/ansible/roles/common/templates/heka-openstack.toml.j213:06
elemoine_is the final state13:06
elemoine_note that Swift is not treated the same way – Swift still uses Syslog13:07
elemoine_see https://review.openstack.org/#/c/279490/9 (wich you -1'ed)13:07
sdakeelemoine must havebeen tired during original review13:09
sdakeignore my comment13:09
sdakei'll fix up the reviews now jus ta moment13:09
elemoine_no problem at all13:10
*** fthiagogv__ has quit IRC13:12
*** Allen_Gao has quit IRC13:13
*** Serlex has joined #kolla13:14
sdakeelemoine I thought gerrit top was first patch gerrit bottom was last patch13:15
sdakeelemoine your sayign gerrit top patch is last patch, gerrit bottom is first patch13:15
sdakeelemoine this is why I was confused by the comment13:15
sdakeerr by the change13:15
* sdake learning new gerrit ropes yet again13:15
elemoine_gerrit is broken :)13:15
*** Allen_Gao has joined #kolla13:16
sdakei like the related changes full view13:16
elemoine_it depends on the current patch13:16
sdakethats a cool feature13:16
elemoine_I like it too but I find the order confusing at times13:16
sdakeelemoine did you get my request for filing a techdebt bug13:18
sdakeabout unifying all the commonality you have in extend_start if thats possible13:18
elemoine_I had done it already13:18
elemoine_just a sec13:18
sdakeyou had filed a tech debt bug?13:18
elemoine_yes13:18
elemoine_https://bugs.launchpad.net/kolla/+bug/154694413:19
openstackLaunchpad bug 1546944 in kolla "Tech-Debt: Duplicate code in extend_start.sh" [Wishlist,Triaged]13:19
*** salv-orlando has quit IRC13:21
sdakeelemoine can you confirm that all heka work is done with this patch set?13:22
*** pbourke has quit IRC13:23
sdakeelemoine what is your launchpad id?13:23
elemoine_we need to remove Rsyslog but SamYaple suggested that we do that after merging this patchset13:23
sdakeagreed13:23
elemoine_launchpad id: elemoine13:23
sdakeelemoine tbh I didn't think you would hit our deadlines :)13:24
sdakeany bugs found can be fixed in the rcs13:24
elemoine_and I'm currently fixing Swift13:24
sdakenice job!13:24
elemoine_thanks13:24
sdakei want the full stack tho, so work with akwasnie to get her work merged asap13:24
*** pbourke has joined #kolla13:24
sdakewhatever it takes13:24
sdakehey pbourke13:24
elemoine_sure13:24
pbourkesdake: hey13:24
sdakewe have 2 weeks left13:24
elemoine_I've reviewed her ES patch many times and it looks good to me13:25
*** Allen_Gao has quit IRC13:25
sdakeelemoine interested in joining the kolla-drivers team?13:25
sdakethese folks have ability to flip bits in launchpad13:25
sdaketriage bugs and whatnot13:25
*** Allen_Gao has joined #kolla13:25
*** akwasnie has quit IRC13:26
sdakecool13:26
sdakeapologies for coming to these reviews late13:27
sdakebut I thnk there will need to be some integration work done between the two patchsets13:27
*** Allen_Gao has quit IRC13:27
*** Allen_Gao has joined #kolla13:28
elemoine_sdake: sure!13:31
sdakeelemoine what we need now is rechecks on your patchset when it  fials the gate13:31
sdakei have kicked off  some13:31
sdakeand will finish all the rechecks in this patchset this morning13:31
sdakebut I am not around24/713:31
*** Allen_Ga_ has joined #kolla13:31
sdakeI need to sleep and eat and take care of my children13:31
sdakeso if you chould scan the patch set every couple hours for gate failures and recheck the ones that fail ci13:32
sdakeevery 2 hours should do13:32
elemoine_ok13:32
sdakei think we are good to merge this entire patch set13:32
sdakefrom what I've seen soo far13:32
elemoine_as I said I am working on debugging Swift right now13:32
elemoine_but that can be a new patch (on top of the rest)13:33
elemoine_to avoid rebasing the whole thing13:33
*** Allen_Gao has quit IRC13:35
sdakeelemoine_ re:13:39
sdakehttps://review.openstack.org/#/c/275842/2213:39
elemoine_yep13:40
sdakeit logs to /var/log/kolla/heka13:40
sdakeis that correct for keepalived and haproxy?13:40
sdakeshouldn't it log to /var/log/kolla/loadbalance?13:40
sdakeor something like that13:40
sdakeor /var/log/kolla/high-availability13:40
elemoine_it logs to /var/lib/kolla/heka/log13:40
sdakelog is a log device?13:41
*** allen has joined #kolla13:41
elemoine_log is a Unix socket, created by Heka for Syslog-type logging13:41
sdakeok13:41
sdakethanks13:41
elemoine_it works the same way as Rsyslog here13:41
*** allen has quit IRC13:41
elemoine_and I'm trying to do the same for Swift13:42
*** dwalsh_ has joined #kolla13:42
*** dwalsh has joined #kolla13:42
*** Allen_Gao_ has joined #kolla13:43
*** Allen_Ga_ has quit IRC13:45
sdakeelemoine_ rpbolem found in https://review.openstack.org/#/c/275841/2013:45
*** Allen_Gao has joined #kolla13:45
sdakeplease file a techdebt bug to fix it13:45
elemoine_rename of the volume?13:46
elemoine_the "heka" volume13:46
sdakeyes13:46
sdakeheka could be used by soemone else13:46
elemoine_what about mariadb?13:47
sdakethis would surely cuse problems no?13:47
*** Allen_Gao has quit IRC13:47
sdakewhat is mariadb's volume name?13:47
elemoine_and rabbitmq?13:47
elemoine_run docker volume ls13:47
*** Allen_Gao_ is now known as Allen_Gao13:47
sdakei dont have a deployment that works13:47
elemoine_and see the volume names used by kolla13:47
*** shardy has joined #kolla13:47
sdakecan you paste that for m e please13:48
elemoine_sdake: http://paste.openstack.org/show/487573/13:48
sdakemy gear is imapired13:48
elemoine_basically we do not namespace volumes13:48
sdakeok file a bug that all named volumes must be prepended with kolla_13:48
sdakeand we can tackle as one piece of work13:48
elemoine_yeah, a more general bug13:49
elemoine_I'll do it13:49
sdakeusing mariadb as a named volume is sure to cause problems13:49
sdakeelemoine_ link bug so i  can triage please13:51
*** achanda has joined #kolla13:52
*** salv-orlando has joined #kolla13:54
elemoine_I haven't created it yet13:54
elemoine_you want it now?13:54
sdakeelemoine https://review.openstack.org/#/c/275840/1413:59
limamauricionova uses ceph to boot an image?13:59
sdakeyes file all tech debt bugs now13:59
sdakeso  Ican triage13:59
sdakelimamauricio if ceph is configured, yes13:59
sdakeif ceph is configured, glance and nova data are stored in ceph13:59
sdakeincluding boot images etc14:00
limamauricioso, what virt_type i should use?14:00
limamauricioqemu?14:01
*** diogogmt has quit IRC14:01
sdakeif your in a vm yes14:01
*** tzn has joined #kolla14:01
*** tzn has quit IRC14:01
*** tzn has joined #kolla14:01
limamauriciohmm14:01
*** fthiagogv has joined #kolla14:02
limamauricioi'm failing14:02
limamauricio:/14:02
*** diogogmt has joined #kolla14:02
sdakeok well i've got the school rush now, so I  can't help unfortunately - I'll be back later14:03
limamauriciook14:03
limamauriciothanks14:03
sdakeelemoine your patch set looks good to go, lets get  the gate at 100% on all the patch sets14:03
sdakeelemoine and get those tech debt bugs filed on the first patch14:04
sdakeelemoine and get them fixed in your local repo so they are ready to go14:04
sdakethe chown 400 seems most critical - moreso then swift14:04
limamauriciosomeone already boot an image successfully using centos + ceph?14:05
*** jtriley has quit IRC14:06
*** spisarski has quit IRC14:08
elemoine_sdake https://bugs.launchpad.net/kolla/+bug/154753314:12
openstackLaunchpad bug 1547533 in kolla "Tech-Debt: Namespace the Docker volumes" [Undecided,New]14:12
*** pbourke has quit IRC14:12
*** pbourke has joined #kolla14:13
sdakeactually I'm not sure namespacing makes sense14:14
sdakesince we expect dedicated gear14:14
sdakeand the rest of our services are nto namespaced14:14
elemoine_I was wondering too14:14
sdakewell argue more with me then :)14:15
sdake7am - brain not working at its finest :)14:15
limamauriciosomeone already boot an image successfully using centos + ceph?14:15
sdakelimamauricio yes i have in the past14:15
sdakenot after 1.10 tho ;) - my env is not operational enough to do so14:16
limamauricio:/14:16
elemoine_sdake: I preferred to create the bug and argue there :)14:16
limamauricioi tried to boot an image, but it failed14:16
sdakeok14:17
limamauricionow i dont know if my deploy is working well14:17
sdakewell we do need tracking bugs for the first patch in your series14:17
sdakethe chmod 40014:17
sdakeI am retty sure sudoers file must be chmod 40014:17
sdakeand owned by root:14:17
sdakeheka (and rsyslog0 are definately different then mariadb14:18
sdakeheka or rsyslog may be installed in a container by default installation of os down the road14:19
sdakeits a tough call14:19
sdakenamespacing everything would be best ;-)14:19
sdakebut that makes upgrades a huge pita14:19
SerlexHi guys, is it safe to reload a vagrant machine after host was shutdown?14:20
elemoine_sdake: I created bugs for those as well14:24
*** achanda has quit IRC14:24
*** achanda has joined #kolla14:24
*** achanda has quit IRC14:25
*** akwasnie has joined #kolla14:29
*** macsz has quit IRC14:30
*** jtriley has joined #kolla14:33
akwasniehttps://review.openstack.org/#/c/267714/ - can anyone take a look and do a review?14:33
akwasniewith elemoine we would like to start integration of heka and elasticsearch14:34
akwasnieand this review blocks us a bit :)14:34
*** diogogmt has quit IRC14:37
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Fix nova group name in nova.conf.j2  https://review.openstack.org/28046514:38
*** openstackgerrit_ has quit IRC14:43
*** chandankumar has quit IRC14:43
*** openstackgerrit_ has joined #kolla14:44
nihiliferif no "more eyes" will look at that in ~30 mins, i'm just going to give +1w14:47
*** diogogmt has joined #kolla14:49
*** openstackgerrit_ has quit IRC14:49
openstackgerritMerged openstack/kolla-mesos: Fix nova group name in nova.conf.j2  https://review.openstack.org/28046514:50
akwasnienihilifer: nice :P14:51
*** spisarski has joined #kolla14:57
*** openstackgerrit_ has joined #kolla14:57
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Fix glance-registry enable typo  https://review.openstack.org/28046614:58
*** openstackgerrit_ has quit IRC14:59
*** openstackgerrit_ has joined #kolla15:00
*** akwasnie has quit IRC15:02
pbourkeSamYaple: ping15:02
*** tzn has quit IRC15:03
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Split glance group into 2 groups  https://review.openstack.org/28237215:04
*** unicell has quit IRC15:04
*** Jeffrey4l__ has quit IRC15:07
pbourkeanyone here working on upgrades atm?15:07
*** jasonsb has joined #kolla15:10
*** dave-mccowan has quit IRC15:11
openstackgerritMerged openstack/kolla-mesos: Fix glance-registry enable typo  https://review.openstack.org/28046615:13
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Split glance group into 2 groups  https://review.openstack.org/28237215:15
*** blahRus has joined #kolla15:18
*** d_code has joined #kolla15:18
SamYaplepbourke: pong15:24
pbourkeSamYaple: hey man15:24
*** dave-mccowan has joined #kolla15:25
pbourkeSamYaple: I have the following scenario15:25
*** achanda has joined #kolla15:25
pbourkeSamYaple: basically you have a running liberty setup, then move to master and run an upgrade task15:25
openstackgerritMerged openstack/kolla: Added Elasticearch and its deployment.  https://review.openstack.org/26771415:25
pbourkeSamYaple: what Im seeing is the common role does not run, so no kolla-toolbox15:25
pbourkeSamYaple: any idea why that might be, i.e. it runs for -e action=deploy but not upgrade15:26
SamYaplepbourke: i dont quite follow15:27
SamYaplethe common role will run once per play15:27
SamYaplecan you give me a way to replicate it?15:27
pbourkesure, one sec15:27
*** dims_ has quit IRC15:27
SamYaplehey sdake mandre I would like to merge this https://review.openstack.org/#/c/28074915:27
limamauricioI ran docker exec ceph_osd_0 ceph -s and i have it http://pastebin.com/Y3sNveAr15:27
pbourkeor more a few mins, I'll roll back my env and try to get a set of steps15:27
SamYaplebut I dont want the failure to schedule vm to fail the gate15:28
SamYapleso i suggest we launch the vm but dont track the results15:28
SamYapleit will still fail if, say, it cant create a network or upload a glance image15:28
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: [WIP] Add openvswitch support  https://review.openstack.org/28238415:28
SamYaplebut for the booting itself, I dont want to fail for that reason15:28
limamauricioceph is not running very well, right?15:29
openstackgerritMerged openstack/kolla: Launch VM in gate  https://review.openstack.org/28074915:29
*** mbound has quit IRC15:29
elemoine_all the Heka patches but the very first one passed the gates15:29
elemoine_I'm not sure what to do about https://review.openstack.org/#/c/275840/15:30
*** achanda has quit IRC15:30
*** sdake_ has joined #kolla15:30
elemoine_should I recheck it?15:31
*** sdake has quit IRC15:31
*** mbound has joined #kolla15:31
*** Marga_ has quit IRC15:33
SamYaplelimamauricio: I have typically used ceph exclusively, why do you ask15:35
openstackgerritMerged openstack/kolla-mesos: Split glance group into 2 groups  https://review.openstack.org/28237215:35
limamauricioI can not boot an image in the nova15:36
SamYapleelemoine_: that is unrelated to teh failures15:36
SamYapleelemoine_: you can clearly see your stuff builds fine. a recheck should not be needed15:36
limamauricioand i do know if i deploy it correctly15:37
SamYaplesdake_: ping ^ no need to recheck that in my opinion15:37
*** chandankumar has joined #kolla15:37
elemoine_understood15:38
elemoine_SamYaple: I am currently debugging Swift (and making progress)15:38
elemoine_but I want to fix it with a new CR, as opposed to doing a rebase15:39
elemoine_I am pretty sure you'll agree with that :)15:39
limamauricioi'm trying to build and deploy kolla + centos + binary15:39
SamYapleelemoine_: i do. this is why i dont like 15 patches in a stream personally15:40
SamYaplesdake is a big fan of  them for some reason15:40
*** inc0 has joined #kolla15:40
inc0good morning15:40
SamYaplemorning inc015:40
elemoine_and it's hard to maintain for me15:40
SamYapleelemoine_: i would personally soon seen larger patchsets for stuff like this, requiring more thorugh review15:42
elemoine_SamYaple: what do you mean?  I did not understand you15:43
SamYapleelemoine_: dont worry about it. the takeaway is i dont like 20 patchset streams for these reasons!15:44
sdake_the reason I am a fan is so that patches may be reviewed as one unit if people care to do so15:46
sdake_ok i've got a dr appointment back in few hours15:46
sdake_id like the rechecks to finish up - only 3-4 patches don't pass the gate15:46
sdake_we should be able to merge today if we stay on top of the rechecks15:47
SamYaplesdake_: all of them pass now15:47
sdake_all gates/15:47
sdake_i rechecked them a couple hours ago15:47
SamYapleplease dont kill infra resources for unrelated failures....15:47
sdake_i've really got to jet, i'll remove my -215:47
sdake_infra has load management in their system15:48
sdake_they can handle large patch sets15:48
sdake_gotta jet15:48
SamYapleits drags it all down man15:48
sdake_this is not passing the gate https://review.openstack.org/#/c/275841/15:48
SamYaplesdake_: i just saw it and issued recheck15:49
*** fthiagogv has quit IRC15:49
*** fthiagogv has joined #kolla15:49
sdake_this is not passing gate https://review.openstack.org/#/c/279490/915:49
elemoine_SamYaple, sdake_ sorry it was me saying that they were all passing the gate15:50
SamYapleelemoine_: no i looked too15:50
SamYaplethis is the problem with 20 patchset streams...15:50
elemoine_I got confused with something else15:50
SamYapleeasy to miss things15:50
sdake_this is not passing gate:15:50
sdake_https://review.openstack.org/#/c/275841/2015:50
SamYaplesdake_: you already listed that one15:51
sdake_oh sorry15:51
sdake_ok those 3 need to pass gate15:51
SamYaple215:51
sdake_then I'll remove -115:51
SamYaple215:51
sdake_rather -215:51
limamauricioSamYaple, i want to user qemu, but it not works15:51
sdake_ok gotta jet back in couple hours15:51
SamYaplesdake_: no theres only 215:51
sdake_by then hopefully the whole stream passing gate15:51
sdake_bbiaf15:51
*** dencaval has joined #kolla15:51
elemoine_the latter is a python27 problem, while my code does not include python code :)15:51
sdake_elemoine_ i understand15:51
SamYapleelemoine_: in this case though that doesnt matter15:51
sdake_python is a voting gate15:52
SamYaplesdake_: actually no thats a check15:52
sdake_so it has to pass absolutely or the whoel patch stream wont merge15:52
SamYapleit can merge ithout passing that15:52
SamYapleit just has to pass the check run15:52
sdake_oh i thought it was gating15:52
sdake_it hsould be gating ;-)15:52
sdake_bbiaf15:52
sdake_seriously ahve to run15:52
SamYapleit is gating15:52
SamYaplethats a check though15:52
limamauricioyou do it to use qemu? the default value is kvm...15:52
sdake_yes i know15:52
SamYaplegating doesnt occur until merge15:52
SamYapleyou can merge with failed checks15:52
sdake_yes I understand how gating works :)15:53
sdake_ok gotta roll15:53
SamYaplethen we dont need to recheck15:53
SamYapleif you understand :015:53
pbourkeSamYaple: ok - deploy liberty keystone+rabbitmq+mariadb. Switch to master, upgrade just keystone. kolla-toolbox is not started15:54
openstackgerritMerged openstack/kolla-mesos: Fix Mesos-managed volumes  https://review.openstack.org/28229315:54
pbourkeSamYaple: it says 'registering common role has run' but then skips on ahead. whats the deal with that logic15:55
pbourkeso it doesn't run for every role?15:55
*** tzn has joined #kolla15:55
SamYaplepbourke: ah look at common/tasks/upgrade.yml15:55
pbourkeits empty...15:56
SamYapleyup15:56
SamYapleits a stub upgrade file15:56
pbourkeah15:56
pbourkeok15:56
*** fthiagogv has quit IRC15:56
pbourkemakes sense15:56
limamauriciosomeone already got to create an instance of an image using ceph?15:56
*** Liuqing has joined #kolla15:57
SamYaplelimamauricio: all the time15:57
limamauricioaio?15:57
openstackgerritDerek Ditch proposed openstack/kolla: Added script that can build master binary images on centos.  https://review.openstack.org/28239915:57
inc0limamauricio, did you make changes to ceph that enables air?15:57
d_codesdake_: https://review.openstack.org/28239915:57
limamauricioyes15:57
limamauricioi did15:58
openstackgerritSam Yaple proposed openstack/kolla: Upgrade common role  https://review.openstack.org/28240015:58
inc0what are errors then?15:58
SamYaplepbourke: https://review.openstack.org/28240015:58
*** fthiagogv has joined #kolla15:58
limamauricioinc0 http://pastebin.com/TA1Xhdjb docker logs nova_pompute16:00
limamauriciocompute*16:00
*** pbourke_ has joined #kolla16:00
*** tzn has quit IRC16:00
*** pbourke has quit IRC16:01
*** akwasnie has joined #kolla16:02
inc0what kernel do you have on your base system?16:03
*** coolsvap|away has quit IRC16:03
inc0seems like something that can't talk to rbd16:03
d_codeSamYaple: I just read your selinux docs in the repo. Do you know of any specific operations that have caused issues in the past? I’m running selinux in Permissive mode and have yet to get an AVC denial16:03
limamauricio3.10.0-327.el7.x86_6416:03
limamauriciocentos16:03
SamYapled_code: there are many many operations that cause problems, basically all sudo commands16:04
SamYaplemariadb extend_start.sh chown /var/lib/mysql16:04
d_codewhich happens when?  Do I  need to create new domains / projects / networks?16:04
SamYapled_code: "A SELinux-enabled system that runs in permissive mode is not protected by SELinux."16:05
SamYaplejust fyi16:05
d_codeSamYaple: I’m well aware…and I don’t like being in this state. My intention was to help create policies as I’m quite familiar with selinux16:05
limamauricioinc0,  I need to change something in the globals file besides enable_ceph: "yes"16:05
limamauricioSamYaple, i have to run setenforce 0 and set selinux=permissive?16:06
SamYaplelimamauricio: that should be enough16:06
*** salv-orlando has quit IRC16:06
inc0SamYaple, looking at limamauricio trace it seems that libvirt doesn't know how to talk to cep16:07
inc0ceph16:07
inc0it should be in kernel tho16:07
SamYapleinc0: yea i saw. limamauricio is the first one to use centos-source for ceph it seems, so likely brekage16:07
SamYapleinc0: kernel is not involved here16:07
inc0ok16:08
limamauricioI may have forgotten some configuration16:08
limamauricioi'm changing to binary16:08
limamauricio:)16:08
inc0hmm...I don't know if anyone used ceph+centos really16:08
SamYaplelimamauricio: i would suggest testing with binary16:08
SamYaplelimamauricio: im the major proponent of ceph here, and I use ubuntu16:08
limamauricioi'll do16:08
SamYaplesdake deploys centos-binary ceph16:08
inc0both me and Sam use ceph, but we're both ubuntu16:08
d_codeSamYaple: regarding usefulness of build script, as I was stepping through the quickstart and happened to discover kolla when neither master nor liberty would build for binary or source, I walked through the quickstart and found issues that were not 100% clear on how to proceed. sdake_ was a huge help and I produced this script mainly so I could reproduce my results16:08
limamauriciook16:09
d_codesdake_ asked me to submit it16:09
d_codeI can ansiblize it, but don’t have time just yet16:09
SamYapled_code: i meant usefulness being non-idempotent16:09
SamYapled_code: that script breaks if you run it twice16:09
*** coolsvap|away has joined #kolla16:09
d_codewell…not 100%… the git clone and the docker start would fail…I could put checks around those16:10
d_codepip doesn’t care if you run the install more than once, and you can kolla-build all day long (which I did)16:10
d_codebut, could check the state of those items and quit if it’s already there16:11
d_codeor skip16:11
SamYapleif you run that scirpt to kolla build and the build breaks halfway through but you had previous good builds you can easily end up in a state of different base images and not know it16:11
d_codeoh…yeah…that’s true16:11
SamYaplethis is why we recommend cleaning the environment before rebuilding16:11
d_codeso clear out the images?16:11
d_coderun cleanup-images16:11
d_codeor containers maybe16:11
SamYapleim just saying the script needs a bit of work before merge, as is i feel like it may cause more issues that it solves16:11
SamYapleit shouldnt break on rerun and it should have a bit more error handling16:12
d_codesure thing16:12
SamYaplebut the script itself I am all for if it helps which i think it will16:12
d_codefair enough. thanks for the feedback :)16:12
SamYapleanytime16:12
*** akwasnie has quit IRC16:14
*** g3ek has quit IRC16:14
*** g3ek has joined #kolla16:15
d_codeSamYaple: I’ve never used get-pip-.py. Does that let us skip the setuptool depenency?16:16
d_codeI found the script16:16
d_codeah…nm…  it will install it if not there16:17
limamauricioI'm not finding no variable which is defined the virt_type16:18
limamauricionova default is kvm16:19
limamauriciobut i want to use qemu16:19
*** unicell has joined #kolla16:20
SerlexGATHERING FACTS ***************************************************************16:20
Serlexfatal: [control01] => failed to transfer file to /root/.ansible/tmp/ansible-tmp-1455898618.83-24426472018452/setup:16:20
openstackgerritMerged openstack/kolla: Aodh ubuntu binary container  https://review.openstack.org/28051516:21
SamYaplelimamauricio: http://docs.openstack.org/developer/kolla/deployment-philosophy.html#kolla-s-solution-to-customization16:23
*** jasonsb has quit IRC16:23
limamauricio:)16:24
limamauricioSamYaple, i already did it16:24
limamauricio:)16:24
limamauriciobut now i'm testing in binary16:25
elemoine_sdake_ SamYaple I'll soon leave the office for the week-end, feel free to tell me if there's anything I can do for Heka and the gates. I'm happy to make changes if necessary.  I have other patches coming up. Have a good WE.16:26
SamYaplethanks elemoine_ !16:27
*** achanda has joined #kolla16:27
*** vhosakot has joined #kolla16:31
vhosakotSamYaple: morning, I am running kolla-build with 2 threads and see it stuck at    "DEBUG:kolla.cmd.build:manila-base:Getting archive from http://tarballs.openstack.org/manila/manila-master.tar.gz"    for 12 hours now ?16:32
*** achanda has quit IRC16:33
SamYaplevhosakot: sounds like its your network connection/tarballs.opesntack.org failure16:33
SamYaplei would just restart teh build16:33
vhosakotrestarted many times... same issue16:34
SamYaplevhosakot: can you run `http://tarballs.openstack.org/manila/manila-master.tar.gz`16:34
SamYaple`wget http://tarballs.openstack.org/manila/manila-master.tar.gz`16:34
sbezverkSamYaple I built docker container with iscsid and taregtcli, when iscsiadm does discovery from another node, I can see shared by this container targets.. Atthis point everything is manually configured, could you pprovide some guidance how it can be packed as a patch, I have never done it before..16:36
vhosakotSamYaple: the wget worked!16:36
vhosakotbut, it is hung in kolla-build16:36
vhosakotSamYaple: does kolla-build retry hung wget's ?16:38
*** salv-orlando has joined #kolla16:40
*** iceyao has quit IRC16:42
*** mikelk has quit IRC16:49
openstackgerritPaul Bourke proposed openstack/kolla: Upgrade task for Swift  https://review.openstack.org/27685516:49
*** pbourke_ has quit IRC16:49
*** pbourke has joined #kolla16:53
*** tzn has joined #kolla16:55
vhosakotSamYaple: I see kolla-build does not timeout if wget fails.. I'm seeing this issue... shall I file a bug for this ?  ad send the fix (I will add a tirmeout value and retry).. Let me know ?16:57
openstackgerritDerek Ditch proposed openstack/kolla: Addressed whitespace and idempotence for several items.  https://review.openstack.org/28242716:58
*** tzn has quit IRC16:59
vhosakotSamYaple: let me know what you think17:01
*** pbourke has quit IRC17:05
fthiagogvGuys, someone already saw this error ""One or more undefined variables: 'dict object' has no attribute 'stdout'17:05
fthiagogv"" in Task: neutron | Reading  json from variables ??17:05
*** pbourke has joined #kolla17:06
*** pbourke_ has joined #kolla17:08
*** jtriley has quit IRC17:09
*** sbezverk has quit IRC17:09
*** sbezverk has joined #kolla17:10
*** pbourke has quit IRC17:11
*** inc0 has quit IRC17:11
*** inc0 has joined #kolla17:11
fthiagogvDo someone deploy in multinode?17:16
*** cloudnautique has joined #kolla17:16
*** chandankumar has quit IRC17:18
*** chandankumar has joined #kolla17:18
*** inc0 has quit IRC17:20
pbourke_fthiagogv: yes17:21
*** inc0 has joined #kolla17:22
*** inc0_ has joined #kolla17:24
inc0_ok, back to nova upgrades17:24
fthiagogvpbourke_ Do multinode conf have any rule to set the nodes? I set control, network, storage, compute in differents nodes. Is it okay?17:25
inc0_fyi sdake_ SamYaple I also think removing upgrade folder makes sense now17:25
*** inc0 has quit IRC17:26
*** Serlex has quit IRC17:30
sbezverkHow do you guys connect to mariadb in dockers env. to drop and re-initialize db?17:30
*** ssurana has joined #kolla17:30
*** haplo37 has joined #kolla17:30
*** Allen_Gao has quit IRC17:30
pbourke_fthiagogv: I dont fully understand17:31
*** Allen_Gao has joined #kolla17:31
pbourke_fthiagogv: you can configure the node layout in ansible/inventory/multinode if that's what you mean?17:31
fthiagogvpbourke_, yes.17:31
d_codepbourke_: how can I take those changes and put them on the previous review?  do a git revert?17:32
pbourke_d_code: code you will want to use interactive rebase17:33
pbourke_i think it should be outlined in that link I posted17:33
*** spisarski1 has joined #kolla17:34
*** spisarski has quit IRC17:34
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968817:35
*** dims has joined #kolla17:35
inc0_SamYaple, question about https://review.openstack.org/#/c/254395/16/ansible/library/kolla_docker.py@61417:35
inc0_I don't really understand what you mean, all of these functions may return different types, and to cast them out to single one will be incredibly inconvinent and possibly breaking17:36
inc0_especially with pythons type handling17:36
*** Marga_ has joined #kolla17:38
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968817:38
*** gfidente has quit IRC17:41
*** cloudnautique has quit IRC17:41
openstackgerritMerged openstack/kolla: Keep consistent with others for ironic containers  https://review.openstack.org/28055717:43
*** cloudnautique has joined #kolla17:44
*** kproskurin has quit IRC17:44
sdake_back in the office17:46
sdake_inc0_ cool17:46
sdake_vhosakot if your behind a firewll you need proxy setup17:46
sdake_elemoine_ enjoy :)17:46
sdake_d_code agree with samyaple, should not allow run twice17:47
sdake_inc0_ we used  ceph in liberty for our demo on centos-binary17:47
vhosakotsdake_: it worked after retrying 4 times... the code must timeout, print a messgae, and continue, instead of haning...17:47
inc0_ok17:47
inc0_good to know17:47
vhosakotsdake_: will submit a patch for this17:47
sdake_the wget wouldn't timeout if you have your proxy set17:47
d_codesdake_: I made the changes, but I screwed up the amendment when I commited17:48
d_codetrying to figure out how to undo that…I’ve used git quite a bit, but new to gerrit17:48
*** unicell has quit IRC17:49
sbezverksdake I need to reset cinder DB, when I try running mysql -u root -p it does not connect, what is the right way to connect to DB?17:49
openstackgerritDerek Ditch proposed openstack/kolla: Addressed whitespace and idempotence for several items.  https://review.openstack.org/28239917:50
sdake_3 heka patches not passing gate17:50
d_codethere we go17:50
*** achanda has joined #kolla17:50
sdake_sbezverk  are you using password to login?17:50
sbezverksdake_ yes17:51
sdake_sbezverk by not connect  to db, you mean you get a econrefused or you get an invalid password?17:51
vhosakotsdake_: ah, did not know wget wouldn't time if proxy is set17:51
sbezverkERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)17:51
sdake_sbezverk  you need to specify the ip address of mysql17:52
vhosakotsdake_: I still see the same error... no leaked containers, no funny names17:52
vhosakotmsg: The requested image does not exist: 192.168.122.41:4000/kollaglue/ubuntu-source-rsyslog:2.0.017:52
sdake_vhosakot docker images | grep rsyslog17:52
sdake_and paste it not in irc :)17:52
vhosakotkollaglue/ubuntu-source-rsyslog                     2.0.0               6b24cc9a7331        3 hours ago         236.7 MB17:53
vhosakotoops, sorry.. its there17:53
vhosakotwill send all the output in pastebin like yesterday :)17:53
sdake_note a recent patch to the quickstart brought the registry documentation up to date17:53
sdake_vhosakot build.py --registery 192.168.1.122.41:4000 --push17:53
sdake_vhosakot build.py --registery 192.168.1.122.41:4000 --push rsyslog17:53
SamYapleinc0_: im specifically refering to the variable 'result'17:54
inc0_yeah, it just passes what it gets17:55
inc0_it's common practice in python17:55
SamYapleinc0_: im saying dont do that17:55
vhosakotsdake_: cool, I have more updates for quickstart.. will push later17:55
SamYapleit needs to be a dict if you are returning it to ansible17:55
inc0_casting it all to same type might be breaking17:55
*** tzn has joined #kolla17:56
SamYaplelook at the functions, they all return none or True17:56
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968817:56
inc0_return_json makes json out of it17:56
inc0_so it has to be jsonable, so bool, string, dict, none...all works17:56
SamYapleinc0_: i dont like the idea the variable could be None, True, or a dict with data17:56
SamYapleits being returned to ansible17:56
inc0_not as-is17:56
inc0_it goes through jsonification before that17:56
SamYapleso sanitize it to _something_. Wether a dict always, or a bool17:57
SamYaplehonestly the way we use it i think a bool works17:57
SamYaplehey guys I acidentally +W this https://review.openstack.org/#/c/280749/17:57
inc0_but that will either limit it remendously or be prone to problems17:57
SamYaplesoooo im going to submit a patch for this, but its breaking the gate for some hosts sorry17:57
SamYaplei didnt see it til jsut now17:57
inc0_bool works now, but if you try to reuse it in a different way, it's wasted work17:58
inc0_and little benefit to it17:58
inc0_also you -1 on returning bool from method because other methods return bool or none;)17:59
inc0_I think way to solve this issue is to make methods themselves return consistent type17:59
inc0_not casting it afterwards17:59
inc0_and that's beyond scope of this patch18:00
inc0_I will add todo comment tho, ok?18:00
sbezverksdake_ what about running this after cinder db is re-created? "cinder-manage db sync"18:00
openstackgerritSam Yaple proposed openstack/kolla: Quick gate fix  https://review.openstack.org/28244718:00
SamYapleinc0_: sdake_ rhallisey i need a quick review on this https://review.openstack.org/28244718:01
SamYaplesorry for the trouble, i was trying to -W and +W instead....18:01
sbezverksdake_ here is what I get when I try to run db sync http://paste.openstack.org/show/487610/18:01
SamYapleinc0_: no they all return bool or None18:01
SamYapleinc0_: this was intentional18:01
SamYaplethis matches docker-py18:01
SamYaple_however_ all of that is internal ot the kolla_docker module18:02
inc0_so I'd say let's keep it bool or none18:02
SamYapleif you are returning variables to the host (which is new to this type) make it a bool on return18:02
inc0_for ansible18:02
*** tzn has quit IRC18:02
SamYapleI say one type for ansible18:02
SamYapleansible and jinja2 is not as flexible with different type callings18:02
inc0_ok, but that will limit us afterwards to return dicts18:02
SamYapleso _that_ can be the todo18:03
inc0_ok, I can do that18:03
SamYaplethat works for me18:03
SamYapleso it retursn bool now with a TODO to return dict?18:03
inc0_yeah18:04
sbezverk SamYaple I built docker container with iscsid and taregtcli, when iscsiadm does discovery from another node, I can see shared by this container targets.. Atthis point everything is manually configured, could you pprovide some guidance how it can be packed as a patch, I have never done it before..18:04
fthiagogvDo someone know about this error? http://pastebin.com/C5wC0q7R18:04
SamYapleworks for me. I think that means the only thing that needs to change is the results var section18:04
SamYaplesbezverk: youve never submitted a patch to openstack?18:05
sbezverkSamYaple nope, I am in integrator not developer ;-)18:05
SamYaplesbezverk: ok, its a bit of work to setup. youll need to do some reading https://wiki.openstack.org/wiki/How_To_Contribute18:06
SamYaplespecifically the "if you're a developer" section18:06
SamYapleit has instructions on how to setup to submit a patch18:06
sbezverkSamYaple got it, thank you18:06
sdake_fthiagogv haven't seen that, file a bug with reproducer please18:09
openstackgerritMauricio Lima proposed openstack/kolla: Update cleanup-containers to remove ceph containers  https://review.openstack.org/28245118:11
*** Liuqing has quit IRC18:12
vhosakot"./build.py --registry 192.168.1.122.41:4000 rsyslog"  passed, but,  "./build.py --registry 192.168.1.122.41:4000 --push rsyslog"  failed with error  "ERROR:__main__:unable to ping registry endpoint https://192.168.1.122.41:4000/v0/"18:12
sdake_limamauricio you can't just remove the eph containers, you also have to modify /etc/fstab18:12
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439518:13
sdake_vhosakot docker ps | grep registry18:13
vhosakotis up18:13
vhosakot9704003bc20c        registry:2          "/bin/registry /etc/d"   15 hours ago        Up 22 minutes       0.0.0.0:4000->5000/tcp   registry18:13
limamauriciohmm...18:13
sdake_vhosakot the reason rsyslog can't be found is you haven't pushed it to the registry18:13
vhosakotright, I can build rsyslog but cannot push..18:13
fthiagogvsdake_, can you look if this is correct? http://pastebin.com/7p4dZYMW If yes, I will file a bug.18:13
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439518:14
sdake_fthiagogv I don't know what ansible_ssh_pass does18:14
sdake_is that default or something you added in?18:14
sdake_vhosakot which os are you on?18:15
*** jtriley has joined #kolla18:15
vhosakotUbuntu 14.0418:15
sdake_did you set the --insecure-registry flag in your docker daemon startup?18:15
sdake_ps -ef | grep docker18:15
fthiagogvsdake_, set password to authenticate when ansible access via ssh.18:15
vhosakotyes18:15
vhosakot  /usr/bin/docker daemon --insecure-registry 192.168.122.41:400018:16
sdake_what machine is .41, your laptop or something?18:16
vhosakotit is the IP of eth0 on Ubuntu 14.04, the same IP I use to SSH into the Ubuntu host18:16
sdake_vhosakot well that should work, but obiously doesnt18:17
sdake_i am not an ubuntu wizard unfortunately18:17
sdake_it is possible you have ipteables rules blocking port 40018:17
sdake_try telnet 400018:17
sdake_see if that responds with a connection18:17
vhosakot"curl 192.168.122.41:4000" passes BTW18:17
limamauriciosdake, remove the ceph container manually even after run the script18:17
limamauricio:/18:17
sdake_limamauricio what I'm saing is it would make sense to clean up /etc/fstab as well, possibly in cleanup-host18:18
sdake_grep -v ceph /etc/fstab > /etc/fstab may do it ;)18:18
sdake_but that could have unintended consequences18:18
limamauriciooh18:19
limamauricio:)18:19
sdake_you may need to save it to a temporary secure file18:19
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439518:19
sdake_and then copy that over18:19
sdake_/query inc0_18:19
*** unicell has joined #kolla18:19
*** aginwala has joined #kolla18:20
*** unicell has quit IRC18:20
*** unicell has joined #kolla18:20
vhosakotsdake_: tcp6       0      0 :::4000                 :::*                    LISTEN      -18:20
vhosakotfrom netstat18:20
limamauriciosdake, this is a change a little criticism, I will study a safe way to do this18:21
*** mbound has quit IRC18:21
limamauriciosdake, i'm deploying centos/binary now18:22
*** dims_ has joined #kolla18:22
limamauriciodid you already deployed it ?18:23
*** achanda has quit IRC18:25
*** dims has quit IRC18:25
*** ccesario has quit IRC18:25
*** larsks has quit IRC18:25
*** ByPasS has quit IRC18:25
*** clayton has quit IRC18:25
*** mkoderer__ has quit IRC18:25
*** aginwala has quit IRC18:25
*** ByPasS has joined #kolla18:25
*** mkoderer__ has joined #kolla18:26
*** larsks has joined #kolla18:26
*** clayton has joined #kolla18:26
*** bradjones has quit IRC18:27
*** SamYaple has quit IRC18:27
*** hparekh has quit IRC18:27
*** nihilifer has quit IRC18:27
*** cfarquhar has quit IRC18:27
*** SamYaple has joined #kolla18:27
*** cfarquhar has joined #kolla18:27
*** cfarquhar has quit IRC18:27
*** cfarquhar has joined #kolla18:27
*** nihilifer has joined #kolla18:27
*** hparekh has joined #kolla18:27
*** ccesario has joined #kolla18:28
*** bradjones has joined #kolla18:28
*** bradjones has quit IRC18:28
*** bradjones has joined #kolla18:28
*** clayton_ has joined #kolla18:28
vhosakotI see docker-proxy process when I run the registry on 400018:28
*** clayton has quit IRC18:28
*** clayton_ is now known as clayton18:29
vhosakotIs docker-proxy listening on port 4000 expected ?18:30
SamYaplehey inc0_ i posted the wrong pep8 quote in the docker-py patch18:32
SamYaplethe only issue I really have with kolla_docker in your nova patch is the "if container_info is None" part18:33
SamYapleif that can be changed to "if not container_info:" we will be better off18:33
vhosakotSamYaple: Is docker-proxy listening on port 4000 expected ?18:33
SamYaplevhosakot: sounds like you told your registry to start on port 400018:34
vhosakotyeah.. but 4000 is used by docker-proxy in netstat18:34
sdake_vhosakot that is what is supposed to be doing18:34
sdake_vhosakot try turning off iptables18:35
vhosakothaaa18:35
SamYapledid you run it with -p 4000:5000? if so thats what its suposed to be doing18:35
SamYapledocker-proxy is proxying 4000 to 500018:35
vhosakotyes18:35
vhosakotran this    "docker run -d -p 4000:5000 --restart=always --name registry registry:2"18:36
sdake_vhosakot that is what you are supposed to run18:36
sdake_not sure why your push is failing18:36
vhosakotflushed IPt as well "sudo iptables --flush"18:36
sdake_unless the sematics of --registry has changed18:36
vhosakotso, docker-proxy process is not a problem18:37
vhosakotis it ?18:37
*** haplo37 has quit IRC18:37
vhosakotdocker-proxy is working fine.. proxying 4000 to 500018:38
inc0_SamYaple, these are not equivalent18:38
SamYapleinc0_: what is not?18:38
SamYapleoh i know18:38
SamYaplethats teh point18:38
SamYaplethey are not equivelant18:38
SamYaplei know what im asking18:39
vhosakotI can build rsyslog, but cannot push18:39
SamYaplethe api breakage was docker returning None or []18:39
SamYaplethey change things in docker-py18:39
SamYaplehence why i used 'if not <var>:' everywhere inc0_18:39
limamauriciokolla supports linuxbridge?18:40
SamYaplelimamauricio: indeed18:40
SamYaplethough i dont know how tested it is18:40
SamYaplei know ive deployed with it when i added it, but not alot since18:40
limamauriciohmm18:41
inc0_SamYaple, def compare_image(self, container_info=self._get_container_info()): wont work18:41
inc0_self is not defined18:41
cloudnautiqueHello, is there a workaround for the Kolla-toolbox container? Its failing to build on master because of my.cnf conflicts18:41
cloudnautiquebetween Percona and Maria18:41
SamYapleinc0_: only thing i -1 for was the 'if not <var>:' thing, should have made it more clear18:42
SamYaplethough i do think you shouldnt be using an underscore for _get_container_info, i wont push it18:42
inc0_also, about tasks18:42
SamYaplei think its wrong since <class>.get_container_info is useful18:42
inc0_I  saw things changed during rebase18:42
inc0_I'll remove underscore, np18:43
*** achanda has joined #kolla18:43
inc0_SamYaple, do we need to run bootstrap nova compute during upgrade?18:44
SamYapleinc0_: maybe18:44
SamYapletechnically the "upgrade" could happen on a fresh host18:44
SamYaplethink about it18:44
SamYapleupgrade should also do the same job as deploy in the end18:45
inc0_no, I don't agree18:45
SamYaplejust additional tasks18:45
inc0_it does less18:45
inc0_and that might be key18:45
inc0_also things will break on fresh host anyway18:45
SamYapleok again, if i run upgrade, then i run deploy it should never change anything18:45
SamYapleand it will not18:45
SamYapleafter upgrade, running deploy should change nothing18:45
inc0_if you add stuff to conductors inventory18:45
inc0_it will try to stop conductors and there is no such container18:46
SamYaplethats fine18:46
SamYapleit wont break18:46
inc0_at least for now let's assume upgrade is run on same conf as deploy18:46
inc0_in this case might not break, but it might elsewhere18:46
inc0_this is not the use-case I want to tackle right now18:47
SamYapleok im goign to say this again, after i run upgrade.yml i should be able to run deploy.yml with 0 changed18:47
inc0_technically upgrade might be as well "rolling deploy"18:47
SamYapleso if thats not the case, upgrades not done18:47
SamYaplerolling disruptive deploy sure18:47
inc0_if you changed your config in the meantime18:47
inc0_that means your deploy is not done18:47
SamYaplealways arguing about everything huh18:48
inc0_and prerequisite to upgrade is finished deploy18:48
SamYapleyes if you make a chnage AFTER running upgrades, deploy will change18:48
inc0_no, I don't want to introduce scope creep18:48
SamYaplebut i said run upgrades.yml then deploy.yml no changes should occur18:48
SamYapleits not18:48
inc0_2 weeks before mitaka-318:48
SamYaplethis wass always scope18:48
SamYapleupgrades not done if i cant run deploy18:48
inc0_if you keep your inventory way it was18:48
SamYaplethen your upgrade play will fail18:48
inc0_no, why?18:48
SamYaplejust throw the bootstrap stuff in bootstrap service and were done18:49
SamYapleno need for this18:49
inc0_I'm not against it, I'm asking18:49
inc0_I want to understand why it's needed18:49
SamYaplebecause the compute node will fail if it doesnt have the volume bootstraped18:49
SamYaplethere is no harm in bootstraping it if it doesnt exist18:49
*** Marga_ has quit IRC18:50
inc0_ok, but bootstrapping volume is idempotent?18:50
SamYaplewhy fight the envitable failure when the "fix" is just move all the bootstrap_service stuff to... bootstrap_service18:50
SamYapleyes18:50
inc0_if wont break existing one?18:50
SamYapleno18:50
SamYaplewe run it every deploy18:50
inc0_ok18:50
inc0_fyi I didnt fight it18:50
*** sdake_ is now known as sdake18:50
inc0_I just say that "upgrade with different inventory than deploy is not supported"18:51
inc0_it might work, but I won't hold upgrade patches to fix it if it ever become a problem18:51
SamYapleim fine with that, but its likely to happen so if there is a simple change like this that can be done to fix it... well we might as well include it18:51
SamYaplei mean if we catch it now it saves a bug later18:51
SamYaplethis isn't a refactor past what you were already doing18:51
inc0_sure, ofc18:52
SamYaplere the :self._container thing, yea you are right self. is undefined18:52
SamYaplemissed that18:52
inc0_but if it would be more than that then that's my standpoint18:52
SamYaplei mean it just depends on what is more18:53
SamYaplea simple refactor, fine. code changes in extend_start.... maybe a tech-debt bug18:53
inc0_all depends on case I guess18:53
SamYaplebut if we can play with the tasks order until it works for that and prevents bugs I say we should18:53
inc0_https://review.openstack.org/#/c/254395/20 bot failed -> there you go18:54
inc0_thing tho, on multinode will database_created be defined?18:55
inc0_because we include it with "when"18:55
inc0_I'm not sure if ansible will have this fact set up on non-db nodes18:55
SamYapleinc0_: you copied in the wrong task18:56
*** fthiagogv has quit IRC18:56
inc0_aaa yeah, well I need do nova_api db as well18:56
SamYapleinc0_: ok three comments up. all needed18:57
SamYapleno you dont need to create teh db again18:57
SamYapleyou need to db_sync18:57
SamYaplethe db and users are fine18:57
inc0_don't forget we're doing upgrade from liberty18:58
inc0_there was no nova-api db then18:58
inc0_all hail nova18:58
inc0_so I, in fact, think we need to include it in playus18:58
SamYaplehmmm18:59
SamYaplei think that just means you need to call bootstrap.yml instead of bootstrap_service.yml no?18:59
SamYaplefrom upgrade.yml18:59
inc0_hmm...if it won't mess up with original nova database19:00
inc0_it shouldnt'''19:00
SamYapledeploy never does :)19:00
inc0_so in fact we might not split to bootstrap_servie at all19:00
inc0_yeah I'll just do that19:00
SamYapleinc0_: not split it out at all?19:03
SamYaplethen do we really need to for the other services?19:04
SamYapleno no inc0_ you still need to19:04
inc0_why?19:04
SamYaplewe did that because the db_sync only runs after database creation19:04
SamYapleso what you need to do is run boostrap.yml and then bootstrap_service.yml from upgrade.yml19:05
SamYapleotherwise the service will never trigger a db_sync19:05
inc0_yeah, database_created19:05
inc0_that was the reason for splout19:05
inc0_split19:05
*** Serlex has joined #kolla19:06
SamYapleso we still need splitout, but for nova (since it has a new db) we need to call boostrap.yml _and_ boostrap_service.yml19:06
sdakewhere are the docker proxy operation commands that someone put in an etherpad?19:06
sdakeI am having trouble locating them.19:06
openstackgerritMerged openstack/kolla: Quick gate fix  https://review.openstack.org/28244719:07
SerlexAnyone here having problems starting rsyslog container?19:08
inc0_but then bootstrap_service will be called twice19:08
inc0_we can run api-db creation in upgrade play19:08
*** mbound has joined #kolla19:08
inc0_and tag it as todo: remove from next release19:08
inc0_one of special tasks that will be valid only for L->M19:08
SamYapleinc0_: it will be called twice, but run once19:09
inc0_how so?19:10
SamYaplebecause it wont run the first time19:10
SamYapleit triggers on nova database creation, not nova_api database creation19:10
sbezverkSamYaple would it be ok to add iscsid binaries to cinder-volume container? The reason I am asking is because it needs access to volume group in order to create LVM volume if iscsid runs in a separate container it will also need access to volume groups to map to iscsi target.19:10
SamYaplenova is the only case where we have two19:10
SamYaplesbezverk: no thats the reason its not a simple fix19:11
inc0_yeah all hail nova19:11
SamYaplesbezverk: doing so means we have multiple processes needing to be tracked in cinder-volume turing it into a "fat container"19:11
inc0_I need to think how to do it well19:11
SamYapleinc0_: and you can't move nova api database creation out of boostrap.yml entirely, since new deploys19:11
inc0_right now I'm rather thinking about adding this task to upgrade.yml19:12
SamYapleif you just call bootstap.yml then boostrap_service.yml from upgrades.yml it will work fine19:12
SamYapledon't duplicate teh task please19:12
inc0_and including just bootstap_service19:12
SamYapleim just going to -1 if you dup the task19:12
inc0_it will not be idempotent19:12
SamYapleit will19:12
inc0_no19:12
SamYapleyes19:13
sbezverkSamYaple but in the case of separated approach you need to develop Docker specific cinder API so the cinder volume process instead of just creating a lvm volume need to send a create command to iscsi container to create it..19:13
inc0_if I include bootstrap19:13
inc0_itself19:13
SamYapleit will19:13
inc0_let me finish19:13
Serlexi guess not19:13
inc0_if I include bootstrap twice19:13
SamYaplesbezverk: yes it is not trivial19:13
inc0_first one with database_created conditional19:13
inc0_or database_created and api_database_created rather19:13
SamYaplesbezverk: you can include the _tools_ in the cinder-volume container. you can;t launch the process from there19:13
inc0_it will not tic because I create just one of them19:14
*** Marga_ has joined #kolla19:14
inc0_and in upgrades if I add bootrap_service unconditionally later on, it will try to syncdb each time it is run19:14
inc0_db created or not19:14
*** achanda has quit IRC19:14
SamYapleok inc0_ the first run of bootstrap.yml will create nova_api_db. but it wont trigger bootstrap_service.yml19:14
SamYaplehttps://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/bootstrap.yml#L9019:14
inc0_and that might lead to uncontrolled migrations19:14
SamYaplethats just database_created19:15
SamYaplethe second run of bootstrap_service.yml will run the db_sync19:15
*** Marga_ has quit IRC19:15
inc0_and will run it always, while it should be run once19:15
inc0_that's why we have database_created in the first placve19:15
SamYaplewell no you should aalways run db_sync when you do an upgrade19:15
SamYaplebut i dont know what you are arguing for19:16
SamYapleor against for that matter19:16
inc0_I'm trying to think if this will break stuff later on19:16
*** Serlex has quit IRC19:16
sdakegate is bust19:16
inc0_don't blame me for being careful in that19:16
sdakethese 3 heka reviews are blocked on gate not working19:16
SamYaplesdake: yea its not all from that patch earlier, some of it is19:17
SamYaplesdake: the ubuntu gates are from the early merge but the fix is up19:17
SamYaplethe centos gates are bust19:17
SamYaplepackaging issues19:17
sdakeheka is failing on all the gates19:17
sdakehttps://review.openstack.org/#/c/275840/1419:17
SamYaplei know, i just explained why19:18
SamYapleyou need to fix centos19:18
SamYaplethe ubuntu gates are reporting failues, but there is a fix up gfor that19:18
SamYaple(it actually gets to deploy vm and that fails)19:18
*** Marga__ has joined #kolla19:18
SamYapleactually sdake this just merged https://review.openstack.org/#/c/282447/19:19
SamYapleso ubuntu gate should be good on out. centos has packaging issues19:19
sdakeSamYaple this is what your talking about? http://logs.openstack.org/40/275840/14/check/gate-kolla-dsvm-build-centos-binary/78f470f/console.html#_2016-02-19_18_06_08_63919:20
SamYaplesdake: yea19:22
SamYaplethast unrelated to any patch, just a enw failure19:22
sdakeyup19:22
openstackgerritSam Yaple proposed openstack/kolla: Add a Dockerfile for Heka  https://review.openstack.org/27584019:23
sdakeubuntugate failing on elasticsearch19:24
sdakehttp://logs.openstack.org/40/275840/14/check/gate-kolla-dsvm-build-ubuntu-source/43a31e1/console.html#_2016-02-19_18_04_44_67919:24
*** diogogmt has quit IRC19:24
sdakepretty sure thats a new failure too that is unfixed19:24
sdakeSamYaple can you fix that elasticsearch problem plz19:25
*** vhosakot has quit IRC19:25
sdakei'll look into the centos problem now19:25
openstackgerritDave McCowan proposed openstack/kolla: Implement Option for Two VIPs to separate API traffic  https://review.openstack.org/28251319:25
*** diogogmt has joined #kolla19:25
dave-mccowansdake ^^19:26
sdakedave-mccowan yup atm we are blocked onthe gate being busted19:26
* sdake groans19:26
SamYaplesdake: i see no problem with it. i think elasticsearch went down or messed up19:26
sdakei have rechecked it 3 or 4 times19:26
sdakethe package has probably been renamed19:27
*** vhosakot has joined #kolla19:28
sdakeok folks, we need to make a decision, to merge heka today, or wait until the gate is ready to go19:28
sdakeheka has been tested by atleast 2 CRs19:29
SamYapledave-mccowan: reviewed. looks good! a few comments19:29
sdakethe reason we wouldn't be able to merge heka today is because it requires a rebase on master after these centos percona and ubuntu elastic search problems are fixed19:29
SamYaplesdake: i vote merge it. well sort the bugs as they come19:29
SamYaplemitaka-3 is around the corner and we need heka for logging19:30
sdakeya thats where i stand on it as well19:30
sdakeinc0 jpeeler rhallisey mandre19:30
SamYaplepbourke_19:30
sdakeinc0_19:30
sdakepaul is probably asleep19:30
SamYaplepaul is probably drinking....19:30
rhalliseyI reviewed a few19:30
rhalliseyI thought they were good19:30
sdakerhallisey scroll up a little bit dude ;)19:30
SamYaplerhallisey: the question is, merge them now or wait for gate (which has several issue ATM)19:31
rhalliseyoh I see19:31
rhalliseyI'm find with merging it.  I think we can sort it out19:31
* sdake paying 1 us dollar for a working gate ;)19:31
inc0_SamYaple, will database_created be present on deploy on compute node?19:32
sdakeinc0_ any feedback on above please19:32
SamYapleinc0_: no, but its not checked by those tasks19:32
inc0_it's checked on include19:32
SamYapleoh i see your point19:32
SamYapleyea i jsut go that19:32
SamYaplegot*19:32
*** jmccarthy has quit IRC19:32
SamYapleoh wait wait19:32
SamYapleit will be yes inc0_19:32
SamYapleinc0_: i worked that out way before liberty19:33
SamYaplehttps://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/bootstrap.yml#L1419:33
SamYaplethe next line registers it on _all_ hosts19:33
sdakeok folks i'm going to pull tlhe trigger on heka19:33
dave-mccowanthanks SamYaple.  do you have some context behind why to add a second vrrp_instance, instead of combining them under one?19:33
SamYaplesdake: do it19:33
sdakeplease please get the gate working today :)19:34
dave-mccowannot doubting, btw, i just want to learn.19:34
jpeeleri say merge it...19:34
SamYapledave-mccowan: seperate tracking also can possibly provide a bit of unintentional loadbalancing (including intentional load balancing down the road)19:34
SamYapledave-mccowan: external and internal are on different nodes, and that can be force by policy19:34
SamYaplebut mostly because that jinja2 you have is REALLY ugly19:35
SamYaple:P19:35
*** dwalsh_ has quit IRC19:35
*** dwalsh has quit IRC19:35
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439519:35
sdakei can't do anything for it atm, itsi n a recheck and gerrit is blocked from voting19:36
SamYaplesdake: thats not true19:37
SamYapleI can change my vote19:37
*** dwalsh has joined #kolla19:37
SamYaplemaybe your auth is screewd up19:37
sdakei cant?19:37
sdakewierd19:37
sdakei can on other reviews19:37
sdakeletme logout and login19:37
dave-mccowanSamYaple could the two instances share the same check_alive script without changes?19:37
SamYapleyou are on an old patchset19:37
SamYapleremove the patchset number in the url19:37
SamYapledave-mccowan: yea19:38
sdakeok that problem is solved19:40
sdakeheka INC19:40
*** diogogmt has quit IRC19:40
*** dwalsh has quit IRC19:42
*** dwalsh has joined #kolla19:44
SamYapleok inc0_ i have reviewed it. it looks good, one comment on includes19:46
*** diogogmt has joined #kolla19:46
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439519:48
inc0_done19:48
sdakeSamYaple thoughts on this comment welcome in the review please https://review.openstack.org/#/c/282513/1/tools/openrc-example19:49
sdakeinc0_ two very minor nitpicks in your patch19:55
sdakeinc0_ but i'd like to keep the code sanitary could you fix and we will merge asap19:55
SamYaplesdake: i replied19:56
SamYapleyou should find it funny19:56
sdakeSamYaple I am tlaking about this review https://review.openstack.org/#/c/254395/2319:56
sdakenot sure which one your talking abou t;)19:56
SamYaplesdake: https://review.openstack.org/#/c/282513/1/tools/openrc-example19:57
sdakeoh that one19:57
SamYaple:)19:58
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439519:58
inc0_there you go sdake19:58
sdakeinc0 thanks19:58
inc0_god my head hurts19:59
inc0_let's get this one done today19:59
*** tzn has joined #kolla19:59
SamYapleinc0_: its already +2+W19:59
SamYapleinc0_: just go to sleep19:59
inc0_sleep? I'm going to try one of whiskeys we bought from dark corner20:00
SamYaplemmmm20:00
sdakeoh right whisky20:01
sdakei need to get my address to sam ;)20:01
sdakeinc0_ i think the amount of punishment you have taken today feels like my whole week :)20:01
sdakenow heat and neutron in the queue and we are done with openstack upgrades from a "in the queue" perspective ;-)20:02
*** limamauricio has quit IRC20:03
inc0_yeah I'll review it all later20:03
*** tzn has quit IRC20:03
inc0_next week - infra upgrades20:04
*** dwalsh has quit IRC20:04
*** chandankumar has quit IRC20:05
sdakei was thinking inc0_20:05
inc0_sdake, in our presentation I think we should start from kolla 1.1.020:06
sdakeupgrade in copy_once case20:06
sdakedo config's need to be rebuilt?20:06
sdakeinc0_ sounds great, just need someone to do the work ;-)20:06
inc0_sdake, configs may change between releases20:06
inc0_(nova is prime example now)20:06
sdakeinc0_ yes that is what i am getting at20:06
inc0_and since we're restarting all the containers, it will copy new one20:06
sdakeoh right20:07
sdakeok nm then20:07
*** jmccarthy1 has quit IRC20:11
*** jmccarthy has joined #kolla20:11
sdaket-2 weeks to mitaka-3!!20:13
dave-mccowanSamYaple sdake  I have written a bash script that creates a haproxy-ca.crt and haproxy.pem suitable for TLS on the external VIP.   I assume I can stick that in the tools/ directory.  what is a good destination directory for the generated files (.key, .crt, .pem, .cnf)?20:20
openstackgerritSam Yaple proposed openstack/kolla: Upgrade cinder playbook  https://review.openstack.org/27804920:24
openstackgerritMerged openstack/kolla: Use "optional" for ceph confs  https://review.openstack.org/28080820:25
openstackgerritMerged openstack/kolla: Add a Dockerfile for Heka  https://review.openstack.org/27584020:25
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder infrastructure  https://review.openstack.org/27666720:28
SamYapleoh jeez20:29
SamYaplesdake: all the heka patches are out of date20:29
SamYapleim going to be rebasing them20:29
*** cloudnautique has quit IRC20:30
*** dims_ has quit IRC20:31
openstackgerritSam Yaple proposed openstack/kolla: Add Heka to common role  https://review.openstack.org/27584120:32
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect HAProxy and Keepalived logs  https://review.openstack.org/27584220:32
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder for RabbitMQ  https://review.openstack.org/27666820:32
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect RabbitMQ logs  https://review.openstack.org/27584420:32
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder for OpenStack  https://review.openstack.org/27584520:32
rhalliseyrebase!20:32
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Nova logs  https://review.openstack.org/27584620:32
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder for MariaDB  https://review.openstack.org/27584720:32
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect MariaDB logs  https://review.openstack.org/27584820:32
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Glance logs  https://review.openstack.org/27676020:33
openstackgerritSam Yaple proposed openstack/kolla: Make Ansible write its logs into "kolla_logs"  https://review.openstack.org/27919120:33
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder for Keystone/Apache  https://review.openstack.org/27919220:33
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Keystone logs  https://review.openstack.org/27919320:33
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Neutron logs  https://review.openstack.org/27948920:33
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Swift logs  https://review.openstack.org/27949020:33
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Cinder logs  https://review.openstack.org/28125920:33
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Heat logs  https://review.openstack.org/28132720:34
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Murano logs  https://review.openstack.org/28132820:34
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Magnum logs  https://review.openstack.org/28132920:34
SamYaplerhallisey: they werent even in sync with each other! so i couldnt just cherrypick at the end :)20:34
rhallisey:20:35
rhallisey:D20:35
*** achanda has joined #kolla20:35
SamYapleits ok rhallisey i asked elemoine not to rebase so much while we were reviewing. its all done now. no harm20:36
*** haplo37 has joined #kolla20:37
*** tzn has joined #kolla20:40
*** rhallisey has quit IRC20:40
*** sdake has quit IRC20:44
dave-mccowanSamYaple when you're hacking kolla and have a change to just one container, what's the fastest way to re-deploy?  can i kill and start just one container?  is that advisable?20:45
SamYapledave-mccowan: yea thats fine20:46
dave-mccowanwhat's the command to kill one container?  /me is a docker newb20:46
*** tzn has quit IRC20:47
SamYapledocker rm -f <container_name>20:47
*** ayoung has quit IRC20:52
*** ssurana has quit IRC20:53
*** tzn has joined #kolla20:55
*** dencaval has quit IRC20:56
*** jasonsb has joined #kolla20:58
*** ssurana has joined #kolla20:59
*** jtriley_ has joined #kolla21:00
openstackgerritMerged openstack/kolla: Upgrade common role  https://review.openstack.org/28240021:00
*** pbourke_ has quit IRC21:00
*** alyson_ has quit IRC21:02
*** jtriley has quit IRC21:02
*** tzn has quit IRC21:05
*** jtriley_ has quit IRC21:11
openstackgerritMerged openstack/kolla: Playbook for nova upgrade  https://review.openstack.org/25439521:15
openstackgerritMerged openstack/kolla: Add Heka log decoder infrastructure  https://review.openstack.org/27666721:15
*** jtriley has joined #kolla21:18
openstackgerritMerged openstack/kolla: Add Heka to common role  https://review.openstack.org/27584121:18
openstackgerritMerged openstack/kolla: Make Heka collect HAProxy and Keepalived logs  https://review.openstack.org/27584221:18
*** achanda has quit IRC21:18
openstackgerritMerged openstack/kolla: Add Heka log decoder for RabbitMQ  https://review.openstack.org/27666821:18
openstackgerritMerged openstack/kolla: Make Heka collect RabbitMQ logs  https://review.openstack.org/27584421:19
*** achanda has joined #kolla21:21
SamYapleits merging21:22
SamYapleITS MERGING21:22
*** jasonsb has quit IRC21:24
openstackgerritMerged openstack/kolla: Upgrade cinder playbook  https://review.openstack.org/27804921:27
*** cloudnautique has joined #kolla21:30
*** shardy has quit IRC21:31
openstackgerritMerged openstack/kolla: Add Heka log decoder for OpenStack  https://review.openstack.org/27584521:40
elemoine_Thanks for the rebases SamYaple!21:41
SamYapleelemoine_: its late for you, ill handle the merge conflict as well unless you say otherwise21:43
*** d_code has quit IRC21:44
*** dave-mccowan has quit IRC21:44
*** jtriley has quit IRC21:45
*** cloudnautique has quit IRC21:50
*** jtriley has joined #kolla21:53
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Murano logs  https://review.openstack.org/28132821:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Magnum logs  https://review.openstack.org/28132921:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Nova logs  https://review.openstack.org/27584621:56
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder for MariaDB  https://review.openstack.org/27584721:56
openstackgerritSam Yaple proposed openstack/kolla: Add Heka log decoder for Keystone/Apache  https://review.openstack.org/27919221:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Cinder logs  https://review.openstack.org/28125921:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Heat logs  https://review.openstack.org/28132721:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Keystone logs  https://review.openstack.org/27919321:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Swift logs  https://review.openstack.org/27949021:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Neutron logs  https://review.openstack.org/27948921:56
openstackgerritSam Yaple proposed openstack/kolla: Make Ansible write its logs into "kolla_logs"  https://review.openstack.org/27919121:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect MariaDB logs  https://review.openstack.org/27584821:56
openstackgerritSam Yaple proposed openstack/kolla: Make Heka collect Glance logs  https://review.openstack.org/27676021:56
*** dave-mccowan has joined #kolla21:57
*** cloudnautique has joined #kolla21:59
*** salv-orl_ has joined #kolla22:03
*** salv-orlando has quit IRC22:06
*** ByPasS has quit IRC22:07
*** ByPasS has joined #kolla22:13
*** jtriley has quit IRC22:20
elemoine_SamYaple do as you think is best...22:23
SamYapleelemoine_: i rebased them22:29
*** daneyon has quit IRC22:30
elemoine_Did the commits pass the gate this time?22:30
*** sdake has joined #kolla22:34
SamYapleelemoine_: some of them22:35
sdakeyo22:35
SamYapleabout halfway merged22:35
*** dims has joined #kolla22:36
*** JoseMello has quit IRC22:38
openstackgerritMerged openstack/kolla: Make Heka collect Nova logs  https://review.openstack.org/27584622:40
*** achanda has quit IRC22:44
*** tzn has joined #kolla22:44
*** achanda has joined #kolla22:45
*** tzn has quit IRC22:48
*** achanda has quit IRC22:50
elemoine_Wondering why merging a few patches takes so much time. I guess I need to better understand OpenStack's gating/ci system.22:50
sdakeelemoine_ it goe sthrough a gate job22:50
sdakein order22:50
sdakeall openstack patches that enter the repo are serilaized22:50
sdakenot per project22:50
sdakebut entirely serialized22:50
elemoine_I see. I'm sure there's a web page explaining the full process22:51
sdakehttp://zuul.openstack.org/22:51
sdakepart of the issue is I think they are still going through gate checks because of sam's rebase22:52
*** tzn has joined #kolla22:52
SamYaplesdake: i think they are serialized per project...22:53
sdakeopenstack infra will run check jobs in parallel22:53
SamYapleit actually runs check and gate jobs in parallel22:54
sdakethe top of zuul says right what the integrated queue does :)22:54
sdakewell whatever it does, there is a visualization of it - enjoy :)22:54
sdakei'm off for a early friday - been rough week home alone with the kids - need some hotdog refillz22:54
*** Allen_Gao has quit IRC22:55
*** Allen_Gao has joined #kolla22:55
*** blahRus has quit IRC22:55
sdakeActually, the issue I am seeing is the kolla_docker ansible library module is trying to index a dict like a list, which is causing the KeyError exception.22:56
*** vhosakot has quit IRC22:58
sdakeSamYaple smoenoen complainign about rsyslog not working22:58
sdakefwiw I have heard this compalint here on irc about 4-5 times in the last cuple of days22:58
*** vhosakot has joined #kolla22:58
SamYaplesdake: yea im ignoring it until heka22:59
sdakedo you know what the issue is?22:59
SamYaplehavent even begun to look into it23:00
SamYapleso much going on23:00
sdakerelated to keyerror exception?23:00
sdakei'll tryt o get more info23:00
sdakeseems like a keyerror shouldn't be hapepning rsyslog or not23:00
openstackgerritMerged openstack/kolla: Add Heka log decoder for MariaDB  https://review.openstack.org/27584723:00
openstackgerritMerged openstack/kolla: Make Heka collect MariaDB logs  https://review.openstack.org/27584823:01
openstackgerritMerged openstack/kolla: Make Heka collect Glance logs  https://review.openstack.org/27676023:01
vhosakotsdake, SamYaple:  I debugged entire day today, I can push and pull ubuntu image to 192.168.122.41:4000,  but  kolla-ansible  throws the error23:02
vhosakotmsg: The requested image does not exist: 192.168.122.41:4000/kollaglue/ubuntu-source-rsyslog:2.0.023:03
vhosakotI have flushed all my iptables rules and chains23:03
SamYaplevhosakot: that image does not exist on your registry then23:03
SamYapledoes it exist in `docker images`23:03
vhosakotwhich image rsyslog ?23:03
SamYaple192.168.122.41:4000/kollaglue/ubuntu-source-rsyslog:2.0.023:03
sdakevhosakot are you sure your using the --registry flag to build?23:04
*** achanda has joined #kolla23:04
vhosakotI see this line in "docker images"23:04
vhosakotkollaglue/ubuntu-source-rsyslog                         2.0.0               6b24cc9a7331        9 hours ago         236.7 MB23:04
sdakevhosakot that looks lik you didn't build with the --registry option23:04
vhosakotshould it be  "192.168.122.41:4000/kollaglue/ubuntu-source-rsyslog"  instead of  "kollaglue/ubuntu-source-rsyslog"  ?23:05
sdakeyes23:05
vhosakotno, I did not use the --registry argument for kolla-build...23:05
vhosakotshould I ???? !!!!!23:05
sdakeI mentioned thtat about 6 hours ago ;-)23:05
*** haplo37 has quit IRC23:05
sdakeor yesterday even23:05
sdakeand its in our build documentation23:05
vhosakotthe quickstart does not mention that :)23:05
sdakeyour right about that, perhaps it should23:06
sdakebut the build docs mention it23:06
vhosakotaah23:06
vhosakotI ran  "sudo kolla-build --retries 0 --base ubuntu --type source "23:06
vhosakotI need to add --registry flag to this right ?23:06
sdakeuse --registry 192.168.122.41:4000 --push23:06
vhosakotfor kolla-build ?23:06
vhosakot./doc/image-building.rst is the build guide ?23:07
sdakehttp://eavesdrop.openstack.org/irclogs/%23kolla/%23kolla.2016-02-19.log.html#t2016-02-19T18:12:3323:07
sdakethere you said you tried it and push failed23:07
sdakedid you fix some problem with your ability to push?23:07
vhosakotI did it with ./build.py in /kolla/cmd.... did not pass it to kolla-build command23:08
sdakethat is the same thing23:09
vhosakotyes,    "./build.py --registry 192.168.1.122.41:4000 --push --base ubuntu --type source rsyslog"  fails23:09
sdakeSamYaple can you work with vhosakot on this, i've got to take my children to dinner23:09
sdakeor they will starve ;(23:09
sdakebye23:09
vhosakotcool, thanks! good night sdake23:09
vhosakot:)23:09
vhosakotyes, I see kolla-build calls kolla/cmd/build.py23:12
*** sbezverk has quit IRC23:16
*** tzn has quit IRC23:25
*** spisarski1 has quit IRC23:28
*** sdake has quit IRC23:35
*** rhallisey has joined #kolla23:36
*** Marga_ has joined #kolla23:51
*** Marga__ has quit IRC23:54
dgonzalezhi jpeeler, are you on?23:58

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