Monday, 2016-01-04

*** salv-orl_ has joined #kolla00:06
*** salv-orlando has quit IRC00:09
*** jasonsb has joined #kolla00:12
*** asalkeld has joined #kolla00:13
*** tzn has joined #kolla00:18
*** suro-patz has quit IRC00:35
*** tzn has quit IRC01:09
*** salv-orl_ has quit IRC01:11
*** salv-orlando has joined #kolla01:12
*** tzn has joined #kolla01:26
*** suro-patz has joined #kolla01:39
*** tzn has quit IRC01:41
*** gtt116__ has joined #kolla01:44
*** gtt116_ has quit IRC01:44
*** tzn has joined #kolla01:53
*** tzn has quit IRC01:58
openstackgerritSam Yaple proposed openstack/kolla: Bump versions of os-client-config  https://review.openstack.org/26305602:20
openstackgerritSam Yaple proposed openstack/kolla: Bump versions of ansible in kolla-ansible  https://review.openstack.org/26308602:20
*** Allen_Gao has joined #kolla02:22
mandrehappy new year \o/02:29
mandreso many things got merged during end year vacations02:32
mandreyou guys never rest?02:32
SamYaplenihilifer: catching up on the issue02:35
SamYaplenihilifer: are you saying kolla-ansible the container? or kolla-ansible the playbooks02:35
SamYaplei sounds like you are attempting to reuse the ansible playbooks we have to deploy mesos02:36
SamYaplemandre: happy new year!02:36
SamYaplemandre: i do not rest, no.02:36
mandreSamYaple, indeed02:44
mandreso we're not using the ansible docker module anymore?02:45
*** sdake has joined #kolla02:47
SamYaplecorrect02:48
SamYapleall the patches have merged :D02:48
SamYapledocker is unblocked!02:48
SamYaplemandre: gate test to prove it https://review.openstack.org/#/c/261601/02:49
*** sdake_ has joined #kolla02:49
mandreSamYaple: congrats02:50
mandreI'm going to remove the version pinning in vagrant02:51
SamYaplecool02:51
openstackgerritMerged openstack/kolla: Unblock Docker pinning in gate  https://review.openstack.org/26160102:51
SamYapledocker 1.10 will also allow us to do neutron thin containers (finally)02:51
SamYaplethats due feburary02:51
*** sdake has quit IRC02:52
SamYapleso im going to get the reviews up early and have the team test with the dev version of docker02:52
mandreall great news02:53
sdake_evening folks02:53
SamYaplehey sdake_02:53
SamYaplelong time no see02:54
sdake_ya we have been on a 2 week shutdown02:54
sdake_i'm back in action now htough02:54
sdake_and teeth are all in good health02:54
SamYapleawesome!02:54
sdake_we are going to be moving fast now ;)02:54
SamYaplejust was telling mandre we got kolla_docker all in place and converted02:54
SamYaplewe are officially unblocked02:54
sdake_nice!02:54
sdake_does it work well?02:54
sdake_I haven' ttried it02:54
sdake_been in midst of remodel of house02:54
SamYaplei mean its not worse. i havent had any issues02:55
SamYapleits a heck of alot more readable02:55
sdake_cool and it works with any version of docker?02:55
sdake_did itmerge, or does it still need reviews?02:55
SamYapleyes and no02:55
SamYapleits all merged, kolla is converted02:55
sdake_nice02:55
SamYapleit will work with any, but we are requiring docker 1.9 now to use named volumes02:55
SamYapleso its only tested with 1.8.2 and 1.902:56
sdake_nice02:56
SamYapleim not planning on keeping it working with all versions of docker-py and docker, just the ones we 'support' in kolla02:56
SamYaplethat should actually keep it from getting out of control like the official ansible one02:56
openstackgerritMartin André proposed openstack/kolla: Remove docker version pinning for vagrant envs  https://review.openstack.org/26309602:59
sdake_sounds good03:00
*** sdake_ is now known as sdake03:00
mandrehey sdake03:02
mandreagreed SamYaple, let's keep the module in a manageable state03:02
SamYapleyea mandre it will grow with time, adding and removing, just like the rest (probably a bit more though)03:03
SamYaplebut the removing is key03:03
SamYaplethe ansible one is trying to work with all versions of everything forever03:03
SamYapleesh03:03
SamYaplei mean i dont disagree with them, but it makes everything so obtuse03:04
SamYaplemandre: sdake https://review.openstack.org/#/c/262614/03:05
SamYaplethats my new project03:05
*** hparekh has quit IRC03:05
mandrehey cool, what does ekko mean?03:11
sdakeyou spelled scalable incorrectly :)03:13
sdakebest wishes with your new project sam03:14
sdakehope we dont see less of you in kola world ;)03:14
*** Allen_Gao has quit IRC03:14
sdakemandre Greek Meaning: The name Ekko is a Greek baby name. In Greek the meaning of the name Ekko is: Sound.03:15
sdakethere is one possible translation for you;)03:15
SamYaplemandre: ekko as in echo as in copy03:16
sdakeword on the street is docke r1.8.2 is sort o lik ea LTS - meant for production deployments03:17
mandregoogle translate autodetects it's Norwegian for echo03:17
sdakeso we wil. probably want to support that version03:17
SamYaplenah it doesnt have volumes support03:17
SamYapleplus to go to thin contaienrs we will actually need to be doing docker 1.10 for mitaka03:17
SamYapleand thats not released yet03:17
SamYaplethin neutron containers*03:17
*** bmace has quit IRC03:18
sdakei'm pretty happy we jus tremoved a painful depenendenc from our system03:18
*** bmace has joined #kolla03:18
SamYaplenow we can use registry v1 and v2 again!03:18
* mandre is out for lunch03:19
sdakei was using registry v103:19
sdakebut  ithink an older version of docker03:19
*** hparekh has joined #kolla03:19
sdakei dont recall03:19
sdakebrain flush03:19
SamYapledocker >=1.9 and ansible docker module == no v1 registry support ever again03:19
sdakeroger03:20
sdaketat sucks03:20
SamYapleits a single line fix too03:20
SamYaplebut they said "v1 is deprecated so no change for that"03:20
SamYaplei would agree with them if v2 registry wasnt awful03:20
SamYapleits getting better, but it still requires suplicate pushing of layers!03:21
SamYapleridiculous03:21
sdakeit is a hard problem to solve03:21
sdaketidiely03:21
SamYaplei did it in one line03:21
SamYaplehttps://review.openstack.org/#/c/262842/3/ansible/library/kolla_docker.py03:21
sdakeno i mean the duplicate pushing thing03:22
SamYapleoh yea. i just think its funny they pushed v2 registry when its clearly not ready03:22
SamYapleit *might* be ready by docker 1.1003:22
sdakeya that was a big error in judgement03:22
sdakethat has caused their company all kinds of harm03:22
SamYaplei think it was more about scalability03:22
SamYaplev1 registry was killing thier backend03:22
SamYaplev2 is actually really good for them, bad for devs03:23
sdakebuy more hardware03:23
sdakeprobleme solved ;)03:23
SamYaplev2 also improves pull for clients03:23
SamYaplei would say _most_ people are benifiting. just not the devs03:23
sdakeits the devs that are pushing docker ;)03:24
SamYapleindeed03:24
sdakeso their main audience, is being shat upon03:24
sdakeanywY nice job, we have a good working solution now ;)03:25
sdakeI'll have to spin it up tomorrow when i  get back to work for the year03:25
SamYaplesounds good03:25
sdakesecure boot i sbusted on my server,s o Ihave to reinstall my os03:26
* sdake growls03:26
SamYaplesetting up a PXE boot server is the way to go03:26
SamYaplei rekick weekly03:26
SamYapletakes about ~30 min03:26
*** Allen_Gao has joined #kolla03:27
*** unicell has quit IRC03:28
*** unicell has joined #kolla03:28
*** unicell1 has joined #kolla03:31
*** unicell has quit IRC03:33
*** coolsvap|away is now known as coolsvap03:33
*** suro-patz has quit IRC03:37
*** Allen_Gao has quit IRC03:37
*** unicell has joined #kolla03:39
*** unicell1 has quit IRC03:41
*** Jeffrey4l_ has joined #kolla03:41
*** klint has joined #kolla03:46
*** Allen_Gao has joined #kolla03:54
*** suro-patz has joined #kolla04:03
*** Allen_Gao has quit IRC04:08
*** ssurana has joined #kolla04:13
*** ssurana has left #kolla04:13
*** sdake has quit IRC04:14
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-mesos: Updated from global requirements  https://review.openstack.org/26289704:15
*** Allen_Gao has joined #kolla04:25
mandreSamYaple here?04:31
*** Allen_Gao has quit IRC04:55
*** suro-patz has quit IRC04:56
*** suro-patz has joined #kolla04:56
*** suro-patz has quit IRC04:58
*** diga has joined #kolla05:03
*** salv-orl_ has joined #kolla05:07
*** salv-orlando has quit IRC05:07
*** Allen_Gao has joined #kolla05:09
nihiliferSamYaple: i meant kolla-ansible as ansible/ dir of kolla, sorry for confusion05:36
nihiliferand yea, i'd like to reuse some stuff from it to deploy mesos by ansible05:36
nihilifermostly kolla_docker, of course05:37
*** Jeffrey4l_ has quit IRC05:37
*** Jeffrey4l_ has joined #kolla05:50
nihilifermandre: hey, if you want to touch vagrant stuff today, can you also disable selinux somehow in bootstrap scripts?05:52
nihiliferwe recently had some people here having problem with this05:53
nihilifersed -i -r "s,^SELINUX=.+$,SELINUX=permissive," /etc/selinux/config05:53
nihilifershould be fine05:53
nihiliferor i can do this, but much later, because now i'm digged in the different stuff ;)05:54
*** suro-patz has joined #kolla05:54
nihilifer'n05:54
* nihilifer feels sorry because of making Dan Walsh sad, but our Docker volumes forces us to do this05:55
mandrehey nihilifer, sure I can do it05:57
mandrenihilifer, do we have a bug for the selinux issue?06:03
nihiliferprobably nope06:03
*** maestro has joined #kolla06:04
mandrei'll fill one quickly06:05
mandrewhat kind of issues with it, do you recall?06:06
nihiliferno rights to write on volume06:06
*** salv-orlando has joined #kolla06:06
mandrethx06:06
nihiliferbecause selinux needs svirt_sandbox_file_t flag on directory mounted as a dir, to not prevent access to it06:07
*** salv-orl_ has quit IRC06:09
nihiliferwell, i registered some blueprint about *enabling* selinux, but it seems to be hard now, almost impossible - to use selinux properly, imo we should figure how to ensure that i.e. ceph container, which should be authorized to r/w to /dev. is really a ceph container and only it's allowed06:09
nihiliferprobably in some future version of docker there will be a mechanism for hashing container images06:10
nihiliferthat would be halpful06:10
nihiliferhelpful*06:11
mandreyeah the right thing is to disable selinux in vagrant06:12
nihiliferyep, no better options for now06:12
mandrei don't even see the point of having it enabled in a dev environment06:12
nihiliferif selinux would work for us, maybe for being sure that it really works even in dev environment06:13
nihiliferbut well, that may happen in some far far future06:13
nihiliferprobably not in mitaka and even the next release ;)06:14
nihiliferhmm... s/probably/surely :P06:14
mandremeaning probably never in computer time :)06:15
openstackgerritMartin André proposed openstack/kolla: Set selinux to permissive in Vagrant  https://review.openstack.org/26313806:28
mandrenihilifer, ^06:28
openstackgerritMerged openstack/kolla: Documentation improvements.  https://review.openstack.org/26305506:42
*** suro-patz has quit IRC06:47
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133106:51
*** suro-patz has joined #kolla06:57
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133107:00
openstackgerritMerged openstack/kolla: Remove docker version pinning for vagrant envs  https://review.openstack.org/26309607:03
*** Jeffrey4l_ has quit IRC07:11
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133107:11
openstackgerritMerged openstack/kolla: Support v1 and v2 registry - kolla_docker  https://review.openstack.org/26284207:13
*** suro-patz has quit IRC07:16
*** suro-patz has joined #kolla07:17
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133107:18
*** reddy has joined #kolla07:18
*** suro-patz has quit IRC07:21
*** Jeffrey4l_ has joined #kolla07:29
*** salv-orlando has quit IRC07:34
*** salv-orlando has joined #kolla07:35
*** reddy has quit IRC07:39
*** salv-orlando has quit IRC07:42
*** salv-orlando has joined #kolla07:42
openstackgerrithardik proposed openstack/kolla: Ansible files for mistral containers.  https://review.openstack.org/26187607:48
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix the docker may return a empty dict when pull images  https://review.openstack.org/26303707:55
*** Jeffrey4l_ has quit IRC07:59
*** Allen_Gao has quit IRC08:00
*** Jeffrey4l_ has joined #kolla08:12
*** Allen_Gao has joined #kolla08:14
*** chandankumar has joined #kolla08:18
*** godleon has joined #kolla08:25
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix the docker may return a empty dict when pull images  https://review.openstack.org/26303708:31
*** Jeffrey4l__ has joined #kolla08:32
*** Jeffrey4l_ has quit IRC08:33
*** salv-orlando has quit IRC08:34
*** salv-orlando has joined #kolla08:35
*** akwasnie has joined #kolla08:39
*** shardy has joined #kolla08:44
*** maestro has quit IRC08:44
*** godleon has quit IRC09:04
*** egonzalez has joined #kolla09:04
*** sdake has joined #kolla09:08
*** maestro has joined #kolla09:08
*** maestro has left #kolla09:12
*** gfidente has joined #kolla09:38
*** gfidente has joined #kolla09:38
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133109:43
*** diga_ has joined #kolla09:45
*** diga has quit IRC09:46
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133109:46
*** pbourke has joined #kolla09:48
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: [WIP] Vagrant multinode deployment  https://review.openstack.org/26224209:51
*** jmccarthy has joined #kolla09:54
*** Jeffrey4l__ has quit IRC09:58
*** openstackgerrit has quit IRC10:02
*** openstackgerrit has joined #kolla10:02
*** coolsvap is now known as coolsvap|away10:04
*** Jeffrey4l__ has joined #kolla10:11
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133110:11
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133110:28
*** klint has quit IRC10:30
openstackgerritArtur Zarzycki proposed openstack/kolla: Horizon ubuntu binary container  https://review.openstack.org/26320510:40
*** klint has joined #kolla10:46
SamYaplemandre: im here now10:48
openstackgerritArtur Zarzycki proposed openstack/kolla: Horizon ubuntu binary container  https://review.openstack.org/26320510:52
*** tzn has joined #kolla10:54
openstackgerritSam Yaple proposed openstack/kolla: Update kolla_docker documentation  https://review.openstack.org/26284410:58
sdakeis michal rostecki around?10:59
sdakemorning folks ;)11:00
sdakenihilifer  ping11:00
sdakehow close is https://review.openstack.org/#/c/236198/5 to being completed?11:01
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix the docker may return a empty dict when pull images  https://review.openstack.org/26303711:05
openstackgerritMerged openstack/kolla: Set selinux to permissive in Vagrant  https://review.openstack.org/26313811:08
nihilifersdake: i'll try to get it done till wednesday11:08
sdakenihilifer fantasic - would like to get that fixedasap ;)11:08
nihiliferok. btw, we plan to release mitaka-2 on 21th Jan?11:09
sdakenihilifer, I think what we should do is just cut mitaka-1 now11:09
sdakeand yes release mitaka-2 on schedule11:09
sdakeand probably add a backup to the tagging process in case i fall ill in the future ;)11:10
sdakeSamYaple up for taking on that responsibiliity?11:10
nihilifersdake: should i move this but to mitaka-2 then?11:11
nihiliferbug*11:11
sdakenihilifer let me handle the moving please11:11
sdakei will do today11:11
nihiliferok11:11
SamYaplesdake: sure11:16
SamYaplehey nihilifer want to talk about the kolla-ansible in mesos?11:17
sdakeSamYaple cool - I'll handle tagging, but if I'm late, i'll still hndle tagging, if i need to hand off for some medical reason (I have bad eeth for example) I'll let you know via email. ok?11:17
nihiliferSamYaple: yes11:17
SamYaplesdake: thats fine11:17
SamYaplenihilifer: ok so are you going to be needing everything, or just the library/kolla_docker.py?11:17
nihiliferjust kolla_docker11:18
sdakeSamYaple your in the kolla-release group now11:18
sdakejust make your own signing key11:19
sdakei am just going to tag mitaka-1 where it is atm11:19
SamYaplesdake: roger11:19
sdakeand we can make an announcement wednesday saying it may or may not work ;)11:19
SamYaplenihilifer: hmm. i hate to say it, but a copy may be the right choice here.11:19
sdakealong with all of the changes using our standard release announcement etherpad process11:19
SamYaplenihilifer: if you do not update the one in the kolla-mesos repo, we should be fine. perhaps set it to read-only?11:20
sdakenihilifer  can you give me a tldr status report on the mesos repo?11:20
SamYaplei don't like the idea of involving submodules/subtrees with git11:20
sdakeyes no submodules please11:20
sdakeit just overly complilcates the workflow11:21
* sdake has finall8y convinced SamYaple ;)11:21
SamYaplesdake: im fine with submodules if the whole repo is needed, not a single file11:22
nihilifersdake: mesos repo currently has 1) vagrant for all-in-one mesos installation 2) yaml config files for each service, similar to those from ansible in kolla 3) command line tool pushing configuration to zookeeper and running the containers on mesos+marathon (or mesos+chronos for bootstrap)11:22
SamYaplemy new repo is merged!11:22
SamYaplejoin me on #openstack-ekko11:23
nihilifersdake: and 4) extended start script, which creates config files from zk11:23
sdakethe yaml files are a mesos input?11:24
nihilifersdake: currently supported services are mariadb, rabbit, glance, cinder, keystone and horizon11:24
nihilifersdake: not exactly. yaml files define what's pushed to zookeeper11:25
SamYaplefyi sdake, mysql+pymysql is the new default across the openstack. pymysql has python3 support so all connection strings should be that11:25
sdakeso they are an input to the cli tool?11:25
SamYaplewe switched kolla over a while ago11:25
sdakeSamYaple  thanks I saw that in a review and was curious what that was all about11:26
nihilifersdake: now i'm working on multinode mesos installations by ansible. then i'll continue on brining support of the other services (probably i'll begin from neutron)11:26
nihilifersdake: yes, they're input for cli11:26
sdakecool so sounds like its single node atm then with bringup via vagrand?11:27
sdakevagrant?11:27
nihilifertes11:27
nihiliferyes*11:27
sdakehope you can make our wednesday meeting so we can write the release announcement together11:27
sdakeor someone else with the appropriate understanding of the changes11:28
nihilifersure11:28
sdakecool sounds like i plan11:28
sdakei need to reinstall my centos distro today because secre boot is busted for some reason11:29
* sdake groans11:29
*** shardy has quit IRC11:29
*** shardy has joined #kolla11:30
nihiliferSamYaple: copying over kolla_docker sounds awfull, but yeah, no better choice for now11:30
sdakeSamYaple would you like to try to make the tag today so i can walk you through any problems you have (so you can learn how to do it)11:30
nihiliferSamYaple: besides cloning kolla in vagrant which i'm doing currently in WIP patches i sent:/11:31
SamYaplesdake: ok. is there special openstack things or just git tag/push?11:31
sdakethere is some special magic11:31
sdakebu8t you have tag permission push becasue of kolla-release11:31
sdakethe magic is documented11:31
sdakefirst step is to create a signing key11:31
SamYaplenihilifer: yea the copy isn't great. but if you set your kolla-mesos copy to read-only and -2 any changes in the kolla-mesos branch it shouldn't be too bad11:32
SamYaplenihilifer: but i agree, not amazing. might be the cleanest though. that module won't change often (well it might in the next few days, but not long term)11:32
sdakeya copy as unideal ss it is, seems like best solution here, as long as we treat the koll repo s the porper upstream for the module11:32
SamYaplei want to start the process of splitting kolla-ansible off before mitaka-211:33
sdake3 weeks - get cracking ;)11:34
SamYaplei can get it merged into project-config in that time, not problem. we need to get everyone on the same page. i was planning that for this meeting11:35
SamYapleupcoming meeting*11:35
SamYaplepbourke: hey man!11:40
pbourkeSamYaple: hey happy new year :)11:40
*** dims has joined #kolla11:40
*** dims has quit IRC11:40
SamYapleyou as well11:41
*** dims has joined #kolla11:41
sdakepbourke happy new year dude11:41
sdakewe are still all alive and its a new year :)11:41
sdakemy tooth didn't kill me ;)11:42
pbourkesame to you, good to be back11:42
sdakeya over the last 3-4 weeks i feel a bit what it is like to be unemployed11:42
sdakei was bored to death11:42
*** Jeffrey4l__ has quit IRC11:43
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133111:45
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133111:58
sdakeSamYaple pbourke re swift12:04
sdakeand ceph12:04
sdakeceph has a rockin auto disk detect mechnaism12:04
sdakecan we make swift have the same thing?12:04
SamYaplesdake: yes and no. ceph has a rockin add-disk-on-the-fly mechanism. swift does not12:06
SamYapleso we would be in the business of autogenerating rings12:06
*** salv-orl_ has joined #kolla12:06
sdakefundamentally the problem i keep hearing over and over with swift and kolla is -etoohard12:07
*** salv-orl_ has quit IRC12:07
sdakei dont hear that with ceph12:07
*** salv-orl_ has joined #kolla12:07
sdakewould like to solve that - however is best ;)12:08
*** salv-orlando has quit IRC12:09
*** tzn has quit IRC12:10
SamYaplebecause swift is fundementally a PITA to setup and manage12:10
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133112:10
SamYaplewe can take a more active control in swift, but that means limiting what the end user can do with it12:11
SamYapleor its just alot of manual work on the enduers part12:11
sdakeis both an answer that we could deliver on?12:18
sdake"easy mode limited config" + "hard mode full customization"\12:18
SamYaplefull customization means reimplementing ring config as ansible code12:19
sdakeright12:19
sdakeoh12:19
sdakeno12:19
sdakei mean full customization via the operator12:20
SamYapleyup12:20
sdakesorry 6am ;)12:20
SamYaplethats what i meant to12:20
SamYapleeither we lock down the ring generation, or we reimplement it12:20
sdakei mean the operator is responsible for generating ring configs int he had mode config12:20
SamYaplethen we cant autoadd disks12:20
sdakehad/hard12:20
SamYapleand the ceph disk code doesnt matter12:21
sdakeok, well this is probably8 agood topic for the midcycle12:21
SamYapleindeed. swift is annoying12:21
sdakeits a bear to ssetup12:22
sdakebut people like it because its dep free12:22
SamYapleok im heading into the office. afk12:22
sdakeenjoy12:28
sdakehey guys zuckerberg is giong to implement AI12:28
sdakein his spare time12:29
sdakewhile two generations of maniacal PHD+ brainpower has failed12:29
openstackgerritMerged openstack/kolla: Fix the docker may return a empty dict when pull images  https://review.openstack.org/26303712:30
pbourkehis last implementation it turned out had humans sitting typing responses12:30
sdakehaha12:31
sdakefunny :)12:31
sdakefwiw, I dont use facebook ;)12:32
*** tzn has joined #kolla12:32
nihiliferlucky you12:32
ajafore12:36
pbourkeare insecure registries supported by the new kolla_docker module?12:38
*** sdake has quit IRC12:39
nihiliferpbourke: it's probably not the business of kolla_docker module12:39
nihiliferafaik, insecure registries can be enabled only on the docker service's config12:40
*** sdake has joined #kolla12:40
nihiliferin case of redhat based distros - /usr/lib/systemd/system/docker.service12:40
pbourkenihilifer: hmm that's true. just trying to figure it out in the context of https://review.openstack.org/#/c/262843/4/etc/kolla/globals.yml12:41
nihiliferhere you have a solution - https://github.com/openstack/kolla/blob/master/dev/vagrant/bootstrap.sh#L6012:41
nihiliferawww, ok12:42
nihiliferhmm... sorry, that insecure_registry option in ansible module was actually for docker-py using http (instead of https), sorry for confusing you12:43
nihiliferwell, in Sam's patch it seems to be working without anny additional flags12:43
*** rhallisey has joined #kolla12:45
*** reddy has joined #kolla12:46
*** diga_ has quit IRC12:46
pbourkeI actually can't see how it would work with an insecure reg12:46
pbourkebut I'll take your word that it does12:46
rhalliseymorning12:49
sdakeinsecure registry flag happens in the docker.service file imo not  the docker.py file12:52
sdakerhallisey happy new years!12:52
rhalliseyhey happy new years!12:52
rhalliseysdake, boy you're up early12:52
*** sdake_ has joined #kolla12:53
*** Allen_Gao has quit IRC12:56
*** Allen_Gao has joined #kolla12:56
*** sdake has quit IRC12:57
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133112:59
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133113:07
*** dave-mccowan has joined #kolla13:08
*** inc0 has joined #kolla13:11
inc0good morning everyone13:11
*** salv-orl_ has quit IRC13:13
nihiliferhey inc0, happy new year13:14
inc0you too13:14
*** salv-orlando has joined #kolla13:14
inc0I heard you got hit by winter?13:14
nihiliferyes13:14
nihilifer-15 degrees13:14
nihiliferso after not so cold holidays, is a little bit shocking ;)13:16
inc0yup...well...let's just hope it won't stay this way till April, like it did few years ago13:16
barthalionsnow in April was awesome13:23
*** Jeffrey4l__ has joined #kolla13:24
inc0yeah, and christmas were warm that year, so it was just opposite to what it should be13:25
SamYaplepbourke: yes they are13:26
openstackgerritMerged openstack/kolla: Update kolla_docker documentation  https://review.openstack.org/26284413:26
SamYapleupstream docker deprecated that option13:26
SamYaplehey rhallisey13:26
SamYaplepbourke: nihilifer https://github.com/docker/docker-py/blob/master/docker/api/daemon.py#L37-4113:28
*** reddy has quit IRC13:28
SamYapleits no longer used on the client side, only set on the daemon to allow which "insecure registries" are ok to connect to13:28
SamYapleclient cant override anymore hence the deprecation13:28
SamYaplemorning inc013:29
inc0hey SamYaple, so ekko is a thing:)13:30
SamYapleit is indeed13:30
inc0cool! At last I get to write some python13:32
rhalliseySamYaple, inc0, hey guys happy new year!13:35
inc0you too13:35
rhalliseythanks13:36
openstackgerritMerged openstack/kolla: Remove unused params for kolla_docker  https://review.openstack.org/26284313:37
*** unicell1 has joined #kolla13:38
*** reddy has joined #kolla13:41
*** unicell has quit IRC13:41
*** klint has quit IRC13:57
*** gtt116_ has joined #kolla14:05
*** dwalsh has joined #kolla14:05
*** gtt116__ has quit IRC14:08
SamYapleif I could get some reviewer love on the named volume patch it would be much appreciated (note, must use docker 1.9 and docker-py 1.6) https://review.openstack.org/#/c/261843/14:09
inc0SamYaple, what part exactly requires sorted? https://review.openstack.org/#/c/248481/9/tools/version_check.py14:11
*** sdake has joined #kolla14:11
SamYapleinc0: if i remember corerctly (and mandre has changed the logic a bit) but when i did it it used sorted to ensure the version numbers lined up and the latest was successfully choosen14:12
SamYaplenot the logic itself, but the data coming into the logic14:12
*** sdake_ has quit IRC14:12
SamYaplebeautifulsoup didnt return a deterministic list or something like that14:12
*** v1k0d3n has joined #kolla14:13
*** Kennan has quit IRC14:14
SamYapleeither way keeping them sorted is the most readable output. whats your problem with sorted again inc0 ?14:14
*** Kennan has joined #kolla14:15
*** dwalsh has quit IRC14:17
inc0it's not a problem, just iteritems looks better imho, more pythonic14:22
inc0also there is slight change in sorted logic between 2 and 314:22
inc0and that is in 2 it returns list and in 3 it's an iterator14:23
inc0here that won't affect anything, but it might later on14:23
SamYapleah i see. hmm if we go iteritems then well have to have another layer to sort the output14:28
SamYaplenot ideal14:28
inc0well, anyway it's not bad, it just could be better, I don't think we need to sort output really, but it doesn't hurt14:29
*** jpeeler has joined #kolla14:29
*** jpeeler has joined #kolla14:29
SamYaplesince this is a user readable output, i think we do14:29
SamYaplewhen this gets changed to a bot to propose things, we absolutley dont14:30
inc0also, upstream_version is a dict14:30
inc0so it's not sorted14:30
inc0order you put stuff there has completely no effect14:31
SamYaplethat may have changed. we still want sorted output though. a sorted dict is a great way to ensure that...14:31
inc0you don't use sorted dict there14:32
nihiliferyou guys mean OrderedDict or what?14:33
SamYaplethat doesnt affect the output inc014:33
inc0yeah, OrderedDict14:33
SamYaplenihilifer: we are calling it by sorted(dict())14:33
nihiliferah, i see it now, sorry14:33
*** stvnoyes has joined #kolla14:34
inc0SamYaple, what you do there is sorted(dict()) -> this will produce sorted list of keys of dict, then with that you populate upstream_versions which is just plain dict, and then use this one14:34
inc0and order in which you add stuff to upstream_version has completely no meaning14:34
*** dwalsh has joined #kolla14:34
inc0so as it currently looks like, sorted() seems redundant14:35
inc0unless I'm missing somethingt14:35
SamYapleinc0: you are missing the fact that this is a for loop and it prints things i think14:35
SamYaplethis is user output14:35
nihiliferi'd propose to change MAJOR_VERSIONS_MAP to OrderedDict14:36
nihiliferand then iteritems14:36
inc0yes, it works on upsteam_version and local_versiuon14:36
inc0and again, way you add stuff to it doesn't mean anything14:36
inc0they seem sorted, because that how dicts in python works14:36
inc0but in fact they might not be14:36
stvnoyesstatus14:36
SamYaplenihilifer: then we have to get six involoved14:38
SamYaplei dont wanna get six involved :(14:38
inc0SamYaple, try to remove sorted and see if it changes anything14:38
SamYapleinc0: it does14:39
SamYaplebecause it hashes those keys and then loops through the hashes in order14:39
nihiliferSamYaple: you already have six there, so what's the problem?14:40
SamYapleoh i didnt realize that nihilifer. like i said mandre took over the patch a while back. I only care about sorted output with the lest complication14:40
SamYapleordereddict seems to be the way to go14:41
nihiliferyea14:41
*** chandankumar has quit IRC14:41
inc0yeah, make it ordered dict14:42
*** reddy has quit IRC14:48
akwasniehi guys, happy new year!:)14:49
inc0hey Ala, hows life?14:49
SamYaplehappy new year akwasnie!14:49
akwasnieSam, I have one question about kolla_docker in logstash. https://review.openstack.org/#/c/252968/7/ansible/roles/elk/tasks/logstash.yml14:50
SamYapleshoot14:51
akwasnieExpose and command parameters are required for logstash container but are not supported by kolla_docker. Should we add them to kolla_docker or create Dockerfile for logstash and specify port that should be exposed there?14:51
SamYapleakwasnie: i don't think either of those are _required_. The CMD should be in the config.json and the expose is only useful when not using --net=host (and we should be using net=host everywhere)14:52
*** rmart04 has joined #kolla14:53
openstackgerritMerged openstack/kolla-mesos: Updated from global requirements  https://review.openstack.org/26289714:53
*** sdake_ has joined #kolla14:55
akwasnieoh thanks Sam, I'll try it14:56
*** sdake has quit IRC14:58
*** sdake has joined #kolla15:00
openstackgerritMerged openstack/kolla: Bump versions of os-client-config  https://review.openstack.org/26305615:02
openstackgerritMerged openstack/kolla: Convert to named volumes instead of data container  https://review.openstack.org/26184315:02
*** sdake_ has quit IRC15:03
*** shakamunyi has quit IRC15:15
*** barra204 has quit IRC15:15
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Dockerfiles for Mesos  https://review.openstack.org/26133115:16
*** sdake_ has joined #kolla15:22
*** sdake has quit IRC15:25
*** blahRus has joined #kolla15:27
nihiliferSamYaple: about your latest comments15:29
SamYaplethe structural thing?15:29
nihiliferwe already have situation when openstack-base is in some outside directory15:29
nihiliferand all the dirs line nova/ etc. are inheriting from that15:29
SamYapleok. thats a fair point15:29
nihiliferi think that mesosphere is analogical here15:29
SamYapleyea. we did break that rule when doing openstack-base15:29
*** shakamunyi has joined #kolla15:29
SamYapleyouve sold me15:29
*** egonzalez has quit IRC15:32
*** chandankumar has joined #kolla15:34
*** sdake has joined #kolla15:38
*** sdake_ has quit IRC15:39
sdakenihilifer will you be making it in person to the kolla midcycle?15:41
*** blahRus1 has joined #kolla15:49
*** blahRus has quit IRC15:50
*** rahulshr has joined #kolla15:50
rahulshrHi Guys, I need your suggestion15:50
SamYaplerahulshr: ok!15:50
rahulshrI have deployed kolla using all in one config15:50
rahulshrnow I am trying to make it multinode ie to add one compute node15:51
sdakenice - what was your impression of the deployment process - just say whatever comes to mind ;)15:52
rahulshras per my understanding I have to deploy the registry and build the images again with that registry15:52
sdakerahulshr you need to use a registry when doing multinode15:52
pbourkerahulshr: I think you should just need to add the new node to your inventory file and redeploy15:52
sdakeyou can do it without a registry but your life will be much simpler with a registry15:52
SamYaplerahulshr: that is the way you should do it, however for testing you can push the images by hand to a second node15:52
rahulshris it possible to do it without building again?15:53
SamYapleyes what sdake said15:53
SamYaplerahulshr: you can15:53
sdakeyup you can push to the second node15:53
rahulshrok15:53
SamYapleyou can `docker import/export` the images15:53
SamYaplebut again, i don't recommend it. its long. setting up a registry is quick and easy15:53
rahulshrhow can I push multiple images in one go?15:53
pbourke--registry foo:5000 --push15:54
pbourkepass above args to your build15:54
*** cloudnautique has joined #kolla15:54
rahulshrsdake since I was new with kolla/openstack I have to do the deployment couple of time but I hated the kolla-build time :)15:55
*** cloudnautique has quit IRC15:55
sdakepbourke he means wihtout a registry15:55
sdakerahulshr  roger on the build time - that is indeed annoying15:55
sean-k-m1you should be able to manually push the currently built images to a regestry also without rebuilding them correct.15:55
sdakesean-k-m1 yes you can also do that15:55
sdakeso docker has an image cache - this is what "docker images" shows you15:55
*** cloudnautique has joined #kolla15:55
sdakeanythign in the image cache can be pushed to a registry15:55
rahulshryes I can ush manually but there are arnd 50 images15:56
rahulshrI was thinking if there is some docker cmd to push all in one go15:56
sdakerahulshr probably easiest is to cut nad past ethe list and then make a bash script out of it to do the job15:56
sdakeotherwise you can use awk to do the job15:56
rahulshrhmm ok15:56
sdakeperhaps SamYaple  can come up with some simple awk script to do it - for me i'd jsut do docker images and manaully create a script to do it with 50 commands in it15:57
sdakebut I roll hacky on 1 time jobs ;)15:57
rahulshrlet me try the script then15:58
SamYaplerahulshr: you want to push local images to the regstiry?15:59
SamYaplei have a script for that15:59
SamYaplewell not so much a script. but i do `docker images | awk '/kollaglue/ {print $1}' | xargs -n1 -P1 docker push`16:00
SamYapleadjust the value of -P for parallel16:00
SamYapleif you have other kollaglue images, you may want to change the match to the registry name like `docker images | awk '/name_of_registry:5000/ {print $1}' | xargs -n1 -P1 docker push`16:01
rahulshrThanks SamYaple16:04
*** rmart04 has quit IRC16:08
*** reddy has joined #kolla16:18
*** ajafo has quit IRC16:26
*** akwasnie has quit IRC16:26
*** coolno1 has joined #kolla16:30
coolno1hello16:30
coolno1need some help in safely upgrading our open stack setup16:30
SamYaplecoolno1: what is your question?16:31
coolno1we have got a 2 node setup where each node acts as controller as well as compute node currently16:31
coolno1We need to add another compute node and if this succeeds we will add lot many compute nodes16:31
coolno1how do we go about it without impacting the current setup16:32
*** ajafo has joined #kolla16:32
coolno1SamYaple: details as above16:32
SamYaplecoolno1: is this a kolla set?16:32
coolno1yes corrct16:32
coolno1*correct16:32
SamYapleit should be as simple as adding the node to your inventory file and rerunning the playbooks16:32
SamYapleif you ahve updated images then its going to try to restart and pull in those changes16:33
coolno1will it bring down the existing setup- by which I mean their are users which are currently using VM's spawned out of openstack setup16:33
rahulshrI think you just have to edit a mulitnode file16:33
SamYaplecoolno1: no it will not, unless you have updated/rebuilt the images in some way16:33
SamYaplethe playbooks are idempotent, they should only change things if things need to be changed16:34
coolno1SamYaple: Thanks for this info will try it out16:34
coolno1rahulsr: what is multinode file?16:34
SamYaplefor your info: if this was a fresh vanilla setup, you could just add the compute to the inventory and rerun all the playbooks and only the compute node would have changes16:34
SamYaplecoolno1: your inventory file16:34
coolno1SamYaple: aah, we do not use the name multinode16:35
SamYapleyea its fine16:35
SamYaplethose inventory files in the repo are examples16:35
coolno1SamYaple: Okay got it, so just add another hostname in our inventory file an rerun kolla deploy16:36
coolno1SamYaple: that should do I guess?16:36
openstackgerritSam Yaple proposed openstack/kolla: Allow common role to pull images  https://review.openstack.org/26284616:36
openstackgerritSam Yaple proposed openstack/kolla: Allow ceph role to pull images  https://review.openstack.org/26284716:36
coolno1in the [compute] section ofcourse16:36
SamYaplecoolno1: correct. that is all16:38
SamYapleagain, if the underlying images have changes it may try to restart your services16:38
coolno1SamYaple: I have a local registry16:39
SamYaplebut if they havent youll be fine (have you rebuilt the images?)16:39
coolno1SamYaple: No I haven't, I have got a docker registry which host all the images and those are intact(have not been touched)16:40
coolno1SamYaple: I hope this should be safe?16:40
SamYaplecoolno1: yes it should be fine then16:41
SamYapleif it is not, please keep all the info and logs (and ansible output)16:41
SamYapleit is also safe to stop ansible while running if you see a problem16:41
SamYaple^C16:41
coolno1stop ansible?16:42
coolno1SamYaple: can you please elaborate?16:42
SamYapleif you run the playbooks and see a problem (restarting of your contaienrs for example) you can stop ansible mid-run safely16:42
SamYapleand rerun it later16:42
coolno1SamYaple: aah okay, but starting container does not mean my users VM will be impacted?16:43
coolno1as compute node does not use any containers16:43
SamYaplecorrect, its a new compute node16:43
coolno1may be only for sometime the VM's may be inaccessible (for example say neutron containers are restarted)16:44
coolno1and hence networking becomes unavailable16:44
SamYapleno you should not be impacted at all because only the new compute node should have anything that has changed on it16:44
SamYaplebut if containers do get restarted, then yes you will be impacted as you describe16:45
SamYaplei am stepping away from lunch. please let me know if you have any issues coolno116:45
coolno1SamYaple: Okay so looks like it is safe to add another compute node, I will try this later tonight and will probably get back to you tomorrow16:45
SamYaplealso let me know if you dont have any issues!16:45
SamYaplesounds good16:45
coolno1SamYaple: sure will let you know16:46
coolno1thanks a lot16:46
*** unicell1 has quit IRC16:47
*** unicell has joined #kolla16:47
nihilifersdake: yes, in 99% i'll be there in person16:50
*** diga has joined #kolla16:50
nihiliferlet me confirm that later this week16:50
*** barra204 has joined #kolla16:51
*** shakamunyi has quit IRC16:51
*** sacharya has joined #kolla16:51
*** unicell has quit IRC16:52
pbourkenihilifer: what does kolla-mesos-deploy assume to be on the deployment host?16:52
*** ssurana has joined #kolla16:55
nihiliferpbourke: zookeeper and mesos+marathon16:55
pbourkenihilifer: k that's what I thought, thanks16:56
nihilifernp16:56
*** diga has quit IRC16:57
*** nihilifer has quit IRC17:00
SamYaplepbourke: you coming to the midcycle?17:02
pbourkeSamYaple: no17:02
SamYaplenooooo17:02
*** coolno1 has quit IRC17:02
SamYaplebut the beers...17:02
pbourkewe discussed this before :)17:03
SamYaplei know i know17:03
SamYaplebut you should still try17:03
*** nihilifer has joined #kolla17:04
*** diga has joined #kolla17:05
pbourkeId like to but it's too far to travel for 2 days17:05
*** diga has quit IRC17:05
*** diga has joined #kolla17:06
SamYaplemake it a week!17:06
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Playbook for keystone upgrade  https://review.openstack.org/25756817:07
pbourkestop tempting me17:08
pbourkemesos is a pita to install17:08
*** chandankumar has quit IRC17:08
openstackgerritSidharth Surana proposed openstack/kolla: Make galeradb bootstraping robust  https://review.openstack.org/25496117:10
*** diga_ has joined #kolla17:10
*** diga has quit IRC17:10
*** diogogmt has joined #kolla17:11
*** reddy has quit IRC17:12
*** diga_ has quit IRC17:15
*** nihilifer has quit IRC17:17
*** nihilifer has joined #kolla17:18
*** sdake_ has joined #kolla17:23
*** chandankumar has joined #kolla17:24
*** sdake has quit IRC17:25
SamYaplesdake_: food is fine in the building, trust me. ill bring it in if there is any issue (and there wont be)17:31
SamYaplepbourke: tempted17:31
pbourkeSamYaple: your untapped checkins have been doing the trick17:32
SamYaplepbourke: thats mostly from the same place17:32
pbourkeahem, but its not kolla not the beer right17:32
SamYapleright uhh yeaa17:32
SamYaplepbourke: want to work on a backup project?17:32
SamYaplegot a new one in openstack17:33
SamYapleekko17:33
SamYapleits official17:33
pbourkeyup im watching it in gerrit17:33
pbourkeill probably lurk for a while and see if it sparks my interest17:33
SamYaplejoin us in #openstack-ekko17:33
pbourkealready there17:33
SamYaplecool :)17:34
pbourkeyou guys seem to have discussed it previously, any tasks for a newbie?17:34
SamYaplepbourke: i talked a bit with inc0 the other day, but nihilifer is as new as you to it17:37
SamYaplesince they are both going to be at the midcycle for kolla, i was going to carve out some ekko time then17:38
SamYaplepbourke: i am more than happy to give the run down for you guys17:38
*** chandankumar has quit IRC17:46
*** dwalsh has quit IRC17:49
sdake_SamYaple ack, sounds good thanks bro17:53
*** sdake_ is now known as sdake17:56
sdakeSamYaple is the venue the actual servosity office or some startup incubator?17:57
sdakeI htink you told me in the past but i don't recall atm17:57
SamYaplestartup indubator would probably be most accurate17:57
SamYaplebut our office is here17:57
SamYaplewe have shared confrence rooms17:57
sdakecool17:57
sdaketo get in the building, requires a badge or badgless entry?17:58
sdake(this stuff goes int eh wiki)17:58
SamYaplego through the first floor during business hours (all hours?) and no badge17:58
*** suro-patz has joined #kolla18:00
*** vinkman has joined #kolla18:03
*** vinkman has left #kolla18:03
*** salv-orl_ has joined #kolla18:06
*** v1k0d3n has quit IRC18:06
*** salv-orl_ has quit IRC18:06
*** salv-orl_ has joined #kolla18:07
*** reddy has joined #kolla18:08
*** jasonsb has quit IRC18:08
*** salv-orlando has quit IRC18:08
*** dwalsh has joined #kolla18:10
*** reddy has quit IRC18:13
sdakenice cisco is funding midcycle dinner on tuesday - yay :)18:20
SamYaplew00t18:21
sdakenow for breakfast and soda ;)18:21
*** v1k0d3n has joined #kolla18:24
*** tzn has quit IRC18:31
*** openstackgerrit has quit IRC18:32
*** openstackgerrit has joined #kolla18:32
*** akwasnie has joined #kolla18:40
*** smartshader has joined #kolla18:48
*** Allen_Gao has quit IRC18:56
*** Allen_Gao has joined #kolla18:57
*** sdake has quit IRC19:08
*** gfidente is now known as gfidente|afk19:08
*** opennode has joined #kolla19:20
*** openstackstatus has quit IRC19:20
*** openstackstatus has joined #kolla19:20
*** ChanServ sets mode: +v openstackstatus19:20
*** sdake has joined #kolla19:21
opennodehi! Im trying to deploy latest master branch (as stable/liberty does not get pass mysql haproxy user creation on centos 7) but deploy fails with “Starting rsyslog container” task with the following error msg: AttributeError("'Client' object has no attribute 'create_host_config’”,)19:23
sdakeopennode haven't seen that error before19:24
opennodecan I debug somehow more before failing bugreport?19:25
sdakeopennode note we just changed to a kolla-developed ansible module for communicating with docker because of untactable upstream problems with the ansible docker module, so there may be a bug or two19:25
sdakeopennode lets see if SamYaple has any suggestions19:25
sdakehe wrote the module for the most part iiuc19:25
opennodeaha ok19:25
akwasnieSamYaple: are you there?19:25
SamYapleopennode: do you have any logs? how is it failing? what message19:25
SamYapleakwasnie: here i am19:25
opennodeI actually dont wont to build and deploy master branch - just stable/liberty didnt work out for me either...19:26
opennodeTASK: [common | Starting rsyslog container] ***********************************19:26
opennodefailed: [localhost] => {"changed": true, "failed": true}19:26
opennodemsg: AttributeError("'Client' object has no attribute 'create_host_config'",)19:26
opennodeFATAL: all hosts have already failed -- aborting19:26
opennodeansible/library/kolla_docker.py failing perhaps?19:27
SamYapleopennode: that is due to a bas os-client-config19:27
SamYaplewhen did you build these images?19:27
opennodejust now19:27
SamYaplehmmm19:27
opennodeIm on centos 7.1.150319:28
SamYapleopennode: what version of docker and docker-py?19:28
opennodeie the build/deploy host19:28
SamYapleon the deploy host19:28
opennodeDocker version 1.8.2-el7.centos, build a01dc02/1.8.219:28
opennodepython-docker-py.noarch          1.4.0-118.el7                         @extras19:28
SamYapleah yes. you need docker 1.9+ and docker-py 1.6. see http://docs.openstack.org/developer/kolla/quickstart.html19:28
SamYaplethese reqs _just_ changes as of today19:29
akwasniei am working on adapting ELK patchset to kolla_docker and - we discussed earlier today how to handle missing command param in ansible for kolla_docker, and I have a question regarding how to handle the configuration file part19:29
opennodeok thnx19:29
SamYapleakwasnie: ok19:29
SamYaplelike the config.json thing?19:29
akwasniewe can use config.json to run commands with specific params, but right now ELK containers do not use kolla base image but the oficial ones for elastic, logstash and kibana19:30
SamYapleohh. hmmm19:31
SamYaplehmmmmm19:31
akwasnieso - this will require to have additonal dockerfiles for E, L and K for each distro19:31
SamYaplethats an interesting case19:31
SamYapleyea akwasnie to do it the way the other ones work, then yes19:31
akwasniedo we want them to be inherited after kolla base and have all the specifics for each service copied into them19:31
SamYaplewe should discuss this in the meeting on Wednesday19:31
SamYaplethat would be my vote, to build our own19:32
SamYaplebut it is additional work19:32
akwasnieor, inherit after original items and implement specifics for each distro?19:32
akwasnies/items/images19:32
SamYapleakwasnie: my vote would be building our own from scratch, but this is somethign we should talk about in the meeting wednesday with a larger audience19:32
akwasnieok, should I add this to agenda?19:33
opennodeone thing more - any ides why stable/liberty branch “TASK: [mariadb | Creating haproxy mysql user]” is producing this error:19:33
opennodeFile \"/usr/lib64/python2.7/site-packages/cryptography/hazmat/backends/interfaces.py\", line 12, in <module>", "    @six.add_metaclass(abc.ABCMeta)", "AttributeError: 'module' object has no attribute 'add_metaclass'"], "warnings": []} ?19:33
SamYapleyes. additionally, you may want to add a mailing list question (if you want)19:33
akwasnieok, thanks for help, SamYaple :)19:33
SamYapleopennode: stable liberty only works with docker 1.6.0 to 1.8.2, and docker-py <= 1.4 i believe19:34
SamYapleopennode: but that looks like the mysql module in the kolla-ansible contianer. so im not sure19:34
SamYapleive not seen that. i woudl recommend filing a bug19:34
opennodeit might be variation of https://bugs.launchpad.net/kolla/+bug/149178219:35
openstackLaunchpad bug 1491782 in kolla "Fail to create haproxy mysql user" [Medium,In progress] - Assigned to Sidharth Surana (ssurana)19:35
SamYapleopennode: normally that bug you linked is due to the database not running19:36
opennodeyes - I have different error actually - just the same outcome :)19:36
opennodeok I will file a bug19:36
*** rahulshr has quit IRC19:37
*** dims_ has joined #kolla19:46
*** dims has quit IRC19:47
openstackgerritSam Yaple proposed openstack/kolla: Allow common role to pull images  https://review.openstack.org/26284619:48
openstackgerritSam Yaple proposed openstack/kolla: Allow ceph role to pull images  https://review.openstack.org/26284719:48
openstackgerritSam Yaple proposed openstack/kolla: Allow common role to pull images  https://review.openstack.org/26284619:49
openstackgerritSam Yaple proposed openstack/kolla: Allow ceph role to pull images  https://review.openstack.org/26284719:49
*** tzn has joined #kolla19:50
opennodefiled https://bugs.launchpad.net/kolla/+bug/153096219:51
openstackLaunchpad bug 1530962 in kolla "mariadb "Creating haproxy mysql user" task failing with "no no attribute 'add_metaclass'" error" [Undecided,New]19:51
sdakeakwasnie  agree we should discuss on wednesday19:53
sdakeakwasnie can yo uadd to the the agend aplease19:53
openstackgerritAlicja Kwasniewska proposed openstack/kolla: Added ELK containers for centralised logging  https://review.openstack.org/25296819:54
*** daneyon has joined #kolla20:04
*** akwasnie has quit IRC20:04
*** tzn has quit IRC21:08
*** tzn has joined #kolla21:15
*** tzn has quit IRC21:21
*** inc0 has quit IRC21:24
*** tzn has joined #kolla21:41
*** diogogmt has quit IRC21:57
*** sdake has quit IRC22:00
*** sdake has joined #kolla22:00
*** dwalsh has quit IRC22:04
*** rhallisey has quit IRC22:11
*** salv-orl_ has quit IRC22:15
*** gfidente|afk has quit IRC22:16
*** shardy has quit IRC22:33
*** Allen_Gao has quit IRC22:37
*** Allen_Gao has joined #kolla22:38
*** sacharya has quit IRC22:48
SamYapleok everyone. Here si the pull review. please have a look https://review.openstack.org/#/c/262846/23:02
SamYapleits passing gate and working23:02
SamYaplenotice the change to the tools/kolla-ansible specifically, its important23:03
*** blahRus1 has quit IRC23:04
*** sacharya has joined #kolla23:33
*** sacharya has quit IRC23:37
*** tzn has quit IRC23:45
*** yuanying has quit IRC23:50
*** yuanying has joined #kolla23:51

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