Monday, 2015-06-22

*** bradjones has quit IRC00:22
*** bradjones has joined #kolla00:23
*** bradjones has joined #kolla00:23
*** jasonsb has quit IRC00:26
*** jasonsb has joined #kolla00:27
*** jasonsb has quit IRC00:31
*** dimsum__ has quit IRC00:39
*** dimsum__ has joined #kolla00:41
*** dims_ has joined #kolla00:50
*** dimsum__ has quit IRC00:50
*** erkules_ has joined #kolla01:05
*** erkules has quit IRC01:08
*** dimsum__ has joined #kolla01:17
*** dims_ has quit IRC01:17
*** dims_ has joined #kolla01:40
*** dimsum__ has quit IRC01:41
*** erkules_ is now known as erkules01:54
*** jtriley has joined #kolla02:16
*** jtriley has quit IRC02:20
*** jtriley has joined #kolla02:46
*** jasonsb has joined #kolla02:59
*** jtriley has quit IRC03:00
SamYaplesdake_: https://review.openstack.org/#/c/193870/03:09
SamYapleyou saw that right?03:09
*** sdake_ has quit IRC03:10
*** dims_ has quit IRC03:40
*** sdake has joined #kolla04:04
*** dimsum__ has joined #kolla04:41
*** dimsum__ has quit IRC04:46
*** Haomeng|2 has joined #kolla05:11
*** Haomeng has quit IRC05:15
*** nihilifer has joined #kolla05:26
nihilifergood morning05:27
digasdake: Hi05:28
SamYaplemorning diga nihilifer05:29
digamorning SamYaple05:30
digacan you check this BP, I have just registerd - https://blueprints.launchpad.net/kolla/+spec/kolla-compose-script05:30
digaSamYaple: you can edit the details if you want05:31
SamYaplediga: it looks like sdake already approved it?05:31
SamYapleoh sorry nvm05:32
digaNo, that was kolla-ansible05:32
SamYapleim not certain we can approve this because im not sure what the state of kolla-compose is going to be. As far as I know we are keeping that the default deploy method for single hosts05:33
*** nihilifer has quit IRC05:46
digaokay05:52
digasdake suggested me to draft a BP on this05:54
SamYaplediga: yea im ok with the change proposed. but i haven't seen the path forward discussed anywhere and I dont want to step on anyones toes05:54
digaok05:55
digaSamYaple: If it is fitting to our path, then we may reject this BP05:55
digaI dont mind if this not approves05:56
*** dasm has joined #kolla06:15
*** inc0 has joined #kolla06:22
inc0good morning06:22
*** erkules has quit IRC06:22
*** erkules has joined #kolla06:22
dasminc0: hello06:23
dasmall: good morning06:23
SamYaplemorning diga inc006:23
SamYapleinc0: got a minute to talk about templating dockerfiles?06:23
inc0let me get cup of tee06:24
inc0brb 10mins06:24
inc0tea even06:24
SamYapledrinking tee sounds painful06:24
inc0well, no better way to get you up and awake right?06:24
SamYaplenothing like a good ole suprise trichotomy06:25
digaMorning SamYaple, dasm, inc006:31
inc0allright, we have one less tee in site, what's up SamYaple?;)06:41
inc0SamYaple, also, look at comment here plz: https://review.openstack.org/#/c/187981/06:48
SamYapleinc0: sure but i dont think you get the issue at hand with the container06:56
inc0I know you're reffering to this PID checking stuff06:57
SamYapleif we take down the loadbalancer, the vip needs to come down as well since it wont be going anywhere06:57
SamYaplei understand your concern, but keepalived has all kinds of ways to check who gets the vip06:57
SamYapleit doesnt need a pid check06:57
inc0but it will even without HAProxy, for example to APIs themselves06:57
SamYaplein its current form, the keepalived container it is not reliable06:58
SamYapleit needs some check script06:58
SamYapleno neccessarialy pids06:58
inc0yeah, but we don't know what that script will be06:59
SamYaplewe should figure that out06:59
inc0that's admins decision06:59
SamYaplesure, but we need a way to incorporate it in the container06:59
SamYapleright now there is no way t odo so06:59
inc0I don't like PIDs, that's for sure07:00
SamYapleagreed. plus it wouldnt work due to seperate pid namespaces07:01
inc0(I'm not even sure if we can get other containers PID without some hacking around)07:01
SamYapleputting haproxy and keepalived in the host pid namespace works, but it has other issue (i know from yaodu)07:01
inc0we can make keepalived+haproxy combined container07:02
SamYaplei wont say no to that, but that violates the one process per container thing07:02
inc0yeah, and limits options07:02
SamYapleit may be what we have to do for the sake of reliability, but lets think of other optiosn first07:02
SamYaplethe keepalived script can literally be any script07:03
SamYapleso we need a way for keepalived to know haproxy is live07:03
SamYapleI would say a shared socket plus a script that checks into the socket to see if it responds07:04
SamYapleso haproxy provides the socket and responds, the script access the socket and lets keepalived know its active07:04
inc0uhh, but that means we can't use container x without container y07:04
SamYaplecorrect07:04
inc0on same host moreover07:05
SamYaplei am aware. we have no rule against that07:05
inc0I'd rather go for haproxy+keepalived container in this case07:05
inc0for sake of usability07:06
SamYaplewe have a rule against that07:06
SamYapleso we have agreed to thin containers. if we are going to break that rule, it has to be decided that we will break it07:06
SamYaplethe reason I would vote against the fat container is that when the haproxy config needs to be reloaded, we would have t oreload the keepalived service as well which is very disruptive07:07
*** mstachow has joined #kolla07:12
inc0yeah, I guess07:14
inc0but I also dislike having HAProxy hardcoded to keepalived07:14
inc0this pretty much says "yeah, you have keepalived for example for Rabbit, but no, you can't use it"07:14
mstachowo/ all07:15
SamYapleinc0: rabbit goes through haproxy07:15
inc0I think this is counterintuitive07:15
SamYaplemstachow: hey07:15
inc0it can it doesn't have tpo07:15
*** athomas has joined #kolla07:15
SamYaplebut why would you want keepalived for rabbit07:15
SamYapleopenstack can talk to all the rabbit servers directly07:16
inc0active-passive rabbit isn't that bad of an idea07:16
SamYaplebut it wouldnt be07:16
SamYapleit would still need to be clustered07:16
SamYapleand partitions would still occur07:16
SamYaplekeepalived wouldnt know about that stuff07:16
inc0I'm not even considering partitions, because keepalived has no support for there07:17
inc0(see my comments in HA spec)07:17
inc0I guess I just dislike idea of binding one container to another07:17
inc0implicitly07:17
SamYaplewell it wouldn't be07:18
SamYapleit would be a script keepalived calls07:18
SamYaple_what_ script it calls can be variable07:18
inc0I guess we can add check_live.sh to keepalived container07:18
inc0and call this one07:18
inc0and let people meddle with it should they want to07:19
SamYapleyes this is what i have been proposing07:19
SamYapleits not a lock in07:19
inc0and what would be default?07:19
SamYaplehaproxy07:19
inc0shared socket stuff?07:20
inc0that requires a bit more than a script07:20
inc0and we get to square one07:20
SamYaplehow d oyo ufigure square one?07:20
inc0keepalived needs haproxy07:21
inc0whether you like it or not07:21
SamYapleconfigurably.07:21
SamYaplewhere is the disconnect here?07:21
inc0(btw, mstachow, Sam, have you seen this one? https://www.youtube.com/watch?v=Nzq9epS2b1A)07:22
inc0hold on, let me read about socker sharing in Docker07:22
inc0(I'm still Docker newbie)07:22
SamYapleinc0: just share the /run folder07:22
SamYapleinc0: those SWTOR videos always look so good07:22
SamYaplegame was a bit of a disappointment07:23
inc0yeah, game itse;f not-so07:23
inc0but trailers and music are 10/1007:23
*** diga has quit IRC07:24
*** nihilifer has joined #kolla07:24
inc0I'll go gram some food and think of this as I go07:27
inc0brb07:27
nihilifersdake: are you here?07:32
SamYaplehe has teeth issue07:34
inc0SamYaple, allright, exposing /run and adding new check_alive.sh script which will, by default, check HAProxy socket makes sense07:37
inc0or...even better!07:37
inc0check if something is listening on :500007:38
SamYaplethat might work better. lets think about it07:39
inc0that will create dependency on keystone07:39
inc0or haproxy, or any lb you'd want07:39
inc0and we could expose ENV variable to override default port07:40
SamYapleif yo uwanted to go that route then oyu would have to be able make multiple keepalived containers on the same host07:40
inc0not unless we'd make possible to look for several ports07:41
*** akwasnie has joined #kolla07:41
inc0and unless all of them are being listened on, don't migrate07:41
SamYaplethats getting pretty ugly07:41
*** gfidente has joined #kolla07:41
*** gfidente has joined #kolla07:41
SamYaplethere is no way to dynamically update that list of listening07:42
inc0you'll have to restart service07:42
inc0even redeploy container07:42
inc0default would be just 500007:43
*** bradjones has quit IRC07:43
inc0you'd be able to deploy keepalived per service if you'll change IP per service07:43
SamYaplerunning multiple keepalived per host requires more work than you think07:44
inc0also, remember that we keep script outside, so if someone want's to change it, he's free to do so07:44
inc0yeah, I'm not too concerned about that because that's pretty hardcore07:45
inc0if someone want's to do this, he'd have to support it07:45
*** bradjones has joined #kolla07:45
*** bradjones has joined #kolla07:45
SamYaplei dont like the port thing for haproxy because the haproxy could have issues but still be listening. If the socket responds, all is good07:46
SamYaplelets go that route for the default script07:46
SamYapleas you said you can add in whatever you want for other scripts07:46
SamYaplethe other scripts can listen on a port07:46
inc0yeah07:46
inc0and single port or multiple?07:46
SamYaplethats the scripts job07:47
SamYaplethe script just needs to return positive07:47
inc0I'll do netstat -nalp | <some nifty grep> anyway07:47
inc0yeah, as default07:47
inc0I'll expose env to override port anyway07:47
*** nihilifer has quit IRC07:48
inc0aaand do single port for now07:48
inc0let's not go too far ahead, if someone want's I'll +1 on patch with multiple ports07:49
SamYaplethe haproxy socket script will need to be there as per the HA spec07:50
*** nihilifer has joined #kolla07:50
inc0but maybe as part of haproxy container?07:50
SamYapleit has to exist in the keepalived container07:51
inc0ehh, I don't want 2 default scripts tho07:51
SamYaplehaproxy is the default script07:51
inc0but socket exposure?07:51
inc0I think we agreed that this is some wizadry which might go sideways07:52
SamYapleim ok with other options, but not port checks07:52
SamYaplethe socket check? no07:52
SamYaplethe port check, yes07:52
SamYaple07:46 < SamYaple> i dont like the port thing for haproxy because the haproxy could have issues but still be listening. If the socket responds, all is good07:52
inc0also, we already nearly have keepalived container, and no haproxy container yet07:54
inc0do we want not-working-container-unless-we-land-another-bp thing upstream?07:54
inc0how about add check later?07:55
SamYapleas it so the keepalived container has no use at the moment. we need the check to make it useful. the haproxy container is not required to write the check07:56
SamYaplestands*07:56
inc0why? you'll have full active-passive07:57
inc0but you'll have failover07:57
inc0api's doesn't need LB to work07:57
SamYapleassuming all services run on all nodes. but what happens when a service fails?07:57
SamYaplethe vip doesnt move07:57
inc0yeah07:57
SamYaplewe need a check script.07:57
inc0but you'll get *something* right now07:57
SamYaplethe haproxy check script is required as per the HA spec, that needs to be in the container07:57
inc0full node failure07:58
inc0it will, let's just do this in another patch07:58
SamYaplewhy would we merge half a container?07:59
inc0it's functional as it is07:59
SamYaplei disagree that is is functional07:59
inc0not fully functional07:59
inc0well, full node failure will get vrrp moved right?07:59
*** nihilifer has quit IRC07:59
SamYapleall service failures will not get the vrrp moved, right?08:00
inc0hence not fully functional08:00
SamYaplehence no merge08:00
inc0and we can solve this one by port checking08:00
SamYaplewe need it to check the services08:00
*** diga has joined #kolla08:00
SamYaplehaproxy handles those checks per the ha spec08:01
SamYapleso it needs to check haproxy08:01
SamYapleif you dont want to write it, I can finish the patch. but we do need the check08:02
*** bradjones has quit IRC08:02
inc0so we drop this patchset until HAProxy lands...08:02
inc0that's kinda sux, because it already had +W08:03
inc0and just rebase didn't make this happen08:03
SamYapleif thats the way you want to interpt it, but thats not what I said08:03
inc0right now checking of HAProxy is pointless, because there is no HAProxy08:03
inc0container08:03
inc0so we don't assume people will install it on host08:03
inc0so default check won't work08:04
inc0and there is no alternative check which works, as you've pointed out08:04
*** shardy has joined #kolla08:05
SamYapleyou havent even registered a blueprint for this08:05
inc0https://blueprints.launchpad.net/kolla/+spec/keepalived-container08:07
inc0it's set to implemented because as I said, only rebase prevented it to get into tree08:07
SamYapleah its marked as implemented08:07
SamYaplewell sdkae marked it as implemetned which it is not08:07
SamYaplejust because this was missed in previous reviews does not make the issue go away08:07
SamYaplewe do need a check script08:07
inc0but we can't do check script you want right now08:08
inc0I'm ok to make it, but not binding it to HAProxy right now08:08
inc0because we don't have it at all08:08
SamYapleyou can implement the check script right now. you dont have to use it.08:08
SamYapleyou can have the check-haproxy.sh and a check-null.sh08:09
inc0all I'm saying, let's add check-haproxy when we'll have it08:09
inc0it doesn't have to be one patchset08:10
SamYaplethis blueprint isnt complete without it08:10
inc0no bp is ever complete in software world08:10
SamYapleif you have no futher things to add, we can end the discussion08:11
inc0let's just finish off - you don't agree with no haproxy check?08:12
inc0and just adding noop check right now?08:12
SamYaplethere is no infrastructure for a check in place at all. a noop check is fine, but a check needs to occur08:13
inc0I'm ok with adding check ifra08:13
inc0I agree on this one08:13
inc0but I don't agree to add haproxy check right now08:13
SamYaplethen this blueprint isnt implemented08:14
inc0I'd rather add noop or port check now and file a bug to add haproxy later08:14
SamYapleno08:14
SamYaplewe arent filing a bug for somethign tahts part of a bp08:14
inc0I didn't mark it as such;)08:14
inc0we can do this without bug08:14
inc0but having a bug is good way to keep this in mind08:14
*** bradjones has joined #kolla08:14
*** bradjones has joined #kolla08:14
SamYaplenot when the conatienr hasnt even been commited yet08:14
inc0Sam, then what do you really want? to implemnt useless check?08:15
SamYapleif you want ot implement as-is, add the noop check to just return true08:15
inc0then this container is useless until HAProxy08:15
inc0so let's not merge it08:15
SamYapleill implemetn the haproxy check and we can close this bp08:15
inc0but it won't work08:16
inc0anyway, I'll implemnt noop08:16
SamYaplemake sure to update the commit to partially implements blueprint08:16
inc0or port (I'd rather add port check, however faulty, that's better than nothing)08:16
SamYapleno make it a noop08:16
SamYapleport can be optional it you wish08:17
*** nihilifer has joined #kolla08:17
inc0noop it is then08:17
SamYapleon second though, we can keep it as implemented and close the BP once the noop checks are in place. We can replace the checks on the haproxy BP, but we do need the check infrastructure in place in the keepalived container08:22
inc0yes, thank you08:22
inc0let's do that08:22
*** nihilifer has quit IRC08:23
SamYapleyes, but the check infratrcutre still needs to exist.08:23
inc0I'll do this, I agree with you on this one08:23
SamYaplethe haproxy script would only be 2-3 lines large you realize08:23
inc0I know, but it's just timing08:24
inc0there is no haproxy yet. that's all08:24
SamYaplesure but you just fought me for 40 minutes on 2-3 lines08:24
SamYaplewe both need to communicate better08:24
inc0I guess08:24
inc0we need to get a drink at midcycle08:24
SamYapleor two08:24
inc0and get wasted. This helps with future communication08:25
SamYaplefirst rounds on me how about that08:25
inc0drink in my book means "generally undefined amount of alkohol in any number of carriers"08:25
inc0I won't say no to that08:25
SamYapleinc0: updated the review with our conversation08:27
inc0cool, thank you, I'll get to implementation08:27
*** shardy has quit IRC08:35
*** shardy has joined #kolla08:36
*** bradjones has quit IRC08:38
*** bradjones has joined #kolla08:40
*** bradjones has joined #kolla08:40
openstackgerritPaul Bourke proposed stackforge/kolla: Minor doc fixups in dev-quickstart.md  https://review.openstack.org/19054308:57
openstackgerritPaul Bourke proposed stackforge/kolla: Move ansible/README.md under docs/  https://review.openstack.org/19054408:59
openstackgerritPaul Bourke proposed stackforge/kolla: Add base image for oraclelinux  https://review.openstack.org/19101309:00
openstackgerritPaul Bourke proposed stackforge/kolla: Fix broken cinder symlinks for fedora  https://review.openstack.org/19362509:00
*** inc0 has quit IRC09:02
*** inc0 has joined #kolla09:03
*** shardy has quit IRC09:08
*** shardy has joined #kolla09:08
*** pdb is now known as pbourke09:08
*** inc0 has quit IRC09:23
*** inc0_ has joined #kolla09:23
*** shardy has quit IRC09:36
*** shardy has joined #kolla09:37
inc0_SamYaple, btw you wanted to talk about config templates?10:00
SamYaplenot anymore10:00
SamYaple;)10:00
SamYapleyea give me a minute10:00
SamYapleok inc0_10:06
SamYapleso I want to rewrite the build script to use python queues and multithreading for performance10:07
SamYapleI rewrote it in bash to be parrallel but it just go more complicated10:07
SamYapleduring the rewrite would be the perfect time to do the templating10:07
SamYapleI was thinking of using jinja210:07
inc0_do we need that performance? don't forget multithreading 1. isn't very good in cpython and 2. is much harder in debugging10:08
inc0_jinja2 is cool, I used this a lot for configs10:08
SamYapleinc0_: multithreaded building, as in this thread does this build, this one does that build10:08
SamYapleim not rewriting docker10:08
inc0_Ansible uses jinja as well?10:08
SamYapleinc0_: it does, hence why i think its a good choice10:08
inc0_and other stuff can consume these tpls10:09
inc0_which is nice as well10:09
SamYapleBasically we just want these builds to happen in parallel. It takes 40 minutes to build, in parrallel it took me 10 minutes10:09
inc0_yeah, makes sense10:10
inc0_network will be more utilized10:10
SamYapleeverything will be10:10
SamYapleanyway. That shouldn't be too hard to do, but the templating needs some thought10:11
SamYapleit would be easy for different distros to share common sections wihtout symlink speghetti10:11
SamYaplebut it would make the files more comlicated to read10:11
SamYapleI was thinking large if sections. {% if base == centos|fedora|rhel } do %}10:12
inc0_or subsections like10:12
* SamYaple says syntax is not garunteed accurate10:12
inc0_if centos => include centos10:13
inc0_centos.j210:13
inc0_we can make this readable10:13
inc0_even for larger sessions10:13
SamYaplethe issue I have with that is now its a bunch of files, harder to read10:13
inc0_for smaller, just plain if10:13
SamYaplebut also centos and fedora share alot of sections10:13
SamYapleso now the file centos.j2 needs to be generic10:14
inc0_I wouldn't think too much about that tho10:14
inc0_it should be solver per-case10:14
*** dimsum__ has joined #kolla10:14
SamYapleBut jinja2 you think would be a good choice? it sounds like we have options10:14
inc0_jinja2 is great imho. I have good experience with using it as config templating tool10:15
*** nihilifer has joined #kolla10:15
SamYaplesame10:15
inc0_also, we'll just use basic stuff10:15
SamYapleshouldnt be hard to convince others either since well be doing it in ansible10:15
inc0_forloops and such, and that's good in jinja as well10:15
inc0_good == easy10:15
SamYaplei cant see why we would need loops in the docker files, but its good to have for sure10:16
inc0_you know what I mean10:16
SamYapleWe can implement the templating first, but if we want it before liberty we have to move fast10:16
SamYaplethis overrides discussions about what we will support as well10:17
inc0_yeah10:17
SamYaplewe can support whatever wihtout having a multiplying number of container files10:17
inc0_it was me who wanted generated Dockerfiles remember?;)10:17
SamYaplethats why I am talking to you10:17
SamYaplethough at the time you didnt offer up jinja2, i did ask what that would look like, remember :)10:18
SamYapleI think jinja2 can make generated files clean and readable10:18
inc0_well, I haven't paid much thought about technologies themselves, but I10:18
inc0_I'd go for jinja as first choice10:18
SamYaplenow you say it10:19
* SamYaple rolls eyes10:19
SamYaplesome of my ansible workload is being removed since there is work upstream10:19
inc0_well...communication...drinks10:19
SamYapleim talking to the folks driving it and probably going to move that along10:19
SamYaplespecifically the keystone modules and other OS modules10:19
SamYaplethe docker module will need some work, but that can happen later10:20
inc0_let's not solve all problems right now10:22
inc0_we'll fail10:22
SamYaplethe templating can be done without anything buildwise changing to much10:26
SamYapleim worried about duplicate work with all the source containers were building10:26
inc0_with templating there won't be too much of it10:27
inc0_not as much as without it anyway10:27
SamYaplemerging 5 containers into one x 30-40 different services gets hefty work wise10:27
SamYapleIf you are not interested in pushing this forward right now, it probably wont make it before Liberty since ive got stuff on my plate. If you are interested in driving it I will be able to contribute in the container merging10:29
inc0_I can't say how much time I'll have for that10:31
inc0_we need to land production-ready tripleo10:31
inc0_even if it won't land fully in L, that's not that bad10:31
inc0_as long as mechanism will be there10:31
inc0_also, let10:32
inc0_lets move this on meeting10:32
inc0_maybe we'll get additional people10:32
SamYaplemight be the case there10:32
*** nihilifer has quit IRC10:33
*** nihilifer has joined #kolla10:37
*** sdake has quit IRC10:43
*** britthou_ has quit IRC10:43
*** apmelton has quit IRC10:43
*** apmelton has joined #kolla10:43
*** britthouser has joined #kolla10:43
*** sdake has joined #kolla10:44
*** dimsum__ is now known as dims10:48
*** dims has quit IRC10:53
*** inc0_ has quit IRC10:54
*** dims has joined #kolla11:05
*** nihilifer has quit IRC11:05
*** nihilifer has joined #kolla11:17
*** rhallisey has joined #kolla11:21
*** sdake_ has joined #kolla11:27
sdake_morning11:27
openstackgerritMerged stackforge/kolla: Fix broken cinder symlinks for fedora  https://review.openstack.org/19362511:28
*** sdake has quit IRC11:30
SamYaplesdake_: morning11:35
nihilifermorning sdake_11:36
sdake_samyaple can you ack this https://review.openstack.org/#/c/193900/11:38
sdake_morning nih*11:39
SamYaplesdake_: https://review.openstack.org/#/c/193870/11:39
SamYapleyou ack i was first!11:39
SamYaple:P11:39
SamYaplei dont care which is merged, lets just pick one11:40
nihiliferone general question - when do we plan to approve bp about ubuntu containers?11:41
sdake_samyaple I approved your change11:42
sdake_nih* is one written yet?11:42
nihiliferyes, it's written, but not approved11:43
nihiliferhttps://review.openstack.org/#/c/189853/11:43
nihiliferaww, not this11:43
openstackgerritMerged stackforge/kolla: Unbreak the gate  https://review.openstack.org/19387011:43
nihiliferhttps://blueprints.launchpad.net/kolla/+spec/install-from-ubuntu11:43
sdake_needs an assigneee to be approved11:44
SamYaplenihilifer: we can approve it. i dont have the cycles to implement it but I have most of the containers in yaodu11:44
SamYapleI was the intended assignee originally11:44
nihiliferyaodu?11:46
nihiliferhowever, I can help with making ubuntu containers, I need them ;)11:48
SamYaplenihilifer: sorry https://github.com/SamYaple/yaodu/tree/master/ansible/roles/docker_build/templates/ubuntu11:49
SamYaplethose are some templates (yaodu was based on source installs) but that should get you started if you want to lead that11:49
SamYaplenihilifer: do you want me to assign the blueprint to you?11:51
nihiliferSamYaple: yes, assign me please11:51
SamYapleive got two entries for nihilifer in launchpad, nihilifer-old and mrostecki?11:52
nihilifermrostecki is a correct one11:53
SamYapleassigned11:53
nihiliferthanks11:53
SamYaplethe non openstack containers you should be able to pull from Yaodu in the link above. That should get oyu started11:53
SamYapleive worked out all the deps there11:54
*** shardy has quit IRC11:57
*** shardy has joined #kolla12:02
*** inc0 has joined #kolla12:13
*** britthou_ has joined #kolla12:16
*** jtriley has joined #kolla12:16
*** britthouser has quit IRC12:17
pbourkesdake_: hope the tooth is holding up. Did you have a question for me over the weekend or does it matter now?12:36
*** jmccarthy has quit IRC12:37
inc0from mail he wrote it seems not too much matters now12:38
*** shardy has quit IRC12:39
*** shardy has joined #kolla12:39
*** jmccarthy has joined #kolla12:40
*** dwalsh has joined #kolla12:44
*** jtriley has quit IRC12:45
*** dwalsh has quit IRC12:50
*** bradjones has quit IRC12:52
openstackgerritMichal Jastrzebski (inc0) proposed stackforge/kolla: Keepalived container  https://review.openstack.org/18798112:54
*** shardy has quit IRC12:54
*** bradjones has joined #kolla12:54
*** bradjones has joined #kolla12:54
*** shardy has joined #kolla12:56
inc0SamYaple, take a look plz12:57
SamYapleinc0: yup looks good12:57
inc0yay.12:57
SamYaplecan you confirm that when the script fails the vip moves?12:57
inc0hold on, I'll test that12:57
*** jtriley has joined #kolla13:03
openstackgerritPaul Bourke proposed stackforge/kolla: Move ansible/README.md under docs/  https://review.openstack.org/19054413:04
openstackgerritPaul Bourke proposed stackforge/kolla: Minor doc fixups in ansible-deployment.md  https://review.openstack.org/19054613:04
openstackgerritPaul Bourke proposed stackforge/kolla: Add base image for oraclelinux  https://review.openstack.org/19101313:05
*** dwalsh has joined #kolla13:06
sdake_mornn g again13:09
inc0hi sdake_ you alive?13:14
*** jtriley has quit IRC13:14
mstachowhi sdake how are u?13:16
sdake_i'm fineonc013:17
*** pbourke has quit IRC13:19
*** pbourke has joined #kolla13:19
pbourkesdake_: sourced some heroin?13:20
inc0I've heard morphine is good for creativity13:21
*** shardy has quit IRC13:22
*** shardy has joined #kolla13:22
*** shardy has quit IRC13:22
*** shardy has joined #kolla13:22
*** pradk_ is now known as prad13:24
mstachowor You can also break your leg. In this case You will have still tooth pain, but leg pain will be greater (:13:24
* mstachow watching Happy Tree Friends :)13:24
inc0also you'd have more space around your seat in plane13:24
*** dasm is now known as dasm|afk13:26
mstachowI've got question about rabbit in ha. Is it acceptable to distribute rabbit cookie through whole rabbit cluster via env variable?13:33
sdake_pbourke i got a friend who has a drug dealer to get me "blues" which are 30mg oxycodone13:34
sdake_and I split them in 4 pieces13:34
sdake_my dentist said he would write me some oxycodone when he got back tuesday13:34
pbourke:D13:35
pbourkedentist, drug dealer, whats the difference13:35
sdake_40$ a peice13:36
sdake_rediculous but gets rid of the pain13:36
pbourkeakwasnie: hi you around?13:38
akwasniehi yes13:38
* jmccarthy doesn't want to know what a pain level of 8 on the holy f*ck scale is like13:39
inc0I have some hardcore painkillers at home, I've got a bottle after my tooth removal, and I keep them just in case13:39
*** jtriley has joined #kolla13:40
pbourkeakwasnie: just wondering how you're doing with the keystone source patch. did the review comments sound ok etc?13:40
*** absubram has quit IRC13:41
akwasnieyes, i'm working on them now and try to make it worked13:47
SamYaplehey guys. Looks like most of the modules for ansible have been written and landed upstream thanks to the efforts of a few folks and openstack shade13:47
SamYapleso we shouldn't have to maintain big modules, only a few targeted ones for our needs13:47
inc0SamYaple, where are these modules? anslible-openstack project?13:50
SamYapleinc0: no13:51
SamYaplehttps://github.com/ansible/ansible-modules-core/tree/devel/cloud/openstack13:51
SamYapleall the needed modules are expected to land in 2.013:52
inc0wo, cool13:52
SamYaplewe may need to pull them in (and a few noncommited ones) if the license permits13:52
SamYaplebut we can drop them with 2.0 drops13:52
*** kevsi has quit IRC13:54
openstackgerritPaul Bourke proposed stackforge/kolla: Seperate check_required_vars one per line for Glance  https://review.openstack.org/19415214:02
*** jtriley has quit IRC14:02
inc0SamYaple, after some tinkering I've confirmed, check works14:03
inc0as it is14:03
*** jtriley has joined #kolla14:04
inc0pbourke, about stub config14:05
inc0it is usable right now14:05
inc0just will not confirm anything works underneath, so it will migrate vrrp only when host dies14:05
inc0but that's something14:05
SamYapleinc0: does it migrate when the script returns false?14:05
inc0it does14:06
SamYaplecool14:06
inc0I've changed default script to failing on usual master14:06
inc0and it works14:06
inc0I mean second node gets IP14:06
*** shardy has quit IRC14:07
*** shardy has joined #kolla14:07
pbourkeinc0: ok sounds good14:07
SamYapleinc0: alright if oy ucan address the most recent comments ill +2 it and we can get this merged14:08
*** nihilifer has quit IRC14:09
inc0you mean socat?14:10
SamYapleinc0: socat and the check-script documentation. just need a bit more info. and the few nitpicks since youre already doing another patch.14:11
SamYaplethe nitpicks wouldnt hold up the merge, but since youre there14:11
*** jtriley has quit IRC14:11
*** jtriley has joined #kolla14:12
inc0SamYaple, what's socat for here?14:12
SamYaplesocat is needed for talking to unix sockets14:12
inc0ah, for later check14:13
SamYapleyes14:13
inc0ok, makes sense14:13
inc0hmm14:18
inc0something's not right14:18
SamYaple?14:18
inc0I've made test check script which does if -f /test then echo foo; exit 114:19
inc0this should move vrrp once the moment I "touch /test" right?14:20
SamYapleif the exit is in the if statement, sounds right14:20
inc0then I've did something wrong :/14:20
SamYapleuse `docker exec` to change the script live14:21
SamYapledo something simple14:21
SamYaplehave it be `exit 0` by default14:21
SamYaplechange it to `exit 1` and see i it flips14:22
*** thomasem has quit IRC14:28
*** thomasem has joined #kolla14:29
inc0ok, that's it, I'm going home14:32
inc0with a lot of colorful swears coming out of my mouth14:32
inc0cya tomorrow14:32
*** inc0 has quit IRC14:37
openstackgerritPaul Bourke proposed stackforge/kolla: Add all missing check_required_vars for Glance  https://review.openstack.org/19416614:37
*** shardy has quit IRC14:41
*** shardy has joined #kolla14:42
*** jruano has joined #kolla14:49
*** shardy has quit IRC14:49
*** shardy has joined #kolla14:49
*** shardy has quit IRC14:49
*** shardy has joined #kolla14:49
*** absubram has joined #kolla14:50
*** sdake_ has quit IRC14:52
*** thomasem has quit IRC14:57
pbourkehttp://docs.openstack.org/infra/shade/ - "However, if what you want is to be able to write an application that talks to clouds no matter what crazy choices the deployer has made in an attempt to be more hipster than their self-entitled narcissist peers, then shade is for you."14:58
*** thomasem has joined #kolla15:02
openstackgerritRyan Hallisey proposed stackforge/kolla: Auto generate minimal environment variables doc  https://review.openstack.org/18581415:03
*** thomasem has quit IRC15:04
*** thomasem has joined #kolla15:04
*** thomasem has quit IRC15:04
*** jpeeler has joined #kolla15:05
openstackgerritRyan Hallisey proposed stackforge/kolla: Auto generate minimal environment variables doc  https://review.openstack.org/18581415:06
*** thomasem has joined #kolla15:06
openstackgerritRyan Hallisey proposed stackforge/kolla: Auto generate minimal environment variables doc  https://review.openstack.org/18581415:08
*** thomasem has quit IRC15:11
*** thomasem has joined #kolla15:11
*** thomasem has quit IRC15:12
*** thomasem has joined #kolla15:12
*** thomasem has quit IRC15:12
*** thomasem has joined #kolla15:13
*** thomasem has quit IRC15:13
*** daneyon has joined #kolla15:17
*** thomasem has joined #kolla15:17
*** nihilifer has joined #kolla15:19
*** daneyon_ has joined #kolla15:26
*** daneyon has quit IRC15:29
*** pbourke has quit IRC15:32
*** pdb has joined #kolla15:38
*** pdb is now known as pbourke15:38
*** shardy has quit IRC15:44
*** shardy has joined #kolla15:50
*** shardy has quit IRC15:57
openstackgerritMichal Rostecki proposed stackforge/kolla: Move Designate-Sink start.sh to docker/common  https://review.openstack.org/19420515:59
*** shardy has joined #kolla16:02
*** jasonsb has quit IRC16:04
*** nihilifer has quit IRC16:32
*** nihilifer has joined #kolla16:33
*** daneyon has joined #kolla16:46
*** daneyon_ has quit IRC16:47
*** Slower_ is now known as Slower16:49
*** shardy has quit IRC16:50
*** shardy has joined #kolla16:51
pbourkeaway till Friday folks if anyone is looking for me16:52
*** daneyon_ has joined #kolla16:58
*** daneyon has quit IRC16:58
*** daneyon has joined #kolla16:59
*** jasonsb has joined #kolla17:02
*** daneyon_ has quit IRC17:03
*** dims has quit IRC17:09
*** dims has joined #kolla17:09
*** sdake_ has joined #kolla17:18
*** daneyon has quit IRC17:18
*** daneyon has joined #kolla17:19
*** daneyon has quit IRC17:20
*** daneyon has joined #kolla17:21
*** daneyon has quit IRC17:23
*** shardy has quit IRC17:25
*** shardy has joined #kolla17:26
*** shardy has quit IRC17:26
*** shardy has joined #kolla17:26
*** daneyon has joined #kolla17:30
*** vinkman has joined #kolla17:32
*** gfidente has quit IRC17:35
*** dwalsh has quit IRC17:58
*** shardy has quit IRC18:00
*** shardy has joined #kolla18:00
*** rhallisey_ has joined #kolla18:09
*** _mstachow has joined #kolla18:09
*** rhallisey has quit IRC18:09
*** dwalsh has joined #kolla18:17
*** rhallisey_ has quit IRC18:47
*** rhallisey has joined #kolla18:57
openstackgerritMerged stackforge/kolla: Move Designate-Sink start.sh to docker/common  https://review.openstack.org/19420519:05
*** dwalsh has quit IRC19:08
openstackgerritHarm Weites proposed stackforge/kolla: Configure Heat service domain  https://review.openstack.org/19430819:09
*** akwasnie has quit IRC19:11
*** dwalsh has joined #kolla19:24
openstackgerritRyan Hallisey proposed stackforge/kolla: Add option to not run db sync  https://review.openstack.org/19431319:31
*** shardy has quit IRC20:00
*** shardy has joined #kolla20:02
openstackgerritRyan Hallisey proposed stackforge/kolla: Add option to not run db sync  https://review.openstack.org/19431320:32
openstackgerritRyan Hallisey proposed stackforge/kolla: Remove Keystone's variable defaults  https://review.openstack.org/19435320:32
openstackgerritRyan Hallisey proposed stackforge/kolla: Add option to not run db sync  https://review.openstack.org/19431320:37
rhalliseyhmm let's see if that breaks the gate..20:45
*** shardy has quit IRC20:47
*** shardy has joined #kolla20:47
*** shardy has quit IRC20:53
*** shardy has joined #kolla20:53
*** nihilifer has quit IRC20:54
*** sdake_ has quit IRC20:56
*** rhallisey has quit IRC20:58
*** dwalsh has quit IRC21:21
*** juggler has joined #kolla21:21
*** absubram has quit IRC21:24
*** nihilifer has joined #kolla21:54
*** jtriley has quit IRC21:59
*** jasonsb has quit IRC22:20
*** jtriley has joined #kolla22:26
*** daneyon has quit IRC22:52
*** daneyon has joined #kolla22:53
*** jtriley has quit IRC23:00
*** shardy has quit IRC23:06
*** shardy has joined #kolla23:07
*** jtriley has joined #kolla23:09
*** jasonsb has joined #kolla23:13
*** prad has quit IRC23:20
*** jruano has quit IRC23:35
*** jtriley has quit IRC23:42
*** athomas has quit IRC23:44

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