Wednesday, 2015-11-04

*** Hui has quit IRC00:01
*** cloudnau_ has joined #kolla00:01
*** cfarquhar has quit IRC00:05
*** cfarquhar has joined #kolla00:06
*** cfarquhar has quit IRC00:06
*** cfarquhar has joined #kolla00:06
*** cloudnautique has quit IRC00:06
*** cloudnau_ has quit IRC00:06
*** Kennan has joined #kolla00:07
*** tpot has quit IRC00:10
*** daneyon has joined #kolla00:12
*** daneyon_ has quit IRC00:15
*** slagle has quit IRC00:19
SamYapleasalkeld: We shall soon have multinode (in a single node) gating.... mwahaha!00:20
SamYaplei smell a talk for the next summit00:20
asalkeldcool00:20
SamYapleive got it all worked out locally00:20
asalkeldother teams could use that00:20
SamYapleindeed00:21
asalkeldone way to sell kolla as a devstack replacement00:21
SamYaplei just launched 6 "nodes" locally00:21
asalkeld(for the gate)00:21
SamYapleusing OVS (so it should even be able to test DVR)00:21
*** kproskurin has quit IRC00:22
SamYaplewhats very interesting about the gates is that they could be done one of two ways, everyone building master (time is clearly not the issue here) or the same way as devstack with a cached version for hours or days ago00:23
SamYapleeveryone building master would be the best for finding breakage... but also the best at breaking :)00:23
asalkeldwell most projects could get away with only rebuilding their own image and having old images for other services00:25
SamYapleyea thats what they do right now with devstack to a degree, i think00:25
asalkeldan even more agressive approach is to have a pool of running kolla openstacks and just update the services that have changed00:26
asalkeldmuch faster00:26
SamYapleyes. that is an idea. i like it00:27
SamYaplewould have to find a way to decontamitane the services (drop the db and all00:27
asalkeldyip, could get messy00:27
SamYaplenot sure how well it would work for all projects00:27
SamYaplebut you are right, much faster00:27
SamYaplei only worry about not building the images all together because of dependacies00:28
*** dims has joined #kolla00:28
asalkeldi see you not the only one to spell dependencies wrong ;)00:30
SamYaplei speel all hte stuff wrong00:30
asalkeldyar, write a spec and you too will start feeling all sensitive about it :-(00:32
SamYapleyea i dont know whats up with that. but it is what it is00:32
SamYaplesmall price to pay i suppose00:33
asalkeldyip00:34
*** sdake_ has quit IRC00:34
openstackgerritAngus Salkeld proposed openstack/kolla: Spec: Deploy Kolla images using Mesos  https://review.openstack.org/24108600:35
asalkeldhopefully the last update ^00:35
SamYaplei would prefer to see specification spelled out00:35
*** diogogmt has quit IRC00:42
*** sdake has joined #kolla00:44
*** vhoward has joined #kolla00:44
*** slagle has joined #kolla00:47
*** vhoward has quit IRC00:49
*** slagle has quit IRC00:52
*** slagle has joined #kolla00:54
*** kklimonda has joined #kolla00:58
*** cemason has joined #kolla01:00
*** ssurana has quit IRC01:02
*** achanda has quit IRC01:02
*** cemason has quit IRC01:05
*** daneyon_ has joined #kolla01:06
SamYapleasalkeld: if you were wondering how i was going to do the dind stuff.... this beauty will be a part of the equation01:07
SamYapledocker ps -a --no-trunc | awk '/kolla_*/ {print $1}' | xargs -n1 sh -c "btrfs su li -a /var/lib/docker | sed -e 's|<FS_TREE>|/var/lib|g' | awk '{print \$(NF)}' | xargs -n1 -I{} echo btrfs su sn {} /var/lib/docker/btrfs/subvolumes/\$1{}" sh01:07
asalkeldwowzer01:08
SamYaplethis avoids the need for a registry :)01:08
SamYaplei just snap all the built images into the new docker containers01:08
*** daneyon has quit IRC01:08
*** tfukushima has joined #kolla01:08
SamYapleno extra used space :D01:08
asalkeldso have you thought more on the custom script stuff?01:09
SamYapleyea what blueprint are we doing tha work under?01:09
SamYapleill throw up a patch01:09
asalkeldmmm, not sure01:10
SamYaplelet me know and ill throw something up01:10
asalkeldcool, happy to help01:10
SamYapleshould be clean01:10
SamYapleill throw up whats in my head and you can take it away from there to make it what you need01:10
*** tfukushima has quit IRC01:10
SamYaplecollaboration yay01:10
asalkeldthanks01:11
*** tfukushima has joined #kolla01:12
asalkeldshould just be able to override "load_config()"01:13
asalkeldbut probably means passing in the config type and ZK adress into the ENV01:14
SamYapleor we can just pass in config.json in an env variable01:14
SamYapleacross the board01:14
SamYaplemaybe that wont work01:15
SamYapleidk01:15
asalkeldyeah, what ever works01:15
asalkeldsource: {{ container_config_directory }} could point to zk://<ip/path01:20
SamYaplethat was my thoughts on implementation01:20
asalkeldi am cool with  that01:20
SamYapleyou are welcome to put up a patch for that if you want. you dont have to wait on me01:21
SamYaplejust add me as a reviewer if you do01:21
SamYapleotherwise ill do it, i just dont want to hold you up asalkeld01:21
asalkeldok01:21
*** dolpher has joined #kolla01:23
asalkelddag that is a lot of start.yml 's to add KOLLA_CONFIG=<> to01:35
SamYapleyea im actually working on improving that01:36
SamYapleim going to remove the non DRY declerations from that01:36
SamYapleasalkeld: maybe you can reuse the CONFIG_STRATAGEY variable01:37
SamYapleright now it is COPY_ONCE and COPY_ALWAYS01:37
SamYaplemaybe a zookeeper flag to branch?01:37
SamYapleitll be the quickest patch to testing anyway01:38
asalkeldsteve what's that maintained01:38
SamYaplewell for testing you can override it before you do all that extra work01:39
asalkeldyip01:39
SamYaplebut I am going to remove alot of that duplication01:39
SamYapleits a pita01:39
kklimondahi.. kolla on atomic/coreos, is this something that has been considered, and decided not to pursue, or just no one had time to test and develop it?01:40
SamYaplekklimonda: harmw did stuff with that01:40
SamYaplewe have considered it, its a timing thing01:40
SamYaplewe have actually architected alot of stuff _around_ planning for atomic type systems01:41
kklimondamhm, and how well does kolla support neutron plugins? After doing my current openstack deployment with contrail, I've started thinking about how to make it less.. messy, started looking at containers + coreos/atomic as an alternative, and then coworker mentioned kolla - I've just started digging through your repo, but it's getting late, so I've decided to throw some quick questions on irc :)01:46
kklimondahow well does it support neutron plugins, or even how much work do you anticipate it would take to get that into kolla01:46
SamYaplethere have been some efforts around that01:47
SamYaplewe dont expect much trouble, just integration is a pain01:47
SamYaplepain to agree on*01:48
SamYaplepersonally at my house I use SR-IOV in a little fork01:48
kklimondamhm, I guess I'll start lurking about, and deploy "vanilla" stuff that kolla comes with, to see how it goes01:49
SamYaplesounds good :)01:49
SamYaplewe are in a big documentation improvement push so feel free to ask question01:50
kklimondathanks, what about doing OS upgrades n->n+1? is this something you've tested, and if so, which version should I start with, and upgrade to? kilo->liberty, juno->kilo?01:52
openstackgerritAngus Salkeld proposed openstack/kolla: WIP: Add support for loading kolla config from ENV  https://review.openstack.org/24143701:52
openstackgerritAngus Salkeld proposed openstack/kolla: WIP: add support for copying files from a "zk://" source  https://review.openstack.org/24143801:52
*** ssurana has joined #kolla01:52
SamYaplekklimonda: the only branch you should be using right now is liberty, that is kolla 1.0.0 release01:52
asalkeldSamYaple: ^ totally not tested, just to share01:52
SamYapleasalkeld: will review01:53
asalkeldhaha, could be totally lazy and use: http://leemoonsoo.blogspot.com.au/2009/04/howto-mount-zookeeper-using-fuse.html02:09
asalkeldmount zookeeper02:09
asalkeld:-O02:09
asalkelds/bindmount/zk-fuse02:09
SamYapleyea i dont think fuse comes with any bloat02:10
*** dims has quit IRC02:13
*** bmace has quit IRC02:28
*** bmace has joined #kolla02:28
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Add Docker in Docker container  https://review.openstack.org/24144402:33
*** unicell has quit IRC02:37
*** CBR09 has joined #kolla02:42
*** vhoward has joined #kolla02:45
*** vhoward has quit IRC02:50
*** rhallisey has joined #kolla03:08
*** unicell has joined #kolla03:11
*** CBR09 has quit IRC03:30
*** CBR09_ has joined #kolla03:30
*** dims has joined #kolla03:33
*** klint has joined #kolla03:40
*** achanda has joined #kolla03:44
*** CBR09_ has quit IRC03:48
*** CBR09 has joined #kolla03:57
*** dims has quit IRC04:03
*** ssurana1 has joined #kolla04:04
*** achanda has quit IRC04:04
*** ssurana has quit IRC04:06
*** britthou_ has joined #kolla04:06
*** daneyon has joined #kolla04:08
*** kragniz_ has joined #kolla04:10
*** britthouser has quit IRC04:11
*** daneyon_ has quit IRC04:11
*** kragniz has quit IRC04:11
*** cloudnautique has joined #kolla04:12
*** cloudnautique has quit IRC04:18
*** cloudnau_ has joined #kolla04:18
*** asalkeld has quit IRC04:19
*** tpot has joined #kolla04:28
*** asalkeld has joined #kolla04:30
* asalkeld now paying for getting "free" giveaways at summit "the spam begins..."04:33
openstackgerritRyan Hallisey proposed openstack/kolla: Fix RHEL builds  https://review.openstack.org/24146204:33
* rhallisey goes to sleep04:33
*** rhallisey has quit IRC04:33
SamYapleWAKE UP04:33
SamYaplei did food. back to dind gate04:39
asalkeld:-)04:39
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Add Docker in Docker container  https://review.openstack.org/24144404:45
openstackgerritSam Yaple proposed openstack/kolla: Adjust gate btrfs setup  https://review.openstack.org/24146504:45
*** achanda has joined #kolla04:54
*** dwalsh has joined #kolla05:03
*** kragniz_ is now known as kragniz05:18
*** ssurana1 has quit IRC05:21
*** ssurana has joined #kolla05:25
*** ssurana has quit IRC05:32
*** cloudnau_ has quit IRC05:47
SamYaplesdake: ping05:49
*** CBR09 has quit IRC05:52
*** jasonsb has joined #kolla06:04
*** kjelly has joined #kolla06:10
*** sdake has quit IRC06:18
*** unicell1 has joined #kolla06:40
*** unicell has quit IRC06:41
*** cloudnautique has joined #kolla06:48
*** tfukushima has quit IRC06:49
*** akwasnie has joined #kolla06:49
*** tfukushima has joined #kolla06:50
*** cloudnautique has quit IRC06:53
*** akwasnie has quit IRC06:53
openstackgerritSam Yaple proposed openstack/kolla: Remove unused setup_fedora.sh  https://review.openstack.org/24149807:12
openstackgerritSam Yaple proposed openstack/kolla: Restrucutre gate scripts  https://review.openstack.org/24149907:12
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150007:12
*** cloudnull has quit IRC07:27
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150007:32
*** tpot has quit IRC07:33
*** cloudkiller has joined #kolla07:36
openstackgerritSam Yaple proposed openstack/kolla: Adjust package name for Ubuntu Ironic  https://review.openstack.org/23864007:43
*** slotti has joined #kolla07:46
*** achanda has quit IRC08:07
*** dwalsh has quit IRC08:09
*** shardy has joined #kolla08:20
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150008:21
*** cloudkiller is now known as cloudnull08:28
*** mbound has joined #kolla08:36
*** gfidente|afk has quit IRC08:38
*** diga has joined #kolla08:39
*** jmccarthy has joined #kolla08:45
*** cloudnautique has joined #kolla08:49
*** cloudnautique has quit IRC08:54
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150008:54
*** gfidente has joined #kolla08:59
*** diga has quit IRC09:13
*** tfukushima has quit IRC09:39
*** tfukushima has joined #kolla09:39
*** gfidente has quit IRC09:44
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Add Ansible support for Magnum  https://review.openstack.org/23622309:44
*** gfidente has joined #kolla09:50
*** athomas has joined #kolla09:52
*** akwasnie has joined #kolla09:57
openstackgerritSam Yaple proposed openstack/kolla: Add Docker in Docker container  https://review.openstack.org/24144410:02
openstackgerritSam Yaple proposed openstack/kolla: Remove unused setup_fedora.sh  https://review.openstack.org/24149810:02
openstackgerritSam Yaple proposed openstack/kolla: Restrucutre gate scripts  https://review.openstack.org/24149910:02
openstackgerritSam Yaple proposed openstack/kolla: Adjust gate btrfs setup  https://review.openstack.org/24146510:02
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150010:02
*** pbourke has joined #kolla10:11
*** fedorastack has joined #kolla10:13
*** vbel has joined #kolla10:13
*** fedorastack is now known as khomkrit10:15
*** khomkrit has left #kolla10:18
*** diga has joined #kolla10:24
*** dolpher has quit IRC10:24
*** tfukushima has quit IRC10:27
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150010:29
*** vbel has quit IRC10:40
*** pbourke has quit IRC10:45
*** slotti has quit IRC10:45
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150010:46
*** slotti has joined #kolla10:48
*** cloudnautique has joined #kolla10:50
*** Kennan has quit IRC10:53
*** cloudnautique has quit IRC10:55
*** khomkrit has joined #kolla10:56
*** Kennan has joined #kolla10:56
*** pbourke has joined #kolla10:59
*** kjelly_ has joined #kolla11:10
*** akwasnie has quit IRC11:12
*** Kennan has quit IRC11:51
*** Kennan has joined #kolla11:54
*** diga has quit IRC12:16
*** dims has joined #kolla12:18
openstackgerritMerged openstack/kolla: Use default disk image size for centos/7  https://review.openstack.org/24070412:18
*** akwasnie has joined #kolla12:21
*** Kennan has quit IRC12:22
*** Kennan has joined #kolla12:25
*** achanda has joined #kolla12:40
*** achanda has quit IRC12:42
*** dims has quit IRC12:43
*** cloudnautique has joined #kolla12:51
*** cloudnautique has quit IRC12:56
*** dolpher has joined #kolla13:05
*** dims has joined #kolla13:09
*** dims has quit IRC13:20
*** inc0 has joined #kolla13:38
inc0hello13:38
*** dolpher has quit IRC13:44
*** inc0 has quit IRC13:49
*** dolpher has joined #kolla13:51
*** stvnoyes has quit IRC13:51
*** dolpher has quit IRC13:51
*** kjelly_ has quit IRC13:51
*** stvnoyes has joined #kolla13:52
*** dolpher has joined #kolla13:54
*** vhoward has joined #kolla14:00
*** rhallisey has joined #kolla14:01
*** dolpher has quit IRC14:04
*** vhoward has quit IRC14:20
*** pbourke has quit IRC14:26
*** klint has quit IRC14:29
*** pbourke has joined #kolla14:30
openstackgerritRyan Hallisey proposed openstack/kolla: Fix RHEL builds  https://review.openstack.org/24146214:33
*** pbourke has quit IRC14:36
*** pbourke has joined #kolla14:37
*** openstackgerrit has quit IRC14:47
*** openstackgerrit has joined #kolla14:47
*** cloudnautique has joined #kolla14:52
*** cloudnautique has quit IRC14:57
*** CBR09 has joined #kolla14:59
*** Hui has joined #kolla15:04
*** blahRus has joined #kolla15:26
*** ssurana has joined #kolla15:42
*** dmsimard has joined #kolla15:44
*** jmccarthy1 has joined #kolla16:10
*** jmccarthy has quit IRC16:10
*** jmccarthy1 has quit IRC16:10
*** jmccarthy has joined #kolla16:11
*** cloudnautique has joined #kolla16:21
*** cloudnautique has quit IRC16:22
*** cloudnautique has joined #kolla16:22
*** mbound has quit IRC16:25
*** inc0 has joined #kolla16:27
inc0good afternoon16:27
nihilifero/16:28
pbourkehi inc016:28
pbourkeinc0: do you find images slow to build in poland?16:28
pbourkeim wondering is there some way of tweaking package sources to speed things up16:28
inc0I haven't been building for a moment, I'm kinda swamped16:29
inc0let me try now16:29
pbourkemeh, dont worry about it16:29
*** egonzalez has joined #kolla16:29
nihiliferwhen we have a meeting today?16:32
inc0I guess16:32
inc0I'll be semi afk16:32
inc0tho16:33
britthou_I think now? looks like defcore meeting is still running in openstack-meeting-416:33
inc0no, in one hr16:33
nihiliferI see on wiki that 16:30 UTC16:33
nihilifernow it's 16:33 UTC ;)16:33
*** britthou_ is now known as britthouser16:34
inc0my calendar says in 1hour16:35
nihiliferok16:35
inc0but well, that might be due to time change16:35
inc0gosh I hate daylight savings16:35
nihiliferthat daylight save change is so confusing...16:35
britthouserI like daylight savings, not a big fan of daylight spending16:36
inc0badum tss;)16:36
nihilifer:D16:37
*** cloudnautique has quit IRC16:38
*** unicell has joined #kolla16:38
*** unicell1 has quit IRC16:40
*** cloudnautique has joined #kolla16:41
*** achanda has joined #kolla16:44
britthouserLooks like defcore meeting (in openstack-meeting-4) started their meeting at 16:00UTC, but they are scheduled to start at 15:00UTC.  I think everyone is suffering from time change. =)16:48
pbourke:/16:50
*** britthouser has quit IRC16:52
*** britthouser has joined #kolla16:52
*** athomas has quit IRC16:52
*** egonzalez has quit IRC16:57
*** athomas has joined #kolla17:00
*** slotti has quit IRC17:14
nihilifertheir meeting ended17:14
*** egonzalez has joined #kolla17:14
*** CBR09 has quit IRC17:15
*** daneyon_ has joined #kolla17:16
*** egonzalez has quit IRC17:18
*** egonzalez has joined #kolla17:19
*** daneyon has quit IRC17:19
*** mfalatic has joined #kolla17:20
*** egonzalez has quit IRC17:20
*** egonzalez has joined #kolla17:21
*** egonzalez has quit IRC17:28
rhalliseyno sdake huh?17:30
*** egonzalez has joined #kolla17:30
rhalliseyI can run the meeting if he's not around.  But are people here?17:31
rhalliseyinc0, pbourke you guys around?17:31
*** egonzalez has quit IRC17:32
bmacepb was about 40 mins ago.17:32
rhalliseywere kinda an hour off UTC here..17:32
rhalliseykinda would like to do some mitaka BP planning..17:33
rhalliseyday light saving may have gotten the best of us here17:33
bmaceyeah, there were a couple of kollaclient things we wanted to bring up too, to see how folks felt about it.17:33
rhalliseySamYaple, around?17:34
nihiliferyep, I also wanted to discuss some Mitaka BPs17:34
nihiliferasalkeld: you here?17:34
rhalliseybmace, I don't know mow much discussion we can get since looks like we only have 3 here atm17:35
*** cloudnau_ has joined #kolla17:35
*** cloudnau_ has quit IRC17:35
*** cloudnau_ has joined #kolla17:36
bmaceyeah, i appreciate that, looks like the 2nd consecutive weekly meeting skip (same happened the week before tokyo)17:36
rhalliseythis one I think was a bit more important since we clearly have some things that need to be discussed17:36
nihiliferok, it seems that asalkeld and inc0 are not here, so no point in discussing Mesos17:36
inc0nihilifer, I'm here, but Angus is in AUS, so it's late night for him17:37
inc0let's meet tomorrow morning17:37
nihiliferinc0: ok17:38
*** cloudnautique has quit IRC17:38
rhalliseybmace, ok sorry I guess we will just have to mention it to sdake when he's around17:39
bmaceyeah, sdake and i had talked about the issues already, we just wanted to pass them by a larger audience.  next week i guess.17:39
bmacehopefully :)17:40
rhalliseyI guess we will blame to time change :(17:40
bmacewell, regardless if it was now or an hour ago, a bunch of folks aren't around17:40
*** akwasnie has quit IRC17:41
*** ChanServ sets mode: +o rhallisey17:42
*** rhallisey changes topic to "Kolla IRC meetings on Wednesday 16:30 UTC (Day light savings doesn't apply) - Agenda @ https://wiki.openstack.org/wiki/Meetings/Kolla - IRC channel is *LOGGED* @ http://eavesdrop.openstack.org/irclogs/%23kolla/"17:42
*** rhallisey sets mode: -o rhallisey17:42
rhallisey:/17:43
pbourkerhallisey: missed your notification there17:45
*** Slower_ has quit IRC17:45
pbourkeassumed the meeting was not happening17:45
rhalliseypbourke, well I was going to run it if we had enough people aorund17:45
pbourkewhats the deal with daylight savings though, it should have been an hour ago right?17:45
rhalliseyya it should've been, but someone else made the same mistake17:46
*** v1k0d3n has joined #kolla17:51
v1k0d3nNo guest IP was given to the Vagrant core NFS helper. This is an17:52
v1k0d3ninternal error that should be reported as a bug.”17:52
v1k0d3nhello everyone. i tried to run the vagrant demo for kolla today, and got an error. "17:52
v1k0d3ncrap...well that came out wrong. haha17:52
v1k0d3nline 3 before line 1. anyway, is that a vagrant specific error or has anyone seen this error before?17:52
pbourkev1k0d3n: recommend you set provider to virtualbox in the Vagrantfile17:52
nihiliferv1k0d3n: hello17:52
pbourkev1k0d3n: unless you have experience using vagrant-libvirt and nfs17:52
v1k0d3nhi...sorry for that garbage dump :)17:53
v1k0d3nah, i was going to do that, but when i did a vagrant status it showed virtualbox by default so assumed i was good.17:53
v1k0d3ni will do that!17:53
v1k0d3nthanks17:53
*** unicell1 has joined #kolla18:03
*** unicell has quit IRC18:03
openstackgerritHui Kang proposed openstack/kolla: Add error handler for unknown build type  https://review.openstack.org/24170718:05
*** cloudnau_ has quit IRC18:05
*** cloudnautique has joined #kolla18:06
*** inc0 has quit IRC18:25
openstackgerritHui Kang proposed openstack/kolla: Add error handler for unknown build type  https://review.openstack.org/24172018:29
*** vilobhmm11 has joined #kolla18:53
*** tzn has joined #kolla19:01
*** gfidente is now known as gfidente|afk19:02
*** jmccarthy has quit IRC19:06
*** bradjones has quit IRC19:26
*** guruMeditator has joined #kolla19:32
guruMeditatorGreetings. I am attempting to deploy a Compute node with Neutron that has multiple provider networks. Each provider network is on a different interface. I see that the Neutron external interface is defined with "neutron_external_interface". Is it possible to accomplish this?19:35
*** diogogmt has joined #kolla19:36
diogogmtanybody knows what is the status on the ansible 2.0 integration? http://blog.oddbit.com/2015/10/26/ansible-20-new-openstack-modules/19:36
diogogmtdid everything get migrated to ansible 2.0 or is it still recomended to use 1.9?19:37
rhalliseyguruMeditator, I haven't tried this personally, SamYaple might know, but he's sleeping atm19:43
guruMeditatorThanks rhallisey19:46
*** achanda has quit IRC19:49
*** achanda has joined #kolla19:52
diogogmtanybody has been using the vagrant file form the kolla repo to provision dev environments? https://github.com/openstack/kolla/blob/master/doc/vagrant-dev-env.rst20:00
diogogmtis it up to date?20:00
*** tzn has quit IRC20:01
rhalliseydiogogmt, ya I'm pretty sure it's solid20:04
rhalliseyI haven't used it though20:04
rhalliseymandre or pbourke primary work on it20:04
rhalliseybut I believe it's in good shape20:05
*** _tzn has joined #kolla20:05
diogogmtrhallisey: ok, i’m giving it a try now20:05
*** dwalsh has joined #kolla20:07
diogogmtrhallisey: mandre pbourke : i’ve noticed that only the vagrant libvirt provider supports nfs, any particular reason for it? can i enable nfs for virtual box providers as well? i’m running on a mac an  i usually prefer to use nfs instead of vboxsharing20:11
*** _tzn has quit IRC20:17
*** tzn has joined #kolla20:25
*** khomkrit has quit IRC20:26
nihiliferdiogogmt: it should work20:28
rhalliseydiogogmt, http://eavesdrop.openstack.org/irclogs/%23kolla/%23kolla.2015-11-04.log.html#t2015-11-04T17:52:0120:28
rhalliseyI think this was brought up earlier20:29
diogogmtnihilifer: ok, after i finish the first deployment with vboxshared folders i’ll change to nfs and see how it goes20:30
nihiliferdiogogmt: sure. if nfs on virtualbox will work, then probably we should enable it by default20:33
nihiliferI use libvirt everywhere, so it'd be hard for me to test it today :/20:33
diogogmtnihilifer: makes sense, if it works on my local i’ll open a pull request with the change20:37
diogogmtbtw, do you use vagrant on linux with libvirt?20:37
diogogmtor mac?20:37
nihiliferlinux20:40
nihiliferwith kvm20:41
nihiliferI don't know whether compiling/running libvirt is possible on mac20:42
nihiliferat all20:42
*** inc0 has joined #kolla20:42
inc0hey20:42
*** cemason has joined #kolla20:44
v1k0d3nhey guys...so this image has been building for a long, long time. finally finished with the following...very non-descriptive errors: INFO:__main__:Images that failed to build20:55
v1k0d3nERROR:__main__:gnocchi-a Failed with status: parent_error20:55
v1k0d3nERROR:__main__:gnocchi-b Failed with status: error20:56
v1k0d3nthis was in the vagrant environment...within the vm. any ideas?20:56
rhalliseyv1k0d3n, gnocchi doesn't work20:58
rhalliseyso don't worry about it20:58
v1k0d3nawesome. forgotten already! :)20:58
inc0I personally think we should remove it from codebase21:00
inc0it's obviously not supported21:00
inc0that being said, we want to have full tent21:01
*** dwalsh has quit IRC21:01
*** achanda has quit IRC21:03
*** shardy has quit IRC21:06
v1k0d3nmakes sense21:06
v1k0d3nso ansible is bringing up the environment ultimately. are you guys planning on possibly using kubernetes as a  deployment and scheduling options?21:07
v1k0d3nor something like k8s?21:07
*** dwalsh has joined #kolla21:07
v1k0d3nthis is the first time i have looked at kolla and farthest i've ever gotten with it. the project has my full attention though...i'm fascinated with this project! :)21:08
inc0v1k0d3n, we tried k8s but it doesn't have features we need21:11
inc0like net=host21:11
*** cemason has quit IRC21:11
inc0however, if you look at latest openstack-dev post about kolla, there is lenghty discussion about mesos21:11
v1k0d3nso i guess mesos makes sense...it's a generic scheduler. is that why?21:12
inc0well, marathon does support deployment with stuff like net=host21:12
v1k0d3ncouldn't kubernetes issues be opened to included net=host?21:12
inc0I think they are, not sure tho, not my center of interest;)21:12
inc0anyway, that blocks us, mesos has it implemented21:13
inc0and for now our main way of deployment is ansible, and it will stay this way for now21:13
*** alisonh has quit IRC21:13
v1k0d3nwhat if i can pay them in beer to make this happen. would that work then, or are there other missing features?21:14
*** daneyon_ has quit IRC21:15
v1k0d3nsurely their immediate team isn't so large that a few east coast brews can't adjust some work priorities, right?21:16
inc0well, I also heard about issues with privileged containers21:16
inc0still, I guess I don't really know if it solves any immediate problem;)21:17
v1k0d3neh, no they caved on that one21:17
v1k0d3nthockin was pretty upset about it though from what i was reading in the previous issues lists21:17
*** jasonsb has quit IRC21:22
asalkeldo/21:22
inc0hey asalkeld what are you doing on such...horrible hour to be awake on?21:23
v1k0d3ninc0: is there an example for all-in-one for kolla? looking through does...seems to reference devstack for that information maybe?21:24
v1k0d3ni understand devstack, but seems a little different with the flags/format etc.21:24
v1k0d3noh crap...i think i did it wrong actually21:26
inc0v1k0d3n, https://github.com/openstack/kolla/blob/master/doc/quickstart.rst21:27
v1k0d3nthat build was a big waste lol! i logged into the vagrant host and performed a tools/build.py, rather than kolla-build i guess?21:27
*** alisonh has joined #kolla21:29
v1k0d3ntrying to figure out if i use the vagrant up approach, if i need to still modify /etc/kolla/global.yaml or not21:29
v1k0d3nwelp guess so21:29
inc0tbh I never used vagrant21:30
inc0I always deployed it by hand and it works quite well21:30
v1k0d3nby hand in a vm for testing?21:30
inc0by "by hand" I mean using ansible-playbook command21:31
nihiliferinc0: v1k0d3n: k8s seems to support net=host, pid=host now. but well, mesos supported it earlier. first come, first served :)21:33
nihilifers/mesos/mesos+marathon21:33
*** tzn has quit IRC21:34
nihiliferv1k0d3n: about vagrant, you shouldn't gave to modify global.yaml21:35
nihiliferhave*21:35
nihiliferthere is no difference between running tools/build.py and kolla-build21:36
v1k0d3nnihilifer: awe come on now!? k8s has so much momentum right now21:36
v1k0d3nperhaps consider this?21:36
v1k0d3nhttps://github.com/appc21:37
*** gfidente|afk has quit IRC21:38
nihiliferumm... is this about ACI? and then more related to rkt than docker?21:40
v1k0d3nnot from what i understand. there are sub-sections that i think are more specific to the way orchestration components tie into each other. a modular framework effort.21:41
nihiliferok, I'll take a look on it21:42
v1k0d3nCNI is interesting...coming up with a standard interface in which things like weave, flannel, etc etc would be pluggable into the k8s or mesos overall architecture.21:42
v1k0d3nbut this may simplify it for teams providing containerized applications. so kolla wouldn't have to choose between one or another. the dependancies would be just part of the modular framework.21:43
v1k0d3nbtw...at least in the vagrant envionment...there are complaints about globals.yaml (interface information was incorrect). do i need to change this?21:45
v1k0d3nfatal: [localhost] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute u'ansible_eth1'", 'failed': True}21:45
v1k0d3neth1 is probably the culprit?21:46
v1k0d3nno its the slow user who forgot to "sudo kolla-ansible deploy" sorry for my ignorant moment.21:47
*** dwalsh has quit IRC21:47
v1k0d3nok no it's still there....21:50
*** tzn has joined #kolla21:50
inc0yeah, it happends from time to time21:51
inc0can't remember solution from top of my head21:51
inc0apart of adding enable_haproxy: no to global.yml21:51
inc0so no ha deployment21:51
inc0but if you do aio that shouldn't be an issue21:52
inc0SamYaple, around?21:52
v1k0d3nyeah this is AIO21:52
asalkeldinc0: it's nearly 8am21:52
inc0ah, daylight savings I guess21:53
inc0v1k0d3n, add enable_haproxy: no to global.yml21:53
inc0that should be quick and dirty way to solve it21:53
v1k0d3nok, let me try. does this stay the same? kolla_internal_address: "10.10.10.254"21:54
v1k0d3nthat's default...has nothing to do with my network though :)21:54
inc0good point21:54
inc0change it to your normal ip addr21:55
inc0if you'd do HA deployment - this would be your keepalived floating ip21:55
v1k0d3nwell shoot...in that case then..the interfaces are off too.21:55
*** rhallisey has quit IRC21:55
inc0well, ifaces should be your own ifaces21:56
inc0that was probably root cause of problem;)21:56
v1k0d3nok, that's cool...and makes sense.21:56
v1k0d3nso globals.yaml definitely needs a little tweaking.21:57
v1k0d3ni want to blog about this a little.21:57
inc0to be fair - it's all in quickstart doc;)21:57
v1k0d3nwouldn't mind seeing what you guys are doing with the mesos side as well.21:57
v1k0d3nso if i can run mesos and k8s side by side happily...i want to try it.21:57
v1k0d3n:)21:57
v1k0d3nlol21:57
inc0our plan is to have kolla-ansible, kolla-mesos, maybe kolla-k8s21:58
inc0and so on21:58
v1k0d3ni know...i can't say anything against the qsg...got me to this point so in my book it's freaking amazing! :D21:58
v1k0d3ndude...i would love to help with this!21:58
inc0its all in community21:58
v1k0d3nif there's anything i can do to help with kolla-k8s please let me know21:58
inc0I'm sure mesos guys would love to have help:)21:58
v1k0d3nand i know that nzwulfin from atomic is interested too. we talked about it this morning21:59
inc0about kolla-k8s21:59
inc0you would need to confirm that k8s has all the pieces needed22:00
v1k0d3nso i get this straight...eth0 in globals.yaml is the address i want to ACCESS from the AIO interface is that correct?22:00
inc0then we would need to brainstorm way to generate configs, that will be tricky22:00
*** achanda has joined #kolla22:00
v1k0d3ninc0: i agree...i can talk with the k8s folks and try and get support for this.22:00
inc0in globals.yml there are 2 ifaces22:00
v1k0d3nthere are a couple of other folks interested in this effort too (from a k8s perspective). i think it would get a lot of support.22:00
v1k0d3nso change both to the same for AIO?22:01
inc0network_interface: "eth0" this one should have ip22:01
inc0no, neutron has to have it's own interface22:01
inc0you need at least 2 interfaces to deploy kolla22:01
inc0one for endpoints and such, another one for neutron22:01
nihiliferyes, and if you're running on vagrant, you should have these 2 interfaces22:02
v1k0d3nah, yes...i do22:02
nihiliferand if you say that there are some people interested in running kola on k8s22:03
nihiliferand they can help with implementation22:03
inc0v1k0d3n, about kolla-k8s - the way we see it is more like "you want it- you implement it"22:04
v1k0d3nlol22:04
v1k0d3ndude...inc0...harsh22:04
v1k0d3nbut i understand22:04
inc0didnt mean it this way22:04
nihilifernot harsh, that's what I wanted to write22:04
inc0just...you know22:04
nihilifergo ahead with registering blueprint with k8s22:04
inc0we have plenty on our table right now;)22:04
nihiliferif you have people which can help with it22:04
v1k0d3nno, i get it totally.22:04
v1k0d3neveryone has plenty on their table right now.22:05
v1k0d3ni completely understand.22:05
inc0I'll be happy to provide reviews and guidance, but I'll be frank - not top of my priority list;)22:05
v1k0d3nso i work for large telecom. huge. you know...bought a tv comp recently.22:05
nihiliferthe question is how much time you have for playing with kolla and k8s22:05
v1k0d3nwe have a LOT of old school thinking around here.22:05
inc0so if you want to do implementation, sure, follow kolla-mesos example22:05
nihiliferand especially whether some of you would like work full time on it22:05
inc0that means creating new repo and such22:06
v1k0d3nthe benefit of OS in an orchestrated environment is huge. esp for blue/green deployments.22:06
inc0our main goal is to support 100ish node cluster22:06
v1k0d3nthing is, people have old mindsets...that will never work, why would you ever do that, etc etc. i'm trying to prove out that this can be done, and it actually may be a good idea.22:06
inc0(but with option to deploy huge clusters as well)22:06
inc0but 100 is our priority as it's what most people have22:07
inc0and ansible works in this scale22:07
inc0v1k0d3n, look closely what kolla-mesos will do, you might find allies there22:08
inc0and mesos might meet your requirements just as good as k8s22:08
inc0if you think mesos will be good alternative to k8s, I'd suggest you investing your time to help them22:09
inc0this way you can make this approach work better instad of adding new one22:09
inc0(also would make core team job whole lot easier;) just one new orchiestrator at the time)(22:09
inc0but we're free community and we want to keep our minds as open as possible, so if you want to experiment with k8s, I won't stop you, I'll even encourage you to make a poc or whatever;)22:10
inc0anyway, after this lenghty monologue, I'm going off;)22:11
inc0have a good night folks22:11
nihilifergood night22:11
inc0v1k0d3n, have fun with our project;)22:11
*** inc0 has quit IRC22:12
asalkelddoes any know if it would be possible to use anisble (in kolla) to just generate the configuration (stuff that goes under /etc)22:12
asalkeld(so, don't do the deployment22:13
nihiliferasalkeld: config files are generated by tasks in config.yml of each role22:14
nihiliferso probably if we tag the specific tasks22:15
nihiliferand run ansible only with this tag22:15
nihiliferthat can work22:15
*** sdake has joined #kolla22:17
sdakeyo22:18
asalkeldnihilifer: ok22:22
*** cloudnau_ has joined #kolla22:22
asalkeldnihilifer: it would make for a lot less work in kolla-mesos if we can do that22:23
diogogmtnihilifer: quick question, if i want to submit a pull request to kolla, do i branch off from master and submit the pr to the github repo?22:24
diogogmtif you have a document explaining the dev flow that would be helpful as well22:24
*** jasonsb has joined #kolla22:25
*** cloudnautique has quit IRC22:25
asalkelddiogogmt: https://wiki.openstack.org/wiki/Documentation/HowTo22:26
*** achanda has quit IRC22:26
asalkeldo, that's for docs22:27
asalkelddigging up the right thing22:27
*** cloudnau_ has quit IRC22:27
asalkeldhttp://docs.openstack.org/contributor-guide/first-timers-quickstart.html22:28
asalkelddiogogmt: ^22:28
diogogmtasalkeld: thanks, i’ll check it out22:28
*** achanda has joined #kolla22:30
*** sdake_ has joined #kolla22:30
*** sdake has quit IRC22:31
v1k0d3nnihilifer: question...is there a way to clean and rerun kolla-ansible deploy? seems like i'm getting db errors and wondering if rerunning or cleaning would help.22:32
*** alisonh has quit IRC22:34
*** alisonh has joined #kolla22:37
diogogmtasalkeld: based on the doc you sent do i need to create a blueprint if i want to submit a patch for a non bug? in my case i just want to submit a pull request to update the Vagrantfile22:39
diogogmtshould i create a blueprint?22:40
asalkelddiogogmt: for kolla, only if it is a really big change22:49
asalkeldi'd assume not though22:49
diogogmtasalkeld: exactly, it is just a small change22:50
diogogmtasalkeld: which flow would you suggest i follow?22:50
asalkelddiogogmt: i'd just do a "git review" with a good explaination of the change22:51
diogogmtasalkeld: so for small changes do i need to branch out or can i commit straight to master?22:53
asalkeldyou can use master, but try a little branch - they are easy22:54
asalkeldkeeping your master clean of local changes is a good practise, and makes your life easier22:54
SamYaplesdake_: ping22:56
diogogmtasalkeld: ok, just want to make sure i’m following whatever flow the community already uses22:57
diogogmtthanks buddy22:57
asalkeldno problem22:57
v1k0d3nis there any way to avoid this error? TASK: [mariadb | Creating haproxy mysql user] ********************************* \ "msg": "unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials. Exception message: (2013, 'Lost connection to MySQL server at \\'reading initial communication packet\\', system error: 0 \"Internal error/check (Not system error)\"')"23:06
v1k0d3ni added / enable_haproxy: "no" / as inc0 recommended.23:07
SamYaplev1k0d3n: that error has nothing to do with haproxy since it doesnt go through haproxy23:13
SamYaplethats just creating a dumb user in myself to verify functionality23:13
SamYaplehow many nodes is this v1k0d3n ?23:14
v1k0d3nAIO23:14
v1k0d3njust testing for now...exploring.23:14
SamYaplewhat are the logs for the mariadb container?23:14
v1k0d3nah. interesting23:15
v1k0d3n151104 23:12:06 [ERROR] Can't start server: listen() on TCP/IP port: Address already in use23:15
v1k0d3nso...globals.yaml config error?23:15
SamYaple`ss -plnt` and look for whats listening on the port23:15
SamYapleit sounds like you have mysql running on the machine23:15
SamYapleoutside of kolla23:15
SamYapleunless you changed the default port23:15
bmace+1 to that SamYaple23:15
bmacepretty common23:15
SamYaplevbel is writing some checks to ensure that doesnt happen23:16
SamYapleshoot i missed the meeting today23:17
v1k0d3nhmmm23:17
SamYaplemy time is all out of whack23:17
v1k0d3nso nothing on the host machine is listening on 330623:17
v1k0d3nhowever...within kolla vagrant guest 3306 is still running.23:18
bmaceyou weren't the only one Sam :)23:18
*** jasonsb has quit IRC23:18
bmacei think there was another group having their meeting in our slot23:18
*** jasonsb has joined #kolla23:18
*** tzn has quit IRC23:18
SamYaplev1k0d3n: I don't know much about vagrant, but if you can identify the process running and binding 3306 you can shut it down23:19
SamYapless -plnt will give you the pid23:19
v1k0d3nrunning in OSX...but there is nothing running on port 3306 at all23:19
SamYapleit would be whatever is binding the port on the host docker is running on (be if VM or otherwise)23:20
SamYaplesomething is using it, ss will tell you what so you can stop it23:20
*** diogogmt has quit IRC23:20
SamYaplealternatively i suppose you could just change the port number23:20
v1k0d3nso i had to rerun the ansible deploy a couple of times23:21
v1k0d3nis there a way to clean and rerun?23:21
bmacekill / rm all the containers then re-run?23:21
v1k0d3n3306 is definitely running inside the host...but i believe it was brought up by a previous kolla-ansible deploy. could that be the case?23:21
v1k0d3nok23:21
SamYapleyes i suppose23:22
SamYaplewe recommend a full clean before reruns23:22
bmacedue to the container naming it shouldn't really be possible to have 2 db containers running on the same host..23:22
SamYapleyoure right, but the bootstrap process would break bmace23:22
*** tzn has joined #kolla23:23
*** cemason has joined #kolla23:23
v1k0d3nSamYaple: good to know about full cleans. i figured there had to be a way...didn't realize it would be as easy as just flushing all the containers and deleting (makes sense though)23:24
SamYaplethere should be a tool for that23:25
SamYaplecleanup-containers I believe23:25
SamYaplesome people use it all the time, im not one of them but others say it works23:25
*** diogogmt has joined #kolla23:26
*** asalkeld has quit IRC23:26
v1k0d3ni completely agree. the whole docker stop $(docker ps -a -q) / docker rm $(docker ps -a -q) ...23:26
v1k0d3nis getting old. why should we still have to type all of that?23:27
v1k0d3ntrying deploy again...and...man, this is frustrating...23:27
v1k0d3noh my!23:27
*** cemason has quit IRC23:27
v1k0d3ndoing that command just borked my running registry container!23:28
v1k0d3nwhat an idiot.23:28
v1k0d3nlol23:28
v1k0d3ni'm sitting here laughing at myself at how dumb that was.23:28
*** asalkeld has joined #kolla23:29
bmaceyeah, when doing the stop / rm it is good to also use the distro property name so that you only nuke the kolla specific containers23:29
SamYaplev1k0d3n: it shouldnt have23:29
SamYapleit has an explicit list of things to stop23:29
SamYaplev1k0d3n: https://github.com/openstack/kolla/blob/master/tools/cleanup-containers23:30
v1k0d3nok...didn't see that.23:30
v1k0d3njust started playing with this today.23:30
v1k0d3none of those tools start up the local registry again? :D23:30
v1k0d3nlesson learned...don't do it manually with the "docker rm $(docker ps -a -q)" command23:31
SamYaplev1k0d3n: http://paste.openstack.org/show/478029/23:32
SamYaplethats my bash_aliases file23:32
SamYaplei run kolla_reset23:33
SamYapleyou might be able to tweak it to do what you want23:33
*** blahRus has quit IRC23:40
SamYaplepbourke: ping23:41
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150023:42
SamYapleasalkeld: did you ever determine the size of the zookeeper client?23:42
asalkeldSamYaple: it's just a python client "kazoo"23:42
SamYaple121kB might be just a bit too large for us23:43
SamYaplei would recommend the packaged versions of kazoo (if they exist) otherwise we would have to install pip in the base container23:44
SamYaplethats a bit more of a refactor23:44
SamYaplein the opposite direction23:44
asalkeldsure23:44
asalkeldSamYaple: i am trying to run kolla ansible to just generate the services config (stuff that gets into the bind mount eventually)23:49
asalkeldso i started by tagging one of the config.yml23:49
asalkeldi get this: ERROR: merge_configs is not a legal parameter in an Ansible task or handler23:50
diogogmtasalkeld: i keep getting this error when connecting to gerrit: http://permalink.gmane.org/gmane.comp.cloud.openstack.devel/6008923:50
diogogmtany thoughts?23:50
SamYapleasalkeld: merge_configs is a module i wrote23:50
SamYapleasalkeld: https://github.com/openstack/kolla/blob/master/ansible/library/merge_configs.py23:50
SamYapleadd that to your library directory next to roles23:50
asalkeldSamYaple: i am runing kolla ansible23:51
asalkeldmaybe filtering by tag is stopping this getting setup?23:51
SamYapleno, that sounds like you are missing a file or your directories are out of what23:51
asalkelddiogogmt: try "git review -s"23:51
SamYapleyou should check that 'kolla/ansible/library/merge_configs.py' exists23:52
asalkeldhttp://paste.openstack.org/show/478031/23:52
asalkeldthat's the only change i have23:52
asalkeld file ansible/library/merge_configs.py23:53
asalkeldansible/library/merge_configs.py: Python script, ASCII text executable23:53
*** Hui has quit IRC23:53
diogogmtasalkeld: i did, i keep getting this error: http://pastebin.com/VurmXp9J23:53
SamYapleweird indeed. try running the ansible command directly asalkeld , from the kolla/ansible folder23:54
asalkeldok SamYaple thanks23:54
asalkelddiogogmt: do you have out going ssh blocked?23:55
asalkeldssh://diogogmt@review.openstack.org:29418/openstack-dev/sandbox.git23:56
asalkeldseems to exist: https://github.com/openstack-dev/sandbox23:56
asalkelddiogogmt: grep -A2 gitreview ~/.gitconfig23:57
asalkeld[gitreview]23:57
asalkeldusername = asalkeld23:57
asalkeld(so you don't keep getting asked for your username)23:58
diogogmtasalkeld: i never had a problem like that before, maybe i’ll try the https setting instead23:59
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Deploy multinode in gate  https://review.openstack.org/24150023:59

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