Wednesday, 2015-06-10

*** bradjones has joined #kolla00:00
*** bradjones has joined #kolla00:00
*** jasonsb has quit IRC00:00
*** fangfenghua has joined #kolla00:01
*** dims has quit IRC00:03
*** dims has joined #kolla00:03
*** daneyon_ has quit IRC00:30
*** dwalsh has joined #kolla00:45
fangfenghuamorning folks01:10
*** bmace_ has joined #kolla01:11
*** bmace has quit IRC01:12
*** bmace_ is now known as bmace01:13
*** tobe has joined #kolla01:18
*** dims has quit IRC01:23
*** erkules_ has joined #kolla01:29
*** erkules has quit IRC01:32
*** dwalsh has quit IRC01:40
*** bmace has quit IRC01:48
*** bmace has joined #kolla01:49
*** dims has joined #kolla02:12
*** dims has quit IRC02:23
fangfenghuaSamYaple: did docker 1.7 dev had support mount propagation ?02:28
*** vinkman has quit IRC02:43
*** vinkman1 has joined #kolla02:43
*** bradjones has quit IRC02:52
*** bradjones has joined #kolla02:53
*** bradjones has joined #kolla02:53
*** dolpher has joined #kolla02:59
*** jasonsb has joined #kolla03:01
SamYaplefangfenghua: docker 1.7 has all the features we have been waiting for, including allowing mount propogation03:16
dolpherDoes kolla support running on ubuntu host now?03:38
SamYapledolpher: the containers should run on Ubuntu hosts now after some fixes03:48
bmacehey dolpher, i think a lot of developers run it on ubuntu.  i know all the build stuff works ok on ubuntu since i did it just the other day.  at least 15.04.  didn't have great luck with older ubuntu versions.03:48
*** dolpher has quit IRC03:51
*** dolpher has joined #kolla03:52
dolpherOK, I'm trying Kolla with ubuntu 14.04, and met a few issues. So I just want to make sure it supports ubuntu before I troubleshooting them further03:54
bmacei had a lot of issues with 14.04 as well dolpher which is why i did the upgrade.. i think the version of aufs is a problem, and there were several others.03:55
bmaceif you really want to stick with 14.04 you will probably need to move to using devicemapper or somehow update the aufs past the version they have in the 14.04 repos03:56
dolpherThanks bmace. I'm using 14.04 just because it's a LTS version, I don't have to stick with it. I can move to 15.04, even CentOS for the try04:02
bmacei have tried several between bare metal / vms and so far 15.04 has been the smoothest, at least for me.04:03
bmacei think sdake said he does his devel on whatever the latest fedora rev is.04:04
bmaceso that is likely to work well also04:04
dolpherI'll try with 15.04 first, thanks04:06
bmacemy pleasure dolpher.  i have been through the dev start up process about half a dozen times in the last couple of weeks so if you hit issues hopefully it has been seen, perhaps very recently :)04:07
*** bmace has quit IRC04:21
*** bmace has joined #kolla04:32
*** dolpher has quit IRC04:35
SamYapleanyone around to talk about environment and bindmounted configs?04:42
bmacewell, i think you and i were on the same page.. so if you want a multi-sided discussion i may not help :)04:43
SamYaplenope you will. so new ideas on how we can all play together04:44
SamYapleso the thought ive had with some discussion04:45
bmacefantastic.  as long as it doesn't add a ton of complexity / maintenance i think more is better as far as config options, imho..04:45
SamYaplewe bindmount in a "config" folder. when the entrypoint script starts for keystone (as an example) it looks and says does /opt/kolla/configs/keystone.conf exist?04:46
SamYapleif it _does_ exist we cp it into the container04:46
SamYapleif not, environment variables04:46
bmacethat feels ok to me.. better than leaving a straight up file being used during execution, certainly04:49
SamYaplewell it also means we can, should we choose, validate the file before launching keystone04:49
SamYapleit also allows us to just not use the external config file at all04:49
bmacesure, if we determine the file contents are borked we can either fall back to env or fail (probably the better of the two options)04:50
bmacesanity checking the config sounds like a great idea.04:50
SamYaplei dont like the fallback idea, then you may be running with an unexpected config04:51
SamYaplei would prefer container stop04:51
bmaceagreed, if their intent was to run from the config, and the config is borked, ending up having it running using some other set of values (from env for example) would be pretty confusing04:52
vinkman1So that would mean all the images will bind mount /opt/kolla ?04:55
bmaceor /opt/kolla/config if there is some other data under /opt/kolla that isn't needed by containers.04:56
SamYaplevinkman1: perhaps, but it wouldn't be hard to make a bind mount per service04:56
SamYaple/opt/kolla/keystone, /opt/kolla/glance, etc04:56
SamYaplei dont want one container to have access to all configs04:56
*** bmace_ has joined #kolla04:59
*** bmace has quit IRC04:59
*** bmace_ is now known as bmace04:59
vinkman1So how would that work if I run for example 2 or 3 keystone containers?04:59
SamYaplevinkman1: you cant do that on the same host anyway04:59
bmacei think the assumption is no more than one instance of any given service on a single node.05:00
vinkman1OK, so the orchestration tool will disallow that since Docker does not...05:00
SamYapleits not an assupmtion, it uses the host net namespace. two keystone containers cant bind ot the same port05:00
vinkman1Ahh…kk…05:00
bmaceyes, one way or another one of them would fail even if you tried to bring up 2 on a single host, but i do believe the ansible orchestration is supposed to not have that even tried in the first place.05:01
*** vinkman1 has quit IRC05:02
SamYaplewell the whole architecture is built around not doing that05:02
SamYaplei can't think of a valid reason to run multiple keystone o nthe same host other than testing05:02
SamYapleit really comlicates he design. im not sure ansible will be able to handle that even if we did implement it05:03
bmacemasochism ;)05:03
*** vinkman has joined #kolla05:03
*** nihilifer_ has joined #kolla05:32
*** prad has quit IRC05:39
*** prad_ is now known as prad05:39
*** vinkman has quit IRC05:43
*** bmace has quit IRC05:52
*** bmace has joined #kolla05:53
*** bmace has quit IRC05:59
*** bmace has joined #kolla06:01
*** prad_ has joined #kolla06:48
*** shardy has joined #kolla07:01
*** jmccarthy has joined #kolla07:07
*** bmace_ has joined #kolla07:31
*** bmace has quit IRC07:31
*** bmace_ is now known as bmace07:33
*** athomas has joined #kolla07:52
*** alisonholloway has quit IRC08:11
*** fangfenghua has quit IRC08:18
*** shardy_ has joined #kolla08:18
*** shardy has quit IRC08:20
*** shardy_ has quit IRC08:23
*** shardy has joined #kolla08:24
*** walters has quit IRC08:27
*** walters has joined #kolla08:29
*** shardy_ has joined #kolla08:32
*** shardy has quit IRC08:34
*** shardy_ has quit IRC08:38
*** shardy has joined #kolla08:39
*** mickt has joined #kolla08:40
*** bradjones has quit IRC08:40
*** bradjones has joined #kolla08:42
*** bradjones has joined #kolla08:42
mickttest08:43
SamYapleack08:43
mickt:)08:44
*** jtriley has joined #kolla09:06
*** jmccarthy has quit IRC09:06
*** jtriley has quit IRC09:11
*** jmccarthy has joined #kolla09:15
*** jmccarthy has quit IRC09:20
*** dims has joined #kolla09:27
*** dims has quit IRC09:31
*** alisonholloway has joined #kolla09:33
*** jmccarthy has joined #kolla09:40
*** dims has joined #kolla09:51
*** dims_ has joined #kolla09:52
*** dims has quit IRC09:56
*** jmccarthy has quit IRC10:00
*** jmccarthy has joined #kolla10:20
*** athomas has quit IRC10:37
*** vbel has joined #kolla10:38
*** athomas has joined #kolla10:43
*** absubram has joined #kolla10:59
openstackgerritPaul Bourke proposed stackforge/kolla: Symlink all non Dockerfile resources in images  https://review.openstack.org/19011711:07
SamYaplepdb: did you catch the irc snippet earlier for a way to allow configs managed from the host as well env vars?11:20
pdbSamYaple: I did, but let me read it again :)11:20
SamYaplewere you in the "manage from host" or "manage from container" camp?11:20
pdbmostly manage from host. though I see sdake's side too.  I think your idea above sounds very good11:23
SamYapleok. so environment varible named "legacy" or similar. If it is set, pull in the config file from the host bind mount.11:24
SamYapledo you have a suggestion other than legacy?11:25
pdblegacy isn't the best term imo11:27
SamYapletraditional?11:27
SamYaplei agree about legacy11:27
pdblet me break out the thesauraus :)11:28
SamYapleshazam11:28
pdball these terms in some way suggest that we dont recommend this methhod11:29
pdbin which case why are we adding it11:29
pdbthe simplest to me would just be something like CONFIG_STRATEGY=bind|env11:30
pdband document the ins and outs of each11:30
jmccarthyastral ;)11:34
SamYaplepdb: i like it. time to convince11:38
SamYapleill add areview11:39
SamYaplepdb: so we are on the same page. ansible will generate the config and save it to a location on the host (/opt/kolla/keystone/keystone.conf). We bind /opt/kolla/keystone/ into the container. in the container we cp keystone.conf /etc/keystone/keystone.conf11:44
SamYaplewe make changes externally to the config. on container restart those changes are pulled in11:45
SamYapleif ansible runs again, htose changes are stomped out11:45
*** tobe has quit IRC11:47
*** jruano has joined #kolla12:07
*** dwalsh has joined #kolla12:12
pdbyes12:19
*** bradjones has quit IRC12:26
*** bradjones has joined #kolla12:27
*** bradjones has joined #kolla12:27
*** prad_ has quit IRC12:34
*** prad_ has joined #kolla12:35
*** pdb has quit IRC12:42
*** pdb has joined #kolla12:42
*** nihilifer_ has quit IRC13:06
*** jmccarthy has quit IRC13:10
*** jmccarthy1 has joined #kolla13:10
*** kevsi has joined #kolla13:11
*** jmccarthy1 has quit IRC13:18
*** jmccarthy has joined #kolla13:18
*** jmccarthy has quit IRC13:21
*** jmccarthy has joined #kolla13:21
*** jtriley has joined #kolla13:50
pdbSamYaple: did you have anything in mind as an alternative to the .buildconf files?13:53
pdbI was just putting in a bp to add an arg to build-docker-image, but then it struck me the original intention was probably so you dont have to specify this13:54
SamYaplei dont want to get rid of .buildconf14:06
SamYaplethe way we source them actually allows us to execute code14:06
SamYaple(like pulling down a tarball for a specific source install)14:06
SamYaplemaybe rename it to extras or something14:07
SamYaplepdb: check multi-node spec again, added a comment elaborating what we were talking about14:09
jmccarthyAny folks actively looking into swift at all at the moment ?14:09
SamYaplejmccarthy: i want to get it in, i am not actively looking at it. It has the wierdness of needing disks and mounts so it is likely oging to be up for debate14:10
SamYapleI would prefer to see swift backed by ceph personally since that requires only the swift proxies14:10
jmccarthyOk - would a mention of it come under 'Liberty Priority Review' at all ? I'm new to these meetings - interested to help out here if possible14:12
SamYaplei dont know. sdake handles the coordination. i code monkey things14:13
*** jmccarthy has quit IRC14:13
*** jmccarthy has joined #kolla14:13
jmccarthyOk I'll ping rhallisey and see what's cooking14:21
pdbSamYaple: not so sure about the whole ansible setting the modes part14:21
SamYaplepdb: ansible would always be setting the modes14:22
SamYapleit created the environment variables14:22
pdbI assumed that would be set by the operator prior to deploy14:22
pdbso its clear which method is in use14:22
SamYaplein an ansible config14:22
SamYaplepdb: there will be a single point config to make all of these changes, config type would reside there. it will be clear14:24
pdbright it just sounds like you're describing it as some sort of state machine14:24
SamYapleim not sure how else to work it, but it is late I am tired. You can add a comment there to clarify?14:25
pdbsure14:25
*** nihilifer has quit IRC14:28
pdbSamYaple: replied14:37
SamYapleah pdb i understand the confusion14:37
SamYaplethe env: and bind: were suppose to only run when you chose that method14:38
SamYaplethey dont both run14:38
jmccarthySamYaple: I sent rhallisey a note via irc and launchpad, do you have an idea what might be outstanding or what are the challenges relating to swift offhand ? (i.e. It doesn't appear under this list on github 'The Kolla developers build images in the kollaglue namespace for the following services')14:38
SamYaplepseudo code is pseudo code, mine is no good14:38
SamYaplejmccarthy: yea, the biggest will be the disks14:38
pdbyeah I had a feeling it was just Gerrit messing up the formatting14:39
SamYapleyou have to somehow specify disks, format them and mount them automatically14:39
SamYaplei did this with my ceph implementation, and the same could be done for swift, but it was entirely ansible14:39
SamYapleplus i dont like anything about swift but the proxy14:39
SamYaplethats just personally though14:39
jmccarthyOk, maybe - I was just going to mention ansible, I think maybe some of that voodoo could be handled by initial config via ansible possibly ? Thinking out loud14:40
*** mstachow has joined #kolla14:40
*** openstackgerrit has quit IRC14:41
*** openstackgerrit has joined #kolla14:41
mstachowhello (:14:41
SamYaplehoesntly, thats a big discussion. you could draw up a rough draft of the implementation. then we can discuss14:41
SamYaplemstachow: yo14:41
jmccarthyWill see what Ryan comes back with, and have a think =)14:42
jmccarthymstachow: hiya14:43
bmaceyou still here SamYaple?14:50
SamYaplezombishly bmace14:55
bmacelol.  i can add it on the spec review, but i had one point on your conversation earlier with pdb about the config file stuff.  you mentioned that the config file would be over written with another ansible run.14:57
SamYapleplease mention it here, but definetely add it on the spec too for others14:58
SamYaplethat could be variable, no reason it MUST be overwritten14:58
bmacei was of the thought that when in this bind mod we would not push out the configs.. at that point we are saying, the configs are yours, do with them as you please.. do your own management of their values / distribution. or maybe we need a separate value / bit if we want to enable to them to do that, and then we, on the ansible side would just handle actual restart of containers, etc.14:59
SamYaplewith the option of not overridding it would be what you describe14:59
bmaceright, i think if we specifically call out that it is indeed variable, and provide the variable to control that behavior it would be excellent.14:59
bmacei'll check out the latest spec to see what the wording is in there around this.15:00
SamYaplei want to push the defaults personally as they will be the bare minimum to get openstack running15:00
SamYaplewe can for sure (its literally one ansible "if" statement)15:00
bmacesure.  i think the flow i described in one of my comments for a sort of 'common' scenario was to, for the first run, let kolla do its thing to get all the files with their defaults in place, and then the customer could take control over all the file contents from there.15:01
SamYapleconfigs definetely should be the only part that kolla doesnt _NEED_ to touch, i like hte enduser having full control over it15:01
SamYaplejust so were all on the same page, I am a power to the people kinda guy here. Im an admin/engineer at my job so thats the perspective I am viewing this project from15:02
bmaceyup.  lets all those puppet / chef / whatever existing folks continue to use most of their current config control systems.15:02
*** ccrouch has joined #kolla15:03
SamYapletheyll likely have to tweak it, but sure why not15:03
*** dims_ has quit IRC15:03
SamYaplehonestly it makes it easier to consume the containers with things other than ansible too15:03
bmaceagreed.  nice of us to have our own orchestration if people want it, but the least odd way for people used to traditional open stack administration to get started with the containerized services in their own solutions.15:05
*** jmccarthy has quit IRC15:08
*** dims has joined #kolla15:08
*** dims has quit IRC15:08
*** jmccarthy has joined #kolla15:08
*** dims has joined #kolla15:08
*** rhallisey|pto is now known as rhallisey15:09
*** ChanServ sets mode: +o rhallisey15:10
rhalliseyjmccarthy, hey, I just emailed you back regarding swift15:11
jmccarthyOk cool - lemme check15:11
*** mstachow has quit IRC15:25
*** inc0 has joined #kolla15:27
*** vinkman has joined #kolla15:27
inc0afternoon guys15:27
SamYapleafternoon inc015:31
SamYaplehey rhallisey15:32
rhalliseySamYaple, hey!15:32
*** sdake has joined #kolla15:33
inc0rhallisey, how's cinder going?:)15:34
sdakemorning folks15:34
sdakerhallisey you gtg for running the team meeting?15:34
rhalliseysdake, ya all set15:34
inc0I'm eager to try tripleo + kolla for compute nodes15:34
inc0good morning sdake15:35
rhalliseyinc0, cinder is almost done15:35
rhalliseyvery close15:35
rhalliseyinc0, that patch is also close!15:35
jmccarthyinc0: afternoon, sdake: morning15:35
inc0rhallisey, anything I can help you with? I'm almost done with keepalived15:35
rhalliseyinc0, no I think I'm good, just on PTO so I haven't touched it this week15:36
inc0cool, let me know when you'll have something plz:)15:37
rhalliseysure!15:37
sdakerhallisey nice i my be around for the first few minutes15:38
rhalliseyok cool15:38
sdakei'm supposed tobe at a  demo pod but my ass is dragging15:38
jmccarthySamYaple: I'm the proud owner of a swift bp, go me !15:39
sdakeso if I drop out in the meeting, thats why :)15:39
sdakedirelection of duties :(15:39
SamYaplejmccarthy: go you!15:39
*** blahRus has joined #kolla15:40
SamYaplerhallisey: sdake: can we put config management on the agenda? there is a conversation to be had15:42
rhalliseySamYaple, ya sure15:43
sdakesamyaple there is an entire section devoted to ansible in the agenda15:44
sdakenot guaranteeeing we can get it all out on the table in the time allotted :)15:44
*** ccrouch has quit IRC15:44
sdakebut its there15:44
SamYaplegood deal15:44
*** ccrouch has joined #kolla15:45
*** mstachow has joined #kolla15:56
sdakehey guys does this link sound familiar: http://t.co/tGuWf1eI2215:57
*** mickt has quit IRC15:58
rhalliseymeeting in 1 minute #openstack-meeting-415:59
*** mickt has joined #kolla15:59
*** Kupo24z has joined #kolla15:59
sdakechannel up to 52 peoplz15:59
sdakenew record :)15:59
pdbsdake: yup that one is doing the rounds :)15:59
bmacelol, love that page sdake.16:00
sdake"mongodb is web scale16:00
inc0looks kinda like propaganda16:00
sdake"mongodb is shit"16:00
sdakethats the best part16:00
inc0do you know mango db?16:00
SamYapleits sounds delicious16:00
pdbI didnt get the part where he suggests OpenStack16:01
pdbew16:01
pdb?16:01
inc0https://github.com/dcramer/mangodb more predictible mongo16:01
sdakeya me either16:01
inc0and faster!16:01
sdakethat web page would be so much better if he threw in magnum16:01
bmacelol16:01
*** bmace has left #kolla16:02
rhalliseybmace, meeting?16:02
sdakethen he would be on fire ;)16:02
*** loth has quit IRC16:02
*** bmace has joined #kolla16:02
*** Kupo24z is now known as loth16:02
sdakebmace that page would be so much better if he threw in magnum16:03
sdakethen he would be on fire ;)16:03
bmacesome day sdake.. some day :)16:03
*** loth1 has joined #kolla16:03
*** daneyon has joined #kolla16:06
*** jtriley has quit IRC16:27
*** jtriley has joined #kolla16:28
*** prad has quit IRC16:36
*** mickt has quit IRC16:41
*** mickt has joined #kolla16:41
*** prad_ is now known as prad16:42
*** jtriley has quit IRC16:55
SamYaplefirst16:59
bmacelol17:00
jmccarthyyou ran the light !17:00
*** juggler has joined #kolla17:00
inc0rhallisey, admins wants to keep their configs as it is17:00
SamYaplerhallisey: option 2 needs to exist because as an operator i need to turn on debug for one service on one host without reruning ansible17:00
jugglero/17:00
inc0also they want to keep their fail procedures as it is17:00
jasonsbinc0: is a kolla-provided upgrade strategy a big enough carrot to lure them?17:01
rhalliseySamYaple, I see :), sounds like devstack17:01
jasonsbinc0: IE: do it this way and upgrades with matching configs is handled nicely17:01
SamYapleok, I would like to pose a questions to al lthe people who DONT want option 2, is there a valid reason _not_ to include it?17:01
SamYaplerhallisey: i want kolla to replace devstack, so thats not an insult ;)17:01
sdakewhich was option #2 again?17:02
rhalliseySamYaple, oh I agree17:02
SamYaplebindmount17:02
SamYaplesdake: ^17:02
inc0jasonsb, it is, but I'm sure it will makes things harder for them17:02
jasonsbinc0: true true17:02
rhalliseySamYaple, not meant to be an insult, I suggested the same thing to sdake, I just didn't think operators would want it17:02
sdakeI have two objections, loss of immutability and two sources of truth17:02
SamYaplerhallisey: its all operators want, immutability be damned17:02
sdakewheither that outweighs the value it bringss, open question17:02
SamYaplesdake: those are objections ot making it default, and valid ones17:03
SamYaplethose arent objections to including it17:03
SamYapleits an option for the well informed user17:03
inc0value it brings: it will be easy to deploy kolla on existing clusters with existing config management tools17:03
sdakesamyaple agree17:03
sdakeinc0 we are not solving brownfeild deployment problems ;)17:03
rhalliseyI like default #1 and I'm fine with #2 and #3 as additional methods17:03
pdbsame17:04
sdakewith ansible #3 or #2 would have to be teh default17:04
rhallisey#3 I want to use to build up our stack of cinder/neutron containers17:04
pdbits just the mechanism of #3 I dont like17:04
rhalliseystock*17:04
SamYaplesdake: #3 as the default for ansible, #2 is the optinos17:04
SamYaplecrudini is not available for ansible17:04
rhalliseyok17:04
sdakesamyaple ya I'm pretty sure I just said that :)17:04
rhalliseyin that case I'd vote default #3 and #2 as an option17:05
SamYaplesdake: yea lots of people are saying lots of things17:05
harmwguys, (completely different topic) since most of us are still here I wanted to bringt up a slight change to the meetingschedule17:05
rhalliseyharmw, I did earlier in the meeting17:05
harmwyou did?17:05
rhallisey1600 -> 1700 time change17:05
sdakeduring announcements17:05
SamYapleharmw: i am not going to be able to make 1700, this is way late for me as it is17:05
rhalliseyis that what you were referring to?17:05
harmwrhallisey: yep, that would mean we'd be having the meeting *now*, which works a lot better :)17:06
SamYaplecan we meet halfway with 1630-1730?17:06
SamYapledont know if we can schedule that17:07
rhalliseydoes 16:30 work or even 15:30?17:07
rhalliseysdake, ^ you ok with that?17:07
rhalliseyI think those times don't bother you17:07
sdakemaling list on the timing guys17:07
sdakei can roll with whatever17:07
rhalliseyok cool17:07
jugglercurious can meetbot do half hours?17:07
sdakesure17:08
sdakemeetbot is not aware of "slots" :)17:08
harmwworst case for me, I'd miss the first 30mins (it's already an improvement as it is)17:08
rhalliseyharmw, ya post your concern on the thread17:08
juggleror is it manual set17:08
rhalliseywe can work it out17:08
jugglersdake ah :)17:08
sdakerhallisey i think you have an action to follow up on the thread with the results of the meeting that the time change was nacked :)17:08
jasonsbrhallisey: sdake: if you can accomodate 3 of us from hds would like to attend mid-cycle meetup17:10
jasonsbrhallisey: sdake: i'll get the other two to fill out the doodle17:10
harmwthe mid-cycle meetup was in Amsterdam, right?17:10
sdakewhat is hds17:10
rhalliseyharmw, San Jose17:10
sdakethe midcycle is open to anyone to attend17:10
harmwis that in NL? :p17:10
bmacelol17:11
inc0don't you want Amsterdam? Its cool city with lot's of funny stuff there:P17:11
jasonsbamsterdam sounds nice17:11
*** pdb-mobile has joined #kolla17:11
harmwjeez, you guys sound like genuine tourists :p17:11
jasonsbhitachi data systems17:12
sdakejasonsb oh i thought you meant some kind of acronym that wasn't a company name :)17:12
sdakejasonsb dont care which company you want to attend from your welcome to attend :)17:13
jasonsbsdake: thank you sir17:13
jasonsbsdake: i didn't want to take too many seats if space was limited17:13
inc0if I'd guess, we won't run out of space17:13
sdakejasonsb if 100 people sign up I'm going tobe in trouble :)17:14
sdakebut I expect 10-2517:14
jugglerspillover at a dennys lol17:14
jasonsbsounds good17:14
sdakenot sure on logistics yet17:14
sdakeneed dates so i can pass them on to the facilities folks17:14
jmccarthyThey have Dennys in Amsterdam ? ;)17:14
SamYapledates so i can get time off17:15
*** loth has quit IRC17:15
jasonsbsdake: i'm also going to pitch to tailgaters to use kolla17:15
jasonsbbut its early days for tailgate still17:15
SamYaplelets not let anyone use kolla yet.... were still in alpha17:15
SamYaple:P17:15
jasonsbbut you have SamYaple17:16
jasonsbbam bam all done17:16
SamYaplei am here17:16
sdakeok time to get to the conference before daneyon fires me! :)17:18
SamYaplesdake: get me them dates17:18
sdakesamyaple there is a 1 week clock on signup17:19
sdakeI am not sure what the turnaround on confirmation from facilities is, but I'll let you know the proposed dates17:19
SamYaplei need 30 days notice.... gonna be close. ill tell them about it now so theyll be flexible im sre17:19
sdakeok got to jet17:21
sdakethanks for saying up samyaple ;)17:21
*** daneyon has quit IRC17:21
harmwre:ansible, what I don't see is why there's an additional option avaialbe with that augmented thing17:21
SamYapleme too17:21
jugglercya sdake17:21
SamYaplethe sleep awaits17:21
harmwand who's working on galera again?17:21
harmwinc0 was that you?17:21
jugglerhave a good sleep SamY17:21
sdakeharmw the reason is for cusotmization of deployments17:21
bmacenite Sam17:21
mstachowharmw That's me17:22
harmwsdake: ah, kinda like openstack.env customizations upon stuff inside start.sh (in a very, very rough way)17:22
harmwmstachow: ok17:22
rhalliseyI'm on PTO for the next 3 days I'll be in and out17:22
sdakeyes sort of harmw17:22
sdakehamw i gotta grab a showe rand get to the conference17:23
rhalliseyI'll respond to emails17:23
harmwsdake: think I got it now :)17:23
*** rhallisey is now known as rhallisey|PTO17:23
*** pdb-mobile has quit IRC17:24
harmwSamYaple: I think you objected on merging galera into mariadb container, right?17:24
harmwoh shit, he's asleep17:24
SamYapleharmw: i still get pings on my phone though!17:24
harmwanyway, it's more mariadb 5.5 vs mariadb 10.117:24
harmwlol17:24
SamYapleharmw: i only partly objected17:24
SamYaplei mentioned that an external repo must be used to get meriadb with wsrep/galera support17:25
harmwwsprep was your concern17:25
harmwyea17:25
SamYaplethat might be a no go for rdo stuff17:25
SamYapledunno17:25
harmwmariadb 10.1 comes with wsprep included, so we'll get that automatically when we go to Fedora2217:26
harmwrdo on Centos7 is mariadb5.5, so thats different indeed17:26
harmwbut perhps worth to look into, albeight after finishing the initial work17:26
SamYapleharmw: there is also the same repo with 5.5 and wsrep17:26
SamYaplecentos7 mariadb does not have wsrep (afaik)17:27
harmwprobably not17:27
harmwanyway, it comes with mariadb10.1 so when we can get a hold of that it's only a matter of applying the right config bits17:28
jugglerneed to head out folks. it was nice meeting you all17:30
harmwbtw, why JSON and no YAML?17:30
harmwbye!17:30
harmw(even though they share a lot)17:30
jugglerlater harmw17:30
juggler:)17:30
jmccarthyjuggler: laters17:30
SamYapleharmw: mariadb 10.1 is a beta/dev thing17:31
SamYapledont use that17:31
harmwagreed, didn't know that17:31
*** sdake has quit IRC17:31
harmwI thought it was ready for prime, but perhaps I'm mistaken with 10.017:31
harmwsince the announcemnt I got this info from was from last year17:32
*** rhallisey|PTO sets mode: +o SamYaple17:32
*** ChanServ sets mode: -o SamYaple17:32
SamYapleharmw: i think 10.1 will always be the dev version17:33
SamYaplethey commit there and do unstable things there17:33
*** jasonsb has quit IRC17:33
SamYaplethen pull them in17:33
harmwah, they follow a scheme for that17:33
SamYaplemy understanding at least17:33
harmwok17:33
*** SamYaple has left #kolla17:34
*** jasonsb has joined #kolla17:34
*** SamYaple has joined #kolla17:34
harmwis there an opinion about container logs btw?17:34
*** inc0 has quit IRC17:34
SamYaple> /dev/null17:35
SamYaplelogging is.... tricky. thats a whole other beast17:35
harmwyea17:35
harmwI'm just after some opinions,  before getting my own thoughts into some new BP17:36
jmccarthyGotta jet, laters ! =)17:37
harmwgetting all logs into 1 datacontainer, rsyslog, perhps logstash, something kibana17:37
harmwbye!17:37
SamYapleso most/all? of the openstack services can send to rsyslog directly i believe17:37
SamYaplewe should og that route in my opinion17:37
harmwI'm only just scratching the surface :)17:38
SamYapledont you know it!17:38
harmwif there are great options available, we should go with those17:38
SamYaple(had to deal with this issue for the past year) :(17:38
*** jasonsb has quit IRC17:38
*** jmccarthy has quit IRC17:39
harmwIll give a thought some other day again17:39
*** daneyon has joined #kolla17:40
*** Slower has quit IRC17:44
*** Slower has joined #kolla17:45
digaHi SamYaple17:47
digaWhen is out meeting today ??17:47
diga1700 UTC ??17:47
bmace1600, it is over17:48
SamYapleill never sleep!17:48
bmaceor not the kolla meeting? :)17:48
SamYaplediga: the kolla meeting was at 160017:48
SamYapleif we had something scheduled, I am not remembering it17:48
bmaceit is past 1700 as well utc anyway17:49
digaoops17:49
digaSamYaple: Sorry I missed it today I thought It is at 170017:49
SamYapleto sum up "configs configs configs, configs config config. CONFIGS! Config."17:50
bmacepulling a ballmer there? :)   https://www.youtube.com/watch?v=8To-6VIJZRE17:51
SamYapleballmer is life17:51
*** jtriley has joined #kolla17:52
bmacewell, life is crazy and therefore ballmer is life.. sure, i can go with that.17:52
SamYaplehe brought apple from the edge of bankrupcy17:55
SamYapletoo bad it wasn't hist company17:55
vinkmanThankfully it was not… Otherwise Apple would suck almost as much as Win 8 :D17:56
*** dwalsh has quit IRC17:56
SamYapledoesnt it already though?17:57
* bmace makes some popcorn.17:58
*** jtriley has quit IRC17:58
*** blahrus_ has joined #kolla17:59
* mstachow makes some popcorn too :O17:59
SamYaplewhy? this fight is already over17:59
SamYaplethey gave me an Apple macbook thing at work18:00
SamYapleugh18:00
bmacei actually wouldn't mind one.  seems like some nice hardware.  it is the price points and extreme vendor lock-in that annoys me.18:01
mstachowI don't like this whole "IT fight". I'm respecting everyone with their choices. Moreover - I really like popcorn ;)18:02
bmacelol, agreed about the popcorn + being good with peoples choices mstachow.  i'm not particularly a zealot in either direction.18:03
mstachowhttp://static.celebuzz.com/uploads/2013/06/14/request-five.gif bmace ;)18:05
*** shardy is now known as shardy_afk18:05
bmacelol.  nice msachow. :)18:07
*** daneyon has quit IRC18:14
*** daneyon has joined #kolla18:16
*** jasonsb has joined #kolla18:20
*** bradjones has quit IRC18:23
*** jtriley has joined #kolla18:24
*** bradjones has joined #kolla18:24
*** bradjones has joined #kolla18:24
*** daneyon has quit IRC18:26
SamYaplei like drama. i dont care18:27
*** walters has quit IRC18:32
*** walters has joined #kolla18:33
*** dwalsh has joined #kolla18:42
*** nihilifer has joined #kolla19:07
mstachowbye :) !19:21
*** prad has quit IRC19:23
*** mstachow has quit IRC19:24
*** nihilifer has quit IRC19:35
*** prad has joined #kolla19:47
*** athomas has quit IRC19:52
*** prad_ has joined #kolla19:53
*** prad has quit IRC19:54
*** prad_ is now known as prad19:54
openstackgerritJeff Peeler proposed stackforge/kolla: Fix Heat container env vars and dependencies  https://review.openstack.org/18997419:56
*** sdake has joined #kolla20:06
sdakehey folks20:08
vinkmanThat was a short conference :D20:11
bmacei expect sdake just did it at 2x speed and told them to watch the replay in slow mo if they can't follow ;)20:28
*** Slower has quit IRC20:29
*** jruano has quit IRC20:29
*** sdake has quit IRC20:37
*** Slower has joined #kolla20:45
*** daneyon has joined #kolla20:56
openstackgerritJeff Peeler proposed stackforge/kolla: Fix Heat container env vars and dependencies  https://review.openstack.org/18997421:10
*** dwalsh has quit IRC21:19
*** shardy_afk has quit IRC21:19
*** sdake has joined #kolla21:22
*** jtriley has quit IRC21:36
loth1sdake: you familar with rdo repos vs cloudsig? I'm not sure what the current recommended is to use for kilo/el721:47
*** loth1 is now known as loth21:47
sdakei dont  think there is a vs there21:52
sdakerdo repos are the ones to use i think21:52
sdakei wasn't aware there was overlap21:52
*** daneyon has quit IRC22:06
jpeeleri guess that's the same thing as maintaining packages in fedora, except for centos. i guess it makes sense to have packages in the base distribution (assuming i'm understanding their setup correctly)22:07
*** daneyon has joined #kolla22:44
*** daneyon has quit IRC22:45
*** daneyon has joined #kolla22:45
*** daneyon has quit IRC23:04
*** daneyon has joined #kolla23:07
*** sdake has quit IRC23:10
*** daneyon has quit IRC23:19
*** daneyon has joined #kolla23:19
*** daneyon has quit IRC23:25
*** jasonsb has quit IRC23:26
*** jasonsb has joined #kolla23:27
*** blahrus_ has quit IRC23:34
*** blahRus has quit IRC23:44
*** jasonsb has quit IRC23:50
*** jasonsb has joined #kolla23:50

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