Tuesday, 2016-02-16

*** Kennan_Vacation is now known as Kennan00:03
*** dims has quit IRC00:04
*** cloudnau_ has joined #kolla00:05
sdakenot sure why fastestmirror was added back into the distro00:07
sdakeno bueno00:07
*** cloudnautique has quit IRC00:08
*** cloudnau_ has quit IRC00:10
*** dims has joined #kolla00:11
SamYaplesdake: something probably pulls it in as a dep00:12
sdakerebuilding00:12
sdakemay have been that pip imploded during build00:12
SamYapleinstead of cleaning every time i think centos should just not cache the packages sdake00:12
SamYaplein ubuntu we dont 'apt-get update' everytime00:12
SamYaplewith centos if packages change mid-build your build will be mixed packages00:13
SamYaplenot the case with ubuntu, i made sure of it00:13
sdakei'm not sure how to do that with yum00:13
sdakeapt is  a better tool then yum00:13
sdakethat is why there is this new fangled fedora thing for package managemenet00:14
SamYapleyou can do it with yum00:14
sdakeyou mean not do a cache clean each time?00:14
SamYaplehttp://linux.die.net/man/5/yum.conf00:14
SamYaplekeepcache 000:14
SamYapleyou shouldnt need to clean after that00:15
SamYaplei was thinking of doing that for apt as well00:15
sdakeyup that would be a big improvement00:15
SamYapleinstead of needing apt-clean00:15
SamYaplethough yum clean is way more invloved than apt-clean00:15
dave-mccowansdake INFO:__main__:keystone: yum-plugin-fastestmirror is needed by (installed) yum-3.4.3-132.el7.centos.0.1.noarch00:16
sdakerpm -e --nodeps00:16
dave-mccowansdake same error on httpd00:30
sdakedave-mccowan not sure what is going on with the centos mirros00:30
sdakebut i am reubilding atm00:30
sdakeand everything is bust00:31
sdakeprobably related to us buidling ;)00:31
sdakekolla puts alot of network pressure on the centos mirrors00:31
sdakedave-mccowan d_code this is for example why we can't make the gate voting until we have our own mirrors in openstack infra00:32
dave-mccowansdake no worries.  i'll try again in few hours.00:32
*** jtriley has quit IRC00:32
sdakedave-mccowan i find it odd that it is jus tthat one package00:33
sdakemust have recently updated00:33
sdakeminus the temporary impairment, kolla is looking pretty good00:34
*** salv-orl_ has quit IRC00:38
*** iceyao has joined #kolla00:41
*** iceyao has quit IRC00:41
*** Allen_Gao has joined #kolla00:45
SamYaplewe are close to making the ubuntu gate voting00:46
sdake1 > 000:47
*** aginwala has quit IRC00:51
*** iceyao has joined #kolla01:00
*** dims has quit IRC01:04
*** dims has joined #kolla01:08
*** iceyao_ has joined #kolla01:10
*** iceyao has quit IRC01:13
*** achanda has quit IRC01:13
sdakesamyaple would you mind rebasing https://review.openstack.org/#/c/276328/ so we can see if it goes through the gate properly once we get all this mess sorted out with the dev bindmounts?01:14
sdakeoh nm thats stable/liberty01:15
sdakeSamYaple the stable/liberty gate is currently passing all tests, can you rebase that patch now so we can see if your change passes the gate01:16
*** aginwala has joined #kolla01:17
*** achanda has joined #kolla01:17
*** achanda has quit IRC01:20
*** tzn has joined #kolla01:26
*** kejlly_ has quit IRC01:26
sdakeboy we got a whole lot of conflicting changes and a slew of review backlog01:39
sdakei'm off to dinner, enough fun for one day01:39
sdakebbl possibly01:39
*** Allen_Gao has quit IRC01:41
openstackgerritMerged openstack/kolla: Ensure that /var/lib/zookeeper is owned by user  https://review.openstack.org/28044501:41
*** Allen_Gao has joined #kolla01:41
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix nova tasks  https://review.openstack.org/28046401:42
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix nova group name in nova.conf.j2  https://review.openstack.org/28046501:42
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix glance-registry enable typo  https://review.openstack.org/28046601:42
*** tfukushima has joined #kolla01:50
*** Allen_Gao has quit IRC01:53
*** jasonsb has quit IRC01:56
*** jasonsb has joined #kolla01:57
*** tzn has quit IRC02:00
*** Allen_Gao has joined #kolla02:09
*** daneyon_ has quit IRC02:09
*** iceyao has joined #kolla02:15
*** iceyao_ has quit IRC02:17
*** rhallisey has quit IRC02:22
mandredave-mccowan, what's your docker storage backend? the issue you have is typically caused by an old aufs02:24
mandrehttps://github.com/docker/docker/issues/698002:24
d_codesdake: SamYaple: keepcache=0 doesn’t affect pulling latest package data02:25
d_codeSamYaple: yum actually enforces consistency…it’s transactional in that you can revert changes that occur with it02:25
d_codednf is really the next evolution of yum, and is more of a restructure, but the transactional nature of it stays02:26
d_codeif you want to install packages solely from whatever is in the local repo cache metadata, you use `yum --cacheonly install foo`02:27
d_codeprior to that you can do `yum makecache fast` and it will pull down all the repodata…I do this with Chef because chef will pull down all the metadata everytime, which takes forever02:27
dave-mccowanmandre aufs.  yes, that looks on point.02:28
d_codeSamYaple: the keepcache=0 effectively creates a local yum repo for all the packages you’ve downloaded. By default they are removed once the package is installed successfully (full transaction is complete) to save disk space02:28
dave-mccowanmandre solution is to use centos instead of ubuntu?02:29
mandredave-mccowan, no need to go that far, simply use a different storage backend02:30
mandrehttp://docs.openstack.org/developer/kolla/image-building.html#known-issues02:30
d_codeyou can also specify “metadata_expire” in yum.conf. It defaults to 90 minutes, in which case it shouldn’t download new package metadata02:30
mandredave-mccowan, I'm using devicemapper myself from a centos box provisioned with vagrant02:31
d_codesorry…yum is one of the reasons I left apt distributions…  as a developer, packager, and automated deployer…I find yum much more predictable …  could just be familiarity bias though…except the transactions…those have saved my life02:31
d_codeite…headed to bed…02:31
mandred_code, interesting we can potentially speed up build time by keeping yum metadata on the base image02:36
mandred_code, is there a way to tell yum not to keep downloaded packages around?02:37
dave-mccowanmandre thanks!  that did it.  DOCKER_OPTS="-s devicemapper"02:43
*** iceyao_ has joined #kolla02:46
*** iceyao has quit IRC02:50
mandredave-mccowan: np, glad you fixed it02:53
mandrewhat version of ubuntu are you using? was aufs the default backend?02:53
*** tzn has joined #kolla02:57
dave-mccowanmandre 14.04 with 3.16 kernel.  aufs was the default.02:58
*** salv-orlando has joined #kolla03:16
*** neophy has joined #kolla03:17
*** kexiaodong has joined #kolla03:18
*** aginwala has quit IRC03:19
*** Marga__ has joined #kolla03:20
*** Marga_ has quit IRC03:23
*** Marga__ has quit IRC03:25
*** salv-orlando has quit IRC03:28
*** tzn has quit IRC03:30
*** tfukushima has quit IRC03:33
*** dims has quit IRC03:37
*** aginwala has joined #kolla03:38
sdakeevening folks03:40
*** klint has joined #kolla03:41
*** chandankumar has joined #kolla03:41
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix glance-registry enable typo  https://review.openstack.org/28046603:41
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix nova group name in nova.conf.j2  https://review.openstack.org/28046503:41
*** archjun has joined #kolla04:00
mdnadeemsdake, good eve04:04
mdnadeemsdake, kolla deploy fail on TASK: [mariadb | Waiting for MariaDB service to be ready]04:05
mdnadeemwith error : Container mariadb is restarting, wait until the container is running04:05
mdnadeemdocker logs mariadb shows "/usr/bin/mysqld_safe: line 139: /var/lib/mysql//kolla.err: Permission denied"04:09
*** tzn has joined #kolla04:27
*** iceyao has joined #kolla04:44
*** dave-mccowan has quit IRC04:47
*** iceyao_ has quit IRC04:47
*** achanda has joined #kolla04:48
*** tzn has quit IRC05:00
*** subscope has joined #kolla05:09
*** jasonsb has quit IRC05:09
*** jasonsb_ has joined #kolla05:10
*** iceyao_ has joined #kolla05:12
*** iceyao has quit IRC05:16
*** iceyao has joined #kolla05:18
*** iceyao_ has quit IRC05:21
*** iceyao has quit IRC05:33
*** alisonh has quit IRC05:38
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Make Mesos resources configurable  https://review.openstack.org/28014405:43
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510905:43
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Remove bootstrap playbook for ZooKeeper  https://review.openstack.org/28050205:43
*** kjelly has joined #kolla05:45
*** coolsvap|away is now known as coolsvap05:56
*** iceyao has joined #kolla05:56
*** iceyao_ has joined #kolla05:57
*** tzn has joined #kolla05:57
*** iceyao_ has quit IRC05:58
*** iceyao__ has joined #kolla05:59
*** tfukushima has joined #kolla05:59
*** iceyao has quit IRC06:01
*** iceyao__ has quit IRC06:02
*** iceyao has joined #kolla06:02
*** alisonh has joined #kolla06:15
*** neophy has quit IRC06:15
*** tzn has quit IRC06:30
openstackgerritMD NADEEM proposed openstack/kolla: Aodh ubuntu binary container  https://review.openstack.org/28051506:32
*** cemason has joined #kolla06:32
*** subscope has quit IRC06:34
*** aginwala has quit IRC06:38
*** achanda has quit IRC06:39
*** salv-orlando has joined #kolla06:43
*** tzn has joined #kolla06:45
*** tzn has quit IRC06:45
*** alisonh has quit IRC06:45
*** tzn has joined #kolla06:46
*** salv-orlando has quit IRC06:46
*** alisonh has joined #kolla06:49
*** subscope has joined #kolla06:52
*** tzn has quit IRC06:55
*** subscope has quit IRC06:55
*** coolsvap is now known as coolsvap|away06:58
*** achanda has joined #kolla06:59
*** unicell has joined #kolla07:00
*** Marga_ has joined #kolla07:00
*** Marga__ has joined #kolla07:02
*** Marga_ has quit IRC07:02
*** Serlex has joined #kolla07:04
*** Liuqing has joined #kolla07:05
*** Marga__ has quit IRC07:06
*** Marga_ has joined #kolla07:06
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Make Mesos resources configurable  https://review.openstack.org/28014407:11
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510907:11
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Look for private interface lease  https://review.openstack.org/28052407:11
nihiliferasalkeld: if you are available, could you please look at these 2 commits? https://review.openstack.org/#/c/280502/ https://review.openstack.org/#/c/280524/07:13
nihiliferthe first one fixed mesos deployment at all (for docker 1.10)07:13
nihiliferthe second one fixes vagrant under ubuntu07:13
*** iceyao has quit IRC07:19
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Make Mesos resources configurable  https://review.openstack.org/28014407:20
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510907:20
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Look for private interface lease  https://review.openstack.org/28052407:20
*** iceyao has joined #kolla07:20
asalkelddone nihilifer07:27
nihiliferthx07:27
*** guillaume_ has quit IRC07:41
*** ravla has quit IRC07:45
*** ravla has joined #kolla07:46
*** tzn has joined #kolla07:50
*** fgimenez has joined #kolla07:59
*** chandankumar has quit IRC08:00
*** tfukushima has quit IRC08:03
*** coolsvap|away is now known as coolsvap08:09
*** unicell has quit IRC08:11
*** unicell has joined #kolla08:11
*** chandankumar has joined #kolla08:15
*** shardy has joined #kolla08:16
*** archjun has quit IRC08:17
*** tfukushima has joined #kolla08:17
*** mikelk has joined #kolla08:18
*** tzn has quit IRC08:19
*** tzn has joined #kolla08:20
*** subscope has joined #kolla08:21
*** chandankumar has quit IRC08:21
*** chandankumar has joined #kolla08:25
*** coolsvap is now known as coolsvap|away08:26
*** mikelk has quit IRC08:28
*** salv-orlando has joined #kolla08:30
*** salv-orlando has quit IRC08:32
*** tzn has quit IRC08:34
*** tzn has joined #kolla08:34
*** tzn has quit IRC08:34
*** archjun has joined #kolla08:39
*** mikelk has joined #kolla08:39
sdakemdnadeem thanks for the debug on that08:41
sdakemdnadeem can you please file a bug08:41
*** opennode has joined #kolla08:42
ajafoo/08:43
mdnadeemsdake, I am trying to do it freshly by deleting all container and its volumes, if it again produce then i will lodge a bug08:44
*** kproskurin has joined #kolla08:45
*** opennode has quit IRC08:45
*** athomas has joined #kolla08:45
*** subscope has quit IRC08:50
*** iceyao_ has joined #kolla08:51
mdnadeemajafo, hi08:51
mdnadeemajafo, Your yesterday issue get resolved?08:52
*** iceyao has quit IRC08:52
ajafomdnadeem: hi, yes08:53
mdnadeemajafo, cool, have you ever encounter this kind of issue : http://pastebin.com/cY6fVjrQ08:54
*** mbound has joined #kolla09:02
*** achanda has quit IRC09:03
*** subscope has joined #kolla09:04
openstackgerritAllen Gao proposed openstack/kolla: Keep consistent with others for ironic containers name  https://review.openstack.org/28055709:04
*** achanda has joined #kolla09:06
mdnadeemajafo, sdake , hi the above issue resolve , i just try it freshly by removing  containers and their volumes :)09:08
*** salv-orlando has joined #kolla09:08
*** pbourke has joined #kolla09:13
openstackgerritMerged openstack/kolla: A few silly grammar fixes.  https://review.openstack.org/28036309:15
*** pbourke has quit IRC09:18
*** macsz has joined #kolla09:19
*** achanda has quit IRC09:28
*** akwasnie has joined #kolla09:29
*** archjun has quit IRC09:29
ajafomdnadeem: for me it looks like you've two problems mysql can't access pid file and and can't get port09:30
ajafomy some old container is working or sthg like this?09:31
*** akscram has quit IRC09:33
mdnadeemajafo, Now the problem get resolved by applying work aorund >> removed mariadb container and its volume and again run sudo kolla-ansible deploy09:33
*** akscram has joined #kolla09:33
*** subscope has quit IRC09:40
*** Liuqing has quit IRC09:41
*** pbourke has joined #kolla09:47
*** subscope has joined #kolla09:47
*** tzn has joined #kolla09:49
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Add priviliged flag to nova-api  https://review.openstack.org/28057609:50
*** tzn has quit IRC09:51
*** tzn has joined #kolla09:51
*** pbourke has quit IRC09:54
*** pbourke has joined #kolla09:54
*** tzn has quit IRC09:59
*** tzn has joined #kolla10:01
*** mbound has quit IRC10:01
*** salv-orl_ has joined #kolla10:02
openstackgerritMerged openstack/kolla-mesos: Remove bootstrap playbook for ZooKeeper  https://review.openstack.org/28050210:03
openstackgerritMerged openstack/kolla-mesos: Look for private interface lease  https://review.openstack.org/28052410:03
*** salv-orlando has quit IRC10:05
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Make Mesos resources configurable  https://review.openstack.org/28014410:05
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510910:05
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Fix Chronos tasks cleanup  https://review.openstack.org/28058510:05
*** mbound has joined #kolla10:06
*** Liuqing has joined #kolla10:06
*** tfukushima has quit IRC10:11
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Make Mesos resources configurable  https://review.openstack.org/28014410:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Fix Chronos tasks cleanup  https://review.openstack.org/28058510:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510910:26
*** alyson_ has joined #kolla10:27
openstackgerritMarek Zawadzki proposed openstack/kolla: Added note about root permissions, removed sudos.  https://review.openstack.org/27853210:36
*** subscope has quit IRC10:47
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Fix glance registry conf path  https://review.openstack.org/28060010:49
*** dims has joined #kolla10:51
kproskurinGuys, neutron has “shared” volumes in agents: https://github.com/openstack/kolla/blob/master/ansible/roles/neutron/tasks/start.yml#L18410:53
kproskurinI cant find docker dockumentation about this “:shared” option - https://docs.docker.com/engine/userguide/containers/dockervolumes/10:53
kproskurinFrom there does it came from?10:54
nihiliferfrom 1.10 probably11:00
kproskurinWell, it doesnt work for me in 1.10 ;-\ and I cant find any docs about it.11:01
nihiliferhow it doesn't work?11:02
nihiliferor another question - you're doing this in mesos?11:02
kproskurinYes in mesos, it doesnt start containers with this :shared thing with “error 125”. I cant event find anything about this shared thingy here: https://github.com/docker/docker/releases/tag/v1.10.011:03
kproskurinUbuntu btw, this could be the case11:03
nihiliferkproskurin: does mesos-slave container have docker cli in 1.10 version?11:03
kproskurinyes11:03
nihiliferyou sure? when it was built?11:03
*** dave-mccowan has joined #kolla11:04
kproskurinhttp://fpaste.org/323411/45562071/11:05
nihiliferin /usr/lib/systemd/system/docker.service11:06
nihiliferyou shoud have11:06
nihiliferMountFlags=shared11:06
nihiliferyou have it?11:06
kproskurinubuntu 14.04 dosnt use systemd yet… iirc11:06
asalkeldalso make sure the docker in the mesos-slave is 1.10 too11:06
kproskurinoh wait. on mesos slave right?11:07
nihiliferyep11:07
nihiliferumm... nope :P11:07
nihilifersorry11:07
kproskurin%-)11:07
nihiliferi mean, shared in settings should be only on host11:07
nihiliferso, i don't know how to set the MountFlags in upstart11:07
kproskurinLooks like this is the case, ill dig how to set it up in ubuntu11:08
nihiliferbut that seems to be thing which should be done11:08
asalkeldkproskurin:https://github.com/openstack/kolla/blob/master/dev/vagrant/ubuntu-bootstrap.sh#L25-L3511:12
*** dims has quit IRC11:12
asalkeldthat's the ubuntu setup11:12
kproskurinit’s a bit strange one. Ubuntu 14.04 by default doesnt use systemd it even dosnt have systemd cli installed11:13
kproskurinbash: systemctl: command not found11:14
kproskurinImo it’s a bad copy paste :-)11:15
kproskurinfrom centos11:15
*** mbound has quit IRC11:15
*** tzn has quit IRC11:16
openstackgerritAllen Gao proposed openstack/kolla: Install python-dogpile-cache for python-ironicclient  https://review.openstack.org/28061511:18
*** subscope has joined #kolla11:18
openstackgerritMerged openstack/kolla-mesos: Fix Chronos tasks cleanup  https://review.openstack.org/28058511:19
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix nova tasks  https://review.openstack.org/28046411:19
*** mbound has joined #kolla11:20
*** dims has joined #kolla11:24
*** achanda has joined #kolla11:28
*** tzn has joined #kolla11:30
*** achanda has quit IRC11:34
ajafokproskurin: systemd is from 15.04 in ubuntu11:38
*** dims has quit IRC11:38
kproskurinI know11:38
*** akwasnie has quit IRC11:39
*** ccesario has quit IRC11:44
*** fgimenez has quit IRC11:48
*** fgimenez has joined #kolla11:50
*** akwasnie has joined #kolla12:01
*** sdake has quit IRC12:06
*** sdake has joined #kolla12:06
kproskurinGound the solution, not sure if it’s ok: mount --make-shared /run12:09
*** dwalsh has joined #kolla12:09
kproskurinpotentialy security risks, imo12:09
sdakehey folks12:10
sdakeanyone know how horizon produces the console in openstack12:10
sdakeis it via vnc?12:10
ajafohi sdake12:11
sdakehey ajao12:12
ajafoI suppose vnc or spice but I'm not sure12:12
*** dwalsh has quit IRC12:14
*** dwalsh has joined #kolla12:14
*** Jeffrey4l has quit IRC12:18
*** dwalsh has quit IRC12:19
Serlex"To provide a remote console or remote desktop access to guest virtual machines, use VNC or SPICE HTML5..."12:28
Serlexthats from the docs sdake12:28
sdakethanks serlax12:29
SerlexActually that was misleading12:30
Serlex"OpenStack Compute supports VNC consoles to guests. The VNC protocol is fairly limited" - " SPICE is a new protocol that aims to address the limitations in VNC and provide good remote desktop support"12:30
*** Jeffrey4l has joined #kolla12:31
*** ccesario has joined #kolla12:31
*** achanda has joined #kolla12:31
sdakeyup i know what spice is in detail12:33
sdakeworked with it in the past12:33
sdakeand vnc as well12:33
sdakei just wasn't sure if horizon used it for the console12:33
sdakei guess it must ;)12:33
*** ccesario has quit IRC12:36
*** achanda has quit IRC12:37
openstackgerritAllen Gao proposed openstack/kolla: WIP: Move ironic-discoverd to ironic-inspector  https://review.openstack.org/28065512:39
*** dwalsh has joined #kolla12:43
*** rhallisey has joined #kolla12:43
openstackgerritJeffrey Zhang proposed openstack/kolla: install the openstack-designate-api in the base stage  https://review.openstack.org/28065812:44
openstackgerritAllen Gao proposed openstack/kolla: Keep consistent with others for ironic containers name  https://review.openstack.org/28055712:55
*** chandankumar has quit IRC12:58
*** iceyao_ has quit IRC13:04
*** chandankumar has joined #kolla13:09
sdakeJeffrey4l quick question13:12
Jeffrey4lsdake, pong13:13
Jeffrey4lsup13:13
sdakeJeffrey4l we a a bunch of at risk items in mitaka-313:13
sdakethings that need to be i n the release that may need R&D attention13:13
limamauriciosdake, init-runonce is updated?13:14
sdakelimamauricio no, but we have a solution for the problem of the /dev bindmount ordering problem13:14
sdakelimamauricio if you care, its not a kolla problem, its a docker-py problem (docker-py doesn't maintain ordering)13:14
Jeffrey4lyea. I know the /dev bindmount issue.13:14
sdakeif you don't care, I can point you at the WIP patch13:14
*** chandankumar has quit IRC13:15
Jeffrey4lBut i have no idea how to fix this.13:15
sdakeJeffrey4l its fixed13:15
Jeffrey4ldocker can not support this case.13:15
sdakesam and i spent all day debugging it13:15
sdakeit can indeed support i t13:15
sdakedocker can do it on command line13:15
Jeffrey4lcool13:15
Jeffrey4lwhat's it?13:15
sdakethe problem is docker-py reorders13:15
sdakeit converts the volume list about 10 different times to lists and dicts etc13:16
sdakeall that conversion changes ordering13:16
limamauriciotools/init-runonce: line 49: neutron: command not found13:16
limamauricio:/13:16
sdakelimamauricio cool you got through a deploy13:16
sdakesudo pip install python-neutronclient13:16
Jeffrey4llimamauricio, you need install python-neutronclient13:16
limamauricio:)13:17
sdakeJeffrey4l can you work on the at risk items?13:17
limamauriciook13:17
Jeffrey4lsdake, fix the docker-py? push a PS?13:17
Jeffrey4lOr?13:17
sdakeJeffrey4l hang tight13:17
sdakehttps://etherpad.openstack.org/p/kolla-mitaka-midcycle-roadmap13:18
sdakeJeffrey4l if you want to work on something big impact, reconfigure playbooks would rock13:18
sdakeright now we have actions for deploy13:18
sdakewe need one for reconfigure13:18
sdakenobody is working on thi problem atm13:19
sdakewe have 3 weeks to sort this out13:19
limamauriciosdake, can init-runonce install neutronclient?13:19
Jeffrey4l(saw the midcycle discuss whole afternoon)13:19
sdakelimamauricio I prefer nt13:19
limamauriciohmm13:19
limamauriciook13:19
sdakelimamauricio we are working on a tool for centos atleast that configures a host for the first time13:19
sdaked_code has a centos script13:20
sdakemaybe it can be put in there, not sure13:20
sdakethat scriptis meant for the deploy targets, not the client nodes13:20
sdakehow I use my openstack environment is I install my clients on my macintosh laptop13:20
Jeffrey4lsdake, what's mean for "reconfigure services on a redeploy" any details?13:20
sdakeand keep a copy of init-runonce on my mac laptop13:20
sdakeand deploy to baremetal13:20
limamauriciook13:20
sdakeJeffrey4l you know how we have the deploy action ?13:21
Jeffrey4lyes13:21
sdakewe want a reconfigure action13:21
sdakeand we want kolla-ansible to be able to trigger it13:21
sdakekolla-ansible reconfigure13:21
Jeffrey4lchange the configure, then restart the service?13:21
Jeffrey4lGot it.13:21
sdakeroger13:21
sdakenot update the containers13:21
sdakenot pull the containers13:22
sdakei'd go with reconfig personally13:22
Jeffrey4lnp. I can handle this.13:22
sdakeeta? :)13:22
sdakei think we need a blueprint, let me check on that13:22
Jeffrey4lsdake, one week is enough? I think I can finish it befor the end of this week.13:23
sdakesounds fantastic13:23
Jeffrey4lsdake, let us back to the /dev bind mount issue?13:23
sdakegotta work correclty with copy once and copy always13:23
sdakeJeffrey4l that is solved13:23
Jeffrey4lsdake, could u explain more for me? what's the docker cli parameter can solve this/13:24
sdakeJeffrey4l if you want  to help out there, test SamYaple's patch in the review queue13:24
* Jeffrey4l is finding13:24
sdakeworking on finding the reconfig blueprint if ther eis one13:25
sdakemoment13:25
Jeffrey4lsdake, this one? https://review.openstack.org/#/c/280429/13:28
sdakeJeffrey4l yup thats it13:28
rhalliseysdake, does this mean copy_once functionality is being left as is?13:28
limamauriciosdake, my deploy kolla + manila + ceph ran perfectly13:28
limamauricio:)13:28
limamauricioAIO :)13:28
sdakerhallisey I assume Jeffrey4l is going to fix that ;)13:28
rhalliseyand the reconfigure action would replace what we talked would be confi_once13:28
sdakerhallisey these are actions in the playbooks13:29
sdakethe strategies don't change13:29
sdakewe still have copy_once and copy_always13:29
sdakethe problem with copy_once is as implemented, it doesn't match the spec, or atleast what I had in mind ;)13:29
rhalliseyso I suppose this goes hand in hand with copy_once then13:29
sdakeyes13:29
Jeffrey4lcopy_once should work as: do not copy if the the configuration file don't change, right?13:29
sdakerhallisey yes13:30
sdakeJeffrey4l let me think for a moment13:30
rhalliseyJeffrey4l, I don't think ansible can detect that13:30
rhalliseyoh wait13:30
sdakerhallisey it could13:30
rhalliseywe came up with a way13:30
Jeffrey4lit could13:30
sdakeJeffrey4l I think that would work, but at the moment the containers have a broad problem13:31
Jeffrey4lbut if so, the result of copy_once and copy_always will be the same?13:31
sdakethe result of copy_once and copy_always from the deployment host is supposed to be the same!13:31
Jeffrey4lOh sorry, i am wrong.13:31
sdakethe result of copy_once and copy_always from a deployment target is supposed to be different13:31
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Add neutron config  https://review.openstack.org/26510913:31
*** salv-orl_ has quit IRC13:32
Jeffrey4lsdake, yea, u are right.13:32
sdakewell I filed a bug on copy_once13:33
sdakenow cana't find it13:33
Jeffrey4lat the deployment stage, the copy_once and copy_always works the same like now. at the reconfiguration stage, the copy_once works like copy_always.13:33
sdakechecking email moment13:33
Jeffrey4lrhallisey, you asked a good question. thanks. :D13:35
rhalliseycopy_once = pick up config if there's a change copy_always = pick up config no matter what13:35
rhalliseyJeffrey4l, sure no problem.  We talked a bit about this at the midcycle so I figured I would bring up the same points13:36
*** salv-orlando has joined #kolla13:36
Jeffrey4lrhallisey, I do not think so. copy_once should mean pick up the only once.13:36
rhalliseyJeffrey4l, yes that's the way I see it too13:36
Jeffrey4lso which one is expected?13:37
rhallisey^^^ that is the way it's intended13:37
rhalliseysdake, can you clarify13:37
rhalliseyright now, copy_once literally is copy only one time13:37
SamYapleyo13:38
Jeffrey4lmorning SamYaple13:38
SamYaplemorning Jeffrey4l13:38
sdakeJeffrey4l copy_once is a misnomer13:38
rhalliseybut pretty sure when it came up first it was intended to be copy when config chages13:38
rhalliseySamYaple, hey13:38
sdakeit should probably b e called copy_immutable13:38
SamYaplerhallisey: no it was intended to be immutability13:38
SamYaplebut yea13:38
sdakerhallisey is correct13:38
SamYaplei dont think so13:39
SamYaplelook at the ansible spec13:39
sdakedid someone closee the bug i filed on this point?13:39
sdakeI can't find it13:39
rhalliseywhere's the original text! XD13:39
Jeffrey4lif rhallisey is right, the result of the copy_once and copy_always will be the same.13:39
rhalliseyJeffrey4l, yup13:39
sdakei put the original text in there, and basically said it was not implemented according to spec ;)13:39
SamYaplesdake: well youre wrong then. spec says it should work like it does13:40
Jeffrey4land meaningless to have two configure options.13:40
sdakewell I filed bug to clear it up13:40
SamYaplehttps://launchpad.net/bugs/154428713:40
openstackLaunchpad bug 1544287 in kolla-mesos "unable to launch containers, Unexpected Env format for 'ContainerConfig.Env'" [Critical,Confirmed]13:40
sdakeI guess I file another13:40
SamYapleignore that bug13:40
SamYaplerhallisey: https://github.com/openstack/kolla/blob/master/specs/ansible-multi.rst13:40
sdakebut i think someone closed it and i can't find it13:40
SamYaple"The major difference between these two models is that one offers immutability and single source of truth (CONFIG_OUTSIDE_COPY_ONCE)"13:40
sdakeright13:40
SamYapleCOPY_ONCE has always acted like the spec meant it to13:40
sdakeyou are leaving out the part where it says "reconfigurable"13:41
rhalliseyso I'm not arguing one way or another here just trying to understand the sides13:41
SamYaplesdake: thats because it doesnt say that13:41
rhalliseythe issue with copy_once is if you input the wrong config and your container restarts.  Now you can't get another conifg to replace it XD13:41
SamYaplerhallisey: yea you have to destroy container13:42
SamYaplethis is how ive always expected it to work based on that spec13:42
SamYapleits why i use COPY_ALWAYAS13:42
rhalliseywhich I'm fine with13:42
SamYapleCOPY_ONCE is awful13:42
sdakeThe CONFIG_OUTSIDE_COPY_ONCE model of configuration maintains the immutable and declarative nature of the Kolla containers, as defined by our current Kolla best practices while introducing completely customizable configuration.13:42
Jeffrey4ldoes reconfigure action could save u rhallisey13:42
sdakeyes clearly there was a misunderstanding in how copy_once was implemented13:42
sbezverkHello, are you aware of a traceback generated during kolla-build, http://paste.openstack.org/show/48710613:42
rhalliseyJeffrey4l, oh I use copy_always13:42
rhalliseyJeffrey4l, :)13:42
SamYaplesdake: i think your memory is being selective again. i can assure you this is what you wanted (i have logs)13:43
Jeffrey4lI will COPY_ALWAYS too. ;D13:43
rhalliseyJeffrey4l, reconfig would work, but I think it would break the intention of copy_once13:43
SamYaplerhallisey: no because it would recreate teh container13:43
SamYapleso it would be a new container13:43
sdakeok guys lets focus on the future here13:43
SamYapleso immutability works13:43
sdakewho gives a shit what happened i n the past13:43
SamYapleim pointing out this is how everyone expected it to work13:44
rhalliseysee I was under the impression it would reload configs and restart13:44
SamYaplei said it was a bad idea but meh13:44
rhalliseybut true, it could replace13:44
SamYaplereload on restart would be COPY_ALWAYS though, no?13:44
sdakewhat *I* want with copy_once is for on a config change on the master node, the configs to be reloaded13:44
sdakebut if a config change on the non-master nodes happen, I dont want a configs tobe reloaded13:45
SamYapleyou mean the containers recreated?13:45
sdakeright recreated13:45
sdakecall that what you want13:45
sdakecopy_ocne13:45
sdakecopy_immutable seems better13:45
*** fgimenez has quit IRC13:45
SamYaplewell thats fine, we just need playbooks for that13:45
SamYapleit was a point at the kolla metting13:45
*** dims has joined #kolla13:45
sdakethat is single source of truth with immutability13:46
SamYapleso at this point in time, COPY_ALWAYS would need a restart/nohup, COPY_ONCE would require a recreate13:46
SamYapleplaybooks can handle that13:46
sdakethat seems good13:46
rhalliseyperfect13:46
sdakeI did file a bug here defining the intentions of copy_once once I found out its a pile of shit as is :)13:46
sdakebut it has disappared13:46
SamYapleyup this is what I thought we agreed to at the midcycle (and original ansible spec), sorry if it wasny made clear13:46
sdakeoh13:47
sdakebingo13:47
sdakeplaybooks don't recreate atm13:47
*** fgimenez has joined #kolla13:47
SamYaplethats teh one13:48
SamYaplethey only recreate if image/container meta changes13:48
SamYaplenot openstack configs13:48
SamYapleto reload configs without COPY_ALWAYS requires nuking container and running playbooks again as it always has13:48
sdakeso this can all be rolled into the reconfig action13:48
SamYapleyup13:48
sdakecool13:49
Jeffrey4lclearly.13:49
rhallisey:D13:49
sdakeJeffrey4l did you catch all that?13:50
sdakeJeffrey4l filing blueprint now, so you have something to work with13:51
*** dims has quit IRC13:51
d_codesdake: my script installs neutron client13:51
*** subscope has quit IRC13:53
Jeffrey4lsdake, yea.13:54
openstackgerritSam Yaple proposed openstack/kolla: Make a final check to validate mysql works  https://review.openstack.org/27685113:54
openstackgerritMerged openstack/kolla: Install python-dogpile-cache for python-ironicclient  https://review.openstack.org/28061513:57
Jeffrey4lSamYaple, sdake it the /dev bindmount ordering problem is this https://bugs.launchpad.net/kolla/+bug/1544156 ?13:57
openstackLaunchpad bug 1544156 in kolla "Kolla does not survive reboots" [Undecided,New]13:57
sdakeunforutnately nobody has filed a bug yet13:58
sdakebut the patch appears to work for several people13:58
sdakelimamauricio in particular says it works13:58
sdakei am stuck on NAT + virtualbox not giving me a free VIp to work with13:59
SamYapleJeffrey4l: no _however_ my bind mount fixes that :D13:59
sdakebut will get to that this morning after the school rush finishes13:59
SamYapleor at least greatly reduces that problem13:59
SamYapleJeffrey4l: https://review.openstack.org/28061513:59
limamauriciosdake: i'm testing my deploy13:59
openstackgerritMerged openstack/kolla: Added note about root permissions, removed sudos.  https://review.openstack.org/27853213:59
Jeffrey4lsdake, try use virtio-net adapter14:00
openstackgerritAllen Gao proposed openstack/kolla: WIP: Move ironic-discoverd to ironic-inspector  https://review.openstack.org/28065514:01
sdakeJeffrey4l https://blueprints.launchpad.net/kolla/+spec/kolla-reconfig14:01
Jeffrey4lsdake, roger14:01
sdakeJeffrey4l I am on a mac14:01
sdakeall my linux gear is in the garage atm14:02
*** klint has quit IRC14:02
sdakeand my remodel is stalled on upstream ;)14:02
sdakecircular dependency there14:02
SamYapleJeffrey4l: lets get an initial patch worked out for something like keystone for the reconfigure14:02
SamYaplemake sure everyone agrees on implementation14:02
SamYapleonce base is done it will be simple to throw up the rest14:03
sdakeJeffrey4l ya start with one14:03
Jeffrey4lSamYaple, np14:03
Jeffrey4lSamYaple, really do not think You PS can reduce this. Anyway, i will make some test later.14:04
sdakeok folks I gotta jet for an hour to take my kids to school14:06
sdakeposibly 1.5 hours14:06
sdakeschool madness ftw!14:06
*** salv-orlando has quit IRC14:08
*** ccesario has joined #kolla14:08
SamYaplefor all of those with the kolla_toolbox issue, please try this patch and comment on it. 0914:13
SamYaplehttps://review.openstack.org/#/c/280429/14:13
SamYapleits marked WIP because I can't validate it fixes the issue since i dont have that issue, but it works on ubuntu source14:14
SamYapleits a much cleaner implem,entation too14:14
SamYaplerhallisey: Jeffrey4l mandre pbourke ^^14:14
SamYaplepbourke: a reboot did _not_ fix this toolbox issue for most people like it did for me that night14:14
Jeffrey4lroger14:16
sbezverkSamYaple, after your diff kolla_toolbox needs to be rebuilt?14:18
SamYaplesbezverk: correct14:19
SamYapletechinically the playbooks run without a rebuild, but you wont have logging14:19
SamYapleopenstack will work though14:19
*** subscope has joined #kolla14:22
sbezverkSamYaple I also see a traceback almost everytime when run kolla-build, are you aware of this issue?14:23
SamYaplewhat traceback?14:23
SamYaple(pastebin please)14:24
sbezverkSamYaple this one: http://paste.openstack.org/show/48710614:24
SamYaplesbezverk: i dont think anyone has seen that before14:24
SamYaplewhat version of docker and docker-yp14:24
SamYaple?14:24
sbezverkSamYaple Docker 1.10.114:25
sbezverkVersion: 1.7.014:25
sbezverkfor Docker-py14:25
SamYaplehmmm14:26
SamYaplehost os?14:26
sbezverkcentos 7.214:26
sdakesbezverk are you pushing to a registry?14:26
sbezverksdake yes14:26
sdakedo you ahve the insecure registry flag set?14:26
sdakeps -ef | grep docker14:27
SamYaplesdake: that flag isnt used for registry v214:27
sdakeoh really?14:27
SerlexThis is strange. I had neutron-dhcp-agent failure, I ran it again and now it works14:27
SamYapleand 1.10 doesnt work with v114:27
sdakeyes I know that14:27
sdakebut didn't know insecure registry was a 1.0 only flag14:27
sbezverksdake http://paste.fedoraproject.org/323493/3284614514:27
SamYaplesdake: hmm ill double check that14:27
sdakesbezverk ok the problem is your using registry 1.014:28
SamYaplethey deprecated the docker-py insecure flag14:28
sdakesbezverk registry 1.0 is not compatible with docker 1.1014:28
sdakeyou need registry 2.314:28
sbezverksdake what are my options then? new master required 1.10.1 based on yesterday's discussions..14:28
sdakesbezverk uninstall docker registry rpm14:29
sdakethen run14:29
sdakedocker run -d -p 4000:5000 --restart=always --name registry registry:2:314:29
sdakethen proceed as normal14:29
sdakedoc fix incoming today for  that14:29
sbezverkgot it thank you14:29
*** athomas has quit IRC14:29
SamYapleyou know it wasn't blocked by the docker team14:29
SamYapleso v1 registry not working would be a bug for you guys14:29
sdakewell registery 2.3 is far superiorr in terms of perf why not just use that?14:30
sdakeregistry 1 is unmaintained14:30
SamYapleits not faster than v1 by much14:30
SamYaplebut im not advocating for it14:30
SamYaplejust saying its not a hard switch14:31
sdakei see14:31
sdakei thought it was cmopletely disabled because i t didn't work for me with master ;-)14:31
sdakeso that sounds like a docker bug14:31
sdakeanyway have to jet for a bit14:31
sdaketo drive kiddo to school14:31
SamYapleyea pushing to v1 registry works for me14:33
SamYaplemight be busted in docker-py.... but thats still a bug14:33
SamYapledocker daemon still allows push14:33
*** achanda has joined #kolla14:35
Serlexsdake, any ideas how kolla deploy worked in second run after failing on neutron-dhcp-agent failure14:35
Serlexvery strange14:35
SerlexHorizon doesn't seem to respond though14:36
SamYapleSerlex: what was the time between run?14:36
Serlex3 days14:36
SamYapledhcp failures are associated with not having the MountFlags=shared with the docker daemon14:36
SerlexI gave up about 3 days ago, I thought I do some kolla tinkering today, and it worked -_-14:37
*** jtriley has joined #kolla14:37
Serlexoh! that says it then. I just changed that after reading the conversation on here14:37
Serlexthanks SamYaple14:38
SerlexI made the change blindly lol14:38
SamYapleSerlex: always good to trust the random internet people14:39
*** achanda has quit IRC14:40
*** athomas has joined #kolla14:41
sdakeSerlex was afk ad going afk for about an hour - looks like your sorted14:42
limamauricio2016-02-15 18:30:09.932 22 INFO cinder.volume.manager [req-ae123e1a-2b66-4f2a-9257-83d1a65ed216 - - - - -] Starting volume driver RBDDriver (1.2.0) 2016-02-15 18:30:09.933 22 ERROR cinder.volume.manager [req-ae123e1a-2b66-4f2a-9257-83d1a65ed216 - - - - -] Failed to initialize driver.14:42
limamauricioenable_ceph: "yes"14:43
limamauricio VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: rados and rbd python libraries not found14:44
openstackgerritSam Yaple proposed openstack/kolla: Move socket binding to named_volume  https://review.openstack.org/28042914:44
SamYaplelimamauricio: is this on master?14:44
limamauricioyes14:44
openstackgerritJeffrey Zhang proposed openstack/kolla: also remove the volumes when cleaning up containers  https://review.openstack.org/28072214:45
SamYaplelimamauricio: ubuntu/centos?14:45
limamauriciocentos14:45
limamauriciosource14:45
limamauricioAIO14:45
SamYaplelimamauricio: can fixing it now14:45
SamYapleok*14:45
limamauriciothis is a known bug?14:46
openstackgerritSam Yaple proposed openstack/kolla: Fix missing ceph-common package in cinder  https://review.openstack.org/28073814:47
SamYaplelimamauricio: it is now. thats teh fix14:47
SamYaplei dont test centos so i could not have caught that before limamauricio14:47
SamYaplei guess no one has done centos + ceph + source14:47
limamauricio then I'm the guy ;P14:48
SamYapleiwannabetheguy14:49
limamauriciook, you can be the guy14:50
SamYaplelol its a game14:50
SamYaplea very hard game14:50
*** jtriley has quit IRC14:52
SamYapleJeffrey4l: could you help me with a review here? I need this to finish out the "functional" gate work https://review.openstack.org/28073814:56
Jeffrey4lSamYaple, np14:56
* Jeffrey4l is checking14:56
SamYapleif we are ok with this approach I can move on14:57
*** coolsvap|away has quit IRC14:57
Jeffrey4lSamYaple, reviewed +214:59
*** subscope has quit IRC14:59
mkodererlimamauricio: pls let me know if you need help with testing https://review.openstack.org/#/c/269688/14:59
*** chandankumar has joined #kolla14:59
*** jtriley has joined #kolla15:01
*** coolsvap|away has joined #kolla15:01
SamYapleJeffrey4l: did you submit the review? or are you just letting me know?15:01
Jeffrey4lSamYaple, just let you know :D15:02
SamYaplecool15:03
openstackgerritSam Yaple proposed openstack/kolla: Reduce gate resource usage  https://review.openstack.org/28002915:05
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074915:05
Jeffrey4lSamYaple, I tested serveral times for your rsyslog named volume socket PS. it seem that the issue is really fixed (or at least reduced). But I still have no idea why? could you show the magic?15:05
SamYapleJeffrey4l: i moved the socket into a named_volume15:05
SamYaplethe issue before (I think) is a mount ordering issue from docker-py to docker15:06
*** subscope has joined #kolla15:06
SamYapleso _sometimes_ /dev/log would try to bind in before /dev15:06
Jeffrey4lI saw that. But I think use a named_volume and mount a host folder should be the same.15:06
SamYapleno because look at base/start.sh15:06
SamYaplewe dont bind to /dev/log15:07
SamYaplewe symlink after the contaienr starts15:07
Jeffrey4lOK. got it.15:07
Serlexsomeone help me get horizon working so I can call this successful kolla AIO deployment :D15:08
Jeffrey4lSerlex, error message?15:08
SamYapleSerlex: sure an particular issue?15:09
SamYaplenot deploying?15:09
SamYaplenot building?15:09
Serlex"The connection was reset" via the browser. Horizon container /var/log/http/error_log15:09
Serlex[Tue Feb 16 15:00:53.535568 2016] [auth_digest:notice] [pid 1] AH01757: generating secret for digest authentication ...15:09
Serlex[Tue Feb 16 15:00:53.536990 2016] [lbmethod_heartbeat:notice] [pid 1] AH02282: No slotmem from mod_heartmonitor15:09
Serlex[Tue Feb 16 15:00:53.551720 2016] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.6 () mod_wsgi/3.4 Python/2.7.5 configured -- resuming normal operations15:09
Serlex[Tue Feb 16 15:00:53.551766 2016] [core:notice] [pid 1] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'15:09
SerlexBuilt, deployed15:09
Serlexmore openstack problem than kolla i guess15:10
Serlexor misconfigured networking15:10
Jeffrey4l(use a paste service pls, paste.openstack.org)15:10
Serlexsure15:10
Serlexhttp://pastebin.com/34uBffNQ15:11
SerlexI ran a tcpdump and I can see the HTTP requests coming in15:11
SamYapleSerlex: i do not see this issue on ubuntu15:11
SamYapleill let Jeffrey4l help you out15:11
Serlexbrowser request times out after couple minutes15:11
SerlexI probably did something wrong15:11
SamYapleits hard to mess up this stage of kolla15:11
SamYapleif the other stuff works, its probably not you15:12
*** fgimenez has quit IRC15:12
Jeffrey4lSerlex, try use `nova list` on the host15:12
Jeffrey4ltest other service is ok.15:12
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074915:12
openstackgerritSam Yaple proposed openstack/kolla: Reduce gate resource usage  https://review.openstack.org/28002915:12
sdakeI was thinking - we should limit enabled by default services to basically compute kit15:13
sdakewhich heat is not in15:13
sdakeany thoughts?15:13
SamYaplei agree with no heat, i think horizon is needed15:13
sdakegotta run my kids to school15:13
SamYapleheat doesnt fully work15:13
sdakewhich part is broken?15:14
SamYaplewhen it does it needs ceilometer15:14
sdaketrusts still busted?15:14
SamYapleyou never merged it...15:14
sdakeI never wrote it, nihilifer did15:14
sdakei am pretty sure nihilifer fixed that problem15:14
SamYapleok its got enough cores ill merge15:14
*** fgimenez has joined #kolla15:14
*** fgimenez has quit IRC15:14
*** fgimenez has joined #kolla15:14
sdakeya we shouldn't be single threading on anyone in the community especially me :)15:15
SamYapleyou specifically asked for this15:15
SamYapleI rebased this for you sdake http://pastebin.com/34uBffNQ15:15
SamYapleoops15:15
SamYaplehttps://review.openstack.org/#/c/276851/15:15
SamYapleso please remove -1 when you get a chance15:16
sdakedone and w+115:16
sdakethanks again15:16
SamYapleanytime15:16
openstackgerritMerged openstack/kolla: Use trusts in heat.conf  https://review.openstack.org/23619815:16
sdakefolks, if you ahve patches awaiting review and they have gate failures, please rebase them on master so they will recheck15:17
sdakeit takes a long ime to leave a comment in every patch just for that15:17
SamYapleof note- centos binary will still fail on designate15:18
SamYaplejeffrey has a fix for that15:18
*** blahRus has joined #kolla15:18
sdakethe only gate that should be failing is build-centos-binary15:18
sdakeSamYaple have pointer to review?15:18
SamYaple28065815:18
openstackgerritMerged openstack/kolla: Make a final check to validate mysql works  https://review.openstack.org/27685115:18
SamYaplehttps://review.openstack.org/#/c/280658/15:18
Serlexrunning nova-list15:18
sdakethanks SamYaple thanks Jeffrey4l15:19
sdakeok folks wait for that patch to merge15:19
sdakethen please rebase15:19
sdakei'll send a note to the list15:19
sdakemany notes coming to the list today ;)15:19
sdakeafter I get done dealing with school15:19
sdakebbiaf15:19
sdakeSamYaple odd how the original code installed designate-api in the base image, and someone otok it out, with that big comment above15:20
sdakebbiaf15:20
openstackgerritMerged openstack/kolla: install the openstack-designate-api in the base stage  https://review.openstack.org/28065815:20
*** Liuqing has quit IRC15:21
*** Liuqing has joined #kolla15:22
*** Liuqing has quit IRC15:22
Serlexnova list on a AIO should be fairly quick right?15:23
SamYapleSerlex: it should be quick everywhere15:24
SamYaplebut if its hanging there could be any number of reasons15:24
SamYapleits probably an issue with kolla, but it could be swpaping or a slow system15:24
sdakeSerlex make sure your VIP is an unused IP address on your network15:25
sdakeSerlex if not, kolla will behave exactly as you describe - nova-list being pokey15:25
sdakeor not working15:25
Jeffrey4lSerlex, try `keystone --debug user-list` first, and check why it is blocked.15:26
Jeffrey4ls/why/where/15:26
sdakeserlex docker ps | fpaste15:26
Serlexok one sec15:26
sdakeserlex lets see if all yourcontainers are running15:26
sdakeok really gotta jet15:26
Serlexall but toolbox15:26
sdaketoolbox not running?15:27
sdakedocker logs the toolbox id15:27
Serlexlooks like exited15:27
sdakeit should not exit15:27
Serlexguessing thats bit crucial15:27
Jeffrey4ltoolbox is not big deal. Shoul exit due to the `/dev/log` issue.15:27
sdakegotta go15:27
Serlexok cya15:28
Serlexhttp://pastebin.com/48ffjwkG15:28
Jeffrey4lneutron-openvswitch-agent is restarting.15:28
Serlex"keystone --debug user-list" is showing its trying to connect to proxy im behind off15:28
Jeffrey4lneutron-openvswitch-agent should not be the current issue, too.15:29
Jeffrey4ltry to fix the proxy issue first.15:29
Serlexsure15:29
Jeffrey4lshould remove the proxy?15:29
SerlexI will try without15:29
SerlexDEBUG:keystoneclient.session:Request returned failure status: 40415:36
Jeffrey4lSerlex, more info?15:37
Serlexhmm I don't think my openrc is misconfigured15:37
Serlexsorry that was the output from keystone user-list - http://pastebin.com/AfBTVpii15:38
limamauriciomkoderer: I'll update the patch15:38
limamauricioand you can try to deploy it and create a share :)15:38
SerlexI can see via netsat 10.0.3.17:35357 is listening15:39
*** salv-orl_ has joined #kolla15:40
*** salv-orl_ has quit IRC15:40
*** salv-orlando has joined #kolla15:41
Jeffrey4lSerlex, it should be right. the keystoneclient (i think) should not handle the new type endpoint ( without version ) properly.15:41
Jeffrey4lwait for a moment. Or just try `openstack --debug user list`15:42
SerlexI got a success with openstack --debug user list15:43
Jeffrey4lSerlex, great. Try `openstack --debug server list`15:44
Jeffrey4lI think your root cause is the proxy. After removed that, you can try the dashboard again now.15:45
Serlex"IndexError: list index out of range" for server list15:45
SerlexI can see neutron openswiitch-agent container is in restarting state again15:46
Serlexlogs show15:46
Serlex"2016-02-16 15:43:30.915 1 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-7b980d98-1b95-43b8-b624-ac7f8438cc02 - - - - -] Bridge br-ex for physical network physnet1 does not exist. Agent terminated!"15:46
SerlexI will try dashboard again15:46
Jeffrey4lare you using the latest code? this br-ex issue should be fixed now. Serlex15:47
Serlexoh - no I'm not15:47
Serlexwoops15:47
SerlexBut would that stop dashboard from appearing?15:48
Jeffrey4lSerlex, no.15:48
Jeffrey4lIt just break the boot vms.15:48
SerlexAH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message15:48
*** guillaume_ has joined #kolla15:49
Jeffrey4lthis is not a issue.15:49
*** dave-mccowan has quit IRC15:53
SamYapleJeffrey4l: with the logging patch, im not sure what you are saying15:54
SamYapleits probably still waiting on the socket to appear15:55
Jeffrey4lA simple test, run `logger a` in kolla_toolbox container. this message will be received by the host rsyslog rather than the rsyslog container.15:56
Jeffrey4lSamYaple, ^15:56
SamYaplei think you miss my point15:57
SamYaplecheck whats running in keystone container15:57
SamYapleits probably looping waiting for socket to appear, no15:57
SamYapleunless you didnt do a full rebuild of your containers15:57
SamYapleand then logging just wont work15:57
sbezverkSamYaple your fix seems helping with kolla-toolbox, at least it was created and started properly15:57
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968815:58
sbezverkbut I hit an issue with neutron-dhcp-agent, the container was created but by some reason it has not started..15:58
Jeffrey4lSamYaple, keystone container works. Because it doesn't mount the host `/dev` folder.15:58
Jeffrey4lkolla_toolbox mount the `/dev/` folder and the `/dev/log` file is the hosts.15:59
sbezverkSamYaple when I try to start it manually I get this error: Error response from daemon: Cannot start container 7d273c63087cad3be5d51f023c568072f12e55967ead661e804b2a6354bd7358: Path /run/netns is mounted on /run but it is not a shared mount.15:59
Serlexsbezvek I think that was solved with shared MountFlags in docker.service16:00
SerlexMountFlags=shared16:00
SerlexJeffrey4l16:00
*** akwasnie has quit IRC16:00
SerlexI'm not sure what is stopping horizon, something isn't right, probably network issue16:00
Jeffrey4lSerlex, what's the error now?16:01
sbezverkSerlex Thank you, so I change it and restart docker, right?16:01
Serlexhorizon times out in browser still16:01
Jeffrey4ltry to use a curl command to test ` curl <ip>:80 -vvvv`16:02
Jeffrey4lstill the proxy issue?16:02
Serlexnot proxy16:02
*** salv-orl_ has joined #kolla16:02
Serlex keystone --debug user-list is given me 40416:02
Jeffrey4lare u sure the proxy is removed totally? include the environments in the containers.16:03
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968816:03
Jeffrey4lSerlex, does `nova list` works?16:03
SerlexI've checked various places, I've only added it to .bash_profile today to have a look at kolla at work16:04
Serlexermm16:04
Serlexit does now16:04
Serlexbut its empty16:04
Serlex:-/16:05
*** salv-orlando has quit IRC16:05
Jeffrey4lSerlex, try `curl <ip>:80 -vvv`16:05
*** jmccarthy has quit IRC16:05
*** haplo37 has joined #kolla16:06
Serlex* Connected to 10.0.3.17 (10.0.3.17) port 80 (#0)16:06
Serlexhmm16:06
*** jmccarthy has joined #kolla16:06
SerlexThanks for the help Jeffrey4l, I got to go16:07
SerlexI will give it a go again later16:07
SamYapleJeffrey4l: Oh so you are saying the other containers work, just not the ones mounting /dev16:07
Jeffrey4lSerlex, root cause is?16:07
SamYaple?16:07
Jeffrey4lSamYaple, yup16:07
*** inc0 has joined #kolla16:08
SamYaplewe may have to live with that until heka16:08
Jeffrey4lSamYaple, wait a minute. I think it should, but not tested.16:08
SamYaplei made a note in there16:08
inc0hey, good morning16:08
SamYapleJeffrey4l: with heka we don't need ot bind over /dev/log16:08
SamYaplemorning inc016:08
Jeffrey4lSamYaple, yea.16:08
Jeffrey4linc0, morning16:08
inc0SamYaple, yesterdays weather made us spend night in Dallas16:09
SamYapleinc0: ouch16:09
*** stvnoyes has quit IRC16:09
SamYapleback home now?16:09
*** Serlex has quit IRC16:09
inc0yeah, we arrived like an hour ago16:09
*** stvnoyes has joined #kolla16:10
SamYapleman that explains why you didnt respond to my messages16:10
inc0what messages?16:10
inc0I didn't get any16:11
SamYaplei asked if you arrived16:11
SamYapleon signal16:11
inc0did not recieve.16:11
SamYaplehmm16:11
SamYaplewierd16:11
SamYaplesignal has never been flaky for us before...16:12
inc0anyway, you have your answer now;)16:12
inc0good thing tho that american airlines gave us hotel16:12
inc0so we didn't have to sleep on airport16:12
*** dave-mccowan has joined #kolla16:12
inc0sdake, around?16:13
*** Marga_ has quit IRC16:13
SamYapleyea16:13
*** JoseMello has joined #kolla16:13
SamYapleJeffrey4l: looking at the Heka stuff... that should work16:14
SamYapleanything requiring /dev/log (haproxy/mariadb) can specifcy an alternate log location16:15
SamYapleand the openstack services write to files16:15
Jeffrey4lok16:16
inc0SamYaple, did you figute out what was wrong with docker 1.10?16:16
SamYapleinc0: nothing with docker 1.1016:16
SamYapleit *appears* that somewhere in the kolla_docker->docker-py->docker stack the mounts are getting reordered16:16
SamYapleso /dev/log tries to mount before /dev16:17
inc0meh, thats strange16:17
inc0let me see one thing16:17
SamYaplesince the process for the binds is a conersation from string>list>dict>string>list>dict>rest-api it doesnt suprise me16:17
sbezverkDo not beleive my eyes, deployment has been completed sucessfully :-)16:17
SamYaplethats the path it takes from the yaml to the docker-egine inc016:18
SamYaplesbezverk: horizon and booting vm?16:18
inc0and dict in between messes up ordering I'd bet16:18
SamYapleinc0: we already attempted an ordereddict fix16:18
sbezverkSamYaple Horizon is up16:18
SamYaplein both docker-py and kolla_docker16:18
SamYaplei confirmed it still doesnt break for me with a non-ordereddict16:18
sbezverknetworking config does not look right16:18
SamYaplesbezverk: well youre getting there16:19
sbezverkbut it is minor16:19
*** cloudnautique has joined #kolla16:19
*** cloudnautique has quit IRC16:19
*** cloudnautique has joined #kolla16:20
sbezverkSamYaple, normally for AIO you do not create br-ex and you plug "external" interface directly to br-int16:20
SamYaplesbezverk: thats not normal, no16:21
SamYapleyou _can_ do that I suppose...16:21
sbezverkSamYaple :-) believe me it is, I have done about 100 all in one, and it is the only way to get connectivity16:21
SamYaplethat doesnt make it normal16:22
SamYapleI have done 100's as well and never done that16:22
SamYapledoing it that way prevents scaling to multinode, prevents testing vlan16:22
SamYapleprevents alot actually16:23
d_codesdake: so…still have plenty of things to work on…but I’ve got networking up, provisioned a couple of boxes….  no avc denials at all on CentOS16:23
d_codeI wonder if the new docker selinux package addressed many of the things16:23
*** fgimenez has quit IRC16:24
sbezverkSamYaple I will try to get connectivity with current setup built by kolla-deploy if it does not work I will ping you for suggestions16:24
SamYaplesbezverk: for a single interface deploy it can get complicated16:24
SamYapleis that what you are doign?16:24
sbezverkSamYaple, nope I have 1 interface "external" mapped to routable vlan, 2nd interface is 8021q trunk used for tennats and 3rd interface is management interface16:26
*** fgimenez has joined #kolla16:26
*** fgimenez has quit IRC16:26
*** fgimenez has joined #kolla16:26
*** daneyon has joined #kolla16:27
SamYaplesbezverk: then im confused as to the issue16:30
SamYapledo you have an ip that you use on your "external" interface?16:30
SamYapleif its just L2 then you can create a br-ex without issue16:30
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074916:33
sbezverkSamYaple If you check Red Hat packstack for opensatck installation, when AIO is selected br-ex is not getting created, so I do not know whether it is "normal" or not but it is how we were advised by RH since havana..16:34
SamYaplesbezverk: but see thats different than what you said16:36
limamauricioSam,  ERROR cinder.backup.manager [req-dcc698ac-678e-40da-9b01-1f44799a0f9f - - - - -] Error encountered during initialization of driver: RBDDriver16:36
SamYaplebut i am not talking about those dev tools16:36
limamauriciocinder_backup logs16:36
SamYaplethis is meant for production grade stuff and AIO is the same as multinode16:36
SamYaplethe br-ex stuff is required for neutron-l3-agent only16:37
limamauricioI did your patch, and cinder_volume is ok16:37
limamauricio:)16:37
SamYaplelimamauricio: so cinder-backup has issue though...16:37
SamYaplewhats the full past for that limamauricio ?16:38
*** achanda has joined #kolla16:38
SamYaplesbezverk: what is it you are looking to get out of Kolla in this case? as it stands we need br-ex for external communication for vms, even on multinode. that likely wont change16:39
limamauricioSamYaple -> http://pastebin.com/mk4LbVji16:39
SamYaplewe can scale from AIO to multinode to production multinode and back down to AIO with the system we have, and that means br-ex has to be there even in AIO16:39
*** dwalsh has quit IRC16:39
SamYaplelimamauricio: I found it16:40
SamYapleill fix it, moment16:40
sbezverkSamYaple it is ok, if it works the way kolla deploy builds is it is perfectly fine.., but I wan to change some neutron parameters , to activate them I just restart neutron server container? I selected COPY_ALWAYS in globals.yml16:40
limamauricioOk16:40
SamYaplesbezverk: yes16:42
openstackgerritSam Yaple proposed openstack/kolla: Use "optional" for ceph confs  https://review.openstack.org/28080816:42
SamYaplelimamauricio: test that out16:42
SamYaplecinder-backup was broken for all it would appear :)16:42
sbezverkSamYaple if I need to add a custom neutron plugin, example sriov, any guidance how to accomplish it?16:42
SamYaplewe do not have a plugin architecture thats fully flushed out yet sbezverk16:43
SamYapleright now they would have to be build into the containers16:43
sbezverkSamYaple :-(16:43
SamYaplebuilt*16:43
SamYapleso we can do plugins, but it requires rebuilds16:43
limamauricioThank Sam16:43
*** achanda has quit IRC16:44
*** dwalsh has joined #kolla16:45
SamYaplesbezverk: im afraid you may have taken that the wrong way, we _do_ have plugins, but you have to rebuild the container with a different conf rather than just start a new container16:46
SamYaplei use sr-iov myself16:46
sdakeback in16:49
sbezverkSamYaple, I see great, would you have a wiki or some steps tp build custom container? By some reason I could not find where ovs maps physical server interfaces to ovs bridges.. normally it would be sitting openvswitch-neutron-agent.ini16:49
*** dwalsh has quit IRC16:50
*** tzn has quit IRC16:50
inc0sdake, just came back from SC, did you ask people about backporting thin containers?16:51
*** ssurana has joined #kolla16:53
*** mikelk has quit IRC16:53
*** subscope has quit IRC16:56
SamYaplesbezverk: again, those files are just random files beople use. openvswitch-neutron-agent.ini though hasn't been used since ml2 came around16:59
sdakeinc0 going out today with thatemail16:59
SamYapleyoull find that info in ml2_conf.ini16:59
sdakei was waiting until tuesday so folks would actually read the email :)16:59
inc0kk thanks16:59
SamYaplesdake: that logging patch17:00
SamYaplesocket*17:00
sdakethe one you wrote?17:00
sdakeright17:00
SamYapleyea17:00
SamYapleso Jeffrey4l pointed out somethign great17:00
SamYaplewhen binding in host /dev you cant symlink like the patch does17:00
sdakei guess i should read scrollback ;)17:00
SamYaplebasically what this means is we lose logging for cinder-volume17:00
SamYaple_until_ Heka17:00
SamYaplewith heka (as I made a note of) we shouldnt need that symlink17:01
sdakegot it17:01
SamYaplealso logging for kolla_toolbox, but I can fix that17:01
SamYaplei think17:01
SamYapleeither way after heka both logging issues are solved17:01
SamYaplei think its reasonable to merge now and then focus on heka17:01
sdakemerge your patch?17:02
sdakeI thought I +2'ed it already17:02
sdakejust got back in office haven't read email17:02
SamYaplesdake: no you have a +2 jeffreys comment was after your +217:03
sdakegot it so it needs another review on it17:03
SamYaplewell it needs everyone to understand why it broke17:04
sdakereading review and processing omemnt17:04
*** Marga_ has joined #kolla17:05
SamYaplesdake: i just added comment17:05
SamYaplemake sure to refresh before secodn review17:05
*** Marga_ has quit IRC17:05
*** Marga_ has joined #kolla17:05
sdakeJeffrey4l can you ahve a look at the review here; https://review.openstack.org/#/c/280429/217:06
sdakeso do you need to remove the symlink entirely?17:06
SamYaplewell it wont be needed after heka17:07
SamYaplei dont have to do anything to the patch as-is17:07
SamYaplewith the outcome I say17:07
SamYaplebut after heka no need to use /dev/log17:07
*** blahRus1 has joined #kolla17:07
SamYaplewe can point haproxy and keepalived to a socket anywhere, not just /dev/log17:07
*** blahRus has quit IRC17:08
*** aginwala has joined #kolla17:09
SamYaplefyi sdake im removing lots fo the /run mounts17:12
SamYaplenamed_volumes for all!17:12
sdakewfm17:13
sdakei hated those run mounts17:13
sdakebe careful with libvirt and nova however17:13
sdakeit needs to communicate with systemd on teh host17:13
SamYaplelibvirt and nova are tcp based17:13
sdakeoh right that got changed17:13
SamYapleil probably change it back after the socket thing17:13
SamYaplemaybe. if i can address nihilifer concerns17:13
sdakebut libvirt still may use systemd's dbus docket17:13
*** chandankumar has quit IRC17:13
sdakeI would suggest double checking on a system with systemd your patch for that if you intend to named volumes the run for libvirt and friends17:14
sdakespecifically an upgrade of the container17:14
*** fthiagogv_ has quit IRC17:14
sdakeor separate out the nova patch from the others that way one goes in fast and the other can block for testing17:14
SamYapleill start simple with openvswitch and haproxy17:15
SamYapleyou can review the nova patch17:15
sdakeif you test with systemd that is good enough for me17:16
sdakeif you want me to test it i can do so17:16
*** macsz has quit IRC17:16
sdakeif I can get my env going ;-)17:16
SamYapleim running 15.1017:16
SamYapleso its all systemd17:16
sdakenice17:16
sdakeright17:16
*** mbound has quit IRC17:19
kproskurinand what about poor ubuntu 14.04 users? :-\17:22
SamYaplekproskurin: no issue!17:23
kproskurinBtw, right now ubuntu 14.04 is busted, ‘cos it doesnt have systemd so there is no MountFlags=shared fix17:23
SamYapleworks perfect17:23
Jeffrey4lSamYaple, i have removed my -117:23
SamYaplekproskurin: no its all busted sometimes17:23
SamYaplethats waht my patch is for17:23
kproskurinI did mount --make-shared /run to fix that, but it’s need to be a better way, like upstart job or something17:23
SamYapleoh that17:24
SamYaplekproskurin: d you think we should document modifying the upstrart job to do that/17:28
sbezverkSamYaple After server reboot, kolla-toolbox fails to start even with the patch17:28
SamYapleI understand and agree thats a bit annoying17:28
kproskurinSamYaple: well if we want to support ubuntu 14.04 - yeah we should :-)17:28
SamYaplethats fair17:28
kproskurin‘cos it not working right now17:28
SamYapleand we absolutely do17:28
SamYaplei just added a second upstart job to change it17:29
SamYaplebut maybe modifying the docker one is better?17:29
kproskurincould you send a link to review?17:29
*** fgimenez has quit IRC17:29
SamYaplei dont have one17:29
SamYaplei did it locally17:29
sdakesbezverk can you run docker logs on the kolla-toolbox container id plz17:30
kproskurinI have no idea how to fix it “right”, ‘cos I not fammiliar with upstart. I tried to find something like MountFlags in upstart and looks like there is none17:30
sdakeanad pipe into fpaste17:30
SamYaplekproskurin: we could require a second mount on /run/netns and have only that one be shared17:31
SamYaplesystemd takes care of making mounts shared i think17:31
kproskurinyep, mount -bind or something17:32
SamYaplewell run is a tmpfs anyway17:32
SamYaplewe could just do a second tmpfs17:32
sbezverksdake here you go: http://paste.fedoraproject.org/323634/1455643917:33
limamauricioSamYaple, i think the "true" value must be enclosed in quotes https://review.openstack.org/#/c/280808/17:33
kproskurinSamYaple: just to save your time: findmnt -o TARGET,PROPAGATION in ubuntu 14.04 doesnt know about PROPAGATION flag, so if you want to check is mount is shared you have to look at /proc/self/mountinfo17:34
*** aginwala has quit IRC17:34
sdakesbezverk that is with dockage images of the docker-toolbox id?17:34
SamYaplekproskurin: shoot lol tahts where i was heading17:34
SamYapleok so direct to proc17:34
*** dims has joined #kolla17:34
kproskurinhave to go, bay all!17:35
sbezverksdake yes17:35
sdakesbezverk journalctl -u docker | fpaste17:35
*** vhosakot has joined #kolla17:35
sdakeby kproskurin17:35
SamYaplethanks kproskurin17:35
sdake89 people in hannel17:35
sdakewinning17:35
sbezverkhttp://paste.fedoraproject.org/323635/6441471417:36
vhosakothi all, still working on getting my dev env going.... I filed https://bugs.launchpad.net/bugs/1545926 to update the quickstart guide with missing commands17:36
openstackLaunchpad bug 1545926 in kolla "Update doc/quickstart.rst" [Undecided,In progress] - Assigned to Vikram Hosakote (vhosakot)17:36
SamYaplelimamauricio: can you test that real quick? youre probably right17:36
*** aginwala has joined #kolla17:36
SamYaplevhosakot: fyi, no need for a bug to fix docs17:36
SamYaplevhosakot: but no harm doing so17:36
limamauricioI tested, and i have a invalid json file17:36
*** jtriley has quit IRC17:36
SamYapleyea thats probably right17:36
vhosakotSamYaple: ok, didn't know... so the patch set to update doc need not have a track bug in Launchpad ?17:37
SamYaplelet me look at code17:37
SamYaplevhosakot: correct17:37
vhosakottracking*17:37
vhosakotcool17:37
sdakesandbox issue SamYaple after a reboot it looks like with your patch17:37
SamYaplevhosakot: for docs-only patches17:37
vhosakotcool17:37
SamYaplesdake: ?17:37
sdakesbezverk can you do git shortlog -5 | fpaste17:37
sdakeSamYaple see sbezverk last paste17:37
sdakehe rebooted17:37
sdakeand kolla toolbox container fails to start17:37
sdakewith a sandbox error17:38
sdakehe previously had a deployment rolling17:38
sdakesbezverk  arey ou running the named mount patch in the patch queue (that is what he git shortlog is meant  to determine)17:39
*** kproskurin has quit IRC17:39
sbezverksdake git shortlog does not produce anything, for the patch I dowloaded diff and manually applied with patch command17:39
*** Jeffrey4l has quit IRC17:40
sdakesbezverk there is a far superior way to do it, use cherrypick option in the review screen - copy and paste the operation17:40
sdakeit is possible your patch didn't get applied correctly17:41
*** jtriley has joined #kolla17:41
vhosakotIn the quickstart guide, the part about making Docker use an insecure registry (other_args), the commands are for CentOS.... for Ubuntu, to do this (make docker use insecure registry), I need to have  "DOCKER_OPTS="-H fd:// $other_args"  in the file  /etc/init.d/docker, right ?  After adding this,  I need to retstart the docker service  (sudo service docker restart).. Is this right ?17:41
sdakeor its possible reboot is busted17:41
SamYaplevhosakot: thats correct for 14.04 ubuntu, not past taht17:41
SamYaplein 15.10 you have to edit systemd file17:42
sdakemaster docs in registry are wrong17:42
vhosakotok... yes.. I'm on 14.04... thanks!17:42
sdakeon registry17:42
sdakesomeone is working on a patch atm17:42
sbezverkopenvswitch does not read or use new config. I changed /etc/kolla/neutron-server/ml2_conf.ini to add mapping for tenants interface bridge_mappings = physnet1:br-ex,physnet2:br-tenants_b0 I do not see openvswitch agent plugging br-tenants_b0 into br-int bridge? I rebooted a server but no help. ANy ideas what I am doing wrong?17:43
vhosakotto see how many containers the "kolla-build" command built,  I can check it in "docker images"  right ?17:44
sdakesbezverk  well, if your using copy-once config strategy which is teh default, it unfortunately wont read the config until we get done with the reconfig blueprint17:44
sdakesbezverk another short-term option is to use config-strategy config_always17:44
sdakeor COPY_ALWAYS that is17:44
sbezverksdake I used COPY_ALWAYS17:45
sdakedid you redeploy or just reboot?17:47
SamYaplesbezverk: you have to create br-tenants_b017:47
sdakeyou ahve to redeploy17:47
sdakeit will upgrade and reconfig17:47
SamYapledid you do that?17:47
sbezverksdake just rebooted17:47
sdakejust a reboot wont do it17:47
sdakeyou dont want to reboot your cloud nodes anyway :)17:47
SamYaplelimamauricio: no i meant can you test your suggested change17:47
sdakesbezverk try a kolla-ansible deploy again17:48
sdakeyour existing cloud will not be disrupted17:48
sbezverksdake well, I have a problem then as re-deploy will not work due to a screw up with kolla-toolbox17:48
sdakebut new config options will be put in place17:48
vhosakotsorry for duplicate message.... to see how many containers the "kolla-build" command built,  I can check it in "docker images"  right ?17:48
sdakei hear you with the kolla-toolbox problem, I susicion is the patch was not applied correctly17:48
*** shardy has quit IRC17:48
sdakewipe out all existing containers17:49
sdake(the ones running)17:49
sdakecleanup-containers17:49
sdakein the tools directory17:49
sdakedocker rm -f kolla-toolbox17:49
sdakein your repo git reset --hard17:49
sdakeand run the cherrypick command from gerrit17:49
*** chandankumar has joined #kolla17:49
sdakeor wait for the patch to pull into master17:49
openstackgerritSam Yaple proposed openstack/kolla: Use "optional" for ceph confs  https://review.openstack.org/28080817:50
sbezverksdake ETA for this patch in the master?17:50
SamYaplesbezverk: soon as another core approves17:50
SamYapleinc0: rhallisey ^^ http://paste.fedoraproject.org/323634/1455643917:51
sbezverksdake I will wait then.. thank you17:51
sdakehttps://review.openstack.org/#/c/280429/ needs another core review to review17:51
vhosakothow can I check the list of containers that kolla-build built ?  is "docker images" the right command ?17:51
SamYaplevhosakot: yes17:52
vhosakotcool17:52
SamYaplealso the output from the kolla-build command17:52
SamYapleit tells you what it built17:52
vhosakotyeah... at the end of the output, right ?17:52
vhosakotI see it17:52
SamYapleyup17:52
sdakeSamYaple what is with this gate failure17:53
sdakehttp://logs.openstack.org/29/280429/2/check/gate-kolla-dsvm-deploy-centos-binary/621a359/console.html#_2016-02-16_15_59_21_16917:53
rhalliseySamYaple, this is the named_volume patch?17:53
sdakeyes but it is failing gate, don't +w just yet17:53
rhalliseyI wanted to test it17:53
rhalliseystill having issue with my setup tho17:53
sdakecool please do17:53
vhosakotI see there is no "kolla-build status" command17:53
rhalliseygetting closer17:53
rhalliseyI think someone had this issue earlier..: msg: APIError(HTTPError(u'500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.22/containers/neutron_dhcp_agent/start',),)17:54
SamYaplesdake: i prefer to say the gate is failing my patch17:54
SamYaplerhallisey: MountFlags=shared in your docker.service file17:54
SamYaplethe restart docker17:55
SamYapleits unrelated. its for the thin contaienrs patch17:55
rhalliseySamYaple, did you put that in docs somewhere? /me looks through the q17:55
sdakehave 1 hour meeting, bbiaf17:56
SamYaplerhallisey: sorry man. i have teh patch on my desktop at home17:56
SamYapleits not pushed17:56
rhalliseyhehe17:56
rhalliseyit's ok17:56
SamYaplei wrote it last night17:56
SamYaplei cant remote access my machine yet17:56
SamYaplei thought about it this morning :/ i promised it yesterday17:56
sdakerhallisey do this:17:56
sdakeur1.ca/oj0ii17:57
sdakeshould replace /usr/lib/systemd/system/docker.service17:58
*** achanda has joined #kolla17:59
rhalliseycool thx17:59
sdakeoh meeting ins't until noon17:59
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074917:59
*** cemason has quit IRC18:00
limamauricioSamYaple: same error :/18:00
limamauricioError encountered during initialization of driver: RBDDriver.18:00
*** cemason has joined #kolla18:01
limamauricioSamYaple -> http://pastebin.com/tq7eJ6Vp18:01
*** jtriley has quit IRC18:01
*** Marga__ has joined #kolla18:01
SamYaplelimamauricio: can you confirm the ceph files transfered in appropriatly?18:05
limamauricioyes, i can18:05
*** ssurana1 has joined #kolla18:05
*** Marga_ has quit IRC18:05
*** achanda has quit IRC18:06
SamYapleso they are in the container?18:06
*** ssurana has quit IRC18:06
SamYapleoh nvm limamauricio yea so its in there18:06
SamYaplebut i bet its not the right file18:07
SamYaplelet me check18:07
*** subscope has joined #kolla18:07
limamauricioSam, the files are there18:07
SamYaplelimamauricio: but cinder-backup keyring isnt... right?18:08
openstackgerritSam Yaple proposed openstack/kolla: Use "optional" for ceph confs  https://review.openstack.org/28080818:08
SamYaplecheck this patch out18:08
limamauriciook18:08
SamYaplecinder and cinder-backup have different keyrings18:08
SamYaplethat was only copying in cinder keyring, it needs cinder-abckup18:08
limamauriciooh18:09
limamauricio:)18:09
limamauricioI'll test now18:09
*** Serlex has joined #kolla18:22
*** achanda has joined #kolla18:23
*** jtriley has joined #kolla18:25
*** jasonsb_ has quit IRC18:28
*** gfidente has quit IRC18:29
sdakeinc0 email away18:34
inc0sdake, thanks18:35
sdakefeel free to correct mistatements18:35
openstackgerritMerged openstack/kolla-mesos: Add priviliged flag to nova-api  https://review.openstack.org/28057618:35
sdakethat is how i interpreted thigns :)18:35
openstackgerritMerged openstack/kolla-mesos: Fix glance registry conf path  https://review.openstack.org/28060018:35
openstackgerritMerged openstack/kolla-mesos: Fix nova tasks  https://review.openstack.org/28046418:35
*** jtriley has quit IRC18:35
*** jtriley has joined #kolla18:39
inc0sdake, you didnt call for vote for thin neutron containers:P18:39
sdakeinc0 writing that email - emails take a long time to write ;)18:39
limamauricioSamYaple, same error on cinder_backup, but i created a volume successfully http://pastebin.com/YKmDU4fD18:39
sdakei wanted to keep the threads separate if that makes sense to you18:40
sdakeThere was not a majority approval for another proposal to backport thin containers for neutron which I will handle in a separate email.18:40
inc0sure, no problem18:40
limamauriciomaybe im forgetting something18:41
sdakei say right there its a seprate email ;)18:41
*** gfidente has joined #kolla18:41
vhosakotdoes anyone here successfully use Vagrant for day-to-day kolla dev work... just wanted to check if going the Vagrant route is good.... I;m seeing some issues realted to SSH key mis-match everyt ime I do "vagrant ssh"18:42
sdakevhosakot pbourke and mandre use it18:42
SamYaplelimamauricio: ill have t otest now, nothing else major sticks out18:43
SamYaplelimamauricio: you may try a new deploy18:43
vhosakotpbourke, mandre  do you giys use the Vagrantfile at https://github.com/openstack/kolla/blob/master/dev/vagrant/Vagrantfile18:43
vhosakotguys*18:43
vhosakotI have used Vagrant before... but the SSH key mis-match issue I'm seeing is after I installed kolla, ran kolla-build, and logged out and tried to SSH in back18:44
vhosakotI dont want to debug non-kolla realted Vagrant issues :)18:44
vhosakotrelated*18:44
SamYaplesdake: successful vm launch in gate18:46
SamYapleafter18:46
SamYapleSam Yaple18:46
SamYapleafter * https://review.openstack.org/#/c/280029/18:46
sdakevhosakot mandre and pbourke are likely asleep or on a plane atm18:48
inc0SamYaple, looks cool18:48
vhosakotoh ok.. cool.. np..18:48
vhosakotwill keep the team posted the moment I'm up with kolla18:49
*** chandankumar has quit IRC18:49
vhosakotsdake: do you think a "kolla-build status" is needed ?  or, this is covered by "docker status18:49
vhosakotforgot to add ? at the end18:49
sdakeSamYaple looking sweet:)18:50
sdakevhosakot please expand on what kolla-build status would do18:50
openstackgerritMerged openstack/kolla: Reduce gate resource usage  https://review.openstack.org/28002918:51
SamYaplecan someone give me access to a box with the toolbox sandbox issue?18:51
*** ssurana1 has quit IRC18:52
*** athomas has quit IRC18:52
sdakeyou mean sans your patch?18:53
vhosakotsdake: ok, "kolla-build" builds all the containers and fails few times for bad/flakey mirrors... I am thinking if there should be a kolla command that shows all the docker containers built... Since this info is in "docker images", a command like "kolla-build status" may not be needed...18:53
SamYaplesdake: to test a few things about the underlying issue18:53
SamYaplei j ust need a sysmtem that breaks18:53
vhosakotas a new user, I did not know how to find what kolla-build did18:54
vhosakotuntil I found "docker images"18:54
vhosakotfound == used18:54
sdakeSamYaple yup i can try that this afternoon - but be aware, its on my laptop :)18:54
SamYaplesdake: even better18:54
sdakei have meeting in 6 minutes18:54
sdakeand meeting at 2pm18:54
sdakeand kids at 3pm18:54
SamYaplevhosakot: so the builds are a one-off operation18:54
sdakei'll try to get it setup as soon as possible18:55
vhosakotsdake: ah... got it... not every day18:55
SamYaplekolla-build status wouldn't work because the images on your system dont neccesarily match the dockerfiles you want to build18:55
vhosakotSamYaple: because, the images depend on what registry the user is uwing ?18:55
vhosakotusing*18:55
SamYapleno they depend on the Dockerfile content18:56
sdakeSamYaple so basically i have between 1 and 2 to get you setup18:56
sdakeor 2-:24518:56
SamYaplei just need someone with a failing system18:56
vhosakotgot it.. cool18:56
SamYaplei cant reproduce18:56
sdakeit may take a couple hours to sort how to get you an ip into this vm18:56
sdakeatm the vm is in nat mode rather then getting an ip from my network18:56
sdakei'll sort it out, but need couple hours because of meetings etc18:57
sdakei can definately give my laptop a static ip18:57
*** athomas has joined #kolla18:58
*** gfidente has quit IRC19:00
*** haplo37 has quit IRC19:03
SamYaplecan anyone with the kolla_toolbox issue give me the output of `docker inspect kolla_toolbox`19:05
SerlexHi SamYaple, is that where toolbox container exits?19:07
SamYapleSerlex: if you are asking if toolbox conatiner == kolla_toolbox, the answer is yes19:08
Serlexok running now19:08
*** dwalsh has joined #kolla19:08
SamYapleSerlex: its important that your deploy has broken and the kolla_toolbox container is in the "Created" state19:09
Serlexahh ok, not me then19:09
*** jtriley has quit IRC19:11
*** dwalsh_ has joined #kolla19:15
*** dwalsh has quit IRC19:16
*** ssurana has joined #kolla19:18
*** dwalsh_ has quit IRC19:19
*** jtriley has joined #kolla19:19
*** mbound has joined #kolla19:23
sbezverkSamYaple Do you still need output you requested earlier?19:24
*** unicell has joined #kolla19:26
SamYaplesbezverk: from a kolla_toolbox container in the Created state, yes19:27
sbezverkSamYaple, two minutes then I will bring up a server with broken container19:27
SamYaplew00t19:28
SamYaplemind running a few tests for me too?19:28
sbezverkhmmm, it is in exited state, would it still be ok?19:29
SamYapleprobably not, but why is it in an exited state....19:30
SamYapleit should never be there19:30
Serlexdevaju19:30
Serlexdejavu19:30
sbezverkSamYaple check this http://paste.fedoraproject.org/323714/5102014519:30
sbezverk4f9cfa12ddf2        192.168.80.240:4000/kollaglue/centos-source-kolla-toolbox:2.0.0               "/bin/sleep infinity"   3 hours ago         Exited (-1) 2 hours ago                       kolla_toolbox19:31
*** limamauricio has quit IRC19:31
SamYaplesbezverk: looks like you rebooted or something19:31
SamYaplewhats `docker logs kolla_toolbox` say?19:31
*** dwalsh_ has joined #kolla19:32
Serlexits the same state that I have19:32
SamYaplesurely thats after a reboot Serlex19:32
SamYapleit _cant_ deploy in that state19:32
SamYapleall it does is run /bin/sleep19:32
sbezverkSamYaple, that is correct, the server was rebooted19:33
SamYaplesbezverk: if you say this server gets the toolbox issue, would you be opposed to wiping kolla from it and rekicking kolla?19:34
SamYaplei know you just got it setup so if you want to play with it i understand19:34
SamYaplei just cant replicate this issue anywhere19:34
*** jtriley has quit IRC19:35
sbezverkSamYaple, anything for you to get this issue resolved.. I am opened for a debugging session where I can share access to my server via web conferencing.19:35
vhosakot"curl -sSL https://get.docker.io | bash"  in the quickstart guide installs docker version 1.10.1.. Is docker 1.10 ok ?19:35
sbezverkvhosakot yes19:36
vhosakotcool19:36
SamYaplevhosakot: 1.10+19:37
SamYapleor rather >=1.1019:37
vhosakotso, I don't have to run  "sudo apt-get install docker-engine=1.8.2-0~trusty"  to downgrade docker as docker 1.10 is good... am I right ?19:37
SamYaplevhosakot: correct19:38
SamYaple1.8.2 is for liberty19:38
vhosakotaccording to the quickstart guide, running  "sudo apt-get install docker-engine=1.8.2-0~trusty"  after  "curl -sSL https://get.docker.io | bash"  downgrades docker from 1.10  to 1.8.2...this is needed for Liberty...19:38
SamYaplevhosakot: are you running liberty?19:38
SamYaplemaster==mitaka19:38
vhosakotno, following quickstart...19:39
vhosakotI want latest19:39
vhosakotMItaka19:39
vhosakotI will not run  "sudo apt-get install docker-engine=1.8.2-0~trusty"  and use docker 1.10 on Mitaka...19:39
vhosakotthanks! :)19:39
SamYaplethats it!19:40
vhosakot:)19:40
sbezverkb54f552c9123        192.168.80.240:4000/kollaglue/centos-source-kolla-toolbox:2.0.0               "/bin/sleep infinity"   13 seconds ago      Created                                       kolla_toolbox19:41
SamYaplesbezverk: that looks like the breakage i need to test!19:42
sbezverkhttp://paste.fedoraproject.org/323725/4556517219:42
sbezverkSamYaple anything else tp collect?19:42
SamYaplesbezverk: sure enough!19:42
SamYapletheres the issue19:43
Serlex?19:43
SamYapleSerlex: i see the issue i predicted in the output sbezverk provided19:44
SamYaplelook at mounts between his and mine http://paste.openstack.org/show/487163/19:45
SamYapleerr wrong post19:45
*** nihilifer_mobile has joined #kolla19:45
SamYaplebut the Mounts are different19:45
Serlexawesome SamYaple, you the man19:45
SamYaplenah it doesnt help to predict a problem i cant fi19:46
SamYaplex*19:46
SerlexI should really read what the toolbox container is but the fact my container has exited is a concern/19:46
Serlexor not?19:46
SamYapleSerlex: you reboot though right?19:46
Serlexyes19:46
SamYapleyea thats why19:47
SamYaplerebooting the containers don't start back up in the correct order19:47
Serlexthat means nothing to me, all my other containers are running after reboot19:47
SamYaplewe talked about that as an action point at the midcycle19:47
Serlexoh ok19:47
SamYapleyou should be able to start the kolla_toolbox container19:47
SamYaple`docker start kolla_toolbox`19:47
SamYapleworst case you can remove and recreate19:47
SamYaple`docker rm -f kolla_toolbox` then just rerun playbooks19:47
sbezverkSamYaple, do you mean right now or after it is fixed?19:48
SamYaplesbezverk: no not for you that was for Serlex19:48
SamYaplei have a patch in the queue to work around your issue19:48
sbezverkok19:48
SamYaplebut i still need to _fix_ it, but i need access to a box to do so19:48
SamYapleat least to investigate further19:48
sbezverkSamYaple, and Webex to me server does not work for you?19:49
*** haplo37 has joined #kolla19:49
Serlexwoop I have a horizon19:50
Serlexthank god after hours of dicking around19:50
SamYaplesbezverk: hmm webex work on linux?19:51
SamYapleits been a while since ive used it19:52
*** nihilifer_mobile has quit IRC19:52
SamYaplesbezverk: that might work19:52
vhosakotwhich docker registry version should I use ?  v1 or v2  ?   Should I run  "docker run -d -p 4000:5000 --restart=always --name registry registry:2"  per the quickstart19:53
Serlex2.319:53
sbezverkSamYaple I know it works on Mac, never tried to join from linux ws though19:53
vhosakotso, I need to  "docker run -d -p 4000:5000 --restart=always --name registry registry:2"   right ?19:54
Serlexadd .319:55
SamYaplevhosakot: that would start a v2 registry listening on port 4000  yes19:55
vhosakotok..19:55
Serlexor whatever SamYaple says19:55
SerlexI ran 2.319:55
vhosakotI will run  "docker run -d -p 4000:5000 --restart=always --name registry registry:2.3"  then... thanks!19:55
SamYapleSerlex: vhosakot you can do registry:2.3 if you want registry:2 is the same thing19:55
vhosakotcool!19:55
SamYaplesee the current tags at https://hub.docker.com/_/registry/19:55
vhosakotyep19:56
vhosakotthanks!19:56
SamYaplewith registry:2 when, say 2.4.1 comes out it will retag as :219:56
*** Marga__ has quit IRC19:58
*** Marga_ has joined #kolla19:58
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074919:59
sdakeSamYaple webex will not work on linux19:59
SamYaplesdake: webex says it will19:59
sdakeserlex nice! :)19:59
sbezverkSamYaple, so do you want to give it a try with webex?20:01
SamYaplesbezverk: yea lets give it a try20:02
sdakeSamYaple re sbezverk wrong bind order, you think that is caused by the reboot?20:02
SamYaplesdake: no this is back to the sandbox issue20:03
SamYaplestill trying to troubleshoot it20:03
sdakeyes i thought I said that hours ago :)20:03
sdakemaybe its a different sandbox issue20:03
SamYapleno he is helping me trouble shoot it20:03
sdakekeep in mind sbezverk hand applied the upstream patch20:03
sdakerather then git cherrypicking it20:03
SamYapleagain. this is not whats going on20:03
sdakeok20:04
SamYaplehe is helping me debug not his issue but _THE_ issue20:04
sdakewell I dont have a problem after you patch20:04
SamYaplesince i cant reproduce20:04
SamYaplewithout the patch20:04
SamYapleits fine sdake20:04
sdakei see, you want to get to root cause because you think its still there20:05
*** aginwala has quit IRC20:05
SamYaplewell the root cause is still there, we are just mostly working around it20:05
sdakewhat I dont get is why sbezverk has two /dev mounts in his host config, since your patch only has one20:05
sdakei think in _HIS_ case, he is not running the patch ;-)20:06
sbezverkhttps://cisco.webex.com/join/sbezverk20:06
*** aginwala has joined #kolla20:08
SamYaplesbezverk: its crashing for me :/20:09
SamYaplesdake: i know he isnt, i didnt want him to. i asked him not too20:09
SamYaplesdake: its covered20:09
sdakesounds good20:09
sdakeya webex is bust on linux20:10
SamYapleive done it once or twice20:10
SamYaplebut java always breaks20:10
sdakeyou can use a different webex tool20:10
sdakei forget what its called20:10
sdakewhy dont you try google hangouts20:10
sdakewebex is dependent on a componet of java that open source jdk has deprecated20:10
sdakesomething related to gcc20:10
sdakeyou can theoretically get it to work20:10
SamYapleim running oracle java20:11
sdakebut its a real pain in the ass20:11
sdakei was never actually able to get jwebex to work on linux20:11
sdakeand I tried and tried20:11
sdakeSamYaple one thing you cand o is install a 32 bit vm20:11
sdakeand run webex in that20:11
SamYaplei did at rax, but its PITA20:11
sdakethat will work from my experience20:11
*** rajathagasthya has joined #kolla20:12
SamYaplesorry sbezverk i think ill have to pass on the webex for now20:12
SamYaplebefore the beginning of next week ill have my private openstack cluster running so i should be able to reproduce this in a vm there20:13
sbezverkSamYaple sure, I understand, just was trying to be helpful20:13
*** cemason has quit IRC20:13
SamYaplesbezverk: you were very much so. thanks!20:13
SamYaplesdake: looging patch turned green20:14
SamYaplerhallisey: did you get it working?20:14
*** cemason has joined #kolla20:15
*** sdake_ has joined #kolla20:15
rhalliseySamYaple, not yet.  kolla-toolbox error. APIError(HTTPError(u'500 Server Error: Internal Server Error20:16
*** dwalsh_ has quit IRC20:16
rhalliseyI had to work on something else so I haven't touched it since I got that20:16
rhalliseyI think someone has had that issue before20:17
*** dwalsh has joined #kolla20:17
*** sdake has quit IRC20:17
SamYaplerhallisey: thats the issue the patch is solving, no?20:17
SamYaplewhat state is the container in?20:17
SamYaplekolla_toolbox that is20:17
rhalliseycreated status20:18
rhalliseystuck there20:18
SamYapleyea you either didnt clean the environemnt or you didnt rebuild your containers with the patch20:18
SamYaplei would think maybe you didnt clean the failed kolla_ansible container20:19
vhosakotis there a recommended value for the argument --retries for kolla-build.... or, the default number of retries (3) is used... how many retries does everyone do ?20:20
rhalliseyya I'll get back to it later20:20
rhalliseySamYaple, thanks20:20
SamYaplerhallisey: yup thanks for testing20:21
SamYaplevhosakot: for the build, I actually do 020:22
SamYaplei dont want it to retry if there is an issue20:22
SamYaplein the gate however we are more lienient20:22
SamYaplewe want it to retry20:22
SamYaplethats why the default is 320:22
vhosakotcool20:22
SamYapleit really _shouldnt_ be failing, that indicates a problem20:22
vhosakotright20:22
vhosakotI will do with 0 then20:22
vhosakot"kolla-build --retries 0 "   is this the right way ?20:23
vhosakot?20:25
SamYaplevhosakot: yes20:25
vhosakotcool!20:25
SamYapleor you can set it in /etc/kolla/kolla-build.conf to make it more permanant20:25
sdake_SamYaple ssh samyaple@broked.selfip.net20:25
guillaume_hello guys, is the kolla-toolbox bug fixed?20:25
sdake_lets see if that par tworks20:25
sdake_guillaume_ yes fixed not merged20:25
SamYaplesdake_: still have my pubkey?20:25
sdake_SamYaple yes20:26
guillaume_when it will be merged?20:26
sdake_its in my gmail ;)20:26
sdake_I have it forever20:26
sdake_if you sen dto gmail, i can find it20:26
sdake_if you send to cisco email, well, outlook blows ;)20:26
sdake_see ify ou can login20:26
SamYaplesdake_: refused20:26
SamYapleguillaume_: it will be merged when another core approves it20:27
sdake_samyaple ocnnection refused or login refused?20:27
SamYapleguillaume_: https://review.openstack.org/#/c/280429/20:27
SamYaplesdake_: connection20:27
SamYapleport num?20:27
guillaume_SamYaple and sdake: thanks for you info. I will modified it by hand for today ?20:27
*** dwalsh has quit IRC20:27
SamYapleguillaume_: sounds good. that patch should be merged tomorrow20:28
*** sdake_ has quit IRC20:32
sbezverkAnybody managed to get cinder volume container running?20:32
*** sdake has joined #kolla20:32
openstackgerritSam Yaple proposed openstack/kolla: Move haproxy socket to volume  https://review.openstack.org/28091820:33
SamYaplesbezverk: with ceph, yes20:33
SamYaplesbezverk: cinder+nfs patch is in the queue20:33
SamYaplecinder+lvm is not actively being wokred on20:34
sbezverkSamYaple how about LVM?20:34
SamYaplei had a PoC many moons ago, its technically possible but no patches are up for it20:34
sbezverkSamYaple I see.. anything I could do to make it happen?20:35
sbezverkwill it make to official Mitaka?20:35
sdakeSamYaple try again plz20:35
sbezverkafter all LVM is still a reference confo20:35
sbezverkconfiguration..20:35
sdaketo ssh20:36
SamYaplesbezverk: doubtful, unless someone picks it up20:36
SamYapleit requires us ot containerize iscsi and no one has done that yet20:36
SamYaplei am too overlaoded to start that again20:36
SamYaplesdake: im in. dont know how to elevate20:38
sdakeyour on a mac20:38
sdakeyou need to ssh into my vm20:38
sdakei am working on that next20:38
SamYapleoh this is mac ok20:38
sbezverkSamYaple that puts a big red stop on my activities, all our test beds are using AIO and LVM as a storage..20:38
SamYaplesbezverk: thats disappointing. I wish I could give you better news. I would say its about a week of my time dedicated to get it setup20:39
SamYaplei wish I could give you better news, but I dont have a week to give before Mar 3rd20:39
SamYapleand Mar3rd is mitaka-3 tag20:39
*** cemason has quit IRC20:40
sbezverkSamYaple I understand20:41
*** cemason has joined #kolla20:41
*** dwalsh has joined #kolla20:41
*** subscope has quit IRC20:42
*** aginwala has quit IRC20:46
SamYapleill tell you what sbezverk give me until tomorrow and ill see if I can get the work started for others to finish20:46
*** aginwala has joined #kolla20:49
vhosakotI see 112 Dockerfiles in kolla/docker....  does this mean kolla-build builds all of these 112 containers ?20:53
*** dwalsh has quit IRC20:54
SamYaplevhosakot: it would build 112 images in total if run in full, it only produces ~60 or so services and of those kolla-ansible only deploys ~4020:55
vhosakot"if run in full"   is this an option to kolla-build to build all the 112 containers ?  or "if run in full"  means  kolla-build  + kolla-ansible20:58
SamYaplekolla-build with no paramaters builds 112 images20:59
vhosakotok... that is what I'm doing per the quickstart...  kolla-build21:00
SamYapleyup21:00
vhosakotcool21:02
daneyonSamYaple do you have a moment for me to bounce a question off you?21:07
SamYapledaneyon: for you, always21:07
daneyonthx21:07
d_codehas anyone done PCI passthrough with Kolla?21:07
SamYapled_code: me! but it requires kolla codebase hacking21:08
SamYapled_code: cant do it with native kolla last i checked21:08
daneyonSamYaple I am trying to get Ansible to work with CoreOS21:08
d_codeI can hackz21:08
daneyonSamYaple the 1st issue is that coreos does not include a python interpreter21:08
d_codethe pci passthrough wiki page on openstack.org seems like it’s old…but it suggests that it’s built into nova now21:08
d_codeis the hack to enable the API endpoints?21:08
d_codeI saw the github repo for that, last commit was 3 years ago21:09
daneyonSamYaple i have worked around it in my lab by installing a script on coreos that pulls the python src and does some magic voodoo21:09
daneyonSamYaple I want to get away from that and run python in a container21:09
d_codeSamYaple: just nobody wants to merge it in, or what?21:09
SamYapledaneyon: so you want to run python in a container on core os?21:09
daneyonso everytime i issue python this happens: docker run --interactive --rm --net=none python:2.7-slim python21:09
daneyonSamYaple yes21:10
SamYapleand have ansible commands run _in_ that container?21:10
daneyonSamYaple the above works just fine when I create an alias to the docker run command for python21:10
daneyonSamYaple but when I run Ansible it runs the shell in non-interactive mode and does not respect the alias that I put in /etc/environment21:11
SamYapleyea its not going to. lots of stuff in ansible is hardcoded as /usr/bin/python21:12
SamYapleim not sure there is a way to do what you want to be honest21:12
daneyonSamYaple with the alias set in /etc/environment I can type python --version and docker runs the container and passes the --version command and runs it21:12
SamYaplei did alot of this with the kolla-ansible/kolla-toolbox container21:12
*** jtriley has joined #kolla21:13
SamYapleyea but ansible is going to talk directly to the interpreter21:13
daneyonSamYaple even when I changes the ansible_python_interpreter: "python" it does not work. From my understanding it's b/c ansible uses /bin/sh which does not support aliases21:14
SamYapleim not sure thats the correct reason daneyon21:14
SamYaplewhat yo uneed to test out is if you can have a test.py file that will run python code in a container21:15
SamYaplei couldnt figure out a way21:15
daneyonSamYaple: http://unix.stackexchange.com/questions/52471/how-to-add-system-alias21:15
vhosakotSamYaple: kolla-build built 87 images and 25 images failed to build.  Here is the output  http://paste.openstack.org/show/487173/.  Should I manually rebuild each of the failed 25 images ?21:16
daneyonSamYaple check out the answer with the green checkmark21:16
SamYapledaneyon: but this isn't about aliases21:17
SamYapleansible actually spits out a file with the shebang line that says #!/usr/bin/python followed by python code21:17
*** cemason has quit IRC21:17
SamYapleyou need to get a file like that to run in a docker container without hcanging the file, and I couldnt figure out how to do that21:17
SamYaplethe only other answer was to hack on ansible21:17
SamYapleyou can absolute hack on ansible to get that done to, but its a much bigger commitment21:18
daneyonSamYaple when I change ansible_python_interpreter: "python" ansible uses python instead of /usr/bin/python. I alias alias python="docker run --interactive --rm --net=none python:2.7-slim python"'21:18
daneyonso everytime i python --version, the docker run command is executed21:19
SamYapleill put together a pastebin daneyon so we are on the same page21:19
daneyonSamYaple if you have time to jump on a webex I could share my screen so you see what i'm up to21:20
*** cemason has joined #kolla21:20
*** Marga_ has quit IRC21:21
SamYapledaneyon: i cant webex from linux :/ its borked21:21
SamYapledaneyon: http://paste.openstack.org/show/487175/21:21
*** Marga_ has joined #kolla21:21
SamYaplewithout modifying test.py, you need to make that run inside a container, how do you do it?21:22
*** rajathagasthya has quit IRC21:22
larsksSamYaple: daneyon : https://tmate.io/ is nice for sharing terminal sessions.  It's just tmux w/ remote support.21:22
SamYaplei like tmate21:22
SamYaplelarsks: this thought problem may also interest you21:23
SamYaplesee the paste above? and the following question21:23
*** sdake_ has joined #kolla21:24
SamYaplelarsks: daneyon in this problem, you can modify /usr/bin/python, but not test.py itself21:24
larsksSamYaple: the goal is run with a different python?21:25
*** Marga_ has quit IRC21:25
*** sdake has quit IRC21:25
SamYaplelarsks: the goal is to run with the python interpreter inside a docker container21:25
daneyonSamYaple larsks check this out: https://gist.github.com/danehans/1597a3743cd4848e57cd21:25
larsksI wonder if you can just bind-mount a script that would Do the Right Thing: mount -o bind /path/to/wrapper /usr/bin/python21:25
SamYapledaneyon: but thats an alias, its not the same thing.21:26
vhosakotSamYaple: so, should I rebuild the 25 failed images ?21:26
SamYapleyou aren't running a script21:26
SamYaplevhosakot: im not sure why they failed, but you can try21:26
larsksdaneyon: aliases are really only good for interactive shells, right?  Because anything that calls "exec" doesn't care about your alias.21:26
daneyon^ works as expected when I ssh to my coreos box, but not with ansible, even after changing ansible_python_interpreter: "python"21:26
SamYapleok but even if it does work, its not going to execute the python instructions in the file21:27
vhosakotSamYaple: where can I find the logs why those 25 containers failed ?  /var/log/upstart/docker.log  has just  "ERRO[3732] Handler for GET /v1.22/containers/nova-compute/json returned error: No such container: nova-compute"21:27
SamYapleit will execute everything on the command line21:27
SamYaplevhosakot: when you built the containers, it spits out the failure message21:27
vhosakotSamYaple: no logs are written by kolla-build ?21:27
daneyonAccording to http://unix.stackexchange.com/questions/52471/how-to-add-system-alias it's b/c the alias is not used when the shell is in non interactive mode21:27
vhosakotright.. I saw that21:27
vhosakotok21:27
d_codedocker run --interactive --rm --net=none python:2.7-slim python -c "$(cat test.py)"21:28
d_codeis that cheating?21:28
*** Marga_ has joined #kolla21:28
SamYapledaneyon: i understand your point, what im saying is if aliases worked like you are asking them to it _still_ wouldnt work like you want because ansible doesnt stream files like that21:28
SamYapled_code: actually no21:28
d_code:)21:28
SamYaplebut getting that to work with ansible is the issue21:28
larsksSamYaple: In this situation, does a /usr/bin/python already exist and the goal is get *everything* to run inside a container?  Or just specific things, like ansible modules?21:28
SamYaplelarsks: /usr/bin/python does not exist21:29
larsksSamYaple: Because daneyon is correct that you can tell ansible which python interpreter to use and it will use that instead of /usr/bin/python.21:29
daneyonlarsks that's correct... the alias works great from an interactive shell, but not from Ansible21:29
SamYaplebut will that launch the code from the test.py file?21:29
vhosakotSamYaple: I scrolled up and see this...    ERROR:kolla.cmd.build:nova-compute:Parent image error'd with message "error"21:29
SamYaplemind you, without modifying the test.py file larsks it needs to send it to an interpreter in the docker container21:29
larsksSamYaple: I don't know, it's not clear to me if test.py is something hypothetical, or an ansible module, or...21:30
SamYapleits what the ansible module would look like21:30
daneyonSamYaple larsks I am basicly spawning the python container everytime I issue a python command from the shell21:30
SamYaplepython from the shell is different than python from a file21:30
SamYapleansible streams it to /usr/bin/python (by default) you cant stream into a docker container like that21:30
larsksSamYaple: So in that case, setting ansible_python_interpreter should work, right?  That could be a path to a wrapper script that runs python in a container...21:31
SamYapleit would not, because ansible streams into interpretur21:31
SamYaplelike `cat  test.py | /usr/bin/python`21:31
daneyonSamYaple larsks maybe another option would be to set an env that Ansible uses for all the playbook runs. Something like export PYTHON="docker run --interactive --rm --net=none python:2.7-slim python"21:32
larsksCan you not stream stdin to a docker container?21:32
larsksI thought that worked just fine.21:32
SamYaplenot that I am aware of21:32
SamYapleoh well wait21:32
daneyonSamYaple larsks then set the ansible_python_interpreter to $PYTHON21:32
SamYaplewith interactive yea21:32
SamYaplei guess you can larsks21:32
larsksSamYaple: e.g.: echo hello | docker run -i fedora sed s/hello/goodbye/21:32
larsksYeah.21:32
SamYapleyea i just tested too21:32
SamYapleyou cant without -i21:32
SamYaplebut that makes sense21:33
larsksSo that seems like you've got everything you need.21:33
SamYapleok daneyon give me a moment to test this21:33
*** Marga_ has quit IRC21:33
vhosakotSamYaple: I scrolled up and see this...    ERROR:kolla.cmd.build:nova-compute:Parent image error'd with message "error" .... Is this because  "FROM {{ namespace }}/{{ image_prefix }}nova-base:{{ tag }}"    in nova-compute's Dockerfile is incorrect21:35
*** dims has quit IRC21:37
*** JoseMello has quit IRC21:38
d_codeSamYaple: so…do you have any pointers on PCI Passthrough?  is it not built into Nova as noted here: https://wiki.openstack.org/wiki/Pci_passthrough21:40
d_codethere’s nothing on that page that says how old it is21:41
vhosakotI'm building nova-compute individually21:42
SamYapledaneyon: progress, working through some bugs21:42
daneyonSamYaple :-)21:42
*** macsz has joined #kolla21:43
SamYapledaneyon: wow.21:43
SamYaplei marked this path out a long time ago due to us not using interactive21:44
SamYaplealright so its not pretty21:44
SamYapleyou have to bind in ~/.ansible/ into your container21:44
SamYapleso if you are root that means21:44
SamYaple-v /root/.ansible/:/root/.ansible/21:44
daneyonSamYaple let me try21:45
SamYaplehold on ive got to post you more things21:46
*** jtriley has quit IRC21:46
SamYapleroot@y-work-laptop01:~# cat inv21:46
SamYaplelocalhost ansible_python_interpreter="docker run -u root -v /root/.ansible/tmp/:/root/.ansible/tmp/ --interactive --net=none registry:8182/kollaglue/ubuntu-source-nova-api:2.0.0 python"21:46
SamYapleyou need that in your inventory file21:46
SamYaplenow the fun part is you cant use a pure python container21:46
SamYapleyou have to install python in, say, and ubuntu container21:47
SamYaplea pure python container is missing things that youll need21:47
*** dwalsh has joined #kolla21:47
SamYaplehence why im running with a kolla image up there21:47
vhosakotSamYaple: is running kolla-build multiple times a good idea to rebuild failed images ?21:47
SamYaplevhosakot: it depends on the failure, it wont hurt21:47
vhosakotok21:48
vhosakotSamYaple: Any idea why nova-compute failed with the "Parent image error'd with message "error""  error... I dont see any other error anywhere21:48
larsksSamYaple: daneyon : this seems to work for me: https://gist.github.com/larsks/c1eefeee8f69e77c884921:48
daneyonSamYaple and larsks let me try both solutions and I'll let you know how it goes.21:49
larsksdaneyon: looks like that is basically the same thing.  SamYaple is just including the docker invocation directly.21:50
larsksI missed SamYaple 's message up there...21:50
*** dims has joined #kolla21:50
SamYaplelarsks: youd actually want to do `cat /proc/$$/fd/0 | docker run --interactive --net=none python:2.7-slim python`21:51
*** banix has joined #kolla21:51
SamYapleotherwise blobs will get parsed by bash i think21:51
openstackgerritOpenStack Proposal Bot proposed openstack/kolla: Updated from global requirements  https://review.openstack.org/28094321:51
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-mesos: Updated from global requirements  https://review.openstack.org/28094421:51
*** agasthya has joined #kolla21:51
larsksSamYaple: I don't think bash will do anything horrific with stdin?  I could be wrong.21:51
larsksI only tested it with '-m ping'...21:51
SamYapleit might if you do $@21:51
SamYaplethats bash processing it21:52
SamYaplemaybe idk21:52
*** agasthya has quit IRC21:52
larsksBut that's command line arguments, not stdin...21:52
SamYapleoh yea21:52
SamYaplenvm21:52
SamYaplelong day21:52
SamYapleim actually piping stdin for the script to python directly21:53
SamYapleso for you python wrapper you could do `echo something.py | python-wrapper` and it would not work, yes?21:53
*** jtriley has joined #kolla21:53
*** rhallisey has quit IRC21:55
openstackgerritMerged openstack/kolla: Add manila perms to /var/cache/manila  https://review.openstack.org/28030621:58
openstackgerritOpenStack Proposal Bot proposed openstack/kolla: Updated from global requirements  https://review.openstack.org/28094321:59
vhosakotSamYaple: build nova-compute alone worked21:59
vhosakotbuilding*21:59
SamYaplevhosakot: you can try reducing the number of build threads21:59
SamYaplebut without logs of why it failed i cant help22:00
vhosakotgood point... may be too many threads... will tune it22:00
SamYaplelarsks: daneyon if you set your ansible.cnf to have "pipelining=true" you dont need to do that bind mount!22:01
vhosakotwhen nova-compute failed to build, I scrolled up, and didn't see any logs other than "Parent image error'd with message "error""22:01
larsksSamYaple: I didn't need a bind mount anyway...because I was explicitly setting ansible_interpreter.22:01
SamYaplelarsks: you did22:01
SamYaplebecause by default it doesn't pipeline22:01
SamYapleit sends file to ~/.ansible/tmp22:02
larsksActually, no, I didn't!22:02
larsksThat worked without any bind mount magic.22:02
SamYapleyou must be using pipelining then22:02
SamYapleotehr wise it literally ships a file over for your interpretrt to run22:02
SamYapleyou should check your results22:02
larsksNNNNnnnnoooo...it just ran "sh -c /usr/local/bin/python-wrapper /home/centos/.ansible/tmp/...."22:03
larsksYeah, exactly.22:03
larsksIt runs that file using the value of ansible_python_interpreter.22:03
*** salv-orlando has joined #kolla22:03
SamYaplehmmm22:03
larsksOh wait, I think we are talking about different bind mounts.22:04
larsksI thought you were talking about a bind mount on /usr/bin/python?  But if you mean the one $HOME, then yeah, you're write, I did need trhat.22:04
larsksAnd I see how pipelining would avoid that.22:04
SamYapleyea im talking about home22:04
SamYaplegood22:04
SamYapleim not crazy22:04
larsksYou are also right.  In addition to being write.22:04
SamYaplelol22:04
*** cemason has quit IRC22:04
SamYaplebut with pipelining.... man this could do some things22:04
*** salv-orl_ has quit IRC22:05
SamYaplepipeliniging would work with your script too larsks if you use `cat /proc/$$/fd/0 | docker....`22:06
SamYapleotherwise you would have to use the interpreter straight22:06
*** cemason has joined #kolla22:06
larsksYah.22:07
*** aginwala has quit IRC22:08
*** mbound has quit IRC22:09
*** Serlex has quit IRC22:10
SamYapleok daneyon i think ive fleshed out all the angles here, even with pipelining you would still need to bind ~/.ansible/:/root/ansible/ into the container22:11
SamYaplebut this is entirely doable22:11
daneyonSamYaple Sweet. I'm still playing around with the options22:12
SamYaplethanks larsks for correnting me on the stdin stuff22:12
SamYaplei always forget -i opens stdin22:12
SamYapledaneyon: so you think this will work for you?22:12
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074922:15
*** Marga_ has joined #kolla22:16
*** Marga_ has quit IRC22:17
*** cemason has quit IRC22:17
*** Marga_ has joined #kolla22:17
*** vhosakot has quit IRC22:17
*** Marga_ has quit IRC22:18
*** Marga_ has joined #kolla22:18
*** vhosakot has joined #kolla22:19
daneyonSamYaple I think this will work. Big thanks to you and larsks22:19
SamYaplenah just larsks I would have told you no :)22:20
*** cemason has joined #kolla22:20
SamYaplelet me know how that works for oyu long term, im curious22:20
larsks\o/22:21
*** bmace has quit IRC22:23
*** bmace has joined #kolla22:24
*** tzn has joined #kolla22:25
*** dave-mccowan has quit IRC22:26
*** banix has quit IRC22:26
*** banix has joined #kolla22:27
*** jtriley has quit IRC22:28
*** banix has quit IRC22:29
*** tzn has quit IRC22:30
*** vhosakot has quit IRC22:30
*** vhosakot has joined #kolla22:31
*** macsz has quit IRC22:32
*** vhosakot has quit IRC22:34
*** vhosakot has joined #kolla22:34
*** bmace has quit IRC22:35
*** bmace has joined #kolla22:35
openstackgerritMerged openstack/kolla: Use variables to specify http or https when constructing URLs  https://review.openstack.org/27970722:37
*** rhallisey has joined #kolla22:38
*** cemason has quit IRC22:41
*** cemason has joined #kolla22:41
*** athomas has quit IRC22:46
*** dwalsh has quit IRC22:47
*** dims has quit IRC22:47
*** bmace has quit IRC22:49
*** haplo37 has quit IRC22:52
*** stvnoyes has quit IRC22:53
d_codeSamYaple: regarding the PCI passthrough, what needs to be hacked? is it just including the server API?22:54
d_codehttps://wiki.openstack.org/wiki/Pci_passthrough would suggest it’s already available in Nova22:55
d_codeand that https://github.com/yjiang5/pci_api just needs to be patched into the nova server API22:55
SamYapled_code: thats correct22:56
d_codek…so need to modify the ansible / dockerfile for the nova-server container?22:56
SamYaplethat and a bit of hacking on the pilicy file and you should be good22:56
SamYaplei dont think you do22:56
d_codewhich policy?22:56
SamYaplenova policy.json22:56
d_codeso where does the server side of the API go if not  in the container?22:57
SamYapleim confused22:57
SamYaplewhat do you mean?22:57
d_code:)22:57
*** unicell has quit IRC22:57
d_codeyjiang5/pci_api has 2 dirs…  client and server22:57
*** unicell has joined #kolla22:58
SamYapleoh for the cli stuff22:58
SamYaplei never used that22:58
d_codeclient obviously just goes against wherever you’re accessing the api22:58
SamYaplebut the client stuff would go on the host22:58
SamYaplethe server stuff needs to patch in the container22:58
SamYaplethis is what i meant by hacking22:58
d_codek…that’s what I was thinking22:58
d_codebut…idealy…could modify the build script for the container to happen at build time22:59
d_coderather than manually doing it each time22:59
SamYapleyea put it in the Dockerfile.j222:59
d_codeand submitting a patch to Kolla?22:59
SamYapleno22:59
d_codeis this something that could be merged in?22:59
SamYaplenope22:59
d_code:-(22:59
SamYapleunfortunately not22:59
d_codesad panda22:59
SamYaplenot until nova accepts it22:59
SamYapleafaik they havent22:59
d_codeyeah…the last commit on that repo was 3 years ago22:59
d_code /sigh22:59
SamYaplehoenstly that patch won't change much23:00
SamYaplethere is probably a current review out there someone is rebasing23:00
*** aginwala has joined #kolla23:00
d_codeinteresting…yeah..the patch is literally just providing the api…it’s hooking existing nova.objects.pci_device23:01
vhosakotSamYaple: should I have all 112 containers built successfully in order to run "kolla-ansible deploy"  ?23:01
d_codek…well…I’ll play with this and see if I can get it to work23:01
SamYapled_code: you know its been a while since ive gone down this path, nova may have merged it back before even 201523:01
vhosakotOr, is there a minimum set of containers needed to be built before running "kolla-ansible deploy".... if so, I will make sure that this minimum set of cotnaienrs are built23:02
d_codek…it isn’t in my nova client…so I’ll try to patch that first and see if it blows up :)23:02
SamYapled_code: yea see pci_passthrough_whitelist23:03
SamYaplei think the only thing not merged is the api23:03
SamYaplethe rest can be configured through nova.conf23:03
d_codek23:03
SamYaplei still hack in the api so i can use that on the fly23:04
d_codebe back tomorrow…. dinner time!23:04
*** cemason has quit IRC23:05
*** cemason has joined #kolla23:07
*** guillaume_ has quit IRC23:07
*** sdake_ has quit IRC23:09
*** daneyon has quit IRC23:10
openstackgerritSam Yaple proposed openstack/kolla: Launch VM in gate  https://review.openstack.org/28074923:13
vhosakotSamYaple: keystone failed with error  "ERROR:kolla.cmd.build:keystone:The command '/bin/sh -c yum -y install openstack-keystone         python-keystoneclient         httpd         mod_wsgi     && yum clean all' returned a non-zero code: 1 "23:19
vhosakotSamYaple: all the failed containers failed in the RUN command that installs the service .  is this an issue ?23:20
*** cemason has quit IRC23:23
*** cemason has joined #kolla23:25
*** inc0_ has joined #kolla23:27
*** jtriley has joined #kolla23:29
*** dave-mccowan has joined #kolla23:31
*** tpeoples_ has joined #kolla23:31
*** stvnoyes has joined #kolla23:33
*** jtriley has quit IRC23:34
*** mandre_ has joined #kolla23:35
*** ByPasS_ has joined #kolla23:35
*** another_larsks has joined #kolla23:36
*** clayton_ has joined #kolla23:36
*** inc0 has quit IRC23:37
*** ccesario has quit IRC23:37
*** ByPasS has quit IRC23:37
*** mandre has quit IRC23:37
*** clayton has quit IRC23:37
*** tpeoples has quit IRC23:37
*** larsks has quit IRC23:37
*** bmace has joined #kolla23:37
*** mandre_ is now known as mandre23:37
*** clayton_ is now known as clayton23:37
*** vhosakot has quit IRC23:37
*** ByPasS_ is now known as ByPasS23:37
*** tpeoples_ is now known as tpeoples23:40
*** ccesario has joined #kolla23:43
*** dims_ has joined #kolla23:44
ayoungSamYaple, the patch you need has been queueiong since 1:30 this afternoon:  https://review.openstack.org/#/c/280329/23:44
*** banix has joined #kolla23:50
*** sdake has joined #kolla23:53
*** yuanying has quit IRC23:56
*** yuanying has joined #kolla23:58
sdaked_code re above, we don't have a way in kolla to cusotmize policy files atm23:59
SamYapleayoung: what patch?23:59

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