Friday, 2015-07-31

*** jruano has joined #kolla00:00
*** achanda has quit IRC00:01
*** loth has left #kolla00:06
*** dims_ has joined #kolla00:08
*** inc0 has joined #kolla00:18
inc0good afternoon guys00:19
*** shadower has quit IRC00:23
*** shadower has joined #kolla00:23
*** bmace has joined #kolla00:26
bmacediga around?00:29
*** zhiwei has joined #kolla00:57
*** inc0 has quit IRC01:05
SamYaplehey guys!01:20
SamYapleguess who is not sleeping?01:20
SamYaple<--- this guy01:20
*** jasonsb has quit IRC01:20
bmacehi again SamYaple01:20
SamYaplehello01:22
SamYapleis jenkins all broked?01:22
bmaceSamYaple sort of looks like it, don't see many V+1s lately01:25
*** unicell has quit IRC01:34
*** erkules_ has joined #kolla01:59
*** erkules has quit IRC02:01
*** jtriley has joined #kolla02:09
*** jasonsb has joined #kolla02:25
*** vinkman has quit IRC02:26
*** openstackgerrit has quit IRC02:31
*** openstackgerrit has joined #kolla02:31
*** achanda has joined #kolla02:42
*** jtriley has quit IRC02:49
digabmace: Hi03:17
SamYaplehi03:17
digaSamYaple: Hi03:19
SamYapleo/03:19
digacouldn't attend the Mid-cycle due to workload03:19
bmacehey diga, before i got to deep into it i wanted to ping you about the kolla-ansible command and see if you had done any work on it yet.03:20
bmacei got start working well in my environment and i'm looking at what it will take to do some of the other commands we talked about supporting at the mid-cycle03:21
bmacewell, deploy03:21
bmacewhich does a start03:21
SamYapleyea bmace to do some of the stuff we talked about at the mid-cycle is going to require playbook tweaking03:21
bmaceyup, i'm reading an ansible book :)  looks like a decent amount of tweaking based on how it is implemented right now03:22
digabmace: I think you can start with deploy https://blueprints.launchpad.net/kolla/+spec/kolla-ansible-script03:22
bmacediga ok, i wanted to make sure you didn't have any work in flight before i pushed something in or spent much time on it.03:23
bmacei'll probably get deploy in asap, and put some doc in the script related to the other commands we talked about supporting.  teardown, deployconfig, start, stop <host>, etc.03:23
digasure bmace03:23
SamYaplebmace: nah i dont think so03:24
SamYapleitll be simple03:24
bmacein case you are interested diga the list is from https://etherpad.openstack.org/p/liberty-kolla-midcycle and starts on line 10903:24
SamYaplewe can not use tags and call the config.yml directly03:25
SamYaplemaybe03:25
SamYapleidk03:25
SamYaplei havent thought about it03:25
bmaceyeah, the way we are doing things now makes it as non-obvious as possible, from an ansible point of view, as far as i can tell.  everything seems made to go in one direction, up, at least on any host defined.  you can of course mess with your inventory to make stuff go down, but i think we had not wanted that, at least on stop <host> for example.03:26
bmacehunting down the flow of things is, interesting, but maybe when i get better w/ ansible it won't be quite as bad.03:26
SamYaplei am doing non-standard ansible things to make dev easier. I want to use ansible, but we are Kolla and ansible isnt required03:27
SamYaplewe start getting to fancy with ansible then kolla requires it03:27
digalet me go through the etherpad link bmace03:27
SamYaplei dont want that03:27
*** echoingumesh has joined #kolla03:27
bmacei am not sure those things need to be mutually exclusive.  being able to deploy w/ ansible and being able to deploy independently, yet having reasonably understandable ansible flow.03:28
*** achanda has quit IRC03:28
SamYaplewe have reasonable ansible flow03:28
SamYaplethe _only_ wierd bit is the common playbooks in the upper directory03:29
SamYaplethats just to respect DRY03:29
*** diogogmt has joined #kolla03:30
bmacethe main bits that you actually activate from ansible-playbook end up having pretty much no information about flow in them, which is fine, it just links via tags to other stuff.  most of the other ansible playbooks i have looked at so far had far more obvious flow, but that was probably because they were simpler.03:31
SamYaplewhat do you mean?03:31
*** dims_ has quit IRC03:33
bmacei mean looking at what we have right now and knowing the flow of what files are called from where is pretty non-obvious.  again, i am still reading up on ansible, but it looks to be possible to write playbooks in a way that it is more obvious what is going on.03:33
bmacei guess we end up getting into the main playbooks, from somewhere, which include all the config, start, etc.. and that causes all those to get kicked off, but as far as i can tell we don't document flow anywhere, probably because if you know a lot about ansible, maybe it is obvious.03:34
SamYaplei dont think you have gotten to the part about roles03:35
SamYapleroles are the future and this is very obvious to follow the structure03:35
*** diogogmt has quit IRC03:37
SamYaplebmace: http://docs.ansible.com/ansible/playbooks_roles.html03:40
SamYaplethats what you need to read03:40
SamYaplespecifically the secont on roles03:40
SamYaplesection03:40
*** sdake_ has joined #kolla03:42
*** echoingumesh has quit IRC03:42
*** sdake has quit IRC03:43
*** sdake_ has quit IRC03:45
*** sdake has joined #kolla03:45
bmacehrm, then to do some sort of conditional like a tear down or take down the containers on a specific host, you would prefer a different playbook w/ different roles, or to pass in conditionals on the ansible-playbook command line?03:45
SamYaplebmace: we can't have 'site.yml' for everything03:47
SamYapleI am perfectly fine with a destroy.yml that we can pass values03:47
SamYapleso it will be a seperate playbook03:47
SamYapleat that point its easy to make it do anything you want03:47
bmacesure, at least it would be the same inventory / host list, for the teardown.03:49
*** coolsvap|away is now known as coolsvap03:49
SamYapleyea thats not a problem at all to be honest03:51
*** sdake_ has joined #kolla03:51
SamYaplethe real issue is the configs since we have the defaults/main.yml03:51
SamYaplei can make it work, but im not sure best practice03:51
*** sdake has quit IRC03:52
bmacethat is the odd thing about ansible, where the goal is to reflect a final state, but for a config re-push and restart, we are really sort of in the end state already, which is having all the containers running on the hosts we want.   doing certain programmatic flow sorts of things just feels, off, so far.03:56
SamYapleyea youll get over it bmace03:58
SamYapleits still better than puppet and chef03:58
SamYaplebut i totally get whatyou mean03:59
SamYaplebmace: you do know how to do it though, right?04:01
bmaceyeah, i love how light it is compared to puppet / chef04:01
SamYapleyou can either check the configs match and use that true/false to rekick the container or you can remember that the configs changed and use that info04:02
bmacei like the idea of using the checksum to only re-start the containers that need it04:02
SamYaplebmace: well the containers dont restart now...04:05
SamYaplea config refresh wont restart _all_ containers04:05
SamYaplethe current code only restarts "different than the desired end state containers"04:05
bmaceright, so it would need to track, if we have the "change on config update" bit set, then also restart the container, since we want to be able to re-push configs without restarts, i assume04:09
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Fedora - Install from source for Neutron  https://review.openstack.org/20770904:15
bmacei'll play around with things.  i set args for the inventory / playbook file on the kolla-ansible deploy command.  maybe i'll update the docs and toss that in just so it is that much easier to get folks going w/ ansible.  also, noticed the /etc/kolla stuff was hard coded in a bunch of files.  any issues you know making that variable like we have so many other things?04:18
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Fedora - Install from source for Magnum  https://review.openstack.org/20771004:21
*** sdake_ has quit IRC04:21
*** sdake has joined #kolla04:21
sdakeevening folks04:24
bmacehola04:25
SamYapleevening sdake04:27
SamYaplejenkins seems to not be +104:27
*** sdake has quit IRC04:28
*** sdake_ has joined #kolla04:28
*** sdake has joined #kolla04:31
*** sdake_ has quit IRC04:31
*** sdake_ has joined #kolla04:35
*** sdake has quit IRC04:36
*** sdake_ has quit IRC04:41
*** sdake has joined #kolla04:42
*** sdake has quit IRC04:44
*** sdake has joined #kolla04:45
*** sdake has quit IRC04:47
*** sdake has joined #kolla04:47
sdakeonly 6 purples left ;-)04:49
bmacenot sure if you know, there is no kollaglue/centos-rdo-haproxy so it folks are just playing with kolla out of the box without doing their own local image build ansible won't work without some tweaking (like yanking haproxy)04:51
sdakewhat we reallly need is documentation that says to build your own image04:51
sdakeandgive up on keeping the upstream dockerhub updated04:51
sdakebecause we re doing a poor job of it and its a manual process04:51
bmaceyeah, we do fall behind pretty quickly, based on how quickly the code advances.  not that we couldn't probably push up like once a day and overwrite latest, but we would need some resources and a script to do that.04:52
bmacedepending on how onerous that is, it is sort of nifty to have them up there for people to pull.  i think it easier to set up a system to run pre-built containers than to get container builds working.04:53
SamYaplebmace: i think the built contaienrs will be fine for "intro to kolla" and testing04:56
SamYaplebut if youre really going to use Kolla, you should be building your own image04:56
SamYapleunless we can push after every commit04:56
sdakesamyaple bmace's pont is there is no haproxy container04:56
sdakeso kolla is unusable from the registry atm04:56
SamYaplesdake: there no lots of containers04:56
SamYapleit hasnt been usable for over 2 months04:57
bmacei don't think every commit is necessary.  i think daily would be perfectly sufficient, even every other day.04:57
SamYaplebmace: but it would need to be every commit04:57
SamYapleotherwise it might break during a day04:57
sdakeideally it would be a gated version04:57
sdakewhich mean master, since master is gated04:57
sdake;-)04:57
SamYapleuntil the gated version, people should be expected to build thier own04:58
sdakebut our master gate isn't voting04:58
bmacei am just saying daily would be considerably better than what we have now, which is haphazard04:58
SamYaplebmace: no we need to push at the L1 L2 L3 stages04:58
bmaceif the images we have up on dockerhub are unreliable, having them there at all is misleading04:58
SamYaplethat way it works04:58
SamYapleyou can checkout L2 and have the code work04:58
SamYapleyou can expect master to work with old images04:58
sdakemaster wont work with l1 images samyaple04:59
sdakethat only really applies after l204:59
SamYapleit would have had we pushed l104:59
SamYaplei mean git checkout L205:00
SamYapleeven after we push L2, master cant be expected to work with the dockerhub images05:00
SamYaplebut the L2 tag should05:00
bmacewe might as well turn off the pull from docker hub by default, other tagged versions, if latest isn't going to ever work reliably in development.05:00
bmacethe current behavior is a likely turn off to people trying it out for the first time.05:01
SamYaplebmace: but you would expect a private registry for your built images05:01
sdakesamyaple bmace means peopel giving it a 10 minute spin05:01
sdakenot people th are actually going to use it long term05:01
SamYaplei think this gets solved when we package kolla05:01
SamYaplewe push at l2 and have pip install kolla==L205:02
SamYaplepeople who want to devel can git checkout05:02
sdakereally i think what bmace wants is l2-latest vs l205:04
bmacei think the 10 minute spin actually functioning matters, even for people checking it out for something to contribute to.  we can definitely say have a packaged kolla that works well, and that is what a certain set of people use, and in dev we always build images, and make sure we don't have stuff set up to by default pull from dockerhub05:04
sdakethe 10 minut espin is important05:04
SamYapleif you git checkout you should be expected to build05:04
sdakeagree we need to make that happen05:05
SamYaple10 minute spinup means you use a package05:05
SamYapleor you can git checkout the L2 tag05:05
sdakesamyaple it could happen vi a viarety ways not just packaging05:05
SamYaplelike i said, the L2 tag05:05
SamYapleits going to break daily even if we push daily in master05:05
sdakeit will braek until our gate is voting05:06
sdakean we can't make oru gat evoting until rdo has ha in their registry of rpms05:06
sdakerather their yum repos05:06
*** vinkman has joined #kolla05:06
*** coolsvap is now known as coolsvap|away05:08
sdakebmace if you make a script that canbe run from crontab that git pulls master, i'll lpony up the 50 bucks a month for a rackspace account to push from05:09
sdakegit pulls master builds source builds binary and pushes and then cleans up05:09
bmacei'll have to take a look at the dev guide.  for now maybe it just comes down to making sure people are always building their own images.  code right now that defaults to doing pulls from dockerhub is problematic.05:09
bmacei'm torn.  i don't disagree with sam that, even with daily pushes it is likely to be broken any given day, and for people playing we may be better off just having an l2 / l3 / etc.. and otherwise we just make sure we, as much as possible, document / force people to build the images and let them know that dockerhub images used against master are almost guaranteed to fail.05:13
bmaceonce we have better tests and better gating, being able to push something out that is known to work will be reasonable, but i don't think that is super close.05:14
sdakelets make an effort to get dockerhub rolling05:15
sdakebut I need someone to write a build script05:15
sdakei am a bit busy atm and cant tackle it myself05:15
sdakebut I can do the setup of the env05:15
*** coolsvap|away is now known as coolsvap05:17
sdakewe will push l1, l2, l305:17
sdakebut also l1-latest and l2-latest and l3-latest05:17
sdakel3-latest wil be master for example05:17
sdakein 2-4 weeks i will have gig-e at my house05:20
sdakeand can push from there05:20
sdakeit takes probably about an hour05:20
SamYaplesorry my internet connection tropped05:22
sdakeuber refunded my trip yay :)05:23
SamYaplewhat my point was is if you push all the images. then someone changes start.sh. those images are broke until you push again05:23
SamYapleyou can't expect master to be able to deploy built iamges05:24
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Fedora - Install from source for Ceilometer  https://review.openstack.org/20772305:24
SamYapleyou _can_ expect tags to work05:24
SamYapleso you either pip install kolla, or git checkout --tag05:24
SamYaplethose two should "just work"05:24
sdakeyes i think we should want master to be tire-kickable as well tho05:25
sdakeI get what your saying about tags, we should definatey do that05:25
SamYapleits not possible05:25
SamYapleno until the gate can push05:25
sdakeits possible just not reliable05:25
SamYaplewell then it sounds like we are currently doing it05:25
SamYapleif reliable isnt a requirement then were there05:26
sdakewe are not doing it because nobody has written a script to do it daily05:26
sdakesemi-reliable is a requirement ;)05:26
sdakeas in we expect it to work some of the time05:26
sdakeright nwo it doen't work any of the time05:26
SamYaple100% reliable is tags and packages05:26
SamYaplewe agreed no latest tags at the mid-cycle so what would these even be called05:26
sdakewe can warn people in the documentation that th latest tag in dockerhub is not a reliable exeuction method but may or may not work ;)05:28
SamYaplebut we agreed no latest tag unless it always works05:28
*** jruano has quit IRC05:29
sdakei dont recall that agreement but it was a  busy two days :)05:29
SamYapleif there is no latest tag then its clear "ah i need to build the images" if shit starts downloading then breaks it makes Kolla seem broken05:29
sdakeya i tend to agree with you sam, a git pul from the tag and docker pull from the tag is the way to go - then it works 100% of the time05:30
sdakeand if people want master to work they have ot build images05:30
sdakelets just document it05:30
SamYapleKolla is super reliable by the design and using images. I dont want to mix in this "sometimes reliable" mess05:30
sdakebecause now nobody knows this information outside the dev team05:30
SamYaplesounds good05:30
SamYaplei totally get that05:30
*** achanda has joined #kolla05:30
sdakei'll do that doc fix05:31
sdakeeither tonight or tomorrow morning05:31
SamYapleso for L2 we need to change the default pull tag to liberty2 or something and push taht tag up05:31
SamYapletest that then tag the commit it came from05:31
sdakedo we have pip registered for kolla?05:33
*** sdake has quit IRC05:35
SamYapleha! as if05:35
SamYaplelarsks: help us05:35
SamYapleive personally never made a package for pip05:35
SamYaplelarsks can probably hammer it out in a minute05:36
SamYapleI know it very basic, just never done it05:36
*** sdake has joined #kolla05:41
sdakeok i just registered kolla 0.0.1 with pypi05:47
SamYapleawesome!05:47
sdakenow we need an install05:47
sdake;-)05:47
SamYaplelike packged and all?05:47
SamYapleoh05:47
sdakeno not packaged05:47
SamYapleok yea that shouldnt be hard05:47
SamYaplei just need some cycles for it05:48
SamYaple(or hopefully larsks saves the day, he isn't busy at all)05:48
sdakesamyaple you ahve a bunch of things in needs code review ont he launchpad tracker for l205:49
sdakeare any of those finished?05:49
sdakei was pretty sure aio worked for example05:49
sdakeand the core services are done right?05:49
SamYaplein review05:49
SamYaplei need keepalived merged05:50
SamYaplewere good past that05:50
sdakesamyaple can yo update the states on your blueprints if they are implemented then05:51
sdakeor are you waiting on keepalived?05:51
SamYaplewaiting on keepalived05:51
sdakemandre you around?05:51
coolsvappbourke, around?05:54
*** coolsvap is now known as coolsvap|away06:05
*** coolsvap|away is now known as coolsvap06:13
*** unicell has joined #kolla06:13
*** unicell1 has joined #kolla06:24
*** unicell has quit IRC06:25
openstackgerritMerged stackforge/kolla: Cinder requires the automaton package to be installed  https://review.openstack.org/20669606:39
*** vinkman has quit IRC06:51
*** coolsvap is now known as coolsvap|away07:02
*** coolsvap|away is now known as coolsvap07:10
*** achanda has quit IRC07:16
*** erkules_ is now known as erkules07:27
*** erkules has quit IRC07:27
*** erkules has joined #kolla07:27
*** gfidente has joined #kolla07:36
openstackgerritSam Yaple proposed stackforge/kolla: Add linuxbridge as option to ansible  https://review.openstack.org/20776007:50
SamYaplesdake: ^ that configuration wise should be working for linuxbridge07:50
SamYaplei cant get it to work though because i dont know how to setup linuxbridge07:50
SamYaplein ovs i would create br-ex and add the neutron_interface to br-ex07:51
SamYaplei dont know what to do with this07:51
*** juggler_ is now known as juggler08:10
pbourkecoolsvap: morning08:24
*** athomas has joined #kolla08:35
coolsvappbourke, did you run into issues for nova from source?08:36
coolsvaprelated to lvm08:36
coolsvaphttps://bugs.launchpad.net/kolla/+bug/148007708:36
openstackLaunchpad bug 1480077 in kolla "nova install from source image fails for lvm" [High,Confirmed] - Assigned to Swapnil Kulkarni (coolsvap)08:36
pbourkecoolsvap: not that I recall. Is then when trying to boot an image?08:40
coolsvapno while building the image from Dockerfile08:40
coolsvapi was testing it with fedora08:41
coolsvapit failed so i checked for centos as well08:41
coolsvapits failing there as well08:41
openstackgerritPaul Bourke proposed stackforge/kolla: Implement Swift Containers  https://review.openstack.org/20217108:41
pbourkestrange no I didnt get that08:41
coolsvappbourke, np I am trying to see whats wrong08:42
pbourkeok thanks08:42
openstackgerritMerged stackforge/kolla: Add keepalived to ansible  https://review.openstack.org/20557008:50
openstackgerritMerged stackforge/kolla: Forces metadata to bind to single interface  https://review.openstack.org/20580208:50
openstackgerritMerged stackforge/kolla: Add a doc for Cinder  https://review.openstack.org/20759708:58
openstackgerritMerged stackforge/kolla: Rename role name to service name  https://review.openstack.org/20579809:03
openstackgerritMerged stackforge/kolla: Properly use groups throught Ansible  https://review.openstack.org/20599909:04
*** dwalsh has joined #kolla09:07
*** dwalsh has quit IRC09:12
*** dwalsh has joined #kolla09:13
*** dwalsh has quit IRC09:52
openstackgerritVladislav Belogrudov proposed stackforge/kolla: Add missing slash if docker registry is specified  https://review.openstack.org/20746310:03
coolsvappbourke, got the reasons for failure, https://blueprints.launchpad.net/nova/+spec/consolidate-libvirt-fs-volume-drivers10:05
coolsvapwith this bp the configuration options are chaging, but the imports are not changed10:05
*** athomas has quit IRC10:14
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Temporary change the nova tar url  https://review.openstack.org/20782510:37
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Fedora - Install from source for Nova  https://review.openstack.org/20782710:38
*** athomas has joined #kolla10:40
openstackgerritMerged stackforge/kolla: Add build from source for gnocchi  https://review.openstack.org/20595210:50
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Neutron  https://review.openstack.org/20770910:53
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Magnum  https://review.openstack.org/20771010:54
*** zhiwei has quit IRC10:57
*** dims_ has joined #kolla11:04
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Fedora - Install from source for Horizon  https://review.openstack.org/20783811:07
openstackgerritHarm Weites proposed stackforge/kolla: Vagrantfile and docs  https://review.openstack.org/20423811:14
*** coolsvap is now known as coolsvap|away11:39
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Ceilometer  https://review.openstack.org/20772311:40
*** rhallisey has joined #kolla12:00
openstackgerritRyan Hallisey proposed stackforge/kolla: Fix some spelling and formatting errors in the Cinder doc  https://review.openstack.org/20785912:17
*** thumpba has joined #kolla12:28
*** thumpba has quit IRC12:33
*** athomas has quit IRC12:35
*** coolsvap|away is now known as coolsvap12:36
openstackgerritRyan Hallisey proposed stackforge/kolla: Fix some spelling and formatting errors in the Cinder doc  https://review.openstack.org/20785912:38
*** athomas has joined #kolla12:40
*** coolsvap is now known as coolsvap|away12:43
*** coolsvap|away is now known as coolsvap12:45
openstackgerritPaul Bourke proposed stackforge/kolla: Fix missing quotes in tools/genenv  https://review.openstack.org/20788813:08
*** coolsvap is now known as coolsvap|away13:09
*** coolsvap|away is now known as coolsvap13:16
*** gfidente has quit IRC13:22
*** gfidente has joined #kolla13:26
*** gfidente has joined #kolla13:26
*** coolsvap is now known as coolsvap|away13:30
*** jtriley has joined #kolla13:34
*** diogogmt has joined #kolla13:37
pbourkeI think keystone may be broken13:45
pbourkedoesn't seem to like use_stderr anymore13:46
*** coolsvap|away is now known as coolsvap13:48
*** pbourke has quit IRC13:51
*** coolsvap is now known as coolsvap|away13:51
vbelthe log goes to apache log13:54
vbelGood morning/ evening,  ubuntu server and oracle linux fail to run Kolla containers that use 'su' because of https://github.com/docker/docker/issues/589913:55
*** pdb has joined #kolla13:56
vbelAt the same time su can be replaced with sudo and the workaround works quite well. Shall we replace it for all or just ubuntu/ol images? https://bugs.launchpad.net/kolla/+bug/148020913:56
openstackLaunchpad bug 1480209 in kolla "containers fail to run commands with 'su'" [Undecided,New] - Assigned to Vladislav Belogrudov (vlad-belogrudov)13:56
vbelthis was the reason ol-source-keystone did not populate its database - uses db sync via su13:57
vbeland later on it tried to load some federation code with non-existing xmldsig13:58
rhalliseyoh interesting13:58
rhalliseyya put up a patch to fix that13:58
vbelwill do, no objections for sudo? :) I tried this earlier in our containers because we met the same problem (--net=host containers cannot 'su')13:59
rhalliseyI think it will be fine14:02
*** diogogmt has quit IRC14:06
*** diogogmt has joined #kolla14:17
*** jruano has joined #kolla14:21
*** prad has joined #kolla14:26
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Nova  https://review.openstack.org/20782714:34
openstackgerritVladislav Belogrudov proposed stackforge/kolla: Containers with host networking fail to 'su' on some kernels  https://review.openstack.org/20792514:38
pdbvbel: I seem to be getting this xmldsig problem now14:43
pdbvbel: using config-internal, tables seem to be populated fine14:44
*** coolsvap|away is now known as coolsvap14:44
openstackgerritMerged stackforge/kolla: Temporary change the nova tar url  https://review.openstack.org/20782514:45
vbelpdb: strange, why could not we get it before? Because it was by itself (not in apache)14:46
vbel?14:46
pdbvbel: no idea whats changed :(14:46
vbelI start disliking xmldsig because I could not pip install or compile it :(14:47
pdbthings not going our way today14:47
pdbit seems to be in the ol image only, though can't confirm as centos is failing with another error around use_stderr14:48
pdbvbel: also on your sudo change, is the sudo command available in all images?14:48
vbelit should - will check. If not - will install it14:49
pdbwell that was something I was always a little unsure of, as I know one or two images use sudo for some other things14:49
pdbbut when I spin up a centos-rdo-base container for example I get sudo not found14:49
vbelI am adding sudo to bases14:55
vbelwhere necessary14:55
SamYaplemorning14:55
SamYapleyay! thanks guys you merged my patchs14:56
SamYaplelife is easier14:56
vbelmorning14:57
rhalliseySamYaple, hey having some trouble with getting my allinone ansible going14:58
rhalliseyansible-playbook -i inventory/all-in-one -e ../etc/kolla/defaults.yml -e ../etc/kolla/globals.yml -e ../etc/kolla/passwords.yml site.yml14:58
rhalliseyI'm not able to find my env-vars with that14:59
SamYaplerhallisey: i would recommend absolute paths, and I don't recommend using the etc directory in the repo since you really shouldnt be tweaking those files15:00
SamYaplebut can you expand on what you mean by that?15:00
openstackgerritHarm Weites proposed stackforge/kolla: Vagrantfile and docs  https://review.openstack.org/20423815:00
rhalliseyI get: One or more undefined variables: 'node_config_directory' is undefined15:00
openstackgerritSam Yaple proposed stackforge/kolla: Add Ansible support for Heat  https://review.openstack.org/20552815:01
vbelI tried -e @../etc/kolla  without luck too because it starts asking for /etc/kolla15:01
SamYaplelike I said, it expects this stuff in /etc/kolla i dont know how well realitive paths are going to work15:01
SamYaplerhallisey: but you do need @15:01
SamYapleansible-playbook -e@/etc/kolla/defaults.yml -e@/etc/kolla/globals.yml -e@/etc/kolla/passwords.yml -i ~/kolla/ansible/inventory/all-in-one ~/kolla/ansible/site.yml15:01
SamYaplethats what I use15:02
rhalliseykk15:02
bmacebut then keep in mind you still need all that .conf stuff still in /etc/kolla15:02
SamYaplebmace: thats what i mean15:02
bmacethe "generated" ones end up in /opt/kolla on the machines running containers right?  is someone messing with the variable and setting it to /opt/kolla your concern?  otherwise the files i see it in certainly support variable substitution.15:04
SamYaplebmace: the destination host is all variable substituationed out15:04
SamYapleno issue there15:04
SamYaplethe deploy host has some expectations15:04
bmaceright, at this point all the expectations are defined in tasks, which would allow for substitution of /etc/kolla with something else, like in-place from your dev environment.15:06
SamYaplesure, but we probably should be testing with the defaults15:07
SamYaplei mean if you think of Kolla as an application /etc/kolla is the place you want to store confs15:07
pdbvbel: https://bugs.launchpad.net/keystone/+bug/147579615:07
openstackLaunchpad bug 1475796 in Keystone kilo "using pysaml2 version 3.0.0 breaks keystone in kilo release 2015.1.0" [High,Fix committed]15:07
SamYaplepdb: o/15:08
*** pdb is now known as pbourke15:08
pbourkeSamYaple: morning15:08
vbelpdb: cool! Someone got it right ;)15:08
SamYapledoes anyone here understand the setup for linuxbridge?15:08
pbourkevbel: yeah. now to decide which fix we want to take for kilo15:09
SamYaplefor OVS i create br-ex and add the "neutron_interface" to that bridge. what do I do with linuxbridge?15:09
harmwSamYaple: nothing, linuxbridge doesn't require configuration, or only very little15:09
harmwIll have a look tonight15:09
harmwbut why bridge, if we have OVS?15:10
pbourkevbel: should we be using stable/kilo rather than the 2015.1.0 tag?15:10
pbourkeseems the fix is already merged to stable/kilo15:11
pbourkebut the tag isn't going to change15:11
pbourkeharmw: I retested your vagrant work earlier, all good!15:11
harmwgreat!15:11
pbourkeharmw: the only thing I dont really like is the bridge selection :/15:12
vbelpbourke: yes, looks like stable/kilo is the way to go. Will we have 2015.2.0 ?15:12
SamYapleharmw: we support ALL the things15:12
harmwok SamYaple15:12
pbourkevbel: yeah maybe they retag every so often15:12
harmwpbourke: you mean the specific interface or the fact that it's a public net?15:12
harmwthe user may just change that ofcourse15:13
pbourkeharmw: just the fact that when I type vagrant up it stops and asks to choose an interface15:13
harmwah15:13
pbourkethe confusion start to appear on my face15:13
harmwyes that sucks, and that's why there is a TODO listed :)15:13
pbourke:)15:13
harmwthat realy, realy, realy sucks indeed15:13
vbelpbourke: http://tarballs.openstack.org/keystone/keystone-2015.1.1.tar.gz of July 28, wonder if it is there15:13
pbourkevbel: Id be surprised15:14
SamYapleharmw: so youre saying it magically warps L2 to the "neutron_interface"? it does not seem to be adding that interface to a bridge15:14
SamYaplebtw did you guys see the big tent application? A comment reads 'Definitely "one of us"'15:15
SamYaple:D15:15
pbourkeharmw: that's why I was kind of hinting could we get away with just another host only network for that adapter. but Im guessing its not so easy?15:15
pbourkeSamYaple: :)15:15
harmwSamYaple: ill take a look tonight, ok :p15:16
harmwbig tent, woohoo!15:16
harmwpbourke: yea, well my thing was I wanted a public net to get by with testing float stuff and just be 'fully connected' on that end15:16
pbourkeI think we need 10 votes?15:16
SamYaplepbourke: only 715:17
harmwyou could always edit the Vagrant file btw15:17
*** dims_ has quit IRC15:17
harmwsub-optimal, but still15:17
vbelpbourke: https://review.openstack.org/#/c/184598/ included in 2015.1.115:17
*** dims_ has joined #kolla15:17
vbelso we should rebase :)15:17
pbourkevbel: cool. just bump the tag in our buildconf no?15:18
*** blahRus has joined #kolla15:18
vbelyes, we can try15:18
pbourkedoes this tag exist for every project?15:19
vbellooks like that15:19
vbel2015.1.1 tarballs of July 28 for several projects15:20
SamYapleyou guys keep in mind15:20
SamYaplein Liberty everyone is independant tagging15:20
SamYaplethat wont match for Liberty15:20
SamYaplemake it configurable per project so we can but per project15:20
*** dims_ is now known as dimsum__15:21
vbelok for me15:21
*** pbourke has quit IRC15:30
*** pdb has joined #kolla15:31
*** pdb is now known as pbourke15:32
openstackgerritVladislav Belogrudov proposed stackforge/kolla: Add missing slash if docker registry is specified  https://review.openstack.org/20746315:33
*** daneyon has joined #kolla15:36
*** jruano has quit IRC15:37
openstackgerritVladislav Belogrudov proposed stackforge/kolla: Add missing slash if docker registry is specified  https://review.openstack.org/20746315:38
pbourkequick question on the above15:41
SamYapleshoot15:42
pbourkecould we fix it in globals by having:15:42
pbourkedocker_registry:15:42
pbourkedocker_registry: "{{ docker_registry ~ '/' if docker_registry else '' }}"15:42
SamYaplebut... thats where we are setting docker_registry15:42
SamYaplei want to keep that stuff hidden from view15:43
pbourkefair enough15:43
pbourkejust checking :)15:43
vbelone thing on styling - do we use spaces instead of tabs everywhere?15:47
rhalliseyyikes the dependencies are killing me :(15:47
rhalliseyfrom oslo_i18n import _lazy     ImportError: cannot import name _lazy15:47
rhalliseyhaving trouble with this one ^15:47
vbele.g. in Dockerfiles I see tabs ..15:48
SamYaplevbel: tabs are baaaad15:48
rhalliseyvbel, spaces15:48
vbelok, then will correct RHEL one :)15:49
SamYaplevbel: spaces gaurantee formatting remains the same no matter your system15:49
SamYapleassuming you use a fixed-width font15:49
*** Slower has joined #kolla15:49
vbelmy vim is 4 space tab replace mode too15:49
vbelthanks!15:49
SamYaplemine too15:49
rhalliseySamYaple, is it unsanitary to do the allinone ansible on a single baremetal host?15:50
*** Slower has quit IRC15:50
SamYaplerhallisey: define "unsanitary"15:50
SamYapleits mostly how i dev15:50
SamYaplethen i test against both that and multihost15:50
rhalliseyI'm just trying to get AIO going on my machine15:51
pbourkedoes that strike you as a little ironic given its one of the reasons we use docker?15:51
rhalliseyI don't need a vm or anything right?15:51
rhalliseyjust set the ips to the hosts15:51
rhalliseypbourke, it does15:52
pbourkeI guess config-internal gives you the fully isolated approach15:52
pbourkeI use VMs for all dev but not required15:52
pbourkerhallisey: when you come to try multinode check out harmw Vagrantfile work15:53
*** Slower has joined #kolla15:53
*** jtriley has quit IRC15:53
rhalliseypbourke, kk. I gota get a simple AIO going first15:53
pbourkemakes sense15:53
rhalliseystuck dependency limbo15:54
pbourkeactually, you could still use the vagrantfile15:54
pbourkeand just do AIO on the operator node15:54
SamYaplerhallisey: correct anything works no vm or anything15:54
openstackgerritVladislav Belogrudov proposed stackforge/kolla: Containers with host networking fail to 'su' on some kernels  https://review.openstack.org/20792515:54
SamYaplethe docs need updates now that we have keeplaived and haproxy landing15:54
rhalliseySamYaple, have you seen from oslo_i18n import _lazy     ImportError: cannot import name _lazy15:54
rhalliseyno idea how to get around that15:54
SamYaplerhallisey: old pip?15:55
SamYaplei havent seen it but i suggest pip and wheels15:55
SamYaplepip install -U pip15:55
SamYaplepip install -U wheel15:55
SamYapleseems to be the root of alot of fedora problems15:56
rhalliseySamYaple, are you using fedora or ubuntu?15:57
SamYapleubuntu15:57
SamYaplewith the centos images15:57
SamYaplebut i have tested on fedora15:57
SamYaplewell F2115:57
pbourkecentos works well as a host also15:58
*** coolsvap is now known as coolsvap|away16:02
sdakemorning16:10
SamYaplemorning sdake16:11
SamYaplemy stuff merged. huge load off16:11
*** ashuk has joined #kolla16:13
sdakexwe got 2 mor erollcall votes ;)16:19
sdakeyay victory :)16:19
SamYaplesdake: i posted it in the channler earlier16:20
SamYaple15:15 < SamYaple> btw did you guys see the big tent application? A comment reads 'Definitely "one of us"'16:20
*** unicell has joined #kolla16:22
*** unicell1 has quit IRC16:23
*** ashuk has quit IRC16:25
*** sdake has quit IRC16:26
*** sdake has joined #kolla16:37
*** vinkman has joined #kolla16:37
pbourkelong weekend here in Ireland, gone till Tuesday16:39
SamYaplepbourke: sounds like youll be working on kolla till monday16:41
SamYapleeh16:41
SamYapleeh16:41
sdakebeer-o-holiday ;)16:41
pbourkesdake's version might be more accurate16:41
SamYapleso normal day in ireland?16:42
rhalliseyis it Arthur day? I celebrate that :)16:42
pbourkeha no they had to cancel that16:42
rhalliseysince I love Guinness16:42
rhalliseythey canceled that O.o16:42
pbourkeit was turning into patricks day 2.016:42
SamYaplevbel have you tested https://review.openstack.org/#/c/207925/ across the project?16:43
vinkmanpbourke: so what's wrong with that??? Isn't 2.0 better than 1.0 :D16:43
bmacemaybe wait for 2.1? :)16:44
sdakehey i heard they run guiness in the streets in pipes - is it true16:44
pbourkelol dont think so16:45
bmacethey had it in every pub i went to in england, but i don't think i ever saw anyone order it.16:45
sdakei mean under the streets16:45
vinkmanso do I just bring my own tap ?16:45
pbourkewe have better beer here now :)16:45
sdakenothing like an irish guiness16:46
rhalliseymy favorite16:46
vinkmanpbourke: As long as you don't say Bud ;)16:46
sdakeeven though its a "generic" drink in ireland, there i something about it there16:46
sdakefresher or soething16:46
pbourketrade you guys some guinness for west coast ipa anytime16:46
sdakethe us has alot of fine beers no dobut about it16:46
*** jasonsb has quit IRC16:48
*** jasonsb has joined #kolla16:48
*** vbel has quit IRC16:48
*** vbel has joined #kolla16:49
*** athomas has quit IRC16:53
*** jasonsb has quit IRC16:53
*** kevsi has quit IRC16:57
sdakefor our core members that may not get budget for meeting in Tokyo summit17:06
sdakethere is a travel assistance program that the foundation funds your hotel+airfare17:06
sdakeyour on your own for food/beer17:07
sdakebut its better then not goign :)17:07
sdakehttps://wiki.openstack.org/wiki/Travel_Support_Program17:08
*** achanda has joined #kolla17:09
harmwsdake: now thats nice!17:17
harmwthough Tokyo is no option, it's baby time by then :) more or less17:18
sdakeharmw snce your independent i suspect you would be a non brainer for the foundation to support travel wise17:18
sdakewell congratulatons!17:19
sdakeboy or girl?17:19
harmwboy, okt. 15 is due date17:19
sdakeya hard to abandon the wife during that one ;)17:19
harmwyep17:19
harmwwhere'll it be held in April, is that known yet?17:19
sdakeI had heard barcelona17:20
sdakebut not certain17:20
sdakethe international travel is putting me in an earlygrave :(17:20
harmwdamn, I'd almost say that's to close :p17:20
SamYaplewasnt it supposed to be in Austin again sdake17:24
sdakeoh right austin then barcelona17:25
harmwthats like, TX right?17:25
SamYapleyes17:25
harmwwell, my English is better than Spanish :p17:26
SamYaplesi17:26
sdakewe got 6 epics that need to turn into green amchines17:27
sdake(epics = purple in launchpad)17:27
sdakecan folks update them now that the erview queue is straightened up17:28
daneyonSamYaple ping re: https://review.openstack.org/#/c/207760/17:28
SamYapledaneyon: reviewing now17:28
SamYapledaneyon: Does network_agent_name make sense for nova-net17:29
daneyonsdake said the code is not completely working17:29
SamYaplesince you can specify openvswitch linubridge or nova-net17:29
daneyonthe feedback i provided is general17:29
daneyonnone of the agents make sense for nova-net17:29
daneyoni would go with neutron_network_agent_name17:30
SamYapleright but that is the ansible paramater where you would specfic nova-net is my point17:30
daneyonsomething like network_provider should specify whether to use nova-net or neutron17:30
daneyonor network_manager17:30
SamYaplei cant really do that for the structure of the playbooks17:31
sdakei like network manager since nova networking is a type of manager17:31
daneyoncan u bring me up to speed on what's not working with the patch?17:31
SamYapledaneyon: it doesnt work at all for passing traffic. i dont know linuxbridge17:31
SamYaplefor OVS i would create br-ex and add the "neutron_interface"17:31
SamYaplefor linuxbridge i dont know what that looks like17:31
daneyonpassing traffic between vm's on the same host, external traffic or over a vxlan tunnel?17:32
SamYapledaneyon: they dont even get dhcp17:32
sdakepbourke around still?17:33
daneyonok, if you cerate a neutron net/subnet/router, you should see the dhcp/l3 agents spawn a router/dhcp instance. they should be able to ping one another. Is that the case?17:34
SamYapledaneyon: nope. i see dhcp traffic come out the tap, but i never see it in the namespace17:34
SamYapledhcp* namespace17:34
SamYapledaneyon: is there no bridge setup requirement like with OVS?17:35
SamYapleovs-vsctl add-br br-ex; ovs-vsctl add-port br-ex <interface_name>17:36
SamYaplenothing that needs to be done for linuxberidge/17:36
SamYaplelinuxbridge?*17:36
daneyonSamYaple we do need to map the phy int to the LB bridge, but that should not cause the problems you're seeing.17:38
daneyonhere is the interface mapping that you will need to perform: https://github.com/stackforge/kolla/blob/stable/kilo/docker/neutron/neutron-agents/config-scripts/config-linuxbridge-agent.sh#L24-L2717:38
daneyonSamYaple ^ for the LB agent17:38
daneyonIt almost sounds like something is going on with the vif plugging17:39
*** sdake has quit IRC17:39
SamYapledaneyon: yea i do that in the conf17:40
SamYapledaneyon: does linuxbridge need a special vif17:40
daneyoni would enable debug on n-compute and neutron server/agents and see if you're getting any ERRORs releated to the vif plugging17:40
SamYaplei am not17:40
*** sdake has joined #kolla17:40
daneyonnope17:40
SamYaplethe port comes online all is good17:41
SamYaplei mean like i said, i can tcpdump and see the dhcp traffic on the tap17:41
SamYaplelinuxnet_interface_driver = nova.network.linux_net.BridgeInterfaceDriver17:42
SamYaplethats correct, right?17:42
daneyonwhen u enable debug, can you look at the logs for the details of the conf file that gets loaded. make sure the config that gets loaded matches what is being set by ansible17:42
SamYapledaneyon: i did double check that17:42
SamYaplei had to make some changes, but it sees it all now17:42
daneyonlinuxnet_interface_driver = nova.network.linux_net.BridgeInterfaceDriver is correct17:43
daneyonand compute should be using the noop fw driver17:43
SamYapleyup17:43
SamYaplejust like OVS17:43
daneyonYou may want to try reverting this: https://review.openstack.org/#/c/207760/1/docker/common/neutron/neutron-linuxbridge-agent/start.sh17:44
*** sdake has quit IRC17:44
SamYaplei had to change that to get the options to recognize17:45
*** sdake has joined #kolla17:45
SamYapleit didnt work the other way either17:45
daneyoni thought i saw a bug at some point where neutron did not respect the --config-file /etc/neutron/plugins/ml2/ml2_conf.ini flag17:45
sdakesamyaple can I make this one completed https://blueprints.launchpad.net/kolla/+spec/build-script17:45
daneyonok17:45
sdakeyou canfile bugs for the additional thingsy ou want to tackle17:45
SamYaplesdake: no i need push17:45
sdakethe code is in the code base and afaik nothing else needs reviews17:45
sdakeis that going to happe ntoday?17:46
sdaketoday is deadline for all the things ;)17:46
SamYaplesdake: well then that blueprint isnt done and needs to be pushed back17:46
sdakeok bouncing to l3 then?17:46
SamYapleyea17:46
sdakesounds good17:46
*** gfidente has quit IRC17:46
daneyonSamYaple not sure what else I can say to help you out... sorry.17:47
SamYapledaneyon: no its been a good sanity check17:47
SamYapleits probably a bad config option for me17:47
SamYapleill hammer on it17:47
daneyonif i were in your shoes, i would just set neutron/nova to deb and trace every step in the path and look for an error or some other anomaly.17:48
SamYapledoes the "neutron_interface" ever get pulled into a bridge daneyon?17:48
SamYapleif so that is not happening17:49
daneyonSamYaple neutron_interface as it stands gets pulled into the external LB/OVS bridge.17:49
sdakeharmw ping re vagrant17:49
SamYapledaneyon: does the neutron agent take care of that for linuxbridge? because the OVS agent does not handle that17:49
harmwsdake: shoot17:49
sdakethe patch is in review17:49
sdakewhat is its status17:49
sdakeis it done and just needs approval?17:49
SamYaplesdake: ITS GOT TABS17:50
sdakekeep in mind it doesns't need to be perfect17:50
SamYapleDO NOT MERGE17:50
harmwwait wut17:50
sdakelol its got tabs17:50
SamYaplelol past that the patch looks good17:50
daneyonagain, the interface should not cause the problems you are seeing. You can never map a phy interface for ovs or lb and vm's on the same host should get an ip from the dhcp agent and communicate with one another over the internal ovs/lb bridge17:50
sdakejuly 31 (today) is our deadline for liberty 217:50
SamYapledaneyon: thats a good point.17:50
harmwSamYaple: vagrant got tabs?17:50
sdakei am trying to clean up the state of the launchpad tracker17:50
SamYapleharmw: i left a review17:50
harmwjeez17:51
harmwill take a look17:51
harmwthanks17:51
sdakeharmw besides the tabs, is it goo to go?17:51
SamYapledaneyon: ok well let me think about this17:51
sdakeharmw please get an untabbed review in the equeue, I'll find a couple cores to review it assuming you think its ready to go17:51
daneyonok17:51
harmwsdake: it's usefull already17:51
sdakenice17:51
sdakeif there are techdebt bugs that need filign please file those for librty-317:51
SamYapledaneyon: I appreciate the help!17:52
harmwuhm openstackgerrit ...17:53
harmwwake up please17:53
harmwsdake: SamYaple new Vagrant review is up17:54
sdakeharmw are there techdebt bugs that need filing?17:54
*** jasonsb has joined #kolla17:54
harmwthere are some TODO's but I'd rather see ppl use it first, Ill make sure anything usefull gets in the LP bugtracker17:54
sdakeharmw are the nics created automatically by vagrant?17:55
SamYapleTABS I TELL YOU17:55
sdake(reading the documentation now)17:55
harmwagain tabs?17:55
SamYapletab17:55
SamYaplebut yea17:55
sdakeharmw you said 3 nics get created, are they created by vagrant?17:56
harmwyep17:56
openstackgerritHarm Weites proposed stackforge/kolla: Vagrantfile and docs  https://review.openstack.org/20423817:56
harmwSamYaple: god I missed that17:56
daneyonSamYaple anytime17:56
SamYaplei found a use case for running both linuxbridge and openvswitch in the same cloud17:58
jasonsbsdake: i spoke with some folks about contributing elk for openstack logs17:58
SamYapleit _appears_ that I may be able to do a migration from linuxbridge-openvswitch live!17:58
jasonsbsdake: got a warm response17:58
sdakejasonsb nice :)17:59
SamYaplejasonsb: thats awesome17:59
sdakeharmw there is a -1 on that vagrant review17:59
jasonsbsdake: if we conttributed it it, when would the review have to go up?17:59
harmwsdake: did you refresh?17:59
harmwah17:59
sdakeharmw it is a requet to improve the docs17:59
harmwyea looking at it right away17:59
SamYaplesdake: you just -1 no comment17:59
sdakethen we will merge it17:59
sdakeI left a comment in review #417:59
jasonsbSamYaple: i was happy.  i'm sure you have something which would be a nice contribution too18:00
sdakerather review #10 sorry18:00
SamYaplejasonsb: openstack logs done right with no configuration? that alone is enough18:00
sdakeharmw check out my review comment in #1018:00
jasonsbsdake: (IE; when would review have to go up to have a chance of merging for this cycle)18:01
sdakethis cycle ends today18:01
sdakethen we have l318:01
sdakewhich is august 30 iir18:01
sdakejasonsb one moment18:01
harmwsdake: I would say that is something specific to Vagrant, since Vagrant just creates all the virtual machines to my liking and with the ammounts of RAM and NICS I tell it18:02
sdakejasonsb: https://wiki.openstack.org/wiki/Liberty_Release_Schedule18:02
jasonsbsdake: i think you are going to say review in two weeks18:02
jasonsbto give two weeks to get it through review process18:02
sdakeharmw got it, what I want in the docs is for people to know they dont need 3 nics, but vagrant virtualizes that18:02
sdakejasonsb first step - create a blueprint18:02
sdakei'll place in discussion phase18:02
sdakeonce we have a week of discussion or so, i'll approve blueprint (or any other core reviewer can approve it)18:03
sdakesee the schedule above18:03
jasonsbsdake: ok18:03
harmwsdake: ofcourse they don't, thats my point :) Vagrant takes care of that by instructing the desired virtualisation tool to create specific vms and such, I'm not sure if I should put that in the docs since Vagrant in general covers that aspect18:03
sdakethe feature freeze is september 4th18:03
sdakethat means no new blueprints after september 4th18:03
jasonsbsdake: i dont have a commit yet from my people, but i think its likely to see good support from all parties.18:03
sdakejasonsb cool start with a blueprint18:04
jasonsbsdake: the trick will be in getting it through lots of hands quickly to get approval18:04
jasonsbsdake: you got it18:04
sdakeeen if you dont do it , someone else may implement it18:04
jasonsbsdake: i have two i owe you18:04
harmwopenstack + ELK sounds nice jasonsb18:04
sdakenew blueprints after september 4th will be pushed into m18:05
sdakeso jasonsb I htink we dont really need elastic search18:05
sdakebut we definately want logstash18:05
sdakeso this is the type of discussion that would happen in the blueprint during the discussion phase18:06
jasonsbhmm..  we will have to discuss in bp a bit.  ours is a little bit variation18:06
jasonsbit uses fluentd18:06
sdakejasonsb if you get er in the blueprint we can discuss live during our next wednesday meeting18:07
jasonsbsdake: you got it18:08
sdakewe had talked about using a data container to store all the logs for hte node18:08
sdakei like that idea alot18:08
harmwwhy not use the docker log driver and a rsyslog container to store it all?18:08
SamYaplesdake: yea the elkstacke container can just do that18:08
SamYapleI have a patch in progress for the logging18:08
sdakewe definately need diag+audit sorted out by l318:08
jasonsbSamYaple: and have the logs within easy reach of user18:09
SamYapleharmw: we discussed this at the mid-cycle and rejected it18:09
SamYapleI can go over the reasons if youd like18:09
SamYaplejasonsb: yup :)18:09
sdakesamyaple might as well store that up for our wednesday meeting ;018:09
harmwSamYaple: please do, I'm interested :)18:09
sdake;) I mean18:09
SamYapleharmw: metting it is!18:09
sdakewell if harmw wants to know now feel free to tell him now18:09
harmwsure thing18:09
sdakebut you will probably have to repat yourself18:09
SamYaplei should probably build an etherpad for quick consumption18:09
sdakeharmw can you add somethign to the docs plz18:10
harmwsdake: working on it18:10
sdakesaying that vagrant sets up the eth tuff18:10
sdakecool thanks :) I wasn't sure if you were going to do that or not18:10
sdakejasonsb do you have questions about the above schedule18:10
jasonsbharmw: thank you for kind words.  its hard to right.  crazy long tail problem18:10
sdakesamyaple ya put together an etherpad when your not busy (i.e. tomorrow)18:11
sdakeand we can link that in the blueprint that jasonsb will file18:11
SamYaplesdake: lol not busy18:11
jasonsbsdake: yes kind of.  how much time would you like to give to review process.18:11
jasonsbsdake: is two weeks enough?18:11
sdakejasonsb who knows - depends on how good the code is18:11
sdakethe review process is meant to fix bugs in the code not to bikeshed the design18:12
SamYaplejasonsb: or how small you make the patchsets...18:12
sdakewe bikeshed the design during the blueprint process18:12
sdakeya avoiding reviewer fatigue = win :)18:12
jasonsbok, one step at a time.  lets see if you like the ideas first18:12
sdakelets get a solid design - and discuss at next week's meeting18:12
sdakeits not if "i" ike the design18:13
sdakeits if the team collectively can live with it :)18:13
jasonsb(collective you)18:13
jasonsbsorry for sloppy language18:13
SamYaplejasonsb: no sdake didnt want the configs the way they are18:13
SamYaplecommunity overruled18:13
SamYaplenow hes happy18:13
sdakeconfigs the way they are in which way samyaple18:14
openstackgerritHarm Weites proposed stackforge/kolla: Vagrantfile and docs  https://review.openstack.org/20423818:14
sdakeyou mean bindmount?18:14
SamYaplesdake: you wanted that environment variable this18:14
SamYapleyea18:14
sdakethat is because kevinfox foudn a solution that gives us immutability18:14
SamYapleyea i know18:14
sdakeI dont care about env vs non env, I cared about immutability18:14
SamYapleits not an attack against you18:14
SamYapleto be fair, i promised that with teh configs...18:14
sdakeyup my point is, have to understand the reason - the community didnt overrule me, they came up with a solution to my problem ;)18:15
harmwsdake: there, sattisfied now/ :p18:15
sdakeharmw reviewing moment18:15
SamYaplewell the commnity overruled and _then_ came up with a solution18:16
sdakeharmw maybe I'm dense but I don't see the change18:16
sdakeI wrote the spec based upon kevin fox's input - pretty sure I recall the exact ordering :)18:16
harmwdon't you compare specific patchsets sdake ?18:17
sdakeharmw with my eyeballs18:17
sdakeis there another way?18:17
sdakeis there a compare button?18:17
sdakeif so do teach me sometihing new pls :)18:17
SamYaplesdake: yes18:17
SamYapleyou can compare patchsets18:17
sdakehow18:17
harmwhttps://review.openstack.org/#/c/204238/11..12/docs/vagrant.md18:17
harmwthere18:17
SamYaplesdake: on a per file basis18:17
harmwthats how I've been going tthrough subsequent reviews since before time :p18:17
SamYapleyou can select the patchset at the top of each file18:18
sdakeok one of you will have to walk me through that when I am less busy18:18
harmwsure thing old man :P18:18
sdakebut looks like a fantastic feature I need to know about18:18
harmwoh it is :)18:18
SamYapleman how have you survived! and kept up reviews?!18:18
SamYapleim very happy we can share this with you18:18
harmwbut the above link'll show you exactly what I added in the latest patchset to the docs18:18
*** unicell has quit IRC18:19
sdakesamyaple an you review harm's work pls18:19
sdakeI spend couple hours a day doing reviews18:19
sdakeand manually inspect each request vs change18:19
SamYaple:O18:19
sdakeclearly this seems like a better way18:19
sdakethis being what harm just showed me18:19
SamYapleyea thats what were talking about18:19
sdakeok can you review harm's review samyaple plz18:20
SamYapleon it18:20
sdaketa18:20
sdakeok so we need to make all our tags liberty218:23
sdakeIguess I'll do that18:23
* sdake groans18:23
sdakefirst commit after tag will change it to liberty318:23
sdakesamyaple does that match up with what we discussed yesterday?18:23
daneyonSamYaple sdake I am seeing the following error when starting nova containers: ImportError: No module named cryptography18:23
daneyonare you aware of a patch that fixes this?18:23
daneyonor maybe it's unique to me.18:24
SamYapledaneyon: no but i havent rebuilt today18:24
sdakedaneyon did you just rebuild your containers?18:24
daneyonmy images were built within the last day18:24
sdakethe base image needs that dependency added for rdo18:24
daneyonlooks like my nova images were built 46 hours ago18:24
sdakethat is a essential bug, can you file it daneyon18:24
daneyonthis is my tip: 4d6eaa2 Merge "Tells rabbitmq to listen on single ip"18:25
sdakedaneyon it is because delorean added a dependency but it wasn't added to the rpm18:25
daneyonsdake i built the nova images 46 hours ago, from tip: 4d6eaa2 Merge "Tells rabbitmq to listen on single ip"18:25
sdakedaneyon yes i just read that :)18:25
daneyonso do a pip install cryptography to the nova-base images, correct?18:26
daneyons/images/image18:26
sdakei'd put it in centos base18:26
sdakewith the othe pip installs18:26
sdakesome other package will probably use cryptography18:26
sdakewe are int eh process in openstack of deprecating all our crypto code an using some new library18:27
sdakeI think cryptography is it18:27
daneyonsdake weird the centos base already has pip installing crypto: ../kolla/docker/centos/binary/nova/nova-base/Dockerfile:RUN pip install cryptography --upgrade18:28
sdakedaneyon moment let me look at repo18:29
sdakedaneyon pulling nova repo to see what crypto dep is in requirements.txt still downloading18:31
sdakedaneyon this change just went in in last couple of days https://github.com/openstack/nova/blob/master/requirements.txt#L1518:34
sdakethey replaced openssl with cryptography library18:34
*** jmccarthy has quit IRC18:36
*** jmccarthy has joined #kolla18:36
sdakejmccarthy ping18:38
*** sdake has quit IRC18:42
harmwSamYaple:18:42
harmwname: Writing hostname of host with existing cluster files to temp file18:42
harmwthats also trying to chown root18:42
harmwwhich fails in multihost, just like the other one last week18:42
SamYapleharmw: yea but your patch addressed that right?18:43
SamYapleit just hasnt landed18:44
harmwno, mine didn't look at this piece18:44
harmwit's essentially the same thing18:44
SamYapleoh18:44
SamYapleyea its just another copy18:44
*** sdake has joined #kolla18:44
harmwindeed, I should look through all files perhaps for chowns to root18:44
SamYapleharmw: thats the only one18:44
harmwoh ok18:44
harmwhehe18:45
sdakedaneyon https://github.com/openstack/nova/blob/master/requirements.txt#L1518:45
SamYaplethats the only localaction thats used thoughtout the playbooks18:45
sdakedaneyon cryptography was just added recently18:45
*** jruano has joined #kolla18:46
daneyonsdake adding the pip install to base18:47
daneyonwill test and let u know18:47
sdakeharmw can you ack https://review.openstack.org/#/c/205528/18:47
sdakedaneyon nice if youcn file a bug i'd appreciat it as wel (and link inchannel so I can set properties appropriately)18:48
openstackgerritHarm Weites proposed stackforge/kolla: Remove the explicit chown root  https://review.openstack.org/20801818:48
harmwsdake: done18:48
sdakesamyaple so is the deal that heat is busted atm even once that eview goes in?18:49
sdakebecause of domains?18:49
SamYaplesdake: not sure18:49
SamYaplebut its not complete18:49
SamYapleit bootstraps and stack lists18:49
sdakecan you create a stack?18:49
sdakenot you specifically but can it be done18:50
sdakerhallisey ping18:50
SamYaplesdake: idk, test it out18:51
sdakesamyaple ack18:51
SamYaplei cant build at the moment because of the breakage18:51
sdakewhich breakage18:51
sdakethe nova one?18:51
SamYaplethe base image braeks for me18:51
openstackgerritMerged stackforge/kolla: Fedora - Install from source for Horizon  https://review.openstack.org/20783818:52
sdakewe may have to push our deadline a couple of days as we are entering the weekend18:52
sdakeand it sounds like we have several critical shipping issues18:52
SamYaplewe do18:52
SamYaplethe mariadb bootstrap patch is done but needs testing18:52
harmwfeels like last deadline all over again :p18:52
SamYaplecant build18:52
SamYapleharmw: blame non-source builds18:52
harmwyep18:53
sdakeI think oru last deadline we were pretty on target ;)18:53
openstackgerritMerged stackforge/kolla: Fix some spelling and formatting errors in the Cinder doc  https://review.openstack.org/20785918:53
sdakemandre pbourke rhallisey jpeeler around?18:54
sdakeneed a second review on https://review.openstack.org/#/c/205528/18:54
SamYaplefound breakage18:56
SamYaplegcc not in base18:56
sdakewe have 3 purps left18:56
SamYaple  Running setup.py install for posix-ipc18:56
SamYaple    Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip-build-VPsikn/posix-ipc/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-bViZnu-record/install-record.txt --single-version-externally-managed --compile:18:56
*** SamYaple has left #kolla18:56
*** SamYaple has quit IRC18:56
sdakerofl18:56
*** SamYaple has joined #kolla18:56
harmwomfg :P18:57
harmwawesome18:57
SamYaplesorry18:57
SamYaplei quit for a reason18:57
SamYaplepaste.openstack.org/?reply_to=40662218:58
sdakeis this rdo?18:59
SamYapleyea18:59
SamYaplethis is centos-binary18:59
SamYaplewe cant be pip-upgrading all packages like this18:59
daneyonsdake i cant get crypto to install https://gist.github.com/danehans/fc4ea4f48f7a3b22cd2b18:59
sdakethe correect solution is not to use pip in the binary packaging19:00
sdakeand use copr to build the packages we need19:00
SamYapleep19:00
sdakesamyaple which package did you add for pip building there that generated taht problem?19:01
SamYaplenone19:01
sdakedaneyon yoru have the same problem, missing dependencies19:01
SamYaplei just did a fresh build19:01
SamYaplelooks like oslo upstream updated versions19:02
SamYapleand thats pulling in stuff19:02
sdakeok lets have a time out and figure out what is needed for the remaining 3 blueprints besides this charlie foxtrot that just presented itself on tag day19:03
SamYaplewhich three blueprints19:03
sdakehttps://launchpad.net/kolla/+milestone/liberty-219:03
sdakehttps://blueprints.launchpad.net/kolla/+spec/ansible-service19:04
sdakehttps://blueprints.launchpad.net/kolla/+spec/ansible-multi19:04
sdakehttps://blueprints.launchpad.net/kolla/+spec/vagrant-devenv19:04
SamYapledoes heat count as core here?19:04
sdakethe last one is making it through zuul atm19:04
SamYapleif not thats good to go19:04
sdakeno heat does not count as core19:05
sdakewe may change that definition later ;)19:05
SamYapledown to vagrant then19:05
sdakecore is what we originally defined19:05
sdakeso the other two are done?19:05
SamYapleeverything i have is merged19:05
sdakecan you mark them as such19:05
SamYaplewell except bugs19:05
SamYaplealready done19:05
sdakeyes we can tackle bugs separately19:05
sdakeok bugs next19:06
sdakewe have a mountain of bugs19:06
sdakeabout 20 that I see19:06
sdakelets figure out which ones we absolutely must fix for l319:06
sdakerather for l219:06
sdakehttps://bugs.launchpad.net/kolla/+bug/146877919:07
openstackLaunchpad bug 1468779 in kolla "Need way to select between linuxbridge and OVS" [High,Confirmed]19:07
sdakei'm assigning this to you sam19:07
SamYaplesdake: yup19:07
sdakelinuxbridge is not madnatory for l219:07
sdakehttps://bugs.launchpad.net/kolla/+bug/147306219:08
openstackLaunchpad bug 1473062 in kolla "consoleauth is broken" [Critical,Triaged]19:08
sdakewhat is consoleauth19:08
SamYaplesdake: provides token auth for accessing console19:09
SamYaplerequired for console access19:09
sdakevia horizon?19:09
SamYaplevia web19:09
SamYapledoesnt have to be horizon19:09
SamYapledoesnt require horizon19:09
jasonsbSamYaple: where is your rsyslog configs for all of the services?19:09
sdakeok we should try to fix that - if its even still a problem19:09
jasonsbSamYaple: is it merged yet?19:09
SamYaplejasonsb: it is not, logging is L3 so i have been focusing on closing L2 stuff19:10
SamYaplesdake: i dont know that it is, but i cant confirm atm19:10
sdakeI think all other bugs besides 1473062 can go in l319:10
SamYapleat one point i got a token19:10
jasonsbSamYaple: is it in git-review?19:10
SamYaplejasonsb: nope19:10
jasonsbSamYaple: okedokey thnx19:10
sdakejasonsb we are totally focused for the next days on tagging l219:10
sdakebut feel free to file blueprints for l3 ;)19:10
SamYaplebut im not using rsyslog, im creating a docker volume and using regular file logging for the openstack services19:11
SamYaplejasonsb: since not all services support rsyslog, but all can log to file thats the most consistent way to go19:11
sdakeif we can't get good consensus from the blueprint process on logging we may hav to bit the bullet and do a spec19:11
sdakebut i'd prefer not to do so ;)19:11
sdakeok so besides the CF that is the pip install in the binary images, kolla is ready to go?19:12
SamYaplesdake: https://bugs.launchpad.net/kolla/+bug/147997019:12
openstackLaunchpad bug 1479970 in kolla "Galera bootstrap is broken when starting on multinode" [Critical,Triaged] - Assigned to Sam Yaple (s8m)19:12
SamYaplethat is required l219:12
SamYapleits basically broken for multinode without that19:12
sdakeok we need that fixed then19:12
sdakeconsoleauth is lower priority then our pip problem or our galera bootstrap19:13
SamYaplei have the fix, trying to build and test19:13
SamYaplei removed what we were pip installing19:13
SamYaplethey may have fixed the packages upstream so we dont need to19:13
SamYapletesting now19:13
sdakeif we still have to pip install stuff, I can make copr repos for them19:13
sdakeif youc an get me a list samyaple19:13
sdakei'll do the rpm packaging and knock it out today19:14
SamYaplewill let oyu know if i find anything19:14
SamYaplethe only other important thing we pip install is in barbican19:15
SamYapleand thats known broken19:15
sdakei'm wililng to ship with a busted barbican19:15
sdake;)19:15
SamYaplefor shame!19:15
sdakeits just a milestone not a stable relese19:15
SamYaplei really really want trove for Liberty19:15
SamYaplebut :/19:15
SamYaplewell everything built19:18
SamYapletime for a test19:18
sdakeoslo.service is now available as an rpm19:19
SamYaplei know19:19
sdakeoslo.reports is now available as an RPM19:19
SamYaplethats why i remved it19:19
sdakecachetools is available as an rpm19:20
SamYaplelooksl ike futurist is also pulledi n properly19:20
sdakefurusist19:20
sdakeok well all the shit we install via pip is in the delorean repos now19:20
sdakeexcept for cryptography19:20
sdakeso I'll do a copr of cryptography19:20
sdakeand then we will be set19:20
sdakesam can you file a bug to remove all that pip stuff that is there atm19:21
SamYapleyup19:21
SamYaplei have the patch19:21
sdakeand target it for l219:21
sdakenice19:21
rhalliseyI'll have to see about autmaton19:21
SamYaplejust confirming correctness and booting19:21
SamYaplerhallisey: are you pip installign that?19:21
sdakeautomaton is in the centos repos19:21
SamYapleyea19:21
sdakerather then delorean repos19:21
sdakeso remove automaton too samyaple in your patch plz19:22
SamYaplethe only other thing we pip install is supervisord19:22
sdakethe only thing we are missing is cryptography19:22
SamYaplei dont know why we do, but im not touching it19:22
sdakeoh supervisord19:22
SamYaplewe can ignore it for now19:22
sdakewe can probably find an rpm of that :)19:22
SamYapleprobably19:22
sdakeya if it works with pip lets leae it alone for now19:22
sdakei'll go build an rpm of cryptography19:23
sdakeI may drop off for a bit - my network is wierd atm19:23
sdakesamyaple is there anything else we pip install besides supervisord (and the need for cryptography)19:24
SamYapleugh ansible inventory bug19:24
SamYaplenot a problem. simple fix19:24
SamYaplesdake: nope19:24
SamYaplenot in centos-banry at least19:24
sdakecan you grep the codebaes for pip19:25
SamYaplewell lots for the source install19:25
sdakeI dont have acess atm to my dev system19:25
SamYapleso thats a bad idea19:25
sdakecd to the rdo directory ;)19:25
SamYaplelike i said, centos-binary is clean19:25
SamYapleexcept what we know of19:25
sdakesound sgood19:25
sdakejust got another rv+119:25
sdakewe are allmost there folks :)19:25
sdakean zero complaints19:26
sdakeminus the bugs in the review which were fixed19:26
SamYaplehttps://bugs.launchpad.net/kolla/+bug/148043819:28
openstackLaunchpad bug 1480438 in kolla "remove unneeded pip installs" [Critical,Triaged] - Assigned to Sam Yaple (s8m)19:28
SamYaplehttps://bugs.launchpad.net/kolla/+bug/148043919:28
openstackLaunchpad bug 1480439 in kolla "ansible inventory is missing glance entries" [Critical,Triaged] - Assigned to Sam Yaple (s8m)19:28
sdakeok i am clearing the bugs that hae not been fixed and reassigning to l319:29
SamYaplethose two i have patches for19:29
SamYapleand are needed for l219:29
sdakelets get the patches up sam19:29
sdakeand I'll review/ rhallisey can review19:29
SamYapletesting now19:29
sdakeack19:29
sdakenova is busted btw ;)19:29
sdakeso you wont totally be able to test19:29
sdakebecause of the cryptography depepdnecy which is unpackaged19:29
SamYapleworks fine for me19:29
sdakeit will take 1-2 hours for me to copr it19:30
rhalliseyya I'm having that issue19:30
sdakeare you doing --no-cache?19:30
SamYaplesdake: im even rebuilding the base remember19:30
SamYaplelet me check19:30
sdakewell its deffinately in the code base19:30
sdakebecause both rhallisey and daneyon can't get nova to run19:30
*** bmace has quit IRC19:30
SamYaplebut they had the pip installs in the base19:30
sdakeand building cyrptogrpahy via pip requires gcc, so it needs to be rpm'ified19:30
SamYaplebut ill confirm19:30
rhalliseysdake, sorry I miss typed.  I'm *not* having that issue19:31
sdakecryptography package is in the nova requirements.txt but not in the delorean repo19:31
SamYaplesdake: nope all good19:31
sdakeok before I go do that work19:31
sdakelets get th epatches up and let daneyon rebuild19:31
sdakedaneyon how are you building?19:31
sdakebuild.py?19:31
openstackgerritSam Yaple proposed stackforge/kolla: Removed unneeded pip installs  https://review.openstack.org/20803619:32
SamYapleinstances start and can access networking19:32
SamYaplecryptography seems unneeded at this time19:32
*** openstack has joined #kolla19:35
-cameron.freenode.net- [freenode-info] if you're at a conference and other people are having trouble connecting, please mention it to staff: http://freenode.net/faq.shtml#gettinghelp19:35
openstackgerritSam Yaple proposed stackforge/kolla: Update inventory examples for Ansible  https://review.openstack.org/20803919:36
*** sdake has quit IRC19:38
*** sdake has joined #kolla19:39
sdakesamyaple cn you be pro and pick this up for l2 https://bugs.launchpad.net/kolla/+bug/147629419:40
openstackLaunchpad bug 1476294 in kolla "openrc needs to be made compatible with ansible deploy" [Critical,Confirmed] - Assigned to Sam Yaple (s8m)19:40
sdakeshould be pretty straight forward19:40
sdakeso I was thinking, daneyon is probbly using compose rather then ansible to launch with19:40
sdakemaye compose requires cryptography19:40
daneyonsdake i am using compose19:42
sdakesamyaple give compose a spin19:42
SamYaplesdake: ive only used compose a few times19:43
SamYaplei wont be the quickest to test compose19:43
sdakedaneyon another thing is you might try rebuilding your image since they are 46 hours old19:43
sdakesamypale rebuilt *just now*19:43
*** bmace has joined #kolla19:43
sdakemake sure to rebuidl with no-cache option19:44
sdakeuse build.py its faster19:44
SamYaple./build.py -T<number_of_parallel_build> --no-cache19:44
SamYapledaneyon: ^19:44
daneyonOK19:44
SamYapleoh youre using compose19:44
SamYaple./build.py -T<number_of_parallel_build> --no-cache --type rdo19:44
SamYapleyoull need to do that19:45
sdakeok console auth19:45
*** echoingumesh has joined #kolla19:45
SamYaplesdake: dont know testing now19:45
sdakecan youtest that samyaple19:45
SamYapleBAM19:45
SamYaplefrom __future__ import answersdake19:45
SamYaplesdake: well have L3 deadline and ansible 2.0 issues19:47
sdakelots of green -> https://launchpad.net/kolla/+milestone/liberty-219:47
SamYaplebut we can discuss them after L219:47
sdakewe can backport bug fixes19:47
sdakeinto our stable branch19:47
SamYapleyea but itll be major changes19:47
sdakeif its required to keep something maintained it is what it  is19:48
SamYapleok19:48
SamYaplefair enough19:48
sdakethe only hard rule is no db migrations19:48
sdakesince we dont have a db atm that doesn't affect us19:48
SamYaplewell that cant stay a requirement19:48
SamYaplesince its release indepentandt inside a stabel branch can have db upgrades now19:49
SamYaplenot our choice, requirement from upstream project19:49
sdakerhallisey or harmw we need reviews on: https://review.openstack.org/#/c/208036/19:50
bmaceyeah, had the same question harm..19:51
bmacevery odd to just comment out vs. remove unless it is temporary19:51
SamYaplesdake: to handle the openrc i can build a quick playbook that generates an openrc for the localhost19:51
sdakeplase review https://review.openstack.org/#/c/208039/19:52
SamYapleit needs to be discussed if we dump the openrc on each deploy host19:52
sdakebmace I found it odd too19:52
sdakebut its not rally critical either way19:52
sdakesamyaple what I'd like is for genenv to just generate an openrc.ansible version19:52
harmwhence the +2, I figured we'd want to revert this somewhere in the near future19:52
sdakeand we can tackle something better later19:52
SamYaplesdake: genenv has all kinds of crap that ansible will never use19:53
SamYaplegenenv-ansible is ok19:53
sdakewfm19:53
SamYaplebut genenv is for compose19:53
sdakejust do somethign simple for now19:53
sdakeso I can cut the release plz :)19:53
SamYapleok19:53
bmacei can add a link into it from some kolla-ansible command too if you want, and if you want a kolla-ansible that just does start i could have that in for l2 (today)19:54
openstackgerritSam Yaple proposed stackforge/kolla: Removed unneeded pip installs  https://review.openstack.org/20803619:54
sdakeharmw yo uwill have to re-review that19:55
sdakebmace that woudl be ok but olike next 1 hr or so?19:55
sdakeits getting late core reviewers will start falling off for the weekend soon :)19:56
sdakewe can always do that for l319:56
harmwit already weekend here :p19:56
bmaceas far as start, which works well, i could toss it up now.19:56
sdakecool lets gt what you got in the repo then19:56
sdakeyou can pop up extra work if you want later19:57
sdakemaybe sam could add the generate env to your tool19:57
bmacethe ansible stuff does or does not still use ./openrc?  i left the check to see if it was there from the kolla command.19:57
SamYaplesdake: i can do a genopenrc script19:57
sdakeansible uses a different openrc format bmace19:58
SamYapleit has to be processed by ansible19:58
SamYaplesdake: no thats not it19:59
*** sdake_ has joined #kolla20:01
*** sdake has quit IRC20:05
openstackgerritBorneMace proposed stackforge/kolla: Initial kolla-ansible command - deploy support only  https://review.openstack.org/20804720:05
bmaceit is a pretty simple call into the current behavior described in the ansible doc, with optional variables for inventory and playbook20:06
bmacea small step up from needing to type it all in by hand.20:07
sdake_bmace since the job on kolla-ansible likley not to be done by l2, i'll go ahead and leae it in for l320:07
SamYaplebmace: any reason not to write this properly in python?20:07
SamYaplethis script is going to grow alot20:08
SamYapleif we dont write it in python now we will just rewrite it20:08
sdake_ya it will be in python at some point20:08
sdake_howeever i am good with it in shell for this releaes20:09
SamYaplefor what we need it to do, it needs to be in python for L320:09
bmacei guess it depends on what the plan is for this script.  this isn't what i have been working on to manipulate the inventory file, etc.  this is just calling into ansible-playbook to perform some operations.  the full cli is done in python, of course, w/ cliff, babel, etc.20:09
sdake_with an immediat eplan to refactor it into python20:09
SamYaplesdake_: thats the wrong call. its going to have to be rewritten before L3 is over20:09
sdake_what do the arguments do20:09
bmaceone arg sets the inventory, the other the playbook, if not passed in it uses the defaults, all-in-one and site.yml20:10
sdake_yes so this code already exists20:10
sdake_no reason to rewrite it in thenext few hours20:10
*** Hui has joined #kolla20:10
sdake_we can do that next week ;)20:10
sdake_i dont htink bmace has objections to rewriting this code in python20:10
sdake_i just have objection to rewriting it at last minute in python20:10
SamYaplesdake_: i set the milestone on this for L3 like a week ago though20:11
SamYapleno reason to merge code we wont use20:11
sdake_yes it is is still l320:11
bmacei'm not re-writing this in python right now.  if we don't want it, dump it.  if we want something so people don't need to call ansible-playbook for l2, keep it20:11
sdake_i think people will use it20:11
SamYapledont agree with that decision20:12
sdake_i see no harm in merging now and rewriting in python later20:12
SamYaplei think we all understand each other, just a difference of opinion20:12
sdake_bmace are you going to get angry if soemone comes along and rewrites this script in python later?20:13
bmacenot in the least :)20:13
sdake_that would be the only harm I could see happen20:13
SamYaplelike i said, we are all on the same page, same information. Just different opinion20:13
SamYapleno problem. we are all adults :)20:13
bmacei'm not attached to the stuff i write.  depending on what it is to become do it in Go or Java for all I care :)20:13
sdake_so samyaple can you live with it then :)20:13
SamYapleyep20:13
sdake_cool thansk :)20:14
bmacei hate shell scripts, so i like it to be something else, but for how simple it needed to be at present, if it was just calling into ansible-playbook to do things anyway, basing it on the kolla command was the fastest and simplest path.20:14
sdake_cool I hate typing the million commands to nasible anyway20:15
sdake_bmace i -1'ed the review, couple things need addressing20:15
bmaceah, yup, sorry, forgot to hit it w/ bashate locally :/20:15
sdake_and the argument list20:16
sdake_so if we can somehow get the environment gen in this script that would be good :)20:16
bmaceactually, tox -e bashate didn't complain20:17
bmaceand that was the same spacing from the kolla command20:17
bmacemaybe it is different for case statement?20:17
sdake_wfm then as long as it passes the voting gate i'm good :)20:18
sdake_zuul needs more minerals20:20
SamYapledamn we really need to do the core/contrib thing20:21
rhalliseybmace, O.o I was going to write that nice20:22
Hui@Sam, to run the ansible kolla script, is it mandatory to run it on the target node?20:23
SamYapleHui: ansible can be run from anywhere that has ssh access to the destination nodes as defined in the inventory20:23
SamYapleso with the right inventory, you dont have to run it on the target node20:24
Huiansible-playbook -i inventory/tygris2-multi -e @../etc/kolla/defaults.yml -e @../etc/kolla/globals-tygris2.yml -e @../etc/kolla/passwords.yml site-tygris2.yml --tags "mariadb"20:24
Huithis is the command I used to start only the mariadb20:24
bmaceanything special you want for arg usage output sdake?  something like: Usage: $0 deploy <inventory> <playbook> ok?20:24
sdake_wfm bmce20:25
bmacekk20:25
SamYapleHui: right now starting mutli node mariadb is broke. I have a fix in place waiting to test it20:25
sdake_might put the defaults in there20:25
SamYapleshoudl be merged by end of day Hui20:25
sdake_eg inventory - defults to all-in-one20:25
sdake_playbook defaults - to site.yml20:25
sdake_or something20:25
HuiI changed to the all in one file20:26
SamYapleHui: for the record, it expects all the files to be present in /etc/kolla/20:26
openstackgerritBorneMace proposed stackforge/kolla: Initial kolla-ansible command - deploy support only  https://review.openstack.org/20804720:27
sdake_need another core review on https://review.openstack.org/#/c/208047/20:28
HuiSam: do you mean I can not use relative path?20:28
sdake_hui it must be in /etc/kolla20:29
sdake_so right no relative path20:29
Huilet me try again20:29
SamYapleHui: you can use a relative path for the configs, but there are other configs while running the playbooks that require /etc/kolla/config*20:29
SamYapleso for all intents and purposes, you can't use realative paths20:30
daneyonSamYaple do you see this error when running the build script: https://gist.github.com/danehans/4ed37a196392a524eab620:36
SamYapledaneyon: yea gnocchi doesnt build20:38
SamYapleyou should get a summary at the end20:39
sdake_daneyon those are like warnings "xyz didn't build"20:39
sdake_the way it comes out looks like the world ended20:39
sdake_we need to tidy up that error message :)20:39
daneyonok, just wanted to make sure the script will continue on20:39
SamYapleyea jpeeler is working on improving the output daneyon but thats safe to ignore20:39
SamYapleyea it should be "Processing: neutron-linuxbridge-agent" right now20:39
SamYaplei dont log errors, i just spit out the traceback in that initial script20:40
SamYaplejpeeler is doing proper logging20:40
sdake_actually is doing the marriage thing atm :)20:40
SamYaplei hope he is properly logging20:41
*** rhallisey has quit IRC20:44
sdake_do we hve any outstanding patches that need reviews?20:44
sdake_or are we  ggood to go once the queue finishes merging20:45
SamYaplesdake_: got patches i havent pushed due to lack of testing20:45
SamYapleone required for l220:45
sdake_this is the db problem?20:45
SamYapleyea20:45
sdake_do you need any help or just time?20:46
SamYapletime unfortunately20:46
sdake_how much20:46
SamYapleidk an hour maybe20:46
sdake_cool20:46
SamYaplehttps://review.openstack.org/#/c/205528/20:46
*** sdake_ is now known as sdake20:46
SamYaplethats heat, if you want it in20:46
sdakeyes but  Ican't review it20:46
SamYaplei know20:47
sdakeI'd like it merged20:47
sdakerhallisey is the only core that can merge it atm20:47
sdakeand he just dropped off irc20:47
SamYaplepbourke:20:47
sdakepbourke is gone for the day iirc :)20:47
sdakeits drink-o-clock in ireland atm20:47
SamYapleanyone have his password?20:47
SamYapleI should really take a day off one of these years20:47
*** achanda has quit IRC21:08
*** prad has quit IRC21:14
openstackgerritMerged stackforge/kolla: Vagrantfile and docs  https://review.openstack.org/20423821:16
daneyonSamYaple sdake you don't see this error when starting the keystone container: https://gist.github.com/danehans/6df342656bd5f89499ef21:16
sdakevictory21:17
sdakedaneyon I havn't used compose for a week or two21:17
daneyonok21:17
sdakeso it may be a compose only problem21:17
openstackgerritMerged stackforge/kolla: Remove the explicit chown root  https://review.openstack.org/20801821:17
openstackgerritMerged stackforge/kolla: Update inventory examples for Ansible  https://review.openstack.org/20803921:17
harmwI'm out guys, Ill check back in tomorrow to ack stuff :)21:17
sdakei've been busy focusing on ansible21:17
sdakeharmw sounds good bro thanks for styaing up :)21:18
harmwyoo21:18
sdakegreen is good : https://launchpad.net/kolla/+milestone/liberty-221:18
sdake4 more to go21:18
SamYapledaneyon: no but we dont use pki for config-external21:19
SamYapledaneyon: for the record i just rebuilt from scratch on new node and deployed too21:19
sdakesamyaple we use pki in compose21:19
SamYaplesdake: i know21:19
SamYaplebut thats why i dont see the error, config-external does not21:19
sdakenah the error is abou tconfig_stderr or something21:20
sdakeit has nothing to do with pki21:20
SamYaplesdake: the words at the top are Setting up PKI21:20
SamYapleits in the set of pki stage, is it not?21:20
SamYapleoh nevermind21:20
SamYaplei just read the trace21:20
SamYapleprobably deperacted/removed option21:21
sdakelikely the case21:21
sdakei want our compose code to work when we releae l2 so daneyon if youcould file a bug I'll fix it up21:21
*** echoingumesh has quit IRC21:30
*** echoingumesh has joined #kolla21:30
*** superflyy has joined #kolla21:31
*** echoingumesh has quit IRC21:32
*** echoingumesh has joined #kolla21:33
openstackgerritBorneMace proposed stackforge/kolla: Initial kolla-ansible command - deploy support only  https://review.openstack.org/20804721:40
bmacethis should be far more "normal bash" via use of getopt, arg shifting, etc.21:40
sdakesamyaple can you take a look at bmace's patch21:43
SamYaplenot atm but i will21:44
bmaceguess zuul is getting hammered by lots of people trying to get stuff in for the end of l2? :)21:50
openstackgerritSam Yaple proposed stackforge/kolla: Use sleep during database bootstrap  https://review.openstack.org/20806621:51
SamYaplesorry sdake. got one more L2 bug21:53
SamYaplehttps://bugs.launchpad.net/kolla/+bug/148046821:54
openstackLaunchpad bug 1480468 in kolla "race condition when creating services and users in ansible" [Critical,Triaged] - Assigned to Sam Yaple (s8m)21:54
*** sdake has quit IRC21:54
*** sdake has joined #kolla21:54
openstackgerritSam Yaple proposed stackforge/kolla: Fixes race condition in ansible playbooks  https://review.openstack.org/20806721:56
openstackgerritMerged stackforge/kolla: Removed unneeded pip installs  https://review.openstack.org/20803621:57
*** sdake has quit IRC22:02
SamYaplealright sdake with all the patches in the queue I can successfully start AIO, multinode, and AIO scaled to multinode22:02
echoingumeshhttps://blueprints.launchpad.net/kolla/+spec/central-logging-service22:04
jasonsbSamYaple: sdake: bp for elk service ^^22:05
openstackgerritSam Yaple proposed stackforge/kolla: Use sleep during database bootstrap  https://review.openstack.org/20806622:05
*** Hui has quit IRC22:06
openstackgerritSam Yaple proposed stackforge/kolla: Use sleep during database bootstrap  https://review.openstack.org/20806622:06
SamYaplebmace: got the correct bug this time :/22:07
*** Hui has joined #kolla22:07
bmacenice, other than that the fix looked reasonable :)22:07
SamYaplejasonsb: running into those timing issues for rabbitmq and galera. its fine i can fix them but you called that. I thought I had structured around that issue22:17
*** sdake has joined #kolla22:25
ccrouchSamYaple: can we not do something other than sleep there?22:25
ccrouchhttps://github.com/stackforge/kolla/blob/master/docker/common/base/kolla-common.sh#L4222:25
SamYapleccrouch: we don't use wait_for in config-external22:26
SamYaplei mean not that function, ansible has a wait_for22:26
SamYaplewhat is your issue with sleep there ccrouch ?22:27
sdakestorming badly22:27
sdakemust have angered the rain gods ;022:28
SamYaplezuul soundsl ike a water god22:28
SamYaplemakes sense22:28
ccrouchSamYaple: just a pet-peeve, i don't like using sleep if there is an alternative of polling for the actual desired state to occur22:28
ccrouchthat may not be possible here22:29
bmacezuul is the gatekeeper of gozer22:29
ccrouchbut it is possible in a lot of places22:29
ccrouchi rewatched ghostbusters a few weeks ago. even better than before :-)22:29
SamYapleccrouch: yea i am with you on that. i think that function is very dynamic, it will 'wait_for' whatever command you give it to return true22:29
jasonsbSamYaple: what was the timing issue? sorry forgot!22:30
bmaceccrouch definitely the best of the ghostbuster movies.  the all female version should be.. interesting.  if it is like most remakes, disappointing.  star trek as an exception.22:30
ccrouchSamYaple: +1 its very useful, i borrowed it from TripleO where it was a standalone script22:30
SamYaplejasonsb: fresh rabbitmq cluster; start two or more nodes at the same time and they break22:30
SamYaplejasonsb: one at a time (same config) all good22:30
ccrouchbmace: fingers crossed!22:30
ccrouch+1 on startrek reboot, both excellent22:31
SamYaplebmace: its an exception in the fact that it never happened?22:31
SamYaplesure wish they would make another star trek movie...22:31
SamYapleso far weve gotten two star wars movies without lightsabers22:31
sdakeanother star trek moie is coming but different director22:32
SamYaplesimon pegg is writting it so it might be good22:32
bmaceSamYaple it is an exception in that it was actually a well made reboot.  I think the second was excellent also.  Love Cumberbatch.22:32
sdakehe does verey well in sherlock - worth watching if your into nerc shows :)22:32
SamYaplebmace: yea im with you. it wasn't bad. but it wasn't star trek imo22:32
SamYaplebut hey im a TNG guy22:32
bmacewe are all caught up on his sherlock.  they need to make more of those :/... 4 eps every 2 or 3 years is painful.22:33
*** echoingumesh has quit IRC22:33
SamYaple3 eps22:33
SamYapleevery "wherever they feel like it"22:33
sdakethe best one is where he bets him he cn get him to kill himself ;)22:33
bmaceeven worse.... it is like "new season, yay!!!" then one afternoon of watching and it is done22:33
sdakewith the poison or whatever22:33
*** echoingumesh has joined #kolla22:33
SamYaplesdake: consoleauth looks good to me im closing that bug22:34
sdakeone of my stereo channels isnt working22:34
sdakeme growls22:34
sdakeya mark it invalid22:34
sdakeand untag from release22:34
sdakeerr mielstone22:34
*** echoingu_ has joined #kolla22:35
bmaceSamYaple: i think TNG is optimal star trek as well, but i think the sort of pacing you can do with a series like that just doesn't work for a movie.  would love another trek tv series, though everything they have done since tng has sort of sucked.. voyager / ds9 / enterprise.22:35
*** echoingumesh has quit IRC22:35
sdaketng rocks - best episode is where picard gets tortured and says "I saw 5 lights"22:35
sdakebeen there ;)22:36
SamYaplevoyager i liked, ds9 not so much BUT it was pretty cool for a few reasons22:36
SamYapleenterprise, well they started messign with time travel in the first episode thats lazy writing22:36
sdakelol sam22:36
sdakeso matter of factly ;)22:36
SamYaple"lets take a story thats already been written, wrap time travel around it and tell it again" - star trek for the past 2 decades22:37
jasonsbSamYaple: oh thats right.  do you think its worth looking at the rabbit patch?22:37
SamYaplejasonsb: yea do you still ahve that link?22:37
jasonsbSamYaple: on one hand its non-standard rabbit, on the other i think the user experience is probably better22:37
bmacereally, you don't pull out time travel or prime directive breaking in ep1.. just start of mellow, getting to know the characters.. maybe go to an alien planet, pick up some of the locals, sniff some flowers and go crazy.22:38
SamYapleprime directive was always up for debate too. loved that22:39
SamYaplethe episode with the proto-vulcan race and picard brings the woman up to the ship and she thinks they are gods22:39
SamYaplegreat stuff22:39
*** jruano has quit IRC22:40
jasonsbSamYaple: https://github.com/rabbitmq/rabbitmq-clusterer22:40
openstackgerritSam Yaple proposed stackforge/kolla: Fixes race condition in ansible playbooks  https://review.openstack.org/20806722:40
SamYaplejasonsb: i wonder if we should just push to rabbit 3.5.422:41
SamYaplethen no other changes are needed22:41
jasonsblooks like it22:42
SamYaplewell it wont happen in L222:43
jasonsbthis is an interesting thing.  on one hand, kolla can deploy (in best practices way) many different versions of openstack (theoretically)22:43
SamYaplewell just have to live with rabbit crashing22:43
SamYaplejasonsb: yes!22:43
jasonsbin this rabbit case, hand in hand with best practices is an opinionated install of rabbit22:43
SamYapleif the playbooks dont change, it can deploy everything22:43
SamYaplewell jasonsb you can use 3.5.4 with juno or kilo22:43
jasonsbyes, i think you can kill both birds if done right22:43
jasonsbopinionated install of rabbit would be 3.5.4 and clusterer22:43
jasonsband operators can opt in if this resonates with them22:44
SamYaplesince we generate the config file we dont even need clusterer jasonsb22:44
jasonsbif it doesn't then leave as-is22:44
sdakealmost done: https://launchpad.net/kolla/+milestone/liberty-222:44
sdakeone mor eptach22:44
daneyonsdake SamYaple what does your openrc file look like?22:44
SamYapleexport OS_PROJECT_DOMAIN_ID=default22:44
SamYapleexport OS_USER_DOMAIN_ID=default22:44
SamYapleexport OS_PROJECT_NAME=admin22:44
SamYapleexport OS_USERNAME=admin22:45
SamYapleexport OS_PASSWORD=password22:45
SamYapleexport OS_AUTH_URL=http://192.168.31.10:3535722:45
SamYaplethat should be enough daneyon22:45
SamYaplebut thats for the config-external. the compose stuff works different i think22:45
jasonsbSamYaple: i think still need clusterer?  export RABBITMQ_BOOT_MODULE=rabbit_clusterer22:45
jasonsbSamYaple: and place compiled plugin into .22:45
jasonsbSamYaple: not sure22:45
SamYaplehmm ill test a new rabbit version and get back to you jasonsb22:46
jasonsbSamYaple: neat.  i'm curious what you think of it22:48
jasonsbSamYaple: btw, the rabbit guy who suggested is Michael Klishin22:48
sdakedaneyon the openrc for ansible is different then for compose22:48
jasonsbSamYaple: he said that rabbit people are pledging to support openstack22:48
sdakesamyaple pasted the ansible version22:48
jasonsbSamYaple: so you have a resource if you want22:48
daneyoni am having issues with crus config'ing the keystone user/tenant/ep Trying to figure out the root cause22:49
jasonsbSamYaple: i think they hired a fte solely for this22:49
daneyonI am wondering if crux supports the keystone v3 api22:49
SamYaplejasonsb: awesome! anyone I can reach out too?22:49
SamYapledaneyon: it doesnt22:49
daneyonthen i don;t think compose will work22:49
daneyonsdake ^22:49
sdakewhy wont ompose work daneyon22:51
sdakeit worked a couple weeks ago lst i tested it22:51
*** superflyy has quit IRC22:52
SamYaplejasonsb: oh wow. looking at clusterer more that is fantastic! we can use it much like haproxy where we reload the config on the fly i think22:53
daneyonsdake here is the gist of the error: https://gist.github.com/danehans/3b364989d0745824584522:53
sdakedaneyon you have to use th openrc created by genenv22:54
sdakenot the one pasted by samyaple22:54
sdakeopenrc from genev = config internal22:54
SamYaplesdake: thats inside the keystone container i looks like22:54
sdakeopenrc that is stored on my harddisk = config external22:54
sdakewhile v2 keystone is deprecated, it isn't "deleted" yet22:55
sdakeso config-internal can still make use of it22:55
jasonsbSamYaple: i've been itching to try clusterer too.  I guess pivotal got permission from emc just couple weeks back22:55
jasonsbSamYaple: this is pretty fresh stuff.  Michael Klishin said that they have been using internally for a while for the exact case of22:55
jasonsbSamYaple: having a rabbit which you don't have to babysit as much22:55
jasonsbSamYaple: IE: an appliance for instance22:56
SamYaplejasonsb: i just hesistate to move away from this rabbit packaged by the repo because of updates22:56
SamYaplemost rabbit updates require a full cluster stop which == downtime22:56
jasonsbSamYaple: this is a good question to pose to rabbit people22:56
jasonsbI would say reach out to Michael Klishin <mklishin@pivotal.io>22:56
SamYaplevery good22:57
jasonsband ask him if rabbit people can hang out on kolla22:57
daneyonmaybe it's /usr/sbin/httpd -DFOREGROUND keystone is not starting22:57
SamYaplewgsi might have some deps on V3....22:57
SamYaplei dont know22:57
jasonsbmichael is also active on rabbit-users maillist22:58
sdakedaneyon what is the problem exactly yo urun into22:59
sdakekeystone worked last time I fixed it22:59
daneyonthe keystone container is not starting properly. The container starts but keystone is not running23:01
daneyonlogs show keystone_1    | waiting for Keystone @ http://172.29.74.86:35357/v323:01
jasonsbSamYaple: i reached out to Michael.  give a little bit and see if he replies?23:01
SamYaplejasonsb: ah sure23:02
SamYapleill save the draft!23:02
jasonsbSamYaple: I asked him if there were rabbit people who could help kolla people23:02
daneyonthe keystone db is successfully created and init'd23:02
openstackgerritMerged stackforge/kolla: Initial kolla-ansible command - deploy support only  https://review.openstack.org/20804723:03
daneyonsdake SamYaple according to the OS docs, we need to configure some apache files: http://docs.openstack.org/kilo/install-guide/install/yum/content/keystone-install.html23:04
daneyonis the ansible deploy config'ing these files?23:04
SamYapledaneyon: yes, but so is config-internal23:06
daneyonSamYaple I just reviewed the /etc/httpd/conf/httpd.conf and I don't see any of the req config23:09
daneyonSamYaple can u point me to where config-internal is configuring the apache files?23:11
daneyonSamYaple... nm I see where it's being config'd in the Dockerfile23:13
jasonsbdaneyon: do you have a <VirtualHost *:35357>  section in your apache?23:15
jasonsbdaneyon: should have a bunch of WSGIXXXX stuff in there23:16
daneyonjasonsb i do23:18
daneyonSamYaple and jsonb, As it relates to the Apache config it appears the keystone dockerfile does not match up completely to the OS docs23:20
*** jasonsb_ has joined #kolla23:23
*** jasonsb has quit IRC23:23
SamYapledaneyon: i dont know about the docs23:23
daneyonjasonsb sdake or SamYaple does keystone start for you w/o having ServerName <IP_ADDRESS> in /etc/httpd/conf/httpd.conf23:23
SamYaplei do know that it worked for sdake at one point23:23
SamYapledaneyon: yes23:24
SamYaplethats justa warning23:24
SamYaplesdake sets that to * i believe23:24
daneyonAnd keystone starts for you w/o step 4 in the apache section Copy the WSGI components from the upstream repository into this dir23:25
daneyoncurl http://git.openstack.org/cgit/openstack/keystone/plain/httpd/keystone.py?h=stable/kilo \ | tee /var/www/cgi-bin/keystone/main /var/www/cgi-bin/keystone/admin23:25
SamYapledaneyon: we do that in teh dockerfile23:25
daneyonSamYaple I don;t see the curl comand in the Dockerfile23:26
daneyonCan you point it out for me?23:26
SamYaplei dont think we curl, we copy it from /usr/share23:26
SamYaplefinding line23:27
SamYaplehttps://github.com/stackforge/kolla/blob/master/docker/centos/binary/keystone/Dockerfile#L1523:27
SamYapledaneyon: ^23:27
daneyoni see it23:27
bmacehey SamYaple.  right now we have a mix of values being in the /etc/kolla/defaults.yml /etc/kolla/globals.yml and others being in the roles/xxservice/defaults/main.yml  and there doesn't seem to be a flow where values in globals / defaults from /etc/kolla override those service defaults?23:30
*** daneyon has quit IRC23:30
bmacelike i would sort of expect all default values for each service to be in their role defaults/main.yml and they just override them as necessary in /etc/kolla/globals.yml ?  it is sort of a strange mix right now23:30
*** daneyon has joined #kolla23:31
*** achanda has joined #kolla23:31
SamYaplebmace: defaults in the role are the lowlever23:34
SamYapleeverything overrides them23:34
SamYaplecommandline options (the default/global/password) are the high level23:35
SamYapleeverything overrides23:35
SamYapleerr rather they override everything else23:35
bmacesure, but for some services some values which are in default / global, for example, are not in service/defaults.main.yml23:35
SamYaplebmace: like what?23:35
bmacenova_api_port for example23:36
SamYaplebecause defaults.yml is required23:36
SamYapleand we need to reference nova_api_port in several roles23:36
SamYaplesame with all other ports23:36
bmaceit is still odd to have some service defaults in the global defaults, and some in service specific default files.23:36
SamYaplethose arent service defaults23:36
SamYapleports are global23:36
daneyonseems like i need to  specify ServerName controller <IP> in /etc/httpd/conf/httpd.conf for apache to start.23:37
SamYaplenova_api_port is needed by haproxy, neutron, and nova23:37
bmaceit is the the nova_api.  i appreciate other services need to know it23:37
SamYapleyou can inherit variables up bmace23:37
SamYaplecant*23:37
*** blahRus has quit IRC23:37
SamYaplebut to be fair, the defaults yaml may be moving to the group_vars/all.yml23:38
SamYaplei just need to be sure inheritance still works23:38
bmacei guess the programmatic term would be scope, so no service can see data scoped to roles other than their own, so only data from globals / defaults can be seen across services23:38
SamYapledaneyon: strange, is that an httpd config option you can tweak?23:38
SamYaplebmace: this is scoped. they are referenced at the lowest scope they are needed23:39
SamYaplein this case thats toplevel23:39
daneyonyes, by default it's commented-out23:39
SamYaplecould that default have changed in a package version daneyon ?23:39
bmacei am good with breaking the vars out of a single massive env file like we had it for the docker stuff, but having them in a format that can be more easily processed separate from the jinja stuff in the yml files and in common area would be excellent, imho23:40
bmaceerr.. docker stuff meaning compose23:40
SamYaplebmace: well if you can find a away to do it without duplicating the variable in ansible you go for it23:41
bmacethe way it is right now, allowing programmatic control over those values is a little obnoxious.23:41
SamYaplebmace: anything in globals.yml will override everything else23:41
SamYapleperioud23:41
sdakedaneyon yes i read thoe docs an applied them when I did the keystone conversion to httpd23:42
sdakesamyaple I think the only thing remaining is https://bugs.launchpad.net/kolla/+bug/1476294 - any chance you will wrap up soon on that?23:45
openstackLaunchpad bug 1476294 in kolla "openrc needs to be made compatible with ansible deploy" [Critical,Confirmed] - Assigned to Sam Yaple (s8m)23:45
*** daneyon has quit IRC23:46
SamYaplesdake: i said before i cant just write a script for that23:46
SamYapleit has to go through ansible23:46
SamYaplesince ansible has all the info23:46
sdakeso ansible is going to write out the openrc then?23:46
SamYapleyea, but to where23:46
sdakecwd I guess23:47
SamYapledoesnt work like that23:47
sdakepass in path?23:47
SamYaplewhere is the teplate going to go?23:47
SamYapletemplate*23:48
sdakehel if I know make something up ;)23:48
SamYaplei dont want to throw this in. this needs to be thoughtout23:48
SamYaplethis is your passwords23:49
sdakeok then put  the defualt one in that we create in the home dir23:49
sdakei'd be good with that23:49
sdakewith some instructions that it needs customization23:49
SamYaplewhat do yo mean?23:49
sdakei mean the one youpasted the one that is on my harddisk somewhere just put that in the repo23:49
sdakesome kind of documentation or file or something that people can get rolling with23:50
SamYapleok23:50
sdakethis is l2, doen't hafe to be perfect just hsa to work ;)23:50
SamYaplelike tools/openrc-example ?23:50
sdakewe have an entire 2 months to gold place this part23:50
sdakewfm23:50
SamYaplesounds good23:50
jasonsb_sdake: bp is up for logging service (if you would like to put on agenda for weekly)23:56
*** sdake has quit IRC23:57
openstackgerritSam Yaple proposed stackforge/kolla: Adds an example openrc file  https://review.openstack.org/20809723:58

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