Wednesday, 2016-06-01

*** prithiv has quit IRC00:05
wirehead_rhallisey: if I’m right and it’s just not done, let me know and I can help out. :)00:06
*** mdnadeem has quit IRC00:08
*** mdnadeem has joined #openstack-kolla00:09
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Regression: Kubernetes was rejecting the YAML we were generating  https://review.openstack.org/32362400:12
*** inc0 has quit IRC00:13
*** dims has quit IRC00:14
*** sacharya has quit IRC00:15
*** dims has joined #openstack-kolla00:19
*** ravig has quit IRC00:29
*** sdake_ has joined #openstack-kolla00:29
*** sdake has quit IRC00:30
sdake_inc0 how about making a spec for your work related to includes and macros and stuff00:32
*** pbourke-home has joined #openstack-kolla00:35
*** ravig has joined #openstack-kolla00:37
*** pbourke-home has quit IRC00:38
sdake_rhallisey ping00:39
sdake_jpeeler around?00:40
*** wirehead_ has left #openstack-kolla00:41
*** wirehead_ has joined #openstack-kolla00:41
*** ssurana has quit IRC00:41
*** dcwangmit01_ has joined #openstack-kolla00:48
*** dcwangmit01 has quit IRC00:50
*** sdake has joined #openstack-kolla00:56
*** sdake_ has quit IRC00:59
*** sdake has quit IRC01:02
rhalliseywirehead_, the bootstrap for mariadb should work.  What are you seeing?01:08
rhalliseyits a little sesitive though'01:08
*** weiyu has joined #openstack-kolla01:11
*** sacharya has joined #openstack-kolla01:15
*** rhallisey has quit IRC01:19
*** sacharya has quit IRC01:21
*** zhiwei has joined #openstack-kolla01:23
williamcabanI just pull the latest version from git, is it me or the "--passwords" option in kolla-ansible is not recognized anymore?01:24
williamcabanEven when is displayed as part of the help, the option is not longer listed in the LONG_OPTS01:27
wirehead_rhallisey: so, understanding that the mainline is broken and I’ve got a one-line patch to fix things.01:35
*** sdake has joined #openstack-kolla01:41
*** sdake has quit IRC01:43
*** sdake has joined #openstack-kolla01:47
*** sdake_ has joined #openstack-kolla01:48
*** thumpba has joined #openstack-kolla01:50
*** sdake has quit IRC01:51
*** tfukushima has joined #openstack-kolla01:58
*** unicell has quit IRC02:02
*** sacharya has joined #openstack-kolla02:16
*** thumpba has quit IRC02:16
*** ravig has quit IRC02:22
*** ravig has joined #openstack-kolla02:28
*** pbourke-home has joined #openstack-kolla02:37
*** pbourke-home has quit IRC02:38
*** tyrola has joined #openstack-kolla02:40
*** tyrola has quit IRC02:45
*** yuanying has quit IRC02:50
openstackgerritWilliam Caban proposed openstack/kolla: Closes-Bug: 1587706  https://review.openstack.org/32363402:51
openstackbug 1587706 in kolla "kolla-ansible missing --password option" [Undecided,New] https://launchpad.net/bugs/158770602:51
*** ayoung has quit IRC03:09
openstackgerritMerged openstack/kolla: Install missing package in spiceproxy container  https://review.openstack.org/32305403:16
*** daneyon_ has joined #openstack-kolla03:22
*** daneyon_ has quit IRC03:27
*** ravig has quit IRC03:34
*** ravig has joined #openstack-kolla03:37
*** pbourke-home has joined #openstack-kolla03:38
*** pbourke-home has quit IRC03:39
*** yuanying has joined #openstack-kolla03:47
*** dave-mccowan has quit IRC03:48
*** wirehead_ has quit IRC03:50
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Install missing package in spiceproxy container  https://review.openstack.org/32365003:51
*** wirehead_ has joined #openstack-kolla03:52
*** g3ek has joined #openstack-kolla03:57
*** haplo37 has joined #openstack-kolla03:57
*** ravig has quit IRC04:09
*** david-lyle has quit IRC04:21
*** ssurana has joined #openstack-kolla04:48
*** ssurana has left #openstack-kolla04:49
*** tfukushima has quit IRC04:53
sdake_yo04:53
sdake_Jeffrey4l_ ping04:53
Jeffrey4l_sdake_, pong04:53
*** ssurana has joined #openstack-kolla04:54
sdake_coolsvap ping04:54
openstackgerritMerged openstack/kolla: Add passwords parameter to LONG_OPTS in kolla-ansible script  https://review.openstack.org/32358504:56
sdake_https://review.openstack.org/#/c/32361204:56
sdake_Jeffrey4l_ can you please revview this04:56
sdake_inc0 wants a spec, and I am blocked on elemental support until the spec is either approved or not approved04:56
sdake_remember, requires majority04:56
Jeffrey4l_ok. actually, i am not big fan for this idea. :)04:57
coolsvapsdake_, I will review04:57
sdake_Jeffrey4l_ what is your proposal ?04:58
coolsvapi am open to experiment with this as we discussed at the start, this looks to solve some major headache's down the line04:58
sdake_Jeffrey4l_ before we get into your propoosal can you explain why you dont like the approach04:59
Jeffrey4l_hmm.. let's me think.. i will push something in the ml.04:59
sdake_inc0 has somethign with include files and jinja204:59
sdake_which I think will require approxximately 1800 top level include files be littered all over the repository05:00
sdake_https://review.openstack.org/#/c/323589/05:02
patchbotsdake_: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo05:02
sdake_Jeffrey4l_ have a review of that05:02
Jeffrey4l_ok05:02
sdake_Jeffrey4l_ i'd appreciate you review on the reviews rather then the ml05:02
Jeffrey4l_roger that05:02
Jeffrey4l_i will05:02
sdake_i'd still like to know what you dont like about  the idea05:03
sdake_in 6 months when dockerfile.j2 are in a total charlie foxtrot state, I won't be re-proposing this idea05:03
sdake_now or never, so i wnat to get the complaints out on the table05:04
sdake_so eveeyrone has the correct information to work with05:04
sdake_nihilifer ping05:05
Jeffrey4l_"charlie foxtrot state" means? ( sorry for no idea for this.)05:05
sdake_cluster fuck state05:05
Jeffrey4l_ok05:06
sdake_so what are the issues with the approach then? :)05:06
Jeffrey4l_i need some time for this.. and i will comment what i think in your PS. ok?05:09
sdake_ok05:12
sdake_try to do today please05:13
openstackgerritMerged openstack/kolla: Pin the base distro release version  https://review.openstack.org/31999205:13
Jeffrey4l_np05:13
nihilifersdake_: pong05:15
sdake_nihilifer can you review a spec please05:15
nihilifersure05:15
sdake_https://review.openstack.org/#/c/323612/05:16
patchbotsdake_: patch 323612 - kolla - Introduction of a new DSL: Elemental05:16
openstackgerritMerged openstack/kolla: Add sahara containers  https://review.openstack.org/31726105:16
sdake_nihilifer any chance you can do it now :)05:22
nihiliferyes, i'm looking right now05:22
sdake_thx05:23
*** phuongnh has joined #openstack-kolla05:23
openstackgerritSteven Dake proposed openstack/kolla: Introduction of a new DSL: Elemental  https://review.openstack.org/32361205:29
openstackgerritSteven Dake proposed openstack/kolla: Introduction of a new DSL: Elemental  https://review.openstack.org/32361205:30
sdake_nihilifer ok i'm done making changes for a short bit :)05:30
*** reddydodda has joined #openstack-kolla05:30
openstackgerritSteven Dake proposed openstack/kolla: Introduction of a new DSL: Elemental  https://review.openstack.org/32361205:37
*** pbourke-home has joined #openstack-kolla05:39
*** pbourke-home has quit IRC05:40
sdake_coolsvap can you review https://review.openstack.org/#/c/323612 please05:41
sdake_also please vote one way or another05:42
sdake_nihilifer ^^ :)05:42
sdake_every spec revision that is reviewed should always hae a vote associated ith it, so the spec author knows if he is headed in the right or wrong  direction05:42
*** sdake has joined #openstack-kolla05:52
*** sdake_ has quit IRC05:55
*** coolsvap_ has joined #openstack-kolla06:02
*** unicell has joined #openstack-kolla06:03
*** daneyon_ has joined #openstack-kolla06:05
*** daneyon_ has quit IRC06:10
*** sdake has quit IRC06:15
*** unicell1 has joined #openstack-kolla06:20
*** unicell has quit IRC06:20
*** berendt has joined #openstack-kolla06:26
*** jmccarthy1 has joined #openstack-kolla06:38
*** tyrola has joined #openstack-kolla06:41
*** tyrola has quit IRC06:45
*** tfukushima has joined #openstack-kolla06:52
*** cu5 has joined #openstack-kolla06:59
*** Serlex has joined #openstack-kolla07:02
*** slagle has quit IRC07:06
*** Mr_Broken has joined #openstack-kolla07:10
*** b_bezak has joined #openstack-kolla07:10
*** mikelk has joined #openstack-kolla07:21
*** matrohon has joined #openstack-kolla07:29
Mech422pbourke_: Morning :-)07:34
Mech422pbourke_: if you happen to see sdake_ - could you let him know I think I'm on track with the bonds/vlan stuff...07:34
Mech422pbourke_: it appears that you can just use a veth pair, and hand 1 end of it to kolla ...07:35
Mech422and *presto* its happy :)07:35
*** pbourke-home has joined #openstack-kolla07:39
*** pbourke-home has quit IRC07:40
*** ssurana has quit IRC07:50
*** fragatin_ has joined #openstack-kolla08:03
*** prithiv has joined #openstack-kolla08:05
*** coolsvap_ has quit IRC08:05
*** fragatina has quit IRC08:07
*** nilk has joined #openstack-kolla08:07
*** fragatin_ has quit IRC08:07
*** fragatina has joined #openstack-kolla08:08
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Introduction of a new DSL: Elemental  https://review.openstack.org/32361208:09
*** cristicalin has joined #openstack-kolla08:10
openstackgerritZhijiang Hu proposed openstack/kolla: Check avahi-daemon is not running when using haproxy in prechecks  https://review.openstack.org/32371508:13
*** efoley has joined #openstack-kolla08:17
*** sgordon has quit IRC08:19
*** tyrola has joined #openstack-kolla08:19
*** tyrola has quit IRC08:20
*** mkoderer has quit IRC08:22
*** sgordon has joined #openstack-kolla08:22
*** lmiccini has quit IRC08:22
*** mkoderer has joined #openstack-kolla08:26
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Add support for mistral ubuntu binary containers  https://review.openstack.org/31724008:30
*** pbourke-home has joined #openstack-kolla08:30
*** lmiccini has joined #openstack-kolla08:31
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Updated Gnocchi binary containers  https://review.openstack.org/31725608:31
*** jmccarthy has quit IRC08:31
*** jmccarthy has joined #openstack-kolla08:31
openstackgerritMerged openstack/kolla: Don't always unpack image build results tuple, as it may be None  https://review.openstack.org/32350508:35
*** wmiller has joined #openstack-kolla08:36
*** dmk0202 has joined #openstack-kolla08:38
*** Mr_Broken has quit IRC08:47
*** daneyon_ has joined #openstack-kolla08:47
*** Mr_Broken has joined #openstack-kolla08:48
*** dmk0202 has quit IRC08:48
*** daneyon_ has quit IRC08:52
*** sacharya has quit IRC08:57
*** Lyncos has quit IRC09:01
*** tfukushima has quit IRC09:04
*** Lyncos has joined #openstack-kolla09:05
*** tfukushima has joined #openstack-kolla09:05
*** tfukushima has quit IRC09:07
*** fragatin_ has joined #openstack-kolla09:11
*** Mr_Broken has quit IRC09:13
*** Mr_Broken has joined #openstack-kolla09:13
*** fragatina has quit IRC09:15
*** fragatin_ has quit IRC09:16
*** Mr_Broken has quit IRC09:18
*** Mr_Broken has joined #openstack-kolla09:25
*** fragatina has joined #openstack-kolla09:27
*** fragatina has quit IRC09:31
*** efoley_ has joined #openstack-kolla09:37
*** efoley has quit IRC09:38
*** reddydodda has quit IRC09:38
*** SiRiuS has joined #openstack-kolla09:40
*** cristicalin has quit IRC09:46
*** matrohon has quit IRC09:47
*** Jeffrey4l_ has quit IRC09:48
*** mdnadeem has joined #openstack-kolla09:51
*** reddydodda has joined #openstack-kolla09:51
*** mdnadeem has left #openstack-kolla09:55
*** mdnadeem has joined #openstack-kolla09:55
*** sacharya has joined #openstack-kolla09:57
*** nilk has quit IRC10:00
*** rhallisey has joined #openstack-kolla10:02
*** efoley__ has joined #openstack-kolla10:02
*** sacharya has quit IRC10:03
*** efoley_ has quit IRC10:05
*** tyrola has joined #openstack-kolla10:05
*** nilk has joined #openstack-kolla10:07
*** mdnadeem has quit IRC10:07
*** mdnadeem has joined #openstack-kolla10:07
*** tfukushima has joined #openstack-kolla10:07
*** pbourke_ has quit IRC10:09
*** pbourke_ has joined #openstack-kolla10:10
*** tfukushima has quit IRC10:12
openstackgerritChristian Berendt proposed openstack/kolla: Load the metadata definitions during Glance bootstrap  https://review.openstack.org/32241510:12
openstackgerritMd Nadeem proposed openstack/kolla-kubernetes: WIP: Heat services and pod  https://review.openstack.org/31685010:12
pbourke-homeMech422: hey just saw your messages in the logs10:18
pbourke-homeMech422: that's great news :) maybe you could add your learnings into a section in our advanced configuation docs?10:18
*** zhiwei has quit IRC10:20
*** Mr_Broken has quit IRC10:21
*** zhiwei has joined #openstack-kolla10:21
*** reddydodda has quit IRC10:24
*** reddydodda has joined #openstack-kolla10:25
*** SiRiuS has quit IRC10:25
Mech422pbourke-home: I'm still getting it to deploy - but it passes the prechecks...10:30
Mech422pbourke-home: how/where are the advanced configuration docs ?10:31
pbourke-homehttp://docs.openstack.org/developer/kolla/advanced-configuration.html10:31
*** Mr_Broken has joined #openstack-kolla10:32
*** daneyon_ has joined #openstack-kolla10:36
*** reddydodda has quit IRC10:38
*** tfukushima has joined #openstack-kolla10:38
*** daneyon_ has quit IRC10:40
*** SiRiuS has joined #openstack-kolla10:42
*** tfukushima has quit IRC10:43
*** weiyu has quit IRC10:47
*** prithiv has quit IRC10:50
*** prithiv has joined #openstack-kolla11:02
Mech422pbourke-home: http://pastebin.com/wfMEwTVC11:06
*** mdnadeem has quit IRC11:06
*** mdnadeem has joined #openstack-kolla11:07
pbourke-homeMech422: nice job!11:08
pbourke-homeMech422: are you familiar with how to submit a change via gerrit?11:08
Mech422pbourke-home: I suck at writing - but the bash commands are there for a better writer...Umm - no...11:08
Mech422I've never actually used gerrit11:09
pbourke-homehttp://docs.openstack.org/developer/kolla/CONTRIBUTING.html11:09
*** godleon has quit IRC11:09
pbourke-homelet me know if you need more info11:09
Mech422pbourke-home: ok - btw, I haven't actually got a cluster up with this yet (still configuring stuff) - just basing this on the fact the pre-checks pass11:10
Mech422pbourke-home: I actually setup 'gen', 'externl', 'ceph', 'cephrep', and 'db'/'dbrep' VLANS...11:12
*** slagle has joined #openstack-kolla11:13
Mech422pbourke-home: I thought I could override the 'internal'/'external' networks further down in the config, like you can customize placement of containers11:13
pbourke-homeyou mean different nics for different hosts?11:13
Mech422pbourke-home: well - like 'ceph_net = "${{ internal_network }}"'11:14
Mech422so ceph defaults to using the internal network, but you can provide a different value if you want11:15
Mech422pbourke-home: ahh - here- from globals.yml:11:16
*** reddydodda has joined #openstack-kolla11:16
Mech422# These can be adjusted for even more customization. The default is the same as11:16
Mech422# the 'network_interface'. These interfaces must container an IPv4 address.11:16
Mech422#kolla_external_vip_interface: "{{ network_interface }}"11:16
Mech422#api_interface: "{{ network_interface }}"11:16
Mech422#storage_interface: "{{ network_interface }}"11:16
Mech422#cluster_interface: "{{ network_interface }}"11:16
Mech422#tunnel_interface: "{{ network_interface }}"11:16
pbourke-homehmm yeah but you can't go any more fine grained11:17
pbourke-homecurrently11:17
Mech422pbourke-home: ahh - still - thats a good start :-)11:17
Mech422I got confused last night and thought you mean I only got 'internal'/'external' with no option to override11:17
Mech422this is a nice breakdown :-)11:17
*** mliima has joined #openstack-kolla11:24
*** dave-mccowan has joined #openstack-kolla11:27
mliimamorning guys11:33
coolsvapmorning mlima11:33
*** mdnadeem has quit IRC11:36
*** mdnadeem has joined #openstack-kolla11:37
*** tfukushima has joined #openstack-kolla11:39
*** reddydodda has quit IRC11:40
*** mdnadeem has quit IRC11:40
*** mdnadeem has joined #openstack-kolla11:41
*** mdnadeem has quit IRC11:41
*** mdnadeem has joined #openstack-kolla11:42
*** mdnadeem has quit IRC11:42
*** mdnadeem has joined #openstack-kolla11:42
*** mdnadeem has quit IRC11:42
*** reddydodda has joined #openstack-kolla11:43
*** mdnadeem has joined #openstack-kolla11:43
*** tfukushima has quit IRC11:44
Mech422grrr...openvswitch really should be part of the 'networking' task or something in Ubuntu11:46
Mech422I think I'm getting weird races because Docker is firing off before I've fully configured ovs11:46
*** Mr_Broken has quit IRC11:50
*** mdnadeem has joined #openstack-kolla11:53
*** sacharya has joined #openstack-kolla11:54
*** phuongnh has quit IRC11:56
*** dwalsh has joined #openstack-kolla11:58
*** mdnadeem has quit IRC11:59
*** sacharya has quit IRC11:59
*** mdnadeem has joined #openstack-kolla11:59
*** mdnadeem has quit IRC12:03
*** mdnadeem has joined #openstack-kolla12:04
*** mdnadeem has quit IRC12:05
*** mdnadeem has joined #openstack-kolla12:06
*** reddydodda has quit IRC12:08
*** efoley__ has quit IRC12:09
*** efoley__ has joined #openstack-kolla12:10
pbourke-homesbezverk: ping12:12
openstackgerritPaul Bourke proposed openstack/kolla: Fix typos in cinder-guide.rst  https://review.openstack.org/32382712:13
*** efoley__ has quit IRC12:14
*** openstackgerrit has quit IRC12:18
*** openstackgerrit has joined #openstack-kolla12:18
*** reddydodda has joined #openstack-kolla12:19
*** JoseMello has joined #openstack-kolla12:21
*** tfukushima has joined #openstack-kolla12:22
*** tfukushima has quit IRC12:22
*** tfukushima has joined #openstack-kolla12:22
coolsvappbourke-home, mliima can you review patch 31540712:23
patchbotcoolsvap: https://review.openstack.org/#/c/315407/ - kolla - Update Cinder guide12:23
coolsvappbourke-home, i think i am updating the changes for patch 323827 in the patch set you just submitted i will check and let you know12:24
patchbotcoolsvap: https://review.openstack.org/#/c/323827/ - kolla - Fix typos in cinder-guide.rst12:24
*** Mr_Broken has joined #openstack-kolla12:26
pbourke-homecoolsvap: "As of Newton-1 milestone, Kolla supports LVM2 as cinder backend."12:28
pbourke-homewhat did we use prior to this?12:28
coolsvappbourke-home, there was ceph and LVM did not had support for iscsid and tgtd12:31
pbourke-homehow did lvm work without iscsi12:32
coolsvappbourke-home, i think it was there but not functional12:34
coolsvap scsi-target-utils package was installed in cinder-volume from a long time12:35
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Update Cinder guide  https://review.openstack.org/31540712:38
coolsvappbourke-home, mliima ^^12:38
pbourke-homecoolsvap: another question12:44
pbourke-homewhats the deal with cinder_iscsi_ip_address12:44
pbourke-homedoes cinder_scheduler not choose this12:44
*** ppowell has joined #openstack-kolla12:45
coolsvappbourke-home, no12:45
coolsvapits the operator configuration12:45
coolsvapiscsi ip can be the same system12:45
pbourke-homewhat if you have multiple storage nodes12:46
coolsvapas long as you are having single block storage provider its managed  by cinder plugin12:46
pbourke-homethat's not HA12:47
coolsvapbecause most cinder plugin use the api provided by block storage device12:47
coolsvapthey do not directly interact with the device12:47
mliimacoolsvap, done :)12:47
sbezverkpbourke-home in this case you need to configure multiple lvm section in cinder.conf12:48
sbezverkpbourke-home also very important is NOT use virtual ip address12:48
sbezverkin cinder.conf for lvm backend12:48
pbourke-homeah I see12:49
sbezverkpbourke-home in normal opensatck there is no HA for this backend either so we are not makeing anything worse than already is12:50
pbourke-homesbezverk: sure, Im just trying to figure out how some of this hangs together12:51
*** dave-mccowan has quit IRC12:52
pbourke-homefriend is telling me that cinder_scheduler can see existing cinder_volumes without needing addtional sections12:52
pbourke-homesbezverk: ^12:53
pbourke-homedoes make sense?12:53
*** Jeffrey4l has joined #openstack-kolla12:53
coolsvappbourke-home, i think it cannot afaik12:53
* coolsvap not sure of any recent updates 12:54
pbourke-home:/12:54
coolsvappbourke-home, i might be bit lagging on cinder updates12:54
sbezverkpbourke-home to create a volume you do not need much, so it might work12:54
sbezverkpbourke-home the trick we accomplished was to allow nova-compute to attach a volume to the instance, here you absolutely need iscsi/tgtd12:55
pbourke-homeyes12:55
*** stvnoyes has quit IRC13:03
*** stvnoyes has joined #openstack-kolla13:04
*** dave-mccowan has joined #openstack-kolla13:07
*** sdake has joined #openstack-kolla13:09
coolsvappbourke-home, i did not find any documentation similar to what you mentioned i ll dig around and let you know if i find something13:09
pbourke-homecoolsvap: thanks I'm also digging around13:10
*** b_bezak has quit IRC13:11
*** ayoung has joined #openstack-kolla13:12
*** ravig has joined #openstack-kolla13:17
*** inc0 has joined #openstack-kolla13:17
inc0good morning13:18
*** daneyon_ has joined #openstack-kolla13:18
coolsvapinc0, good morning13:21
berendtinc0 morning. where are you from? it is nearly end of business here :)13:21
inc0berendt, Texas now;)13:21
*** daneyon_ has quit IRC13:23
*** SiRiuS has quit IRC13:29
*** jtriley has joined #openstack-kolla13:32
*** cu5 has quit IRC13:32
*** sdake has quit IRC13:34
*** rmart04 has joined #openstack-kolla13:37
*** tfukushima has quit IRC13:37
openstackgerritJeffrey Zhang proposed openstack/kolla: DO NOT MERGE: TEST MASTER BRANCH  https://review.openstack.org/29490613:43
*** mgoddard_ has joined #openstack-kolla13:44
*** mgoddard has quit IRC13:47
nilkwhat is the point of doing a "Prepare volumes list" and setting a fact instead of directly assigning?13:48
inc0nilk, which role? I don't recall this task13:51
nilknova_compute for example13:52
nilkwith the reject("equalto", "") filter13:52
nilkprevent errors if a variable is empty=13:52
*** sdake has joined #openstack-kolla13:55
inc0hold on, let me take a look13:55
*** sacharya has joined #openstack-kolla13:56
sdakemorning13:56
inc0ahh so prepare volume list is a hacky way to make conditional volumes in ansible13:56
coolsvapmorning sdake13:56
inc0the reject(equalto, "") won't silence errors - it will remove empty string from list13:57
nilkI see13:57
inc0unfortunately we couldnt easily put "if" in volume list13:58
inc0hey sdake13:58
sdakehey inc013:58
inc0nilk, https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/start_compute.yml#L31 that's the reason it exists13:58
nilkn13:59
nilkah I see13:59
sdakeinc0 fwiw you can't -2 a spec13:59
nilkthe Docker module would fail on the empty string14:00
sdakeyou can -1, or +2, or even +1 although that has no impact14:00
inc0I can change to -1 and comment that it's equivalent to -2 in my mind14:00
*** sacharya has quit IRC14:00
sdakeI can explain why if you like, but majority votes are veto free14:00
sdakelet me expalin why majority votes are veto free14:00
sdakei think tha twill help14:00
prithivis anyone still facing issue with ansible 2.1.0 like this http://paste.openstack.org/show/506958/14:01
sdakea majority vote is the last line of tools we have in the community to resolve conflict14:01
sdakeif someone can veto that, then they can keep the conflict14:01
nilkanother question14:01
nilkif I modify a single Docker image14:01
sdakeif there is not a majority vote achieved on any spec for this problem space, then the work just wont be done14:02
sdakeit is that simple14:02
nilkis there a built-in way to redeploy it or do I manually remove the images?14:02
sdakeinc0 also can you put up a spec please for your proposal14:02
*** reddydodda has quit IRC14:03
inc0it's an alternative to yours14:04
inc0but I need to work more on ideas and get some input14:04
inc0for now I'll do lots of PoC, same way as you did14:04
sdakenihilifer had an idea as well14:05
sdakein one of his reviews of m work14:05
sdakehe added in jinja2 code14:05
sdakeand I thought "thats interesting, he thought we were using jinja2 to parse the data"14:05
*** reddydodda has joined #openstack-kolla14:05
sdakeso there is somewhere in the middle where jinja2 holds the metadata and has a generic parser14:05
sdakebecause really mmy python could be written in jinja14:05
inc0well, not really14:06
inc0I mean if we make jinja2 we keep jinja syntax14:06
inc0not yaml14:06
inc0and it is kinda DSL, only one we already use and is fully functional and documented14:06
sdakeoh right14:06
sdakei just woke up14:06
sdakeanyway mashup - might be an idea ;)14:06
inc0well, I'm confident we can solve all the problems you mentioned with jinja14:07
inc0and it won't be ugly jinja14:07
sdakepbourke-home around?14:07
sdakejpeeler mandre ping14:07
nilkas an operator, I really like that I can easily see and modify the dockerfiles14:08
mandrehey sdake14:08
jpeelerhi14:08
nilkactually, I'm doing that right now14:08
sdakemandre long time no chat14:08
sdakehey eff14:08
sdakecan you guys review this specification:14:08
inc0nilk, yeah, I expect lots of people to do it14:08
mandreyeah sdake, been busy :(14:08
inc0nilk, what do you change there14:08
pbourke-homehey sdake14:08
inc0?14:08
sdakehttps://review.openstack.org/#/c/32361214:08
sdakei'd appreciate a vote one way or another - if it needs further attention i'd like to get it done asap14:09
nilkmodify Cinder to use a commercial storage system14:09
inc0yeah, drivers are one of priorities for this cycle14:09
coolsvapinc0, from what we have seen in the first draft of mandre's patch it created a lot of different paths for different set of plugins14:09
inc0one way or another, but in N you'll get to do that without modyfying code14:09
mandrehmm, at first glance, I'm not super hot on the idea of the dsl14:10
*** SiRiuS has joined #openstack-kolla14:10
sdakemandre i wasn't either - you probbaly saw my post to that mirantis cat14:11
sdakemandre its the only viable mechanism i see to do plugins14:11
*** thumpba has joined #openstack-kolla14:11
sdakepbourke-home did some magic with neutron plguins14:12
inc0not true sdake, we can make it work in number of ways14:12
sdakebut tbh its kind of bolted on14:12
mandresdake: not yet, I've been living under a rock for quite some time14:12
coolsvapextensible and operator friendly solution is what i am after, jinja did appeal to me during our summit discussion, but the dsl looks more promising to me, yeah its more effort but its more promising14:12
mandreactually, I disagree on your assertion about the dsl being the only viable mechanism14:12
inc0coolsvap, why it's more promising?14:13
mandreI'm quite pleased with the PoC I posted14:13
sdakerhallisey inc0 i have a dr appointment and have to skip our meeting this mroning14:13
sdakecan one of you run it please?14:13
inc0uhh so we won't discuss it on the meeting?14:13
inc0I can run it, but we need to have this discussion14:13
sdakemandre have a link?14:13
sdakemandre inc0 is also working on a poc14:13
inc0well, not exactly plugins14:13
coolsvapinc0, unified extension14:14
inc0but extensible jinja2 at large14:14
inc0coolsvap, unified as one file?14:14
mandresdake: I think you looked at it14:14
sdakemandre i have not14:14
mandresdake: https://review.openstack.org/#/c/315027/14:14
patchbotmandre: patch 315027 - kolla - [WIP] Add support for third party plugins14:14
coolsvapsingle format14:14
coolsvapwhich I would like to compare both from the jinja2 and yaml14:15
nilkI've just been inserting jinja2 conditionals in the Dockerfile for my plugin14:15
inc0coolsvap, yes, we need this comparison, so let's trade ideas14:15
nilkworks pretty well14:15
inc0nilk, yup, and it's much more powerful than that14:16
nilkbut it might get ugly if there are ten more of them14:16
inc0then you stop using conditionals and move to more advanced structures14:16
coolsvapinc0, yes, the way sdake described i could imagine how it can be extended, TBH I am not able to do the same with jinja2 that easily14:16
inc0coolsvap, which part you're not able to do?14:17
sdakemandre this question has been asked and answered via vote14:17
sdakeTo answer your question, I suppose the containers for 3rd party services such as midonet-api could live in the kolla repo with the condition that the code is open source and we can build the images freely, though we haven't talked about it specifically in the core team yet.14:17
inc0mandre, ad your idea, instead of macro I was thinking about block14:17
sdakemandre your idea looks like it works - what is the special magic text required?14:18
sdakeI don't like allt he dropping we have all over the build.py for things unrelated to building :(14:18
*** berendt has quit IRC14:18
inc0one way to solve complexity of build.py is to use less flags and more config14:19
inc0configs can be huge, that's acceptable if it's huge and well documented14:19
sdakeok,, i'll stop harping on build.py14:19
sdakeI think we all kknow and agree there is a problem there that needs a refactor when time permits14:20
rhalliseyinc0, can you run the meeting. I'll be in 2x meetings14:20
inc0sure14:21
sdakeinc0 spend 20 minutes on midcycle brainstorming - please put in etherpad14:21
mandresdake: basically you invoke a macro to insert snippets of dockerfile14:21
sdakemandre i see how the iplementation works14:22
sdakecan you tell me what the ucustom snippts are that you put14:22
sdakei am curious about user experience14:22
inc0https://review.openstack.org/#/c/315027/4/docker/plugins/plugins_helper.j2 it's all ther14:22
patchbotinc0: patch 315027 - kolla - [WIP] Add support for third party plugins14:22
inc0e14:22
sdakeinc0 mandre said something must be added to build-kolla.conf14:22
sdakebut then doesns't say what :)14:23
mandrethis file is purely for developers, no user need to look at it14:23
sdakekolla_build.conf?14:23
sdakeoperators need to enable and disable plugins14:23
sdakemandre what i'm asking is how do i turne it on14:23
inc0mandre, https://review.openstack.org/#/c/323589/3/docker/base/custom-dockerfile.j2 line 914:23
patchbotinc0: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo14:23
mandreso sdake, you have to enable plugins in kolla_build.conf14:23
inc0can do the same14:23
inc0you put empty blocks in key places of a dockerfile and people can inject whatever they want there14:24
inc0I'm thinking, if we, instad of "enabling neutron plugins" enable code injection in crucial places14:25
*** thumpba has quit IRC14:25
mandreinc0: yeah, I'm not familiar with blocks14:25
sdakeinc0 you recognize that is a dsl on dsl spread out all over the filesystem instead of one file?14:25
mandrelooks like it will work too14:25
inc0that will allow people to go all batshit crazy about dockerfiles, and even post their working somewhere and it keeps compatibilisty14:25
inc0sdake, we can make it work however we want, it's about designing good structure which needs more work and thought14:26
sdakei had thought about the putting inclludes in14:26
sdakeI identified 8 sections that require inclusion14:26
inc0they could provide 3rd party containers based on containers we have easily14:26
mandreinc0: do we really need people to inject code in more than 1 place per dockerfile?14:26
coolsvapinc0, i agree on  it's about designing good structure which needs more work and thought14:26
sdakebut I thought 8 files * 115 containers = 900 include files14:26
sdakeis a bit much14:26
coolsvapand i think its a more refactor than for dsl14:27
sdakemandre if you want to do it properly with jinja2, the answer unfortunately is yes14:27
inc0mandre, well, custom apt sources.list would another place14:27
*** diogogmt has joined #openstack-kolla14:27
inc0sdake, people have to put more stuff in dockerfile...14:27
inc0proxy settings is another14:27
sdakecan handle proxy settings with the merge feqature14:28
inc0how so?14:28
mandreinc0, sdake: right, we've switched the discussion to extensibility rather than purely plugins14:28
sdakeput in elemental-merge.yml14:28
sdakelet the merging take place14:29
sdakemandre extensibility was where the oirginal discussion was14:29
sdakeI just made the statemeent plugins cant be done any other way14:29
sdakeand the answer is perhaps they can14:29
inc0sdake, how do you ensure that it is called BEFORE all other?14:29
sdakemandre what triggered my interest in this work is a need to support custom repos per container14:30
inc0you want to do external_commands >> repos >> packages >>external_commands?14:30
sdakeinc0 that is precisely what the parser does now14:30
inc0so you have multiple external commands?14:30
sdaketwo groups yes14:30
sdakeall_common_commands14:31
sdakeall_commands14:31
sdakeor bin or src14:31
sdakeits right there in the spec14:31
mandresdake: I see where the dsl shines, but I wonder if it's flexible enough14:31
mandrewe often had the case where we needed to tweak out dockerfiles to remove conflicting packages, etc.14:31
nilkcan I prevent kolla-build from re-building all of the base images?14:31
nilkI only want to re-build a single container14:32
sdakenilk no but it doesn't matter, the build is cached14:32
pbourke-homenilk: use the regex feature14:32
sdaketo build a single container specify it at the end of build14:32
mandrenilk: pass that image name to the command line14:32
nilkI did but it's still rebuilding all dependencies14:32
sdakemandre I have heard this same concern a couple times14:32
sdakemandre that we will end up in a situation in which we are unable to proceed because the dsl is not sufficient14:33
pbourke-homenilk: post the full command you're using?14:33
openstackgerritMerged openstack/kolla: Update Cinder guide  https://review.openstack.org/31540714:34
inc0nilk, it will rebuild deps14:34
sdakemandre to that i'd say - its possible, but hihgly unlikely we will ever be etotally cornered with a dsl14:34
inc0but it will be quick as you use cache14:34
sdakemandre at worst case we can add new top level keys to uncorner ourselves14:34
pbourke-homesdake: one concern is it makes it harder to modify for operators14:34
pbourke-homesdake: if what they want to do isn't in the dsl, they sol14:35
mandresdake: by using dockerfile templates, we're sure it's not going to happen14:35
sdakemakes which harder to modify?14:35
nilkpbourke-home: kolla-build cinder-volume14:35
pbourke-homenilk: is it building stuff other than base and cinder-base?14:35
pbourke-home(and openstack-base)14:35
sdakemandre is that the only tradeoff you considering atm?14:35
nilkno but that's exactly the issue14:35
mandrealso, I find the dsl hard to read and understand what's really happening underneath14:35
nilkit rebuilds openstack-base each time and that takes a while14:35
pbourke-homenilk: it has to rebuild dependencies, that's how docker works. but it should be using the cache as sdake mentioned14:36
*** thumpba has joined #openstack-kolla14:36
mandreyou'd better have a small jinja2 dockerfile template that you render thanks to your dsl parser14:36
sdakemandre huh?14:37
sdakemandre actually i think nihilfer suggested that yesterday but my initial poc was in python ;)14:37
mandresdake: let me paste an example14:37
sdakemandre i implementd base already14:38
sdakeand openstack-base14:38
sdakeis that what you mean?14:38
sdakeand mariadb14:38
sdakeand aodh14:38
mandresdake: no, I'd like a stripped down dockerfile that shows the structure of the dockerfile14:39
mandreright now there is no way to know which group of instructions is executed first without looking at the python source code14:40
sdake#. is an ordered list14:40
sdakethe order is right there in the spec14:40
sbezverknilk make sure you do not use --no-cache option, in this case it will not rebuild the base14:42
*** mgoddard_ has quit IRC14:42
nilkno we're not14:42
sdakemliima around?14:42
nilkbut we're using stable/mitaka14:42
*** mgoddard has joined #openstack-kolla14:42
mandresdake: I don't expect the spec to remain up to date with the code14:42
mandreit's a spec, not a doc14:42
sdakewhile I'm busy harassing people, also please use review ryan's patch on kolla-kubernetes14:43
sdakemandre i did write documentation as well14:43
sdakemandre https://review.openstack.org/#/c/322345/14:43
patchbotsdake: patch 322345 - kolla - Documentation for elemental DSL14:43
mandreok, I'll have to read it I guess :)14:43
sdakethe docs need to be true uped with the spec14:44
sdakebut there is extra info in there14:44
sdakei keep specs lean and clean14:44
*** vhosakot has joined #openstack-kolla14:44
sdakemandre obviously I pla nto keep the docs u pto date14:45
sdakebut nott the spec - the spec is an artifcat14:45
sdakect14:45
*** ppowell has quit IRC14:48
*** diogogmt has quit IRC14:48
*** coolsvap is now known as coolsvap|afk14:51
*** ppowell has joined #openstack-kolla14:51
openstackgerritMarc-Andre Gatien proposed openstack/kolla: adding Note for ubuntu 16.04  https://review.openstack.org/32351914:52
mag009_i've removed my repo any idea how I can continue my commit when you delete your repo ?14:55
inc0mag009_, you mean you want to make changes to it?14:55
mag009_yes14:55
inc0you can clone fresh master14:55
mag009_I looked at openstack doc but couldn't found it14:56
mag009_yes sure but how do I continue my commit14:56
inc0then do git-review -s14:56
mag009_I don't want to redo a new change I want to continue my old change14:56
inc0and then on the right side of  https://review.openstack.org/323519 this page there is "Download" button14:56
inc0there is checkout line, copy and execute it14:56
mag009_lol14:56
mag009_oh god14:56
inc0then commit --amend will work on existing commit14:57
mag009_man I was looking everywhere14:57
inc0:D14:57
mag009_lol feel so dumb..14:57
mag009_thx!14:57
inc0so they changed gerrit layout couple months ago14:57
LyncosI feel dumb for you14:57
inc0you wouldn't believe how long it took for me to find this one14:57
dave-mccowanalso "git review -d ######" will checkout a branch with the change.  combining git and gerrit commands in a repo scares me. :-)14:59
mag009_thanks thats a good one15:00
*** diogogmt has joined #openstack-kolla15:00
*** diogogmt has quit IRC15:01
*** Mr_Broken has quit IRC15:06
*** Mr_Broken has joined #openstack-kolla15:06
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Refactor of base Dockerfile to allow custom repo  https://review.openstack.org/32358915:08
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE: demo of how drivers could work  https://review.openstack.org/32397415:08
*** rhallisey has quit IRC15:08
*** JoseMello has quit IRC15:09
sdakeinc0 can you write a spec for your work plesae15:09
sdakeinc0 then it will appear we have dueling specs vying for core reviewer votes :)15:09
inc0told you, first I want to make some code to get to a point when I think it makes sense15:10
sdakeand I guess if neither passes wee will do nothing15:10
sdakeinc0 sounds good15:10
inc0one poc is worth 100 specs imho15:10
sdakeinc0 you didn't htink so and forced me to write a spec :)15:10
inc0but when I'll figure it out, I'll write a spec with end result15:10
*** Mr_Broken has quit IRC15:11
inc0well, you were pretty confident already about what you had15:11
inc0as poc goes15:11
inc0so I want to do the same;)15:11
sdakeyup its incomplete but it work15:11
sdakes15:11
sdakeunderstood15:11
inc0also if you have any feedback and such, it's a discussion15:12
sdakeyup15:12
sdakei wouldl like to see one common mechanism used for everything15:12
inc0take a look at neutron plugin patch15:12
sdakeit shortens the learning curve15:12
sdakeinc0 one thing I can say about either your or mandre's plugin approach is its better then what exists15:13
sdakeanother thing I can say is the jinja2 stuff will confuse operators15:14
inc0let me remind you that I wanted to use full fledged jinja2 from day 115:14
inc0I don't think so15:14
inc0I think DSL will15:14
inc0as it looks simple15:14
inc0but you dont really control what it produces15:14
inc0more than anything ops like transparency and being able to easily figure out what's happening15:15
sdakethe definition of a dsl is it takes an input and produces an output which matches what does the job15:15
inc0Lyncos, isn't that right?15:15
sdaketransparency - I get that15:15
LyncosSorry I didn't follow ... let me catch-up15:15
inc0DSL will obsuce stuff15:15
inc0I said that operators like transparency and jinja2 isn't too complicated for them15:16
LyncosRight15:16
inc0you guys wrote your own jinja2 Dockerfile, was that painful?15:16
sdakethe answer is no15:17
sdakebecause it only used conditionals15:17
LyncosVery hard15:17
Lyncos;-)15:17
sdakei guess the answer is yes :)15:17
mag009_yes well I prefer jinja2 over any puppet15:17
Lyncoslol15:17
inc0haha15:17
inc0Dockerfile is a little more than a bash script15:17
sdakemag009_ we aren't talking puppet here, we are talking this dsl: https://review.openstack.org/#/c/323612/15:17
patchbotsdake: patch 323612 - kolla - Introduction of a new DSL: Elemental15:17
LyncosIt's a love affair between us and Puppet ;-)15:18
mag009_yes I know ;) just a hater for puppet15:18
sdakeoh well if you wrote your own puppet15:18
sdakeyou guys must be seriously hard core :)15:18
sdakeI can't do that myself :)15:18
inc0been there...not a pretty place15:18
inc0puppet is magic sometimes15:18
inc0ansible is so much simpler15:18
mag009_but my point is puppet has dsl and I hate that from it15:19
wirehead_The problem with the DSL is that it requires a certain structure for the generated Dockerfiles but it will be much harder to write inscruitable Elemental.  The problem with jinja2 is that if you aren't carefull, you can cross over into being inscruitable, but you won't worry about things not representable in Elemental down the road.15:19
LyncosJust an out of topic question... is Kolla tested on RedHat enterprise ?15:19
mag009_its a blocker most of the time because you can do simple loop in your manifest etc...15:19
mag009_sort of thing..15:19
*** zhiwei has quit IRC15:20
inc0Lyncos, ask rhallisey for that15:20
mag009_its definitely simpler in jinja if you want my opinion15:20
inc0I'm sure he did all sorts of redhatish crazy15:20
nilkdumb question15:20
pbourke-homeI think both approaches should be able to build a working base image and service image before arguing any further15:20
nilkif I want to interface with an external storage system15:20
nilkwhere does the cinder-volume service go? controller or compute node?15:21
sdakepbourke-home i'd agree to that if people don't wait to review until both specs are complete15:21
sdakebecause who knows when inc0 is done15:21
inc0nilk, I'd go for controller15:21
sdakeI needed this done yesterday15:21
sdakeand it takes me about a week to implement15:21
sdakenow I have to jerk around with a 2-3 weeks specs process15:21
pbourke-homeno15:21
pbourke-homejust finish the poc15:21
nilkit also attempts to use iscsiadm to do things like copying volumes15:21
pbourke-homefor base + keystone15:21
nilkhow does that work with the iscsi container?15:21
pbourke-homeif it works it will be much easier to convince people15:21
inc0sdake, well, and you'll have to jerk around for a full release at least to bring it into working order imho, it's a lot of work15:22
*** SiRiuS has quit IRC15:22
mliimasdake, i'm here15:22
sdakemliima please review https://review.openstack.org/#/c/323612/15:22
patchbotsdake: patch 323612 - kolla - Introduction of a new DSL: Elemental15:22
nilkI backported everything from the iscsi blueprint to stable/mitaka but I don't understand how cinder-volume is supposed to access the iSCSI container15:22
nihilifersdake: inc0: about the jinja2 stuff, sorry, i was barely awake when writing this comment15:22
pbourke-homeright now it only half works so its much more speculation how well it work15:22
inc0nilk, alias iscsiadm=docker exec -it iscsi iscsiadm?15:22
pbourke-homefor all the problems presented in the spec15:22
nihiliferevery solution that will handle pkg versioning is fine for me15:22
nilkinc0: from inside another container?15:23
inc0nihilifer, pkg versioning?15:23
inc0uhh, that'll be harder15:23
inc0sbezverk, can you help nilk15:23
inc0?15:23
sdakepbourke-home fair enough - still please review the spec for errors, so when I finish the prototype in 1-2 days I am not jerking around waiting 2-3 weeks for specs approval15:23
nihiliferinc0: it means, handling the pins we have currently in apt_preferences or version.lock15:23
inc0nihilifer, is customizing apt_preferences bad?15:24
nihiliferfor now we have only ceph pinned, but maybe we'll pin other infra services as well15:24
inc0if you could easily provide your own apt_preferences15:24
nihiliferwell, if dsl wants to provide pkg list via yaml, then pkg versions should be also provided via yaml15:24
inc0but apart from dsl15:24
inc0if you can provide your own apt_prefs15:25
inc0would that work?15:25
inc0nihilifer, https://review.openstack.org/#/c/323589/415:25
patchbotinc0: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo15:25
inc0however I think I have better idea for file organization15:25
inc0so just look at custom-dockerfile and imagine it's placed somewhere nice15:26
sdakewirehead_ hit it right on the hed, relating to the tradeoffs of one approach to another15:26
nihiliferinc0: is this patch an alternative to sdake's idea?15:26
inc0nihilifer, this and few other I'm working on15:26
nihiliferk15:26
inc0basically demo what we could do with jinja alone15:26
nihiliferhave to take a look then15:26
sdakeinc0 one fundamental problem I see with the approach is it uses a piecemeal bolt on approach for each  type of customization15:27
*** SiRiuS has joined #openstack-kolla15:27
inc0what's a piecemeal bolt?15:28
sdakewe already have that and it works15:28
sdakebut its HARD to USE15:28
sdakewe have stuff to handle rpms15:28
inc0but it's flexible15:28
sdakewe have stuff to handle include headers15:28
sdakewe have stuff to handle include footers15:28
inc0we can make it better15:28
sdakewe have stuff to handle from source installs of plugins15:28
inc0by refactoring15:28
sdakeand we have a fith thing iirc15:28
pbourke-homehow do we stop the dsl from becoming bolt on15:28
pbourke-homeas we cant anticpate everything up front15:29
sdakepbourke-home worst csae we make a new dsl15:29
sdakeand we write a python converter15:29
sdakewhich takes all of 1 hour at most15:29
pbourke-homei think that's a little optimistic :)15:29
sdakedepends on how complex the new dsl change is15:29
sdakebut you get the drift, at most under a week for a ocmplete restructure of the dsl15:30
inc0devils in the details15:30
sdakeby the very nature of  the dsl, it doesn't need to bolt on15:30
inc0we craeted initial build script in few hrs too15:30
inc0look where are we now15:30
LyncosI would prefer keeping J215:31
sdakei have doubts, serious doubts, we can unify the structure of the customizations in jinja215:31
sdakewithout having include sections for each type of include we want15:31
sdakethat is the only viable path forward with jinja215:31
sdakewhich ends up with 900 customizatoin files15:31
williamcabanFrom the maintenance point of view (long term), does it really make sense to maintain another piece of code for the DSL (adding a new definition with any future need) than using jinja?15:31
nihiliferirc meeting now?15:31
sdakeya i've got to jet15:31
sdakeinc0 enjoy meeting - 20 minutes on midcycle brainstorming plelase15:32
*** rhallisey has joined #openstack-kolla15:32
pbourke-homein another hours time15:32
sdakeoh right 9:3015:32
vhosakotyeah... 58 more mins to meeting :)15:32
*** rhallisey has quit IRC15:32
sdakewilliamcaban we are ejecting jinja2 with this proposal15:32
sdakeso we aren't maintaining another, we are maintaing a different15:32
*** rhallisey has joined #openstack-kolla15:32
wirehead_I hate time zone math.  Always afraid I'll screw it up.15:32
vhosakotsdake: sbezverk: I'm still resoving magnum issues... will keep you guys posted.. lbaas is rocking in Ubuntu now15:32
*** ravig has quit IRC15:33
vhosakotsaw this issue twice --> https://answers.launchpad.net/ubuntu/+question/29272315:33
nihiliferwirehead_: yes. and i hate daylight savings even more...15:33
*** ravig has joined #openstack-kolla15:33
*** sacharya has joined #openstack-kolla15:34
wirehead_Oh, I hate DST.  Although one of my better moments in my programming career was when my coworkers messaged me after they changed the date DST changed in the US thanking me for making that easy to update without releasing a new version.15:35
wirehead_That made no sense.  Messaged me thanking me for making it easy to update DST without releasing a new version.  Mind you this ran on Windows at banks so a new version was uncool.15:35
*** mbound has joined #openstack-kolla15:36
*** diogogmt has joined #openstack-kolla15:37
*** rhallisey has quit IRC15:44
*** rhallisey has joined #openstack-kolla15:45
*** rhallisey has quit IRC15:45
*** ppowell has quit IRC15:45
*** rhallisey has joined #openstack-kolla15:45
*** coolsvap|afk is now known as coolsvap15:46
*** berendt has joined #openstack-kolla15:46
*** mikelk has quit IRC15:54
*** sdake has quit IRC15:54
nilkanyone here who can help me with iSCSI?15:55
nilkI don't get how other containers are supposed to use the iSCSI one15:55
sbezverknilk sure, what do you need?15:56
nilkwe're trying to interface with a HP 3par storage15:57
nilkas far as we understood, cinder_volume is only managing the storage using its API in this scenario, so it's running on the controller nodes15:57
nilknow, the 3par plugin attempts to run iscsiadm, which fails15:57
sbezverknilk are you on master or stable/mitaka?15:58
*** ravig has quit IRC15:58
nilkstable/mitaka15:59
nilkbackported everything from master which is related to iscsi15:59
nilkexcept the target, of course15:59
sbezverknilk target? are you refering to tgtd?15:59
nilkyes16:00
*** daneyon_ has joined #openstack-kolla16:01
sbezverknilk ok that is the mistake as both tgtd and iscsid are required at least in the case when volume group is on kolla's managed storage node16:03
sbezverknilk I have never tried to use 3rd party iscsi storage, but I would suggest to port ALL iscsi related from master and then in cinder.conf try to use ip address of your external iscsi server16:04
sbezverkagain, it has never been tested ;-)16:04
nilkyes we tried that, it even talks to the storage already16:05
nilkwe also have a custom cinder.conf16:05
*** daneyon_ has quit IRC16:05
nilknow cinder wants to use iscsiadm and can't16:05
*** mdnadeem has quit IRC16:05
nilkwhat's the idea with the iscsid container?16:06
nilkI assume nova talks to it, right?16:06
*** mdnadeem has joined #openstack-kolla16:06
*** mdnadeem has quit IRC16:07
nilktgtd isn't necessary with a 3rd party storage I believe16:07
*** mdnadeem has joined #openstack-kolla16:07
sbezverknilk correct, because we do not provide iscsiadm binaries to cinder_volume container, it uses ONLY tgtdadm helper, there is no lio based helper support for now..16:09
*** mdnadeem has quit IRC16:09
nilklio?16:09
*** mdnadeem has joined #openstack-kolla16:09
inc0nilk, you can simply install iscsiadm in cinder-volume16:10
sbezverkiscsi_helper                    = lioadm16:10
sbezverkinc0 have you tried it? I seriously doubt it will work..16:11
*** fragatina has joined #openstack-kolla16:12
*** prithiv has quit IRC16:12
inc0no, just a thought16:12
inc0I'm not good at iscsi stuff..16:12
inc0I deploy ceph;)16:12
*** sacharya has quit IRC16:13
sbezverkinc0 :-) when you have unlimited number of servers, why not ;-)16:14
inc0nah, ceph is not that bad;)16:15
inc0I used 3 vms for dev16:15
inc0now I use 1016:15
inc0because I can mwhahaha16:15
*** fragatina has quit IRC16:17
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE: demo of how drivers could work  https://review.openstack.org/32397416:17
*** sdake has joined #openstack-kolla16:19
nilksbezverk: I set iscsi_helper to tgtadm, but it still fails16:20
nilkImageCopyFailure: Failed to copy image to volume: Could not login to any iSCSI portal.16:20
sbezverknilk usually it means nova compute does not use correct ip address of iscsi server.16:22
*** sdake has quit IRC16:23
nilkI did end up installing iscsi-initiator-utils in the cinder-volume container16:23
nilkit wouldn't work otherwise16:23
*** prithiv has joined #openstack-kolla16:23
sbezverknilk Since I have never tried it, I would need to setup something with external iscsi and test it..16:24
sbezverknilk when you create cinder volume, does it get created properly?16:25
nilkyes16:25
nilkbut it's not actually doing anything16:25
nilkas soon as I try to clone an image, it attempts to connect from cinder_storage16:26
nilkthere's no iscsid running on that host16:26
sbezverknilk but do you see lv volume gets created on remote iscsi server?16:27
*** prithiv has quit IRC16:28
nilkno16:28
sbezverknilk ok it makes sense, because cinder_volume executes lvcreate on the local host where it is running16:29
nilkwe set volume_driver=cinder.volume.drivers.san.hp.hp_3par_iscsi.HP3PARISCSIDriver16:29
sbezverknilk I see.. at this point I would first try to figure out why HP iscsi driver does not create volume..16:31
inc0meeting my dear kolla'egues16:31
vhosakotmeeting time16:32
*** sdake has joined #openstack-kolla16:32
*** ssurana has joined #openstack-kolla16:43
*** ssurana has quit IRC16:48
*** rmart04 has quit IRC16:52
*** unicell has joined #openstack-kolla16:54
*** unicell1 has quit IRC16:55
*** ssurana has joined #openstack-kolla16:56
*** thumpba has quit IRC16:56
*** unicell has quit IRC16:57
*** ravig has joined #openstack-kolla16:58
*** thumpba has joined #openstack-kolla17:01
*** mbound has quit IRC17:03
*** ssurana has quit IRC17:03
*** ssurana has joined #openstack-kolla17:04
*** thumpba has quit IRC17:14
*** ppowell has joined #openstack-kolla17:15
*** sacharya has joined #openstack-kolla17:15
*** ppowell has quit IRC17:20
*** unicell has joined #openstack-kolla17:30
rhalliseywirehead_, we'll get to gating soon enough. Hopefully we can settle on our bootstrapping/deployment method/tooling then gating shoudl follow17:30
rhalliseyplus kolla-kube doesn't deloy enough services yet17:30
rhalliseywirehead_, I do agree though17:31
inc0pbourke-home, mandre rhallisey quick question, is number of files even an issue?17:31
*** unicell1 has joined #openstack-kolla17:31
rhalliseynot that i know of17:31
inc0I mean we can have one giant file, but that doens't really help with readibility17:31
rhalliseyI guess it's whatever brings readability17:32
inc0yeah, you can't really measure that17:32
inc0but it's refactoring17:32
inc0mandre, btw this is another approach to drivers https://review.openstack.org/#/c/323974/117:33
patchbotinc0: patch 323974 - kolla - DO NOT MERGE: demo of how drivers could work17:33
inc0on example of neutron17:33
*** ppowell has joined #openstack-kolla17:34
*** thumpba has joined #openstack-kolla17:34
*** unicell has quit IRC17:34
wirehead_At the very least, there should be one file per service, perhaps more.17:36
inc0well we have direcory per container17:37
inc0I don't think this is bad17:37
inc0but I might be wrong17:37
openstackgerritMerged openstack/kolla: adding Note for ubuntu 16.04  https://review.openstack.org/32351917:38
*** pbourke-home has quit IRC17:39
nilksbezverk: why isn't /var/lib/iscsi/ shared?17:40
nilkunnecessary?17:41
*** daneyon_ has joined #openstack-kolla17:49
Mech422pbourke_: so no joy with the VETH stuff yet - it appears when Kolla fires up the openvswitch containers, it kills the existing openvswitch config on the host...17:52
Mech422pbourke_: I actually lose connectivity to the boxes as my mgmt net. is configured via ovs17:53
*** ccesario has quit IRC17:53
*** daneyon_ has quit IRC17:54
*** tyrola has quit IRC17:54
*** jmccarthy1 has left #openstack-kolla17:54
*** thumpba has quit IRC17:55
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE: demo of how drivers could work  https://review.openstack.org/32397418:01
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Refactor of base Dockerfile to allow custom repo  https://review.openstack.org/32358918:01
*** dwalsh has quit IRC18:02
inc0mandre, still up?18:03
*** ccesario has joined #openstack-kolla18:06
*** Serlex has quit IRC18:06
*** tyrola has joined #openstack-kolla18:07
* Mech422 wonders if OVS can actually run in a Container and still play nice with host OVS18:09
Mech422there's only 1 kernel module after all...they duel for it ? :-P18:09
*** neophy has joined #openstack-kolla18:11
*** ccesario has quit IRC18:11
inc0Mech422, well both would need to share ovs db18:13
inc0otherwise it will get messy as one ovs will use override flows of another...and I don't even know when that happends18:14
Mech422inc0: if you have an 'existing' OVS setup on the host18:15
*** thumpba has joined #openstack-kolla18:15
inc0you could share existing ovsdb with ovs in container18:16
Mech422inc0: when you fire up the openvswitch-db and openvswitch-switch containers, it wipes out the existing config..18:16
Mech422inc0: I wonder if that would be enough18:16
inc0should be imho18:16
Mech422inc0: the 'host' side should be doing any changes - its all configured at boot18:16
inc0ovs client is just glorified editor of ovsdb18:16
Mech422s/should/shouldn't/18:16
*** zhiwei has joined #openstack-kolla18:17
Mech422inc0: yeah - but it appears the kernel module is propagating changes back18:17
Mech422inc0: I see the 'containerized' config when I run ovs-vsctl show from the 'host'18:17
Mech422and all the 'host' bridges are gone18:18
inc0well, you have some serius mess out there man;)18:18
Mech422but Kolla doesn't delete them explicitly as far as I can find.  I think its just when kolla fires up with an empty ovs db, the kernel module reports that state to the host as well18:19
nilkthe network is not containerized18:19
Mech422inc0: I don't think its really a 'mess' - as you said, if they shared the DB then the state should be the same between them18:19
nilkit's running in the same namespace18:19
Mech422nilk: oh...hmm..18:20
inc0well either way ovs is in kernel, flows are really below namespaces too18:20
Mech422nilk: so just passing the existing ovs db to the container should be fine...it can already see/change everythign on the host anyway18:20
inc0yeah, if you need your host ovs you can try passing it18:21
inc0but I generally suggest wiping host ovs and use kolla's18:21
*** zhiwei has quit IRC18:21
*** ppowell has quit IRC18:21
Mech422inc0: I could do that for my vlan stuff easy enough - just use native vlans18:22
Mech422inc0: not sure how this is all gonna play with midonet though - thats my ultimate goal18:22
inc0so issue is that ansible doesn't see eth0.100 (or whatever your vlan is)?18:23
Mech422inc0: no - actually that all seems to be fine....18:24
*** ccesario has joined #openstack-kolla18:24
Mech422inc0: its just OVS gets 'confused' once Kolla starts driving18:24
inc0but what would be issue with replacing from host with kolla's one?18:24
Mech422inc0: you lost me ?  Once kolla takes over, I lose the management connection to the box...18:25
inc0ahh you're tagging vlans on ovs18:26
inc0?18:26
Mech422actually, if networking is not name spaced - it prolly makes sense to _always_ share the ovs db18:26
Mech422inc0: yeah18:26
ccesariohello folks....18:26
inc0even if it's namespaced18:26
inc0ovs is not namespaced18:26
inc0you can't have ovs per namespace18:26
ccesariodoes someone could confirm if deploy/image build it works with Ubuntu 16.04 ?!18:27
inc0but try sharing ovsdb, give me a moment18:27
inc0as host or inside docker ccesario ?18:27
Mech422inco0: yeah - since they 'both' control the same kernel module, and 'both' see the state - might as well just use 1 state db?18:27
inc0inside docker I don't think it works18:27
inc0exactly18:27
inc0and you really want to have only one18:27
ccesarioinc0, as host18:28
*** tyrola has quit IRC18:28
inc0ccesario, should work..18:28
inc0Mech422, https://github.com/openstack/kolla/blob/master/ansible/roles/neutron/tasks/start.yml18:28
Mech422inc0: is there a 'generic' way to add shares to the containers - or should I start looking for what to hack ?18:28
inc0so first 3 tasks starts ovsdb, you want to remove them18:29
ccesarioinc0, stable/mitaka and trunk ... right!?18:29
inc0ccesario, yeah18:29
ccesarioinc0, thanks by info... ;)18:29
inc0hmmm18:31
inc0and that might be it Mech42218:31
*** mark-casey has joined #openstack-kolla18:31
Mech422inc0: ok - I'll config. 'br-ex' on the 'host' side and rebuild the images18:31
inc0simply not starting container18:31
inc0but not sure, this is new to me18:31
Mech422inc0: yeah - that looks like an elegant way to fix it18:31
inc0elegant it is not, it's kinda hacky, but it might be only way all things considered18:32
Mech422inc0: since the next task starts vswitchd in a seperate container18:32
inc0yeah, I just don't know how they communicate with each other18:32
Mech422inc0: eh ... seems elegant - 1 less container to run ? :-)  No other changes, etc etc18:32
inc0if it works as I hope it works18:33
inc0;)18:33
*** mbound has joined #openstack-kolla18:35
*** mbound has quit IRC18:40
*** ccesario has quit IRC18:41
williamcabanIs there a way to disable the deployment of haproxy + keepalived when doing an external all-in-one deployment? (i.e. when not using the all-in-one with local targets)18:42
*** Jeffrey4l has quit IRC18:42
*** Jeffrey4l has joined #openstack-kolla18:43
inc0globals.yml:  enable_haproxy: no18:43
williamcabaninc0: cool. does that disable keepalived as well?18:44
inc0yeah18:44
williamcabanthx18:44
inc0remeber that you need to change kolla_internal_address to existing one as well18:44
inc0as no more floating ip exists18:44
williamcabanthe internal or the vip or both?18:45
inc0internal will be vip18:45
inc0external as well in that matter, but since we don't use external that doesn;t really matter18:45
williamcabangot it18:45
inc0https://github.com/openstack/kolla/blob/master/etc/kolla/globals.yml#L2618:46
inc0this one18:46
inc0rest will follow18:46
*** JoseMello has joined #openstack-kolla18:49
williamcabanBTW, since few days ago the "kolla-ansible prechecks" always fails with the verification of the "Docker version" (I'm using 1.11.1 in CentOS7) even though the deploy's work18:49
williamcabannot sure if because of the regex_replace or the version_compare18:51
williamcabanhere https://github.com/openstack/kolla/blob/master/ansible/roles/prechecks/tasks/service_checks.yml#L1318:52
*** ccesario has joined #openstack-kolla18:53
*** daneyon_ has joined #openstack-kolla18:56
*** thumpba has quit IRC18:59
*** thumpba has joined #openstack-kolla19:00
*** daneyon_ has quit IRC19:01
*** papacz has quit IRC19:02
*** ssurana has quit IRC19:04
*** mdnadeem has quit IRC19:06
*** mdnadeem has joined #openstack-kolla19:07
*** mdnadeem has joined #openstack-kolla19:07
*** mdnadeem has quit IRC19:07
*** mdnadeem has joined #openstack-kolla19:08
*** mdnadeem has joined #openstack-kolla19:08
*** mdnadeem has quit IRC19:08
*** mdnadeem has joined #openstack-kolla19:09
*** mdnadeem has joined #openstack-kolla19:09
*** mdnadeem has quit IRC19:09
*** mdnadeem has joined #openstack-kolla19:10
*** mdnadeem has joined #openstack-kolla19:10
*** mbound has joined #openstack-kolla19:12
*** Jeffrey4l_ has joined #openstack-kolla19:31
*** godleon has joined #openstack-kolla19:33
*** Jeffrey4l has quit IRC19:34
inc0guys, I need a brainstorm19:39
inc0who wants a brainstorm?19:39
mag009_about?19:39
inc0most convenient way to customize dockerfiles19:39
inc0so I have an idea19:40
inc0create /etc/kolla/dockerfile-customizations19:40
mag009_isn't related to what you guys been talking about DSL19:40
inc0that will look somehow like that19:40
inc0that's exactly this topic19:40
inc0https://review.openstack.org/#/c/323589/3/docker/base/custom-dockerfile.j219:40
patchbotinc0: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo19:40
inc0so if we make it in /etc19:41
inc0and you'll have a lots and lots of blocks like that19:41
mag009_thats if i want to add some stuff to the base image19:41
inc0so single file with {% nova_compute_additional_packages %} and {% neutron_ovs_agent_post_install %}19:41
inc0well I can have single file with ability to fill every hook we put in every dockerfile19:42
inc0would that be convenient?19:42
mag009_look neat to me19:43
mliimawhy make it in /etc?19:43
inc0why not? it's custom19:43
mag009_for my calico stuff I've added a wget .deb19:43
inc0we can use --customization-file=/etc/myprettyfile19:44
mliimaoh19:44
mliima:)19:44
mag009_are you guys going forward with your DSL for the dockerfiles?19:44
inc0I hope not19:44
inc0I'm strongly against it, but we'll vote on it19:45
mag009_i dont think its worth the effort to be honest..19:45
inc0yeah, I'm afraid that it will be more effort than people realize19:45
mliimawe'll choose between them mag009_19:45
openstackgerritRyan Hallisey proposed openstack/kolla-kubernetes: Break deployment procedure into two steps  https://review.openstack.org/32066819:45
*** dave-mccowan has quit IRC19:46
inc0disadvantage of this solution would be that myprettyfile will not be pretty at all19:47
inc0it will be huge mix of code from multiple containers19:48
inc0but we can work on that too19:48
*** ravig has quit IRC19:48
rhalliseywirehead_, ^^ try out that patch19:50
rhalliseythat will split the cli19:50
*** mdnadeem has quit IRC19:52
*** mdnadeem has joined #openstack-kolla19:53
*** mdnadeem has quit IRC19:53
*** mdnadeem has joined #openstack-kolla19:53
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Replacing the bare pod with a replication controller  https://review.openstack.org/32407719:53
wirehead_rhallisey ^^ That’s the Replication Controller change I was talking about.19:55
rhalliseywirehead_, awesome :)19:55
rhalliseywirehead_, I left a comment19:57
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Replacing the bare pod with a replication controller  https://review.openstack.org/32407719:57
wirehead_Okay, didn’t realize that there was a BP19:58
*** mdnadeem has quit IRC19:58
*** mdnadeem has joined #openstack-kolla19:59
rhalliseywirehead_, ya -> https://blueprints.launchpad.net/kolla-kubernetes19:59
wirehead_My prediction is that we’ll be happier if we do that BP sooner rather than later. :)20:00
rhalliseyfor sure20:00
wirehead_It’ll catch all of the hardcoded pod names before they have a chance to roost.20:00
*** SiRiuS__ has joined #openstack-kolla20:01
*** mdnadeem has quit IRC20:02
*** dave-mccowan has joined #openstack-kolla20:04
wirehead_rhallisey: like, after the replication-controllers BP is done, you are going to do ‘bootstrap’ once and then ‘run’ once.20:05
wirehead_rhallisey: there should never be a case where you ‘run’ twice.20:05
*** david-lyle has joined #openstack-kolla20:05
wirehead_rhallisey: which is, obviously, totally opposite kolla-ansible.20:05
rhalliseywirehead_, you will bootstrap again for an upgrade20:05
wirehead_Yeah.20:06
rhalliseybut you won't need to create eh users, ect..20:06
wirehead_That’s probably ‘upgrade’ instead of ‘bootstrap'20:06
rhalliseyideally we want to have a feedback look where as kubernetes can run a pod that will do the db_sync for bootstrapping and again for upgrades20:08
*** SiRiuS__ has quit IRC20:10
Mech422pbourke_: I can't say that commenting out openvswitch-db 'works' - but the deploy seems to be getting farther and I didn't lose access to the boxes20:13
Mech422pbourke_: I'm gonna hit the hay and let it deploy while I sleep20:13
wirehead_Yah.  I think there will be some operator resistance to fully hands-off upgrades, but for the smaller clouds, it’ll go over like chicken fried bacon in Texas.20:13
Mech422pbourke_: oh - I lie - the deploy just finished...20:14
mag009_when I'm using the master repo I use it with ansible 2.0.0 it fail at : Create log volume20:22
mag009_master repo is compatible with ansible 2.0.0 no ?20:22
mag009_guess not :) just tried with 1.9.420:23
mag009_and it worked.20:23
inc0hmm20:31
inc0master should be ansible220:32
*** ssurana has joined #openstack-kolla20:32
inc0sorcery!20:32
mag009_i think its my bad20:33
Mech422inc0: so looks like just commenting out those 3 tasks worked - haproxy is reporting everything up20:33
mag009_I pulled it like last week or so20:33
inc0Mech422, glad to hear that20:33
Mech422inc0: I'll play with it more tonight - might just be able to put a conditional on those tasks not to run if 'br-ex' already exists20:33
Mech422inc0: then it should work with no-existing config, or if you pre-configured OVS for it20:34
rhalliseywirehead_, rc looks good :)20:34
rhalliseyworks like a charm20:34
inc0rather than that add a conf variable external_ovs20:34
inc0that will default to false20:35
inc0and if true don't run ovsdb20:35
*** fragatin_ has joined #openstack-kolla20:35
*** fragatin_ has quit IRC20:35
inc0not sure if we need to run ovs-vswitchd as well20:35
inc0probably not20:35
Mech422inc0: that'd work - I was trying to avoid another setting.  I am running ovs-switchd currently20:35
inc0well, I think it's ok to add this devaulting to false20:36
*** fragatina has joined #openstack-kolla20:36
inc0since it will be highly unlikely scenerio20:36
inc0or rather to keep our standard, enable_openvswitch=true by default20:36
Mech422inc0: it will also help with midonet :-)20:38
Mech422inc0: Ok - now it really is time for bed...g'nite20:38
inc0bye20:39
*** mliima has quit IRC20:46
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE: demo of how drivers could work  https://review.openstack.org/32397420:47
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Refactor of base Dockerfile to allow custom repo  https://review.openstack.org/32358920:47
*** sdake has quit IRC20:49
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE: demo of how drivers could work  https://review.openstack.org/32397420:50
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Refactor of base Dockerfile to allow custom repo  https://review.openstack.org/32358920:50
*** david-lyle has quit IRC20:51
*** neophy has quit IRC20:52
*** neophy has joined #openstack-kolla20:53
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: [doc] change Ansible version to exactly 2.0.x in quickstart.  https://review.openstack.org/32236120:54
*** thumpba has quit IRC20:54
*** ayoung has quit IRC20:55
inc0rhallisey ping20:58
mag009_http://pastebin.com/Z0LkcmxJ20:58
rhalliseyinc0, yo20:58
inc0https://review.openstack.org/#/c/323589/ check this out20:58
patchbotinc0: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo20:58
mag009_i'm getting this when using ansible 2.0.220:58
rhalliseyinc0, do the packages have to be indented like that?20:59
inc0nah, just trying to break this up21:00
inc0so we won't have one giant dockerfile21:00
inc0but refactoring isn't something I'm 100% sure about, we might think more how to break this up21:00
rhalliseyI mean in redhat-binary-packages file21:00
inc0but I'm curious what you think about template-overrides mechanism21:00
inc0well, right now it's literally cut-paste from what we have now21:01
inc0I can make it prettier when we decide what is prettier;)21:01
*** david-lyle has joined #openstack-kolla21:01
inc0https://review.openstack.org/#/c/323589/7/docker/base/debian-dockerfile.j2 line 3421:01
patchbotinc0: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo21:01
rhalliseyinc0, I feel like whoever gets the gate passing will win :)21:01
inc0we'll create bunch of places like that21:01
rhalliseyI do like it much better21:02
inc0https://review.openstack.org/#/c/323589/7/etc/kolla/custom-dockerfile-example.j2 then you override it like in line 1121:02
patchbotinc0: patch 323589 - kolla - Refactor of base Dockerfile to allow custom repo21:02
inc0and you pass path to this file in build.py21:02
*** neophy has quit IRC21:05
rhalliseyinc0, oh nice. So you can import install_yum macro in the service containers21:09
inc0that's gonna be doable easily21:09
inc0but rather than that we'll have common include file with all that macros and such21:09
inc0just need to figure it out21:09
inc0and would like to wait till build.py refactor21:10
inc0so we can do total refactor at once21:10
mag009_inc0: I have the lastest version of the master repo and it still fail with ansible 2.0.X21:10
inc0mag009_, hmm...I'll try it out tomorrow21:10
inc0I'm a bit burned out today21:10
inc0this DSL thing consumed most of my energy21:11
mag009_yes its fine Im doing another cleanup and starting from scratch just to see21:11
mag009_lol21:11
rhalliseyinc0, left you some comments21:13
inc0thanks21:13
inc0yeah I need to clean this one up21:13
inc0but how do you like general idea behind it?21:14
*** jtriley has quit IRC21:20
*** mbound has quit IRC21:22
*** ravig has joined #openstack-kolla21:28
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Replication controllers for Keystone, Memcached, RabbitMQ.  https://review.openstack.org/32410621:28
wirehead_thanks, dims!  Mainline being broken was bothering my fastidious side. :)21:30
dimswirehead_ : i gotta add a functional test!!21:31
wirehead_dims: yep, trying to avoid straying too far from mainline.  Saves merge time. :)21:33
*** ravig has quit IRC21:34
openstackgerritRyan Hallisey proposed openstack/kolla-kubernetes: Break deployment procedure into two steps  https://review.openstack.org/32066821:40
rhalliseycrap did that already verify21:40
rhalliseyif it did, I'll add the last bit in a new patch21:40
*** v1k0d3n has quit IRC21:45
*** sdake has joined #openstack-kolla21:50
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Adding documentation for labels  https://review.openstack.org/32411021:51
sdakevhosakot ping21:58
openstackgerritMerged openstack/kolla-kubernetes: Regression: Kubernetes was rejecting the YAML we were generating  https://review.openstack.org/32362421:58
openstackgerritMerged openstack/kolla-kubernetes: Replacing the bare pod with a replication controller  https://review.openstack.org/32407721:58
openstackgerritMerged openstack/kolla-kubernetes: Adding the password generation step to the docs.  https://review.openstack.org/32236221:59
*** sdake_ has joined #openstack-kolla22:01
*** david-lyle has quit IRC22:01
*** mdnadeem has joined #openstack-kolla22:03
*** sdake has quit IRC22:03
openstackgerritRyan Hallisey proposed openstack/kolla-kubernetes: Break deployment procedure into two steps  https://review.openstack.org/32066822:06
openstackgerritRyan Hallisey proposed openstack/kolla-kubernetes: Add bootstrap method to the quickstart doc  https://review.openstack.org/32411322:06
openstackgerritRyan Hallisey proposed openstack/kolla-kubernetes: Break deployment procedure into two steps  https://review.openstack.org/32066822:07
vhosakotsdake_: ping22:07
*** david-lyle has joined #openstack-kolla22:16
*** sdake_ has quit IRC22:21
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: DO NOT MERGE: demo of how drivers could work  https://review.openstack.org/32397422:21
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Refactor of base Dockerfile to allow custom repo  https://review.openstack.org/32358922:21
*** ravig has joined #openstack-kolla22:22
*** inc0 has quit IRC22:23
*** mbound has joined #openstack-kolla22:23
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Added documentation for building Kolla containers.  https://review.openstack.org/32411622:24
*** ravig has quit IRC22:24
*** mbound has quit IRC22:28
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Adding documentation for labels  https://review.openstack.org/32411022:29
*** vhosakot has quit IRC22:30
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Added documentation for building Kolla containers.  https://review.openstack.org/32411622:31
*** sdake has joined #openstack-kolla22:31
*** daneyon_ has joined #openstack-kolla22:32
*** zhiwei has joined #openstack-kolla22:34
*** daneyon_ has quit IRC22:37
*** zhiwei has quit IRC22:38
*** intr1nsic has quit IRC22:43
*** intr1nsic has joined #openstack-kolla22:45
*** sacharya has quit IRC22:45
*** mark-casey has quit IRC22:56
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Added documentation for building Kolla containers.  https://review.openstack.org/32411622:57
*** godleon has quit IRC22:59
*** berendt has quit IRC22:59
*** JoseMello has quit IRC23:09
*** diogogmt has quit IRC23:33
*** v1k0d3n has joined #openstack-kolla23:40
openstackgerritJeffrey Zhang proposed openstack/kolla: DO NOT MERGE: TEST MASTER BRANCH  https://review.openstack.org/29490623:51
*** sdake_ has joined #openstack-kolla23:54
*** sdake has quit IRC23:58
*** david-lyle has quit IRC23:59

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