Tuesday, 2016-06-07

*** ssurana has joined #openstack-kolla00:00
*** fragatina has quit IRC00:01
*** matrohon has joined #openstack-kolla00:02
*** fragatin_ has quit IRC00:02
openstackgerritKen Wronkiewicz proposed openstack/kolla: Config files having underscores breaks Kolla-Kubernetes.  https://review.openstack.org/32618100:03
*** salv-orlando has quit IRC00:04
*** ssurana has quit IRC00:04
*** mbound has quit IRC00:04
*** salv-orlando has joined #openstack-kolla00:05
*** fragatina has joined #openstack-kolla00:05
*** sdake_ has quit IRC00:05
*** fragatina has quit IRC00:07
*** fragatin_ has joined #openstack-kolla00:07
*** fragatin_ has quit IRC00:08
*** godleon has joined #openstack-kolla00:15
*** asalkeld has joined #openstack-kolla00:16
*** rahuls has quit IRC00:18
*** ssurana has joined #openstack-kolla00:27
*** asalkeld has quit IRC00:37
*** sdake has joined #openstack-kolla00:38
*** zhiwei has joined #openstack-kolla00:44
*** salv-orlando has quit IRC00:53
*** salv-orlando has joined #openstack-kolla00:54
*** sacharya has joined #openstack-kolla00:59
*** sacharya has quit IRC01:04
openstackgerritJeffrey Zhang proposed openstack/kolla: Remove the deprecated kolla-build section  https://review.openstack.org/32570901:05
*** harlowja has joined #openstack-kolla01:08
*** ssurana has quit IRC01:40
*** sdake has quit IRC01:50
*** sacharya has joined #openstack-kolla01:59
*** sdake has joined #openstack-kolla02:11
*** sdake_ has joined #openstack-kolla02:18
*** sdake has quit IRC02:20
*** mark-casey has joined #openstack-kolla02:46
*** mbound has joined #openstack-kolla02:47
*** phuongnh has joined #openstack-kolla02:49
*** yuanying_ has joined #openstack-kolla02:51
*** yuanying has quit IRC02:51
*** mbound has quit IRC02:51
*** matrohon has quit IRC02:51
*** klint has joined #openstack-kolla02:52
*** fragatina has joined #openstack-kolla03:10
*** fragatin_ has joined #openstack-kolla03:11
*** phuongnh has quit IRC03:13
*** fragatina has quit IRC03:15
coolsvapsdake_, evening03:17
*** sdake_ has quit IRC03:38
*** mark-casey has quit IRC03:45
*** daneyon_ has joined #openstack-kolla03:51
*** daneyon has quit IRC03:54
*** daneyon has joined #openstack-kolla04:00
*** daneyon_ has quit IRC04:03
*** yuanying_ has quit IRC04:18
*** yuanying has joined #openstack-kolla04:21
*** salv-orl_ has joined #openstack-kolla04:25
*** salv-orlando has quit IRC04:27
*** dave-mccowan has quit IRC04:35
*** sacharya has quit IRC04:36
*** sacharya has joined #openstack-kolla04:37
*** sacharya has quit IRC04:42
*** sacharya has joined #openstack-kolla05:38
*** salv-orl_ has quit IRC05:40
*** salv-orlando has joined #openstack-kolla05:40
*** sacharya has quit IRC05:43
*** tfukushima has joined #openstack-kolla06:01
*** fragatin_ has quit IRC06:34
*** Mr_Broken has joined #openstack-kolla06:43
openstackgerritJeffrey Zhang proposed openstack/kolla: Bump the ansible version to >2 in the kolla-toolbox  https://review.openstack.org/31162507:01
*** salv-orlando has quit IRC07:04
*** salv-orlando has joined #openstack-kolla07:05
*** Serlex has joined #openstack-kolla07:07
*** daneyon_ has joined #openstack-kolla07:16
*** shardy has joined #openstack-kolla07:21
*** daneyon_ has quit IRC07:21
*** matrohon has joined #openstack-kolla07:23
*** coolsvap is now known as coolsvap|lunch07:25
*** coolsvap|lunch is now known as coolsvap07:26
*** athomas has joined #openstack-kolla07:26
*** mikelk has joined #openstack-kolla07:29
*** salv-orlando has quit IRC07:56
*** salv-orlando has joined #openstack-kolla07:56
*** SiRiuS has joined #openstack-kolla07:57
*** godleon has quit IRC07:59
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix the neutron reconfigure issue  https://review.openstack.org/32628008:01
openstackgerritJeffrey Zhang proposed openstack/kolla: Run more kolla-ansible task in the gate  https://review.openstack.org/32628108:05
*** iceyao has joined #openstack-kolla08:21
*** tyrola has joined #openstack-kolla08:24
*** wmiller has left #openstack-kolla08:42
*** Jeffrey4l has joined #openstack-kolla08:57
*** iceyao has left #openstack-kolla08:57
*** iceyao has joined #openstack-kolla08:58
*** tfukushima has quit IRC09:02
*** tfukushima has joined #openstack-kolla09:02
openstackgerritJeffrey Zhang proposed openstack/kolla: DO NOT MERGE: TEST UBUNTU MULTIGATE  https://review.openstack.org/32630709:04
*** dmk0202 has joined #openstack-kolla09:05
*** tfukushima has quit IRC09:07
*** papacz has quit IRC09:14
*** wmiller has joined #openstack-kolla09:21
*** jmccarthy has left #openstack-kolla09:22
*** jmccarthy has quit IRC09:22
coolsvapJeffrey4l, around?09:22
Jeffrey4lcoolsvap, yup.09:23
coolsvapjeblair, regarding your patch 32628109:23
patchbotcoolsvap: https://review.openstack.org/#/c/326281/ - kolla - Run more kolla-ansible task in the gate09:23
coolsvapdid you had a chance to look at https://etherpad.openstack.org/p/kolla-newton-summit-kolla-functional-gating09:23
coolsvapjeblair, unping09:24
coolsvapJeffrey4l, ^^09:24
Jeffrey4lcoolsvap, checked.09:24
Jeffrey4lso?09:24
Jeffrey4lwhat's your opinion about this?09:24
coolsvapwe need to split the ansible tasks in different gates rather than keeping all09:25
coolsvapso that it gives better coverage of whats working and whats not09:25
*** jmccarthy has joined #openstack-kolla09:25
Jeffrey4li think put it to the same gate should be OK.09:25
Jeffrey4lat least, the precheck, reconfigure here is Ok.09:26
*** tzn has joined #openstack-kolla09:26
*** mgoddard_ has quit IRC09:26
coolsvapyes, but we need to look at a long list of configuration values that can be used to configure kolla09:27
coolsvapprecheck can be here but we need the deploy_aio configurable09:27
Jeffrey4l` but we need to look at a long list of configuration values that can be used to configure kolla` what means by this?09:28
coolsvapif you look at the above etherpad09:28
Jeffrey4lest Reconfigure with copy_always easy09:29
Jeffrey4lTest Reconfigure with copy once easy ? this?09:29
Jeffrey4lso, we will have a gate to test the copy_always, and another gate to test the copy_once?09:30
Jeffrey4lright09:30
coolsvapreconfigure has two ways when we do it09:30
Jeffrey4l?09:30
coolsvapyes09:30
Jeffrey4lin that way, the number of the gate will grow rapidly.09:32
Jeffrey4l(btw, iirc, we talked the copy_once should be removed long time ago)09:32
coolsvapJeffrey4l, yes and sdake said number of gates should not be a concern as long as they do the job in 30-45 mins09:32
coolsvapwhich most of our gates do now, if the gates go beyond the 90min check too often then we need to assess the reasons behind it09:34
Jeffrey4lin this way, kolla will build the image for several times for one PS.09:35
coolsvapthere was one opinion to setup a registry in infra, but i think we need to revisit its status with sdake09:36
coolsvapdo you know anything related to it?09:36
Jeffrey4lno. but the registry is a good idea.09:37
Jeffrey4lOr deploy multi times in the gate.09:37
Jeffrey4l1. build the required image 2. deploy with copy_always, and test then clean 3. deploy with copy_once and test then clean09:38
coolsvapyes and this can be done for most of the combinations09:38
*** mbound has joined #openstack-kolla09:39
coolsvapand thats why we need deploy script configurable09:39
Jeffrey4lkolla have many combination, we can not set each gate for every combination.09:39
Jeffrey4lyes.09:39
Jeffrey4lmaybe we can talk this in the meeting.09:39
coolsvapyes09:39
Jeffrey4lok. cool09:39
*** sacharya has joined #openstack-kolla09:40
Jeffrey4lOr, whatever the conclusion is in the meeting. I expect to merge my PS ( may be add a TODO is better). we need test them.09:41
*** Serlex has quit IRC09:42
Jeffrey4lWhatever the conclusion is in the meeting. I expect to merge my PS right now( may be add a TODO is better). we need test them.  we can make it better in the future.09:42
Jeffrey4lcoolsvap, ^09:42
coolsvapJeffrey4l, yeah add TODO but before merge also it should pass the gate09:43
*** Serlex has joined #openstack-kolla09:43
Jeffrey4lcoolsvap, the reconfigure crashed the gate. another PS fixing it.09:44
coolsvapJeffrey4l, sure no worries i am 100% in on functional gating to start whichever way we can always make it better09:44
Jeffrey4lcoolsvap, about the sanity check. what about to use the tempest?09:45
*** sacharya has quit IRC09:45
coolsvapJeffrey4l, tempest or rally both could work, rally internally uses tempest for verification, so unless we are doing some performance tests tempest should be sufficient i believe09:46
Jeffrey4lrather than write some sanity check script in the ansible09:46
Jeffrey4lagree09:49
openstackgerritJeffrey Zhang proposed openstack/kolla: Run more kolla-ansible task in the gate  https://review.openstack.org/32628109:54
*** daneyon_ has joined #openstack-kolla09:59
openstackgerritDave Walker proposed openstack/kolla: setup_{RedHat,Debian}.sh, make more idempotent  https://review.openstack.org/32634709:59
*** wmiller has quit IRC10:02
*** daneyon_ has quit IRC10:03
openstackgerritDave Walker proposed openstack/kolla: setup_{RedHat,Debian}.sh, make more idempotent  https://review.openstack.org/32634710:07
openstackgerritDave Walker proposed openstack/kolla: setup_{RedHat,Debian}.sh, make more idempotent  https://review.openstack.org/32634710:10
*** pbourke has quit IRC10:12
*** pbourke has joined #openstack-kolla10:12
*** papacz has joined #openstack-kolla10:21
*** athomas has quit IRC10:24
*** salv-orl_ has joined #openstack-kolla10:25
*** tzn has quit IRC10:26
*** mdnadeem_ has joined #openstack-kolla10:28
*** salv-orlando has quit IRC10:28
*** mdnadeem has quit IRC10:31
*** dave-mccowan has joined #openstack-kolla10:35
*** rhallisey has joined #openstack-kolla10:37
*** rhallisey has quit IRC10:38
*** rhallisey has joined #openstack-kolla10:38
*** rhallisey has quit IRC10:57
*** salv-orl_ has quit IRC11:04
openstackgerritJeffrey Zhang proposed openstack/kolla: Run more kolla-ansible task in the gate  https://review.openstack.org/32628111:04
*** salv-orlando has joined #openstack-kolla11:05
*** salv-orl_ has joined #openstack-kolla11:18
*** salv-orlando has quit IRC11:23
*** iceyao has quit IRC11:23
*** iceyao has joined #openstack-kolla11:24
*** mliima has joined #openstack-kolla11:27
*** mgoddard has joined #openstack-kolla11:28
*** tzn has joined #openstack-kolla11:32
*** jmccarthy has quit IRC11:37
*** rhallisey has joined #openstack-kolla11:37
*** jmccarthy has joined #openstack-kolla11:38
mliimamorning all11:41
*** sacharya has joined #openstack-kolla11:41
*** coolsvap_ has joined #openstack-kolla11:44
*** coolsvap has quit IRC11:45
*** sacharya has quit IRC11:46
*** coolsvap_ has quit IRC11:46
*** coolsvap has joined #openstack-kolla11:46
*** dwalsh has joined #openstack-kolla11:47
*** salv-orl_ has quit IRC11:51
*** salv-orlando has joined #openstack-kolla11:52
*** dwalsh has quit IRC11:55
*** salv-orlando has quit IRC11:58
*** salv-orlando has joined #openstack-kolla11:58
*** Jeffrey4l has quit IRC11:58
*** Jeffrey4l has joined #openstack-kolla11:59
openstackgerritMerged openstack/kolla: Remove the deprecated kolla-build section  https://review.openstack.org/32570912:04
*** coolsvap has quit IRC12:07
*** diogogmt has quit IRC12:14
*** diogogmt has joined #openstack-kolla12:16
*** Serlex has left #openstack-kolla12:18
openstackgerritJeffrey Zhang proposed openstack/kolla: Implement Rally docker file  https://review.openstack.org/32641412:18
*** diogogmt has quit IRC12:24
*** tzn has quit IRC12:37
*** diogogmt has joined #openstack-kolla12:37
*** daneyon_ has joined #openstack-kolla12:41
*** salv-orlando has quit IRC12:42
*** salv-orlando has joined #openstack-kolla12:43
*** iceyao has quit IRC12:45
*** daneyon_ has quit IRC12:46
*** Mr_Broken has quit IRC12:53
*** Mr_Broken has joined #openstack-kolla12:54
*** tzn has joined #openstack-kolla12:55
*** ppowell has joined #openstack-kolla12:56
*** Jeffrey4l has quit IRC12:56
*** Mr_Broken has quit IRC12:58
*** klint has quit IRC13:04
*** Mr_Broken has joined #openstack-kolla13:12
*** Serlex has joined #openstack-kolla13:12
*** inc0 has joined #openstack-kolla13:13
*** jtriley has joined #openstack-kolla13:13
inc0good morning13:13
*** dwalsh has joined #openstack-kolla13:22
*** sdake has joined #openstack-kolla13:27
*** sdake_ has joined #openstack-kolla13:34
*** sdake has quit IRC13:36
*** iceyao has joined #openstack-kolla13:41
*** tfukushima has joined #openstack-kolla13:43
*** tfukushima has quit IRC13:43
*** mgoddard_ has joined #openstack-kolla13:45
*** mgoddard has quit IRC13:48
wirehead_inc0: not sure if there's a better way than blindly renaming things.  If I remove wsrep_notify.sh, then mariadb.json complains about the lack of a file.  Create two configs, that means we're really starting to diverge containers with kube-only containers and ansible-only containers.13:59
inc0ok, fair enough,14:00
inc0wirehead_, mind adding this explanation to review14:01
inc0?14:01
inc0for future sake14:01
inc0also changed -1 to +214:01
wirehead_Done.14:02
wirehead_I did a quick check and the majority of config files are dashes, not underscores.14:03
inc0I guess we should catch that in review of this patch14:03
wirehead_I hate dealing with the OpenStack gate, but I also hate not having an OpenStack gate. :D14:11
rhalliseywirehead_, there are others. I know liyi has a patch up for some other _ issues14:21
wirehead_ not sure if there's a better way than blindly renaming things.  If I remove wsrep_notify.sh, then mariadb.json complains about the lack of a file.  Create two configs, that means we're really starting to diverge containers with kube-only containers and ansible-only containers.14:25
wirehead_Err.14:25
wirehead_https://review.openstack.org/#/c/320159/14:25
patchbotwirehead_: patch 320159 - kolla - Replace underscore sign with dash in neutron confi...14:25
mag009_morning!!14:25
wirehead_Well, I can yank some kube-chains later on today, but I think we're kinda stuck on some level because I'm not sure if they'd make such a change in a 1.2.x build regardless.14:28
*** daneyon_ has joined #openstack-kolla14:30
*** mgoddard_ has quit IRC14:33
*** daneyon_ has quit IRC14:35
*** sdake_ has quit IRC14:36
*** mgoddard has joined #openstack-kolla14:43
*** Serlex has quit IRC14:46
*** tzn has quit IRC14:49
*** tzn has joined #openstack-kolla14:54
mag009_guys14:55
mag009_can someone help me out here14:55
mag009_even with lastest images i'm having issue with the inventory / conditional check14:56
*** vhosakot has joined #openstack-kolla15:02
*** absubram has quit IRC15:02
*** mliima_ has joined #openstack-kolla15:08
*** inc0 has quit IRC15:09
*** inc0 has joined #openstack-kolla15:09
*** thumpba has joined #openstack-kolla15:10
*** mliima has quit IRC15:10
*** zhiwei has quit IRC15:15
*** coolsvap has joined #openstack-kolla15:15
*** Jeffrey4l has joined #openstack-kolla15:16
*** vinkman has joined #openstack-kolla15:16
*** mliima_ is now known as mliima15:16
*** thumpba has quit IRC15:24
*** coolsvap has quit IRC15:26
*** sdake has joined #openstack-kolla15:28
openstackgerritJeffrey Zhang proposed openstack/kolla: Implement Rally docker file  https://review.openstack.org/32641415:29
*** coolsvap has joined #openstack-kolla15:30
*** mikelk has quit IRC15:33
*** thumpba has joined #openstack-kolla15:33
*** tzn has quit IRC15:35
*** lifeless has quit IRC15:37
*** vhosakot has quit IRC15:38
*** Mr_Broken has quit IRC15:39
*** Mr_Broken has joined #openstack-kolla15:40
*** ppowell has quit IRC15:41
mag009_finally found my problem...15:41
*** sacharya has joined #openstack-kolla15:42
inc0mag009_, do tell15:44
*** Mr_Broken has quit IRC15:44
mag009_my inventory was missing a group lbaas15:45
mag009_but the error message in ansible give no clue about it15:45
mag009_i did copied the inventory from the latest well I thought15:45
mag009_guess i didnt15:46
mag009_-_-15:46
sdakemag009_ fwiw I agree with you ansible diagnostics are pretty poor15:46
sdakemag009_ i'm not sure what we can do about that in kolla land15:46
sdakeother then offer some type of linting15:46
mag009_but I can deal with that :)15:47
sdakemag009_ in the big scheme of things, a linting project is low priority imo :)15:47
mag009_i'd rather debug ansible than puppet...15:47
*** sacharya has quit IRC15:47
mag009_the only bug left is the delegate_host for the ceph15:48
mag009_it's not a bug but a miss understanding of how delegate work from my end15:48
*** lifeless has joined #openstack-kolla15:49
sdakehey lifeless15:49
sdakehows life less? ;)15:50
coolsvapsdake, good morning15:50
sdakehey coolsvap15:50
*** vhosakot has joined #openstack-kolla15:52
mag009_funny thing tho to know which group I was missing I used inventory_hostname with union of all the group and it  pointed me to the error if I leave the Or it give me a random error15:53
*** absubram has joined #openstack-kolla15:55
mag009_btw anyone had this behavior before the cleanup sometime leave some docker volume ceph_mon_config for example sometime doesn't get cleanup15:58
*** sacharya has joined #openstack-kolla16:03
*** inc0 has quit IRC16:06
*** inc0 has joined #openstack-kolla16:06
Mech422Morning16:06
mag009_it's noon here16:08
mag009_morning!16:09
*** mgoddard has quit IRC16:10
openstackgerritSteve Hindle proposed openstack/kolla: Read partition tables directly, bypassing stale kernel data for ceph.   The Ceph osd bootstrap/startup logic depends upon reading/writing partition names.  Unfortunately, the /sys file system doesn't get updated when partition names change.  To work aroun  https://review.openstack.org/32660916:12
Mech422mag009_: heh - noon actually sounds like a good time to get up :-)16:13
mag009_Mech422: where you at ? west coast?16:14
*** matrohon has quit IRC16:14
wirehead_naw, us westcoasters are just getting to work.16:14
*** daneyon_ has joined #openstack-kolla16:18
Mech422mag009_: yeah - PHX,AZ16:19
Mech422mag009_: but I'm a night owl - so sleeping till noon sounds good in general :-)16:20
*** daneyon_ has quit IRC16:23
*** salv-orl_ has joined #openstack-kolla16:25
*** ssurana has joined #openstack-kolla16:25
*** salv-orlando has quit IRC16:27
ccesariohey guys16:28
Mech422Mornin16:28
ccesariomorning Mech42216:28
*** thumpba has quit IRC16:29
*** dmk0202 has quit IRC16:30
sdakepbourke around?16:30
pbourkesdake: hi16:31
ccesarioguys, according https://github.com/openstack/kolla/blob/master/doc/cinder-guide.rst I 'm getting this error :  http://paste.openstack.org/show/508716/16:31
ccesarioBut running the commands manually on the "host"  it seems work... http://paste.openstack.org/show/508717/16:31
ccesarioany tip !?16:31
*** coolsvap has quit IRC16:33
*** fragatina has joined #openstack-kolla16:34
*** coolsvap has joined #openstack-kolla16:34
*** fragatina has quit IRC16:35
*** fragatina has joined #openstack-kolla16:35
*** vinkman has left #openstack-kolla16:36
Mech422ccesario: all the basics checkout? your ansible user has sudo and all that fun stuff ?16:43
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Make build.py importable lib  https://review.openstack.org/32610816:43
ccesarioMech422, yep.... double checking now16:44
inc0guys I'd appreciate eyes on this https://review.openstack.org/#/c/326108/316:44
patchbotinc0: patch 326108 - kolla - Make build.py importable lib16:44
inc0every change in build.py is hell to rebase16:44
*** iceyao has quit IRC16:51
Mech422inc0: I only have time for a quick look - but it seems fine.  Project_root etc shouldn't need adjusting cuz the code moved 'sideways' to the new directory16:55
inc0yeah, I just want to get this merged sooner rather than later;)16:56
inc0will have more patches moving stuff around soon16:56
Mech422inc0: the relative paths are always what get me in projects like that...16:57
Mech422inc0: always _something_ you forget to adjust :-P16:57
inc0pbourke, rhallisey mandre can anyone please remind my why are we copying whole docker directory to tmp during build?16:58
cineramasean-k-mooney, you around? we had a handful of minor fixes on your bifrost patch, but also we'd like to help you rebase it if you want16:59
cineramasean-k-mooney: really looking forward to getting this landed :)17:00
mandreinc0: two reasons17:01
mandre1. we need to render the jinja2 templates17:01
mandre2. it allows you to change git branch during build17:01
inc0ok fair enough, I'll keep it there for now but I think we should revisit it, maybe there is some way to make docker build from string17:04
*** thumpba has joined #openstack-kolla17:04
inc0then we can render jinja and put it into StringIO17:04
*** Lyncos has joined #openstack-kolla17:09
Mech422inc0: is include_footer the proper place to put extra drivers for neutron? I want to get started on midonet and calico testing ?17:14
inc0Mech422, so we want to completely change way customizations work17:14
inc0hold on17:15
inc0https://review.openstack.org/#/c/324665/17:15
patchbotinc0: patch 324665 - kolla - Mechanism for Dockerfile customization17:15
inc0I think if this lands we'll deprecate include_footer17:15
inc0sdake, ^ any progress on this one?17:16
inc0can I rebase it, remove sample blocks and get this merged? and solve your missing spots in later patches17:16
Mech422inc0: will that get rolled into stable/mitaka ?  Hmm - should I be targeting stable mitaka for new deploys?17:16
inc0Mech422, no, this will be Neutron17:16
inc0for stable mitaka you need to make it work with includes17:17
inc0newton17:17
inc0omg17:17
Mech422inc0: yeah - just occured to me, maybe I should target N, or even kolla-kube?17:17
Mech422inc0: prolly a couple of months before this goes live...17:17
inc0depends what you need really17:17
Mech422inc0: kolla-kube sounds pretty slick... but probably more then a few months out17:18
inc0as for kolla-kube, sure, just make sure you know what you're getting yourself into;)17:18
inc0it might be very slick, but it's a 2 months old project17:18
inc0so it's RnD still17:18
Mech422inc0: yeah - thats what I'm wondering - got a status meeting at the top of the hour - might try to pin a timeline down more17:18
Mech422master targets N now, right ?17:19
inc0yeah17:19
inc0well17:19
inc0master is master17:19
inc0next release will be N17:19
Mech422ohh - and I could ditch ansible 1.9! :-)17:19
inc0yup17:19
*** tyrola has quit IRC17:19
inc0but if you really want kolla for mitaka with midokura17:20
inc0we can work on that too17:20
Mech422any rough timelines for a stable/newton release ?  couple of months ? 6 months ?17:20
inc0with include footer you can do lot of stuff17:20
inc0http://releases.openstack.org/newton/schedule.html Oct 03-0717:20
Mech422inc0: midokura is targeting mitaka right now - but I'm sure they'll support newton as well - they want to become the 'default' network stack for openstack...17:21
Mech422inc0: Ahh thanks....17:21
inc0Mech422, so again, you really can do stuff as for now17:21
inc0it will be hacky but might work17:21
Mech422inc0: I don't mind the hacky bit for home - but I'd really prefer not to have to re-invent everything in a couple of months...17:22
inc0and when proper customization mechanism lands, you can rewrite it in a proper way17:22
Mech422inc0: I'll see who faints if I propose and end of Oct. release17:22
inc0no, not reinvent17:22
Mech422s/and/an/17:22
inc0general idea will be exactly the same17:23
inc0you'll get just a lot of new tools at your disposal and you'll be able to refactor your customizations17:23
inc0so for example for midokura you'll need to uninstall ovs I think17:23
inc0and build everything and then rebuild only neutron client with customization17:24
Mech422inc0: yeah - you uninstall openvswitch-switchd, leave the kernel module, and Mido drives the kernel module via flows17:24
*** tyrola has joined #openstack-kolla17:24
inc0so with include footer you'd need someting like RUN apt-get uninstall openvswitch-vswitchd...17:24
inc0and you'll be able to ditch that in N17:25
inc0so it won't be that horrible17:25
Mech422inc0: KK - thanks...I'll start digging :-)17:25
inc0sure, let me know if I can be of any help, I'd really like to have success story of "kolla running midonet/calico";)17:25
Mech422inc0: me too :-)17:26
Mech422inc0: I need ceilo at some point too17:26
Mech422inc0: though thats not as big a deal as the networking stuff17:27
inc0ceilo patches are proposed already17:27
Lyncosceilo patches ?17:27
Lyncosyou didn't tell me about that yesterday17:27
*** thumpba has quit IRC17:27
inc0https://review.openstack.org/#/c/300574/17:28
patchbotinc0: patch 300574 - kolla - Implement ceilometer ansible role17:28
inc0I did tell you, they're in review17:28
inc0well...a patch, singular17:28
Lyncos:-)17:29
Lyncosah ok17:29
Lyncosthat one17:29
Lyncossorry17:29
LyncosI took a look at Talligent17:31
Lyncosit look awesome17:31
inc0I'm glad17:32
inc0let me know if that meets your needs17:32
Lyncosit would meet our needs if we had the budget tu buy it17:32
inc0I never tested that, but I know people who do and they like it17:32
LyncosI'm speaking about the enterprise  version17:33
*** ravig has joined #openstack-kolla17:39
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Mechanism for Dockerfile customization  https://review.openstack.org/32466517:40
*** salv-orl_ has quit IRC17:41
*** shardy has quit IRC17:41
*** salv-orlando has joined #openstack-kolla17:41
*** signed8bit has joined #openstack-kolla17:45
mag009_neutron_plugin_agent technically i can force a specific plugin in my inventory right ?17:46
mag009_I replaced it with calico but it still load openvswitch17:47
klindgrensdake, you were talking about scaleability of neutron.  We did run into one issue....17:51
klindgrenwe needed to bump the files ulimit otherwise neutron api eventlet work would just exit after a week or so17:52
klindgrenworker*17:52
*** fragatina has quit IRC17:56
*** ravig has quit IRC18:04
*** tyrola has quit IRC18:08
wirehead_sdake / rhallisey : So, dcwangmit01 and I were chatting about uber-dev focused stuff that’s not useful for end-users and is in fact the wrong way to actually run things… but would help us scale-up future Kolla-Kubernetes committers more quickly.  Put that in the hacking.rst or contributing.rst?  Create a doc page that’s even more archane than quickstart?  Put it in the wiki for the time being because it’s too fast-moving r18:09
wirehead_now?18:09
*** diogogmt has quit IRC18:11
*** diogogmt has joined #openstack-kolla18:13
mag009_any objection that change the neutron_plugin_agent variable to look at the inventory18:14
mag009_i realize that it's a general variable but I'd like to have the ability to say X compute use calico and Y compute use openvswitch18:15
*** diogogmt has quit IRC18:15
*** thumpba has joined #openstack-kolla18:16
mag009_unless someone has another proposal I'll make the changes...18:16
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Add customizations for apt keys and packages  https://review.openstack.org/32668818:26
inc0mag009_, soo...you can do that18:28
inc0with config overrides18:28
inc0also if it works with inventory, and it should, that also works18:28
inc0inventory is your own file18:28
mag009_yes but it does not18:28
inc0ahh18:29
mag009_because it doesn't lookup to the hostvars18:29
rhalliseywirehead_, contributing is fine18:29
inc0ok I know why18:29
mag009_I have to tell the start.yml to use the hostvar18:29
inc0so when we call our plays18:29
inc0its ansible-playbook -e @globals.yml18:29
mag009_i do that18:29
inc0and I think value in globals takes priority18:29
inc0do you have this var in globals?18:29
mag009_but I dont want to set a global var18:29
inc0defined?18:29
mag009_I want to be able to say host A = calico , host B = openvswitch18:30
inc0I understand18:30
inc0hold on, let me refresh my ansible18:30
mag009_if I define let say neutron_plugin_agent = "openvswitch"  in global18:30
inc0it's about which variable takes priority18:30
mag009_and set the var in my inventory to calico18:31
inc0no, what I mean, don't define it there at all18:31
inc0and see if it works18:31
mag009_it take the global one18:31
inc0if you define it in inventory only18:31
mag009_ah ok i see what you mean18:31
mag009_hold on18:31
mag009_I'm almost done with the calico integration18:33
mag009_awesome it worked18:34
mag009_lol18:34
mag009_thx inc018:34
inc0cool, glad to hear18:41
*** coolsvap has quit IRC18:41
inc0sdake, ping18:41
*** ppowell has joined #openstack-kolla18:44
*** tzn has joined #openstack-kolla18:48
*** mbound has quit IRC18:51
*** dwalsh has quit IRC18:53
*** tzn has quit IRC18:54
sdakeinc0 anything in globals.yml takes priority and overrides eveerything else18:57
sdakeinc0 wound me18:57
*** fragatina has joined #openstack-kolla18:58
inc0https://review.openstack.org/#/c/326688/1 adding new packages is even easier than I thought18:58
patchbotinc0: patch 326688 - kolla - Add customizations for apt keys and packages18:58
inc0all we need to do is to refactor our current dockerfiles to use variables instead of raw paste18:59
inc0like that https://github.com/openstack/kolla/blob/master/docker/base/Dockerfile.j2#L20819:00
inc0then in customization file you just set new value, you can use var = var + whatever19:00
inc0or just var = whatever19:00
*** dwalsh has joined #openstack-kolla19:03
sdakeso that allows easier override of packages installed19:04
sdakeeither override or addition19:04
sdakehow is that extended to other areas19:04
*** rahuls has joined #openstack-kolla19:04
sdakethere is a case where we want to run raw docker commands as well19:04
inc0then you use original block idea19:05
*** SiRiuS has quit IRC19:09
sdakeinc0 we need bsae_all_apt_packages19:11
sdakebase_bin_apt_packages19:11
sdakeand base_src_apt_packages19:11
inc0I'd rather have if binary then packages = [binary] elif source then packages=[source]19:13
inc0one var, value changes depending on build mode19:13
sdakethe bin and src packages sometimes differ19:14
inc0they do, and that will be reflected in value19:14
inc0also having all the packages for every possible combination in same dockerfile really hurt readibility19:15
inc0we need to decouple it somehow19:15
*** Kennan has quit IRC19:15
Mech422mag009_: If you get a chance - I'd love to see your calico stuff...19:16
*** Kennan has joined #openstack-kolla19:16
sdakeinc0 i find the conditionals the hardeest part of our dockerfiles to read/write19:16
inc0for the record, I was against it from the beggining19:18
inc0I wanted to do it right way back in Santa Clara19:18
sdakecan't change the past19:18
sdakefocus on the future ;)19:18
sdakeat that point in time the decision we made was the best for the project19:18
sdakedoing it "right"sometimes means failing, which at that point was not really an option19:19
inc0well, my point is, now it's time to pay off this tech debp19:19
inc0debt19:19
sdakeinc0 just to be clear, kyouwere agaist which in sc19:20
inc0limting ourselves to only "if"19:20
sdakewell if we go through a massive refactor, I htink we can agree we want it done right this time around19:21
sdakein a way that developers can understand clearly19:21
sdakeso it can be implemented in distributed fashion without having to be inside your brain :)19:21
sdakeinc0 taking the if source pkg = if binary pkg = to its natural concllusion for consistency sake, this applies to all components we assemble?19:22
inc0well, most of them19:23
inc0same goes for keys in apt19:23
inc0might go for repos in yum too19:23
sdakeas well as repos atleast in yum19:23
inc0pretty much anything that is a list19:23
sdakewhat owuld be good is a standard "template"19:23
sdakethat every dockerfile follows19:24
inc0so I don't want to write strict rules from start and let them evolve as we go19:24
inc0but I think it's safe to say that any var/block should start by container name19:24
inc0and then some descriptive suffix that makes sens19:25
inc0e19:25
sdakeconsistency is key19:25
sdakethat lowers learning curve19:25
sdakewhich is hwy i suggested the template idea19:25
inc0sure, but we will develop standards after first few prototypes19:25
sdakeour j2 srt of follows a templat enow19:25
inc0all I'm saying is make first few and then take a look at them and use them as standard19:26
inc0or template as you say19:26
sdakeis there code to build this j2 file you published?19:27
inc0just check it out and it works19:27
inc0--template-override=override-file19:27
sdakei like hearing that19:27
inc0it;s follow up patch from one I submitted last week19:27
inc0https://review.openstack.org/#/c/324665/ I cleaned it up and left only code for mechanism19:28
patchbotinc0: patch 324665 - kolla - Mechanism for Dockerfile customization19:28
inc0so blocks keep working19:28
sdakeinc0 hat is the purpose of line 23119:28
sdake{% block base_ubuntu_package_installation %}19:28
inc0in case you'd like to completely override whole block19:29
inc0and really I could remove pre and post block19:29
inc0because you can acieve both with {{ super }}19:29
inc0like {% block base_ubutnu_package_installation %}RUN my-pretty-custom-command {{super}} {% endblock %}19:30
sdakeshuoudln't line 233 hae a block around it using same logic?19:31
sdakewhat is super19:31
inc0233 is inside this block19:31
inc0{{ super }} => it will fill it with original content19:32
sdakeyes should it be base_ubuntu_repo_installation19:32
sdakein block format19:32
inc0well it installs keys and packages, not repos;)_19:32
sdakebase_ubuntu_key_installatino19:32
sdakethen is w hat i emant ^^ :)19:32
sdakein elemental, keys, rpeos, and package are all separate things19:33
inc0not sure, if you want to manage keys, you do this with var19:33
sdakethe fourth type of thing is raw commands19:33
inc0but regardless, you can put block inside a block19:33
inc0so we can do both19:33
inc0here, if you want custom keys you override variable base_apt_keys to your liking19:34
inc0including stuff like base_apt_keys = "prettykey" + base_apt_keys19:34
sdakewhat i'm getting at is we either don't need line 23119:34
sdakeor we need a line 233 with a block to be consistent19:34
sdakei dont see a whole lot of value in teh line 231 block19:35
inc0well, question tho, what's the use case of overriding line 233?19:35
sdakesame question for line 231 ;)19:35
inc0we can remove both19:35
sdakecool19:35
sdakelets make it minimal but fit the use cases outlined in the elemental spec19:35
inc0thing is, having too many blocks is better than having to few19:35
inc0then pretty much all you need is to turn all install/repo/keys into list-based;)19:36
inc0and it will just work19:36
sdakenext up19:36
sdake230,19:36
sdakeshouldn't that be base_deb19:36
inc0we don't really have naming convention yet19:37
sdakewe are making them now :)19:37
inc0so instead of 2 block19:37
inc0pre and post19:37
sdakeso lets think about it before we go an drewrite 115 dockerfiles19:37
inc0I'd just leave base_ubuntu_package_installation19:37
inc0we can base on os family as debian/redhat19:38
sdakei dont ssee any value in overriding the installation mechanism19:38
sdakeonly what is installed19:38
inc0then we can replace all if base_distro in [ubutnu, debian] with if base_distro_faimly==debian19:38
sdakeya that wont work19:39
sdakedifferent keys19:39
inc0sdake, but do you see value in adding somethign before or after?19:39
sdakewith fedora, different ttools19:39
sdakeinc0 let me switch to a cooler part of my hosue moment19:39
sdakehttps://review.openstack.org/#/c/323612/5/specs/elemental.rst19:41
patchbotsdake: patch 323612 - kolla - Introduction of a new DSL: Elemental19:41
sdake36-5519:41
sdakesometimes repo comes from a file, sometimes repo comes from a uri19:41
sdakeatleast in rpm environment19:42
inc0not in apt world19:42
inc0anyway, easy19:42
inc0macro19:42
sdakewhich not in apt world - you mean from uri?19:43
*** SiRiuS__ has joined #openstack-kolla19:43
inc0http://jinja.pocoo.org/docs/dev/templates/#macros write a macro that will understand repo and install it19:43
inc0sdake, in apt world you have sources.list19:43
inc0just a file19:43
sdakegpg keys can also come from file or uri19:44
sdakedoes this macro go in one master file somewhere and get included in?19:44
inc0macro is a function19:45
*** mliima_ has joined #openstack-kolla19:45
inc0you can call it {{ install_repo(file_or_url) }}19:45
sdakei know its a function19:45
inc0and depending on value of file_or_url will eirther install file or url19:46
sdakemy quetion is do we write teh function once19:46
sdakeor do we copy it to every 115 dockerfiles19:46
inc0or rather print RUN install file or RUN install url19:46
inc0we can have file with common macros and include it in every dockerfile19:46
inc0or have master dockerfule every other dockerfile will extend19:46
sdakeok, that was my original question :)19:46
inc0I think latter is better19:46
sdakei dont see immediate value of extension - inheritence is ah ard concept for alot of people to grasp19:47
sdakewhereas includes are nobrainers19:47
sdakecoud lyou explain how extension would offer a simpler setup?19:47
*** mliima has quit IRC19:48
sdakewhat would b ecool is if there was one master file that did all the work19:48
inc0well, maybe include19:48
sdakeand a lsit of variables in the children j2 files19:48
inc0both will require single line in every Dockerfile19:48
sdakeinc0 don't care about additional line in ever ydockerfile19:49
inc0yup19:49
sdakecare about a) is it simple for our devs to implement b) is it siimpl for operators to override19:49
inc0{% include 'kolla_macros.j2' %}19:50
sdakei know include is  simple19:50
sdakei was asking about extension19:50
inc0I don't understand now.19:50
sdakeextends() is the keywword iirc19:50
inc0it is19:51
sdakewha twould be cool is to write one template that has all the raw work19:51
sdakeand a file that extends it with variables19:51
sdakeintuitively i'm not sure if that would work19:51
inc0problem is there is little raw work19:51
inc0our templats are fairly DRY19:51
inc0unless we want to add macros and stuff, then true19:52
*** mbound has joined #openstack-kolla19:52
*** mliima_ has left #openstack-kolla19:52
sdakei get there is raw work19:52
sdakethat could go in teh children dockerfile.j219:52
sdakebut if we go copy that base.j2 modele around19:52
sdakewe will have the same override blocks all ove the place in the same placess19:53
sdakeseems like a waste ;)19:53
sdakeso bacck to original question19:53
inc0well, if we just include base dockerfiles then we don't use docker cache any more19:53
sdakewould it be possible to psecify jsut the variables and raw stuff in the children j219:53
sdakeand have the parent that we extend from use all that data19:53
inc0yes...just not super valuable imho19:54
inc0our Dockerfile, aside from base, are simple19:54
inc0and we dont want to render 100 huge dockerfiles19:54
sdakei agree - we are talking about making them complex atm :)19:54
inc0we want to render 1 with 90 lines and 99 with 10 lines19:54
sdakeby making a list of variables in each one19:55
sdakeand repos in each one19:55
sdakeetc19:55
inc0I don't understand what you want19:55
sdakei wish i knew jinja better - then i could sho wyou19:55
inc0if you want image to be huge, you don't use docker image features any more19:55
sdakewe want small imagess19:55
sdakeas small as possible19:55
inc0yeah19:55
sdakethat should b e#1 on that list of erquirements ;)19:56
inc0hence base image big, other small19:56
sdakelet me show you example19:56
sdakemoment19:56
inc0if you want custom full build per image, you don't use base image any more19:56
*** tzn has joined #openstack-kolla19:57
Mech422inc0: woot! got the go ahead to start working against HEAD - we'll switch to stable/newton once its released :-)19:57
*** mbound has quit IRC19:57
sdakehttps://github.com/openstack/kolla/blob/master/docker/heat/heat-api/Dockerfile.j219:57
sdakeMech422 newton is 4+ months out19:57
Mech422sdake: yeah - octoberish ?19:57
sdakeMech422 i'd highly recommend against not working with head19:57
inc0Mech422, nice, you can help us with this customization stuff then:P19:57
sdakenovember19:57
inc0sdake, Oct19:57
inc0according to Newton release19:57
sdakeok19:57
sdakeso link above19:58
inc0and working == contributing not prod;)19:58
Mech422yeah - I'm just building POC stuff that can be used to deploy to prod later...19:58
sdakethere we have package we install in the binary case one for centos and one for ubuntu19:58
*** dwalsh has quit IRC19:58
sdakeinc0 what would heat-api.j2 look like in a new world order ;)19:59
sdakeinc0 assumign we threw kitchen sink at it19:59
inc0so what we could do is something like that: << workign on paste >>19:59
inc0http://paste.openstack.org/show/508759/20:02
inc0and install_package macro will understand if centos then yum elif ubuntu then apt20:02
ccesariohey guys ... doe somebody has tested cinder + lvm  ? http://paste.openstack.org/show/508760/20:03
sbezverk_ccesario yes20:03
sdakeinc0 missing repo and key install20:03
sdakeinc0 lets keep iterating o n this20:03
inc0just add macro install_repo and install_key20:04
ccesariosbezverk_, is it needed any magic for this ?20:04
mag009_docker question i have this app where i want to run as user in a docker but it need to create a socket in /run/ how do I proceed in docker ?20:04
mag009_i get a permission denied because the user cannot write in /run20:05
sdakeinc0 macros can take null values and do  the right thing?20:05
sbezverk_ccesario nope, as long as you configure it correctly it works like a charm.. I am running 12 VMs in kolla aio each using 50GB cinder lvm volume20:06
inc0http://jinja.pocoo.org/docs/dev/templates/#macros not sure about null, but default "" or [] should be ok20:06
sdakeinc0 do macros have access to the global namespace - in other words, would it be able to operate on the evariable base_distro20:06
inc0yup20:06
sdakethe reason I ask is fedora uses dnf20:06
sdakeinsteadd of yum20:06
inc0I think so, if not we can add base_distro to argument20:06
sdakeso install_packages would need to be able to handle that20:06
sbezverk_ccesario why do not you use just regular cinder create command for volumes?20:06
inc0but 99% they have global namespace20:07
sdakeinc0 can you find out now - I'd like to get this work rolling20:07
sdakeand if we can come up with a basic template20:07
sdakei'll set the hounds loose20:07
sbezverk_ccesario the way of creating volumes you pasted, really really weird20:07
ccesariosbezverk_, beucase I got error20:08
ccesariosbezverk_, http://paste.openstack.org/show/508714/20:09
sbezverk_ccesario can you get cinder.conf from your cinder_volume container?20:10
sbezverk_ccesario you are on master right?20:11
*** zhiwei has joined #openstack-kolla20:11
sdakeinc0 i really like the last approach you paste20:11
sdaked20:11
sdakeinc0 assuming it would work (the difficulty would be in writing the macros)20:12
inc0sdake, works with global20:12
sdakenice so no extra variable passing needed then?20:12
inc0nope20:13
ccesariosbezverk_, well I did some changes to try identify a error on master code... http://paste.openstack.org/show/508666/20:13
ccesariosbezverk_, already reported on dev-list20:13
inc0so we can easily add install_packages(list_of_packages) macro20:13
sdakeinc0 lets not focus on the base container at first20:13
ccesariomy currently cinder.conf http://paste.openstack.org/show/508762/20:13
inc0that will understand which distro works20:13
sdakewe need install_repos and install_keys too20:14
inc0I'll start with install_packages20:15
inc0you get me names to help20:15
sdakenames to help which20:15
sdakethe macro writing20:15
ccesariosbezverk_, https://www.mail-archive.com/openstack-dev%40lists.openstack.org/msg85315.html20:15
sdakeor the distributed dev20:15
inc0names of people that will help me20:15
inc0both20:15
sdakewith which part20:15
mag009_anyone is working on integrating different auth for the keystone ? ldap for example20:15
sdakei dont think anyone in our community is a jinja2 rocket scientist20:15
inc0I can write all, just will start with one20:15
sdakeso the prototyping work is on you i think20:16
*** zhiwei has quit IRC20:16
inc0but it would be good if I'm not only person in community who ever wrote a macro in jinja;)20:16
sdakebut I will requeest folks in our community to do the implementation work after the macro file is written20:16
sdakeand the prototype is written20:16
inc0I'll get this patch upstream today or tomorrow20:16
sdakeand then just so I am clear20:17
inc0you get the word out and ack https://review.openstack.org/#/c/324665/20:17
patchbotinc0: patch 324665 - kolla - Mechanism for Dockerfile customization20:17
inc0kk?20:17
inc0this one is requirement20:17
sdaketo override heat_api_packages, I'd speciffy heat_api_packages = ['yang'] in a master file somewhere?20:18
inc0in file you provide during build20:18
sdakeok20:18
inc0--template-override20:18
sdakeand that allows replacement or override?20:18
inc0or append or prepend20:18
sdakenice20:18
inc0heat_api_packages = heat_api_packages + ['yang']20:19
sdakeinstall order is repo, key, packages20:19
inc0it's a list, it's ordered20:19
sdakei mean to help you out during dev20:19
sdakethat is the order it has to go in as generated by the dockerfile otuput20:19
inc0althout if you'd do apt-get install pkg1 pkg2 order shouldn't matter20:20
sdakepackage ordering doesn't matter20:20
sdakebut repo and key order do matter in relationship to packages20:20
inc0well, you can't really mix these two20:20
inc0so you'd need to20:20
sdakerepo then key then packages20:20
inc0instal_repo install_package install_more_repos20:21
sdakecan't mix which two20:21
inc0nvm, I know what you mean20:21
inc0and will tell you, not a problem20:21
sdakewfm20:21
inc0we still write Dockerfiles at the end20:21
sdakeso we have 3 of our 4 things completely customizable20:21
sdakethe last thing we need customizable is the raw docker contents20:22
ccesariosbezverk_, have you any tip!??20:22
inc0but before I'm done, ack this plz20:22
inc0https://review.openstack.org/#/c/326108/20:22
patchbotinc0: patch 326108 - kolla - Make build.py importable lib20:22
inc0so I won't have to rebase it more later20:22
sdakereviewing moment20:23
inc0sdake, for raw docker content you have blocks20:23
inc0just put them wherever you want20:23
sbezverk_ccesario not sure, I have never hit any issues with the latest master.. but I would start with cinder.conf check20:25
sdakeinc0 right20:25
sdakeinc0 that was my thinking too20:25
sbezverk_to make sure that it points NOT to VIP but to server's physical interface20:25
sbezverk_and also vg is specified correctly20:26
*** ppowell has quit IRC20:26
sbezverk_ccesario I am about to leave but if you want I am opened for a debugging session via webex tomorrow..20:27
sdakeinc0 ok well this idea seems workable and avoids all of the problems i have had in teh past with the jinja2 changes20:27
ccesariosbezverk_, currently after me change the cinder.conf ... it seems a permission problem happen20:28
sdakeand especially avoids having a whole lotta blocksk in each dockerfile20:28
inc0will make our files A LOT more readable as well20:28
ccesariosbezverk_, sure.... the server has access over ssh20:28
ccesarioif you wants check... we can do it over ssh+screen :)20:28
sdaketo turn off repos in base and only use the repos in heat-api, id do?20:29
sdakeheat_api_repos = ['my_repos']20:29
sdakebase_repos = ['']20:29
sdake?20:29
sdakeinc0 ^^20:30
inc0sdake, when base is built, it's build20:31
inc0built20:31
sbezverk_ccesario what is your time zone?20:31
inc0you can't change base from heat_api20:31
sdakeyes, but it gets built as part of that set of configs20:31
inc0no, it just get builds20:31
inc0built20:31
sdakeright base is rebuilt20:31
inc0and then heat api uses FROM20:32
sdakewith the new base_repos of nothing20:32
inc0then you will have 2 base images20:32
inc0and if you build something else20:32
inc0it will use newer, which is broken20:32
ccesariosbezverk_, UTC-03:0020:32
inc0so you can either change FROM in heat_api to some custom base image20:32
inc0or manually uninstall stuff from heat_api and then install it20:33
inc0it's how docker works..20:33
sdakeinc0 i'm talking about a global build of all containers20:33
sdakewhere each containe rhas its own repo file20:33
sdakeand base has nothing20:33
inc0then you don't really have base20:33
*** dwalsh has joined #openstack-kolla20:33
inc0and this is horrible antipattern20:33
sdakei recognize base would be limited ;)20:33
inc0you will lose benefit of layered builds20:34
sdakepersoanlly I agree that one repo location makes more sense20:34
sdakebut get alot of feedback sure would be nice if repos were cusotmizable per container20:34
inc0if you build base image once, it stays this way20:34
sbezverk_ccesario ok I am -4, I will ping you around 9am tomorrow, 10am your time, let's see what is broken.. meanwhile could you make sure that you have the latest master and freshly build images20:34
inc0so for example20:35
sdakeinc0 yes what my example above did is make sure bbaxe has no repos in it20:35
inc0if you set repo1 in base, then apt-get install foo, it will get installed from repo120:35
inc0if you then change it to repo2, foo will keep being installed in repo120:35
mag009_inc020:35
inc0from*20:35
inc0wassup mag009_20:36
mag009_inc0: any objection to move the dnsmasq directly into dhcp-agent image20:36
inc0and sdake yeah, if you do that you will do horrible antipatter, but will work20:36
sdakemag009_ no objection20:36
mag009_in calico for example I need to replace with calico package20:36
inc0mag009_, yeah, 1 pid per container20:36
sdakeactuallly we hae multiple pids per container20:36
inc0where sdake ?20:36
sdakemost of our containers run multiple pids20:36
sdakebut they do "one job"20:36
inc0hold on, where?20:37
sdakethat is the definition fo a thin container in my book ;)20:37
sdakeheat-api for example spawns multiple api threads20:37
sdakeall api containers behave in this way20:37
sdakei won't even get started on what libvirt spawns20:37
ccesariosbezverk_, sure...  I 'm testing using AIO method20:37
inc0well, but we don't have multiple services20:37
inc0per container20:37
sdakeright that is the "one job"20:38
inc0so dhcp-agent and dnsmasq shouldn't coexist in same container20:38
sdakea thin container is one which does no job or purpose20:38
sdakeno/one20:38
sdakeisn't dnsmasq part of an implementation detail for dhcp?20:38
inc0mag009_, how does calico work? it uses dnsmasq configs?20:38
mag009_yes20:39
inc0then just run separate calico container and mount this config20:39
mag009_the way it work it replaces the neutron dhcp agent20:39
inc0then just replace it;)20:39
mag009_that agent launch a dnsmasq for each zone20:39
inc0well if agent launches dnsmasq that's ok20:40
mag009_i have no control over the dnsmasq the agent launch it20:40
inc0it's like sub-threads20:40
inc0or api threads20:40
inc0in my book;)20:40
sdakeit is a dependency20:40
sdakedependencies don't count for fat containers imho :)20:40
mag009_sure but i'm using the neutron base and since it include dnsmasq when I try to reinstall with the calico version apt-get bitch about it20:41
mag009_dependencies etc..20:41
mag009_its ugly that way..20:41
sdakemag009_ where is dhcp used atm?20:41
sdakein the neutron-dhcp-agent?20:41
openstackgerritMerged openstack/kolla: Make build.py importable lib  https://review.openstack.org/32610820:41
mag009_each compute are a dhcp server20:41
*** jtriley has quit IRC20:42
sdakemag009_ bounce a review off the queue - and we will weigh in20:42
mag009_what I did is create a new container/ Dockerfile called : calico-dhcp-agent20:42
mag009_based on neutron-dhcp-agent20:42
sdakethat sounds good20:43
sdakethe issue is dnsmasq is instaleld in neutron-base?20:43
mag009_yep20:43
sdakejust dont install it20:43
sdakeor uninstall it if it is20:43
sdake(if it gets pulled in as a transitive dep)20:43
mag009_where does it run normally the dnsmasq in a normal installation ?20:43
sdakeno clue20:44
mag009_in a container or with the neutron dhcp agent20:44
sdakei asked you above20:44
mag009_in calico I know20:44
*** ayoung has quit IRC20:44
sdakesbezverk_ do you knwo the answer to mag009_ 's question?20:45
mag009_i think the dnsmasq run within the neutron-dhcp-agent20:45
LyncosI think mag009 is right20:45
sbezverk_sdake sorry which question?20:45
mag009_if that is so why not move the package dnsmasq in Dockerfile of neutron-dhcp-agent20:45
Lyncosbecause when we setup the domain name returned by DHCP .. it is in dnsmasq20:45
mag009_this is my question20:45
mag009_its not a big deal I can work around it but i found it's ugly the way its going to be..20:46
mag009_:)20:46
sdakemag009_ i dont think there is any problem with that -if there is our gate will catch it20:46
sdakemag009_ only way to iknow is to try it :)20:46
mag009_I'll submit a draft tomorrow anyway so we can look over it20:46
sdakeinc0 is there any way i can help with the macro wizardry20:47
sdakeinc0 or any other way20:47
sbezverk_mag009_ would be good to try to move dnsmasq to dhcp agent container20:47
sdakedo do not :) NO TRY20:47
sbezverk_in this case we will not hit similar type of issues20:47
inc0sdake, I'll make a prototype, you find people to change every single yum install to macro;)20:48
sbezverk_when fancy neutron plugin wants to install their own "things" :-)20:48
sdakeinc0 i can handle that part20:48
*** rhallisey has quit IRC20:49
mag009_guys is there a milestone/roadmap for this project ?20:50
sdakemag009_ yes20:50
mag009_like how do you determine the priorities etc..20:50
sdakemag009_ people work on what they like20:50
mag009_lol20:50
mag009_ok20:50
sdakemag009_ I may set priorities on launchpad, but that doen't have much affect ;)20:50
mag009_it'd be nice to have some that are respected tho20:51
sdakemag009_ could you be more specific20:51
mag009_i dont know i just think that it's missing some of the core feature(s) like (ldap integration) as an examples20:52
mag009_it's missing a lot of configurable settings in openstack20:52
sdakemag009_ moment20:52
sdakemag009_ have you read http://docs.openstack.org/developer/kolla/deployment-philosophy.html20:53
sdakemag009_ re ldap and other forms of extension, inc0 and I are working on that right now ;)20:53
mag009_ok20:53
Lyncoswe will need LDAP .. ASAP20:53
mag009_its just an example20:53
sdakenot ldap specifically20:53
Lyncos:-)20:53
sdakebut extension in general20:53
sdakeall the configurable settingss are totally available in kolla20:54
*** kproskurin has joined #openstack-kolla20:54
sdakesee above philosphy document20:54
mag009_yes I will read it20:54
mag009_thx20:54
sdakewhat other core features you looking for20:54
mag009_ldap was one so far.. and it's more about customizing stuff like the domain for dhcp etc..20:55
LyncosLDAP, new version of ceph20:55
mag009_but I guess it says in the doc20:55
mag009_how the customization work20:55
sdakeyou can customize any openstack specific variable20:55
sdakenew version of ceph - you mean newer then hammer?20:56
Lyncosyeah20:56
Lyncosman They are releasing Jewel20:56
Lyncos:-)20:56
sdakewe don't integrate pre-release software typically20:56
Lyncosok20:56
LyncosInfernalis then20:56
sdakeonce its in repos, I suspect someone will take it up20:56
sdakeatm we are stuck with what centos storage sig gives us on centos20:57
sdakesame story re ubuntu20:57
mag009_how do I customize the qemu.conf for example ?20:57
mag009_or dnsmasq.conf20:57
sdakemag009_ ini files can be overridden20:57
sdakeand merged20:57
sdakeqmeu.conf can only be overridden20:57
sdakenot merged20:57
sdakemake your own qemu.conf in /etc/kolla/config/qemu.conf20:58
mag009_ok so I have to run another playbook20:58
sdakeI think - moment20:58
sdakemag009_ to apply your reconfigured settings you run kolla-ansible reconfigure20:58
mag009_yes but for that I need to write my template with my own playbook20:59
mag009_put it in kolla config folder and than run reconfigure20:59
sdakeqemu.conf may not be customizable20:59
sdake(at this time)20:59
mag009_well for qemu I've modified the template to support calico21:00
mag009_I have some requirement for calico21:00
sdakeya we want policy files and other miscallenous files to be configurable via reconfigure21:00
mag009_so I did a if condition if enable_calico than put the extra settings21:00
sdakeits going to happen - essential priority for newton21:00
sdakeatm only ini files are customizable21:00
*** thumpba has quit IRC21:01
mag009_ok gotcha21:01
sdakeother features?21:01
mag009_i see where you guys are going with this make more sense now..21:02
Lyncoswe'll also have to modify the HA model21:02
Lyncosto stop using keepalived21:02
Lyncosand do ECMP21:02
mag009_I've started the work on that21:02
sdakemag009_ you mean ater reading the philosophy document?21:02
sdakewhat is ecmp21:02
mag009_yes21:02
LyncosEqual cost multi path21:02
*** tzn has quit IRC21:02
LyncosBGP load balancing21:02
Lyncoswith health checks on haproxy .. (not sure if it's implemented yet)21:03
mag009_are vip is mounted on each controller21:03
mag009_all we need is haproxy for health check but i've already started doing the work to support ecmp21:03
mag009_well it's basically excluding keepalived21:03
mag009_in our case21:03
sdakewhat software provides the same functionality as keepalived that uses ecmp?21:04
LyncosBHP21:04
Lyncos*BGP21:04
mag009_nothing21:04
*** ayoung has joined #openstack-kolla21:05
Lyncosit's a network technique.. not a software21:05
sdakei see21:05
sdakewell we generally dont say no to patches21:05
sdakebut what you propose I don't know enough about to speak intelligently21:05
Lyncosit's quite easy21:05
Lyncosyou add an IP to loopback interface of each controllers21:05
Lyncosand the network stack is sending equally the traffic to each adevertied host21:06
Lyncosif you want to stop .. you remove the IP from the host21:06
sdakewhich network tack - you mean the switch?21:06
Lyncosand BGP stop advertizing it21:06
LyncosBGP21:06
Lyncos:-)21:06
Lyncoshttps://en.wikipedia.org/wiki/Equal-cost_multi-path_routing21:07
sdakem0ar reading21:07
LyncosBGP will advertise multiple path to reach an IP that is hosted on multiple machine21:07
LyncosThe applet viewer thing in wikipedia show how it work very wall21:09
sdakedevil's advocate here, how is that better then keepalived21:09
Lyncosit scale21:09
sdakei am familiar with bgp at a high level ;)21:09
*** ravig has joined #openstack-kolla21:09
LyncosIt scale better than keepalive.. and also is  active-active strategy21:09
Lyncosinstead of active-passive21:09
Lyncosand there is no single point of failure21:09
Lyncosno need for load balancers .. or moving ip around21:10
sdakedoes it wor with all gear or only specific gear?21:10
Lyncosit's pure BGP21:11
Lyncosso It should work with anything..  but you need to have a full L3 enabled network21:11
LyncosWith cisco you probably have to buy a module that is too expensive21:12
sdakei have a netgear switch (10gb) at my house21:12
*** diogogmt has joined #openstack-kolla21:12
sdakebut I dont think it lists bgp as one of it sfeatures21:12
Lyncos:-)21:12
LyncosWe are using switches running cumulus linux21:12
Lyncosyou can ask inc0 he want to buy one21:13
Lyncos;)21:13
inc0first I need to buy a house;)21:14
sdakeany other features21:14
inc0then lay down 10gig over whole house21:14
sdakeinc0 cat7 ftw ;)21:14
Lyncosfibre is cheaper21:14
Lyncosthe cable is cheaper21:14
Lyncos:)21:14
sdakemy 1k spool of cat7 was about 200 bucks21:14
*** ravig has quit IRC21:15
LyncosWhat you are using Cat7 for21:15
sdake10gig copper switch21:15
inc0Lyncos, 10gig over copper21:15
Lyncosyou can run 10gig on Cat6 no ?21:15
wirehead_That’s so metal.21:15
inc0Lyncos, yeah, cat6 works too21:15
sdakeLyncos depends on the mhz rating of the cabling21:16
Lyncosok21:16
inc0but I think cat7 has longer length limit21:16
sdakeLyncos i couldn't actually find any cat6 at 500mhz or more21:16
*** godleon has joined #openstack-kolla21:16
Lyncosok I see21:16
Lyncosanyway21:16
LyncosAlerting would be a nice feature21:17
LyncosSensu21:17
Lyncosbut I understand this is big21:17
inc0Lyncos, we had session about that in summit21:17
Lyncoscan be big21:17
Lyncoswhat was the conclusion ?21:17
inc0we need a volounteer who will do it;)21:17
Lyncosahah21:18
inc0but we have few options as software stack goes21:18
inc0we can use whisper/cassandra and grafana21:18
inc0anyway, we spoke about that couple weeks ago21:18
Lyncoswhisper/cassandra/grafana this is for Logging no ?21:18
Lyncosnot monitoring21:18
Lyncosor I missed something21:19
*** SiRiuS__ has quit IRC21:19
LyncosCat7 is shielded21:19
wirehead_Well, Prometheus would slot better into the Kubernetes side21:19
inc0nto sure about whisper but grafana is monitoring21:19
*** diogogmt has quit IRC21:19
inc0cassandra is database21:19
inc0we already have logging21:19
LyncosGrafana can send alerts ?21:19
inc0it visualizes stuff21:20
Lyncosyeah21:20
inc0not sure if can send as well21:20
Lyncoswe are using grafana21:20
inc0but I'm pretty sure there will be something that can21:20
Lyncosbut not for alerting21:20
wirehead_There’s basic support for collecting Prometheus metrics directly from the pods and using that to drive Auto Scaling in Kubernetes.21:20
Lyncoswe use sensu for alerting and it connects to the same backend21:20
inc0that makes sense21:20
inc0anyway, whoever take it on will probably have freedom to take tech he/she likes most21:20
LyncosWe may have to do it21:21
LyncosMAG is really good at it :-)21:21
Lyncoshe will kill me21:22
Lyncos:-)21:22
*** diogogmt has joined #openstack-kolla21:22
sdakeinc0 can you crank out those macros today21:23
sdakeand then i'll set the hounds lose :)21:23
inc0testing as we speak21:26
inc0sdake, midcycle is 12-13 in Ralegh right?21:31
inc0Jul21:31
sdakenot in r raleigh21:31
sdakeits in durhum21:31
inc0ah21:31
sdakewhich is 1 hour away21:31
inc0ok, well NC in any case21:31
inc0Lyncos, ^21:31
sdakerdu is the airport21:31
sdakewe have max capacity for 30 people21:32
LyncosDamn21:32
LyncosI'm in vacation21:32
mag009_i want in21:32
sdakemag009_ its ope nto  anyone21:32
sdakei need to get eventbrite setup21:32
LyncosI'll have to move my parentals :-)21:32
mag009_so you were serious about doing it by the beach?21:33
mag009_:P21:33
*** ravig has joined #openstack-kolla21:33
inc0well Durhum is kinda far away from ocean:P21:33
sdakehttps://wiki.openstack.org/wiki/Sprints/KollaNewtonSprint21:33
*** tzn has joined #openstack-kolla21:35
mag009_there's a lake near by21:35
mag009_that will do21:35
*** rhallisey has joined #openstack-kolla21:37
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Mechanism for Dockerfile customization  https://review.openstack.org/32466521:39
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Macro install packages  https://review.openstack.org/32673421:39
inc0sdake, ^21:39
wirehead_It’s winter in the southern hemisphere.  We want the *next* midcyle to be on a beach in Brazil.21:40
wirehead_I’d prefer Sint Maarten.  We could sit on the beach that’s astonishingly close to the airport runways.21:41
*** tzn has quit IRC21:41
inc0wirehead_, brazil is so close to equator that it doesn't really matter21:41
wirehead_OH, right.21:41
wirehead_But those of us not in Phoenix / Texas / California would appreciate the change, I’m sure.21:42
wirehead_If we did it at Sint Maarten, we could settle technical debates not with a sword duel but with a “who can hang on while a 747 takes off” contests.21:42
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Macro install packages  https://review.openstack.org/32673421:43
sdakeinc0 i was thinking you would add the cmplexity of handling repos from raw too21:43
sdakeinc0 so we can validate the approach works21:43
inc0sdake, just test it21:44
inc0there is no magic21:44
inc0anway, I'm off, cya tomorrow21:44
sdakelater21:45
*** inc0 has quit IRC21:45
Mech422inc0: doesn't that macro need to spit out 'RUN' too ?21:48
Mech422or have RUN in the dockerfile?21:49
*** ayoung has quit IRC21:54
*** sdake_ has joined #openstack-kolla22:03
*** sdake has quit IRC22:06
*** sdake has joined #openstack-kolla22:06
*** ayoung has joined #openstack-kolla22:09
*** sdake_ has quit IRC22:10
*** dwalsh has quit IRC22:13
*** vhosakot has quit IRC22:22
*** diogogmt has quit IRC22:22
*** salv-orl_ has joined #openstack-kolla22:24
wirehead_sdake: so, I’m at a bit of an impasse with kubernetes + kolla + ansible.  The memcached config.json file is currently hardcoding to 10.0.2.15.  I want that to be 0.0.0.0 when I’m starting the memcached container (so it listens to everything, mediated by a kube service) but then when other services want to talk to memcached, they need to talk to ‘memcached.openstack'22:25
sdakewirehead_ not sure but i am taking a break right now for 15-20 mins22:26
sdakebbiaf22:26
*** salv-orlando has quit IRC22:27
*** zhiwei has joined #openstack-kolla22:27
*** zhiwei has quit IRC22:32
*** Mr_Broken has joined #openstack-kolla22:34
*** Mr_Broken has quit IRC22:39
*** sdake has quit IRC22:43
*** tzn has joined #openstack-kolla22:51
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Convert Memcached to work without HostNetwork=True  https://review.openstack.org/32675722:51
*** signed8bit is now known as signed8bit_Zzz22:55
*** tzn has quit IRC22:57
*** ravig has quit IRC22:58
*** absubram has quit IRC23:04
*** rahuls has quit IRC23:05
*** ravig has joined #openstack-kolla23:08
*** signed8bit_Zzz is now known as signed8bit23:09
*** rahuls has joined #openstack-kolla23:09
*** kproskurin has quit IRC23:11
*** sdake has joined #openstack-kolla23:12
*** sacharya_ has joined #openstack-kolla23:15
*** sacharya has quit IRC23:15
*** rahuls has quit IRC23:15
*** ravig has quit IRC23:22
*** ravig has joined #openstack-kolla23:22
*** sacharya_ has quit IRC23:25
*** rahuls has joined #openstack-kolla23:26
*** signed8bit is now known as signed8bit_Zzz23:28
*** salv-orl_ has quit IRC23:43
*** salv-orlando has joined #openstack-kolla23:43
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Convert RabbitMQ to work without HostNetwork=True  https://review.openstack.org/32676323:45
*** sdake has quit IRC23:46
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Convert MariaDB to work without HostNetwork=True  https://review.openstack.org/32561323:47
*** ravig has quit IRC23:57

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