Wednesday, 2018-04-04

*** seajay has quit IRC00:00
*** cjloader has joined #openstack-meeting-400:14
*** cjloader has quit IRC00:14
*** cjloader has joined #openstack-meeting-400:15
*** cjloader has quit IRC00:19
*** yamamoto has joined #openstack-meeting-400:28
*** yamamoto has quit IRC00:34
*** mjturek has quit IRC00:36
*** zhubingbing has quit IRC00:36
*** zhubingbing has joined #openstack-meeting-400:39
*** cjloader has joined #openstack-meeting-400:50
*** hongbin has joined #openstack-meeting-400:57
*** spzala has quit IRC01:14
*** harlowja has quit IRC01:19
*** yamamoto has joined #openstack-meeting-401:30
*** cjloader has quit IRC01:32
*** cjloader has joined #openstack-meeting-401:33
*** yamamoto has quit IRC01:35
*** cjloader has quit IRC01:46
*** VW has joined #openstack-meeting-401:48
*** VW has quit IRC01:58
*** hongbin has quit IRC02:22
*** dave-mccowan has joined #openstack-meeting-402:24
*** zhurong has joined #openstack-meeting-402:29
*** yamamoto has joined #openstack-meeting-402:32
*** yamamoto has quit IRC02:37
*** psachin has joined #openstack-meeting-402:44
*** dave-mccowan has quit IRC03:01
*** yamamoto has joined #openstack-meeting-403:33
*** yamamoto has quit IRC03:38
*** VW has joined #openstack-meeting-403:45
*** Sukhdev has joined #openstack-meeting-403:49
*** gcheresh has joined #openstack-meeting-403:55
*** hongbin has joined #openstack-meeting-403:56
*** Sukhdev has quit IRC03:56
*** hongbin has quit IRC04:05
*** VW has quit IRC04:06
*** pcaruana has joined #openstack-meeting-404:27
*** pcaruana has quit IRC04:30
*** yamamoto has joined #openstack-meeting-404:35
*** arcolife has joined #openstack-meeting-404:37
*** links has joined #openstack-meeting-404:39
*** links has quit IRC04:40
*** yamamoto has quit IRC04:40
*** tonyb has quit IRC04:45
*** links has joined #openstack-meeting-404:46
*** yamamoto has joined #openstack-meeting-404:51
*** zhurong has quit IRC04:55
*** anilvenkata has joined #openstack-meeting-404:59
*** gcheresh has quit IRC05:06
*** arcolife has quit IRC05:11
*** harlowja has joined #openstack-meeting-405:16
*** harlowja has quit IRC05:20
*** notmyname has quit IRC05:40
*** notmyname has joined #openstack-meeting-405:42
*** dave-mccowan has joined #openstack-meeting-405:42
*** yboaron has joined #openstack-meeting-405:52
*** notmyname has quit IRC05:54
*** notmyname has joined #openstack-meeting-405:57
*** belmoreira has joined #openstack-meeting-406:03
*** janki has joined #openstack-meeting-406:06
*** gmann_ is now known as gmann06:06
*** dave-mccowan has quit IRC06:09
*** alexchadin has joined #openstack-meeting-406:37
*** paken has joined #openstack-meeting-406:41
*** pcaruana has joined #openstack-meeting-407:01
*** diman has joined #openstack-meeting-407:02
*** imacdonn has quit IRC07:04
*** imacdonn has joined #openstack-meeting-407:04
*** diman has quit IRC07:06
*** chyka has joined #openstack-meeting-407:10
*** diman has joined #openstack-meeting-407:13
*** chyka has quit IRC07:14
*** diman has quit IRC07:44
*** diman has joined #openstack-meeting-407:45
*** d0ugal_ has quit IRC07:46
*** d0ugal has joined #openstack-meeting-407:47
*** d0ugal has quit IRC07:47
*** d0ugal has joined #openstack-meeting-407:47
*** yboaron has quit IRC07:47
*** gkadam has joined #openstack-meeting-407:49
*** diman has quit IRC07:49
*** dwj has joined #openstack-meeting-408:01
*** alexchadin has quit IRC08:02
*** dwj has quit IRC08:03
*** fnordahl_ is now known as fnordahl08:04
*** tinwood_ is now known as tinwood08:06
*** alexchadin has joined #openstack-meeting-408:12
*** arcolife has joined #openstack-meeting-408:17
*** iyamahat_ has quit IRC08:33
*** links has quit IRC08:53
*** paken has quit IRC08:56
*** paken has joined #openstack-meeting-408:56
*** links has joined #openstack-meeting-408:57
*** yboaron has joined #openstack-meeting-409:14
*** salmankhan has joined #openstack-meeting-409:28
*** alexchadin has quit IRC09:35
*** yamahata has quit IRC09:44
*** yamamoto_ has joined #openstack-meeting-410:08
*** beekneemech has joined #openstack-meeting-410:10
*** ejat_ has joined #openstack-meeting-410:11
*** kzaitsev1pi has joined #openstack-meeting-410:11
*** gibi_awa1 has joined #openstack-meeting-410:11
*** cgoncalv1s has joined #openstack-meeting-410:11
*** pcaruana|afk| has joined #openstack-meeting-410:12
*** shaohe_feng_ has joined #openstack-meeting-410:13
*** haleyb_ has joined #openstack-meeting-410:15
*** yamamoto has quit IRC10:15
*** ejat has quit IRC10:15
*** kzaitsev_pi has quit IRC10:15
*** shaohe_feng has quit IRC10:15
*** bnemec has quit IRC10:15
*** cgoncalves has quit IRC10:15
*** pcaruana has quit IRC10:15
*** gibi_away has quit IRC10:15
*** haleyb has quit IRC10:15
*** belmoreira has quit IRC10:16
*** shaohe_feng_ is now known as shaohe_feng10:16
*** cgoncalv1s is now known as cgoncalves10:23
*** salmankhan has quit IRC10:28
*** pcaruana|afk| has quit IRC10:28
*** pcaruana|afk| has joined #openstack-meeting-410:28
*** shaohe_feng has quit IRC10:28
*** shaohe_feng has joined #openstack-meeting-410:28
*** haleyb_ has quit IRC10:28
*** haleyb_ has joined #openstack-meeting-410:28
*** salmankhan has joined #openstack-meeting-410:32
*** alexchadin has joined #openstack-meeting-410:41
*** salv-orlando has joined #openstack-meeting-410:44
*** pbourke has quit IRC10:47
*** pbourke has joined #openstack-meeting-410:47
*** paken has quit IRC11:06
*** seajay has joined #openstack-meeting-411:08
*** belmoreira has joined #openstack-meeting-411:31
*** alexchadin has quit IRC11:47
*** alexchadin has joined #openstack-meeting-412:06
*** salv-orlando has quit IRC12:18
*** salv-orlando has joined #openstack-meeting-412:18
*** salv-orlando has quit IRC12:23
*** salv-orlando has joined #openstack-meeting-412:36
*** snapiri- has joined #openstack-meeting-412:38
*** lyan has joined #openstack-meeting-413:03
*** lyan is now known as Guest4450513:03
*** paken has joined #openstack-meeting-413:04
*** psachin has quit IRC13:04
*** VW has joined #openstack-meeting-413:08
*** pmesserl_ has quit IRC13:09
*** pmesserli has joined #openstack-meeting-413:10
*** salmankhan has quit IRC13:15
*** zhubingbing has quit IRC13:24
*** SotK has quit IRC13:25
*** zhubingbing has joined #openstack-meeting-413:28
*** mjturek has joined #openstack-meeting-413:33
*** links has quit IRC13:35
*** mugsie_ is now known as mugsie13:35
*** mugsie has quit IRC13:36
*** mugsie has joined #openstack-meeting-413:36
*** salmankhan has joined #openstack-meeting-413:37
*** SotK has joined #openstack-meeting-413:37
*** julim has quit IRC13:39
*** dklyle has quit IRC13:42
*** links has joined #openstack-meeting-413:49
*** belmoreira has quit IRC13:59
*** hongbin_ has joined #openstack-meeting-414:00
*** yboaron has quit IRC14:10
*** bobh has joined #openstack-meeting-414:11
*** alexchadin has quit IRC14:16
*** belmoreira has joined #openstack-meeting-414:24
*** julim has joined #openstack-meeting-414:26
*** alexchadin has joined #openstack-meeting-414:27
*** zhubingbing has quit IRC14:27
*** salv-orlando has quit IRC14:33
*** VW_ has joined #openstack-meeting-414:37
*** VW has quit IRC14:39
*** d0ugal has quit IRC14:39
*** snapiri- has quit IRC14:40
*** d0ugal has joined #openstack-meeting-414:41
*** dosaboy_ is now known as dosaboy14:47
*** dklyle has joined #openstack-meeting-414:48
*** haleyb_ is now known as haleyb14:52
*** zhubingbing has joined #openstack-meeting-414:55
*** mgoddard has joined #openstack-meeting-414:56
*** david-lyle has joined #openstack-meeting-414:57
*** Kevin_Zheng has joined #openstack-meeting-414:57
*** dklyle has quit IRC14:57
*** premsankar has joined #openstack-meeting-414:59
*** links has quit IRC15:00
*** yankcrime has joined #openstack-meeting-415:01
*** alexchadin has quit IRC15:04
*** arcolife has quit IRC15:09
*** janki has quit IRC15:14
*** zhurong has joined #openstack-meeting-415:14
*** zhubingbing has quit IRC15:23
*** salmankhan has quit IRC15:25
*** salmankhan has joined #openstack-meeting-415:25
*** yamahata has joined #openstack-meeting-415:31
*** iyamahat has joined #openstack-meeting-415:32
*** salv-orlando has joined #openstack-meeting-415:33
*** cjloader has joined #openstack-meeting-415:34
*** salv-orlando has quit IRC15:38
*** links has joined #openstack-meeting-415:43
*** cjloader has quit IRC15:44
*** cjloader has joined #openstack-meeting-415:44
*** pcaruana|afk| has quit IRC15:45
*** spiette has joined #openstack-meeting-415:47
*** mgiles has joined #openstack-meeting-415:50
*** chyka has joined #openstack-meeting-415:53
*** iyamahat has quit IRC15:55
*** duonghq has joined #openstack-meeting-415:55
*** egonzalez has joined #openstack-meeting-415:56
*** caoyuan has joined #openstack-meeting-415:56
*** salmankhan has quit IRC15:56
*** bmace has joined #openstack-meeting-415:58
Jeffrey4l#startmeeting kolla16:00
openstackMeeting started Wed Apr  4 16:00:09 2018 UTC and is due to finish in 60 minutes.  The chair is Jeffrey4l. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: kolla)"16:00
openstackThe meeting name has been set to 'kolla'16:00
Jeffrey4l#topic rollcall16:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:00
duonghqo/h16:01
spsurya__0/16:01
egonzalezWoo/t16:01
caoyuano/h16:01
*** sadasu has joined #openstack-meeting-416:01
sadasuhi16:01
bmaceo/16:02
pbourkeo/16:02
Jeffrey4l#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:02
Jeffrey4lkolla ocata 4.0.4 is release this week16:03
Jeffrey4lany other announcement from community?16:03
*** ktibi has joined #openstack-meeting-416:03
*** salmankhan has joined #openstack-meeting-416:03
Jeffrey4lguess no, move on16:04
Jeffrey4l#topic newton branch eol16:04
*** openstack changes topic to "newton branch eol (Meeting topic: kolla)"16:04
Jeffrey4lopenstack newton release is eol at 2017-10-2516:04
Jeffrey4land kolla newton is a little out of maintain. there is no patch recently at all.16:05
Jeffrey4lso i propose mark it as eol and delete the branch tool16:05
*** links has quit IRC16:05
Jeffrey4lany idea on this?16:05
Jeffrey4lok, i will sync with release team and make this happen recently.16:07
Jeffrey4lnext16:07
Jeffrey4l#topic retire kolla-kubernetes16:07
*** openstack changes topic to "retire kolla-kubernetes (Meeting topic: kolla)"16:07
Jeffrey4lthis is talked on ML.16:07
Jeffrey4lthe core issue is still no contributor could lead this kolla-k8s.16:08
*** ktibi_ has joined #openstack-meeting-416:08
Jeffrey4lso the current plan is still retrie this project now.16:08
Jeffrey4lfeel free to reply in the mail.16:08
Jeffrey4lok. there is no more agenda items.16:09
*** salv-orlando has joined #openstack-meeting-416:09
Jeffrey4l#topic open discussion16:09
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:09
Jeffrey4lany volunteer?16:10
pbourkeJeffrey4l: there is some contention over my spec to move the start scripts to kolla-ansible16:10
duonghqJeffrey4l, iirc, kfox1111 is willing to help in next few months?16:10
*** iyamahat has joined #openstack-meeting-416:10
*** ktibi has quit IRC16:10
sadasuI am new to this community, but would it be a good idea to bring this up during the summit before retiring kolla-k8s?16:10
Jeffrey4lduonghq, no. him move to other due to the company policy.16:10
pbourkeJeffrey4l: I think we may need to propose a vote but Im not 100% on the mechanics of this16:10
duonghqJeffrey4l, got16:10
Jeffrey4lpbourke, yeah, this should be well designed.16:11
duonghqMay I have two topics after Paul16:11
Jeffrey4lduonghq, sure16:11
pbourkeit seems sdake feels very strongly about it, unsure if there's othrs16:11
Jeffrey4l#link https://review.openstack.org/55095816:11
pbourke*others16:11
Jeffrey4lpbourke, i think we should start a ML to talk about this.16:12
spsurya__pbourke: +1  for voting mechanism16:12
Jeffrey4lwhat's the image should be , and should contains.16:12
pbourkeI can start a ML thread16:12
sdakepbourke the main reawosn I Afeel strongly about it is - i feel it would lead to API degradation16:13
Jeffrey4lone of issue i think is, promise we support other upstream images.16:13
sdakebut ya, ml better place to discuss16:13
*** paken has quit IRC16:13
pbourkeJeffrey4l: well, its not so much a promise as making it easier to do so16:13
spsurya__pbourke: Jeffrey4l what about wait for little more time before start any ML on retire ?16:14
Jeffrey4lyeah, api is important. and the image should support some kind of API.16:14
Jeffrey4lthrough all think to orchestration tool is hard to use.16:15
mgoddardpbourke: I think most of what you want to do can be done via config.json, rather than bind mounting everything16:15
Jeffrey4lspsurya__, what's your throught?16:15
spsurya__Jeffrey4l: i discussed all around16:16
pbourkemgoddard: only kolla images support config.json, that's the issue16:16
spsurya__and i personally feel let it be as it is under kolla umbrella16:16
Jeffrey4lbut sure, we still have time.16:17
spsurya__ans wait for more time16:17
spsurya__rwellum: tried to fix the gate but that actually needed more patches in his thought16:17
pbourkespsurya__: personally I think we've spent more than enough time talking about it16:18
Jeffrey4lrwellum is quiting, too ;/16:18
sdakemgoddard i agree16:18
sdakepbourke config.json is the API :)16:18
Jeffrey4lbare image (without any API) is hard to use.16:19
pbourkei disagree, I think its easier16:19
sdakeeasier isn't the issue, whether its a contract and loosley coupled in the issue16:19
sdakeas raised by the TC thread16:19
mgoddardpbourke: I see. Could this be solved via a layer of abstraction? Some driver in k-a that encapsulates how files are placed into a container?16:19
spsurya__pbourke: agree, but if gates is up then kolla might be supporting on kubrnetes too16:19
Jeffrey4leven lots of upstream officical image support a "entrypoing.sh" file as entrance.16:19
sdakewe want loosley coupled + contract imo16:19
pbourkespsurya__: there is not enough people to support it16:20
mgoddardare other deployment tools using the config.json mechanism?16:20
pbourkemgoddard: no16:20
*** links has joined #openstack-meeting-416:20
pbourkewhich is kind of a big deal imo16:20
pbourkekolla is unique in this regard16:20
mgoddardperhaps I should rephrase16:20
egonzalezmgoddard tripleo does16:20
mgoddardis tripleo using it16:20
mgoddardok, thanks16:20
Jeffrey4ldoesn't triplo use it?16:21
sdaketripleo is using config.json16:21
mgoddardyeah, I was really asking about users of kolla images16:21
Jeffrey4lbut they don't use kolla_logs folder.16:21
spsurya__pbourke: yeah, we need only one strong contributor like kfox1111 sbezverk16:21
sdakeif you raad the long thread with the TC, the config.json exists to solve the problem of "how do people integrate with kolla images" without causing a bunch of problems16:22
sdakethat has worked well as other APIs have worked16:22
spsurya__after that more or less we will have 4-5 contributors16:22
mgoddardI read through the ML chain, just wasn't sure if all users of kolla images used config.json - it could easily be bypassed16:22
egonzalezIt needs to be documented for other projects to consume it but wfm16:22
sdakeegonzalez agreed docs would be good16:23
mgoddard+116:23
*** belmoreira has quit IRC16:23
Jeffrey4ldocs +116:23
sdakemandre offered to write them iiuc :)16:23
pbourkewhats the benefit to this api though16:23
sdakepbourke did you read the TC thread?16:23
sdakethe answer to your queestion is covered there16:23
pbourkelink?16:23
*** zhubingbing has joined #openstack-meeting-416:24
sdakeforgive the spam I don't have a link immediately:16:24
sdake[...]16:24
sdakeThe problems raised in this thread (tension - tight coupling -16:24
sdakesecond class citizens - stratification) was predicted early on -16:24
sdakeprior to Kolla 1.0.  That prediction led to the creation of a16:24
sdaketechnical solution - the Kolla API.   This API permits anyone to16:24
sdakereuse the containers as they see fit if they conform their16:24
sdakeimplementation to the API.  The API is not specifically tied to16:24
sdakethe Ansible deployment technology.  Instead the API is tied to the16:24
sdakevarying requirements that various deployment teams have had in the16:24
sdakepast around generalized requirements for making container16:24
sdakelifecycle management a reality while running OpenStack services16:24
sdakeand their dependencies inside containers.16:24
sdake[...]16:24
sdakeThanks! That's where my fuzzy thought process was leading. Existence16:24
sdakeof a stable API guarantee rather than treating the API as "whatever16:24
sdakekolla-ansible does" significantly increases the chances of other16:24
sdakeprojects being able to rely on kolla's images in the long term.16:24
sdake--16:24
sdakeJeremy Stanley16:24
pbourkeyes I read that16:24
sdakeok - that is why the config.json is needed16:25
pbourkethe config.json doesn't solve these things16:25
sdakei disagree16:25
sdakemailing list thread -> you can post  there your thoughts :)16:26
sdakewhat you propose is treating the API as "whatever kolla-0ansible does"16:26
sdake(in the spec)16:26
sdakethat is not highly regarded by the tc, which imo shouldn't be sticking their nose in this business anyway16:27
mgoddardif we're looking to support other image types in kolla-ansible than the kolla images, why not add the support there, rather than changing the kolla API?16:28
pbourkeactually, config.json is making sure people have to follow whatever kolla-ansible does16:28
pbourkeits the exact opposite effect of what you're describing16:28
sdakeanyone is free to submit a config.json change16:28
pbourkeconfig.json lives in kolla-ansible16:28
*** zhubingbing has quit IRC16:28
sdakeconfig.json API lives in containers16:28
Jeffrey4lpbourke, if we have doc, people won't care about how kolla-ansible does16:28
pbourkewrong!16:28
sdakethe actual values in config.json are speciied in kolla-ansible, i agree with that16:29
mgoddardthere needs to be some contract between the image and the tool, config.json or otherwise. This will always be defined by the image16:29
sdakethe API is within the ontainers - APIs consume the config.json as an input16:29
sdakeanyway I'm not going to get into a heated debate in irc, use the mailing list if you wish to disagree16:29
*** zhurong has quit IRC16:29
Jeffrey4lok, this will be critial spec for kolla. let us continue this on ML. irc is hard to talk ;)16:30
Jeffrey4lpbourke, could you start a new ML for this?16:30
pbourkeJeffrey4l: will do, I think the current one has a bit too much going on16:30
Jeffrey4lthanks.16:31
Jeffrey4lnext topic,16:31
pbourkeone last thing before I forget :)16:31
pbourkecan some core other than myself please approve yankcrime's haproxy review16:31
pbourkehe's been very patient with it i think :)16:32
Jeffrey4lpbourke, i have approved it :D16:32
pbourkegreat!16:32
pbourkethanks16:32
Jeffrey4land thanks yankcrime16:32
Jeffrey4lduonghq, your turn16:32
duonghqJeffrey4l, thanks16:33
duonghqthe first and the simple one is in the patch: https://review.openstack.org/#/c/532128/16:33
duonghqAs I need more variables passed to the extend_start script for rolling upgrade, I think Trinh's suggestion is a good option16:34
duonghqbut it requires changing quite large code base16:34
duonghqso I need other developers' opinion16:34
Jeffrey4lthis is one place i wanna kolla(image) should be improve through pbourke's spec :)16:36
Jeffrey4lneed a easier way to run some simple bash script.16:36
duonghqbut I seem that we need quite long discussion about this topic, I think I'll continue with rolling upgrade with extend_script as it16:37
duonghq*it seems16:37
spsurya__duonghq: may be atm i have not heavily been able to help on upgrade thing....but very soon i will be there to help16:38
pbourkeduonghq: will take me some time to get up to speed on that review, will post comments after the meeting16:38
duonghqspsurya__, pbourke, thanks16:39
Jeffrey4lduonghq, i will review it too.16:39
duonghqand I'll the extend script logic untouch16:39
duonghqJeffrey4l, thank, I wish that we can finish to implement rolling upgrade logic for all core services in this cycle16:40
duonghqand it'll need much review effort16:40
duonghqand much more effort to implement the logic correctly, so I appreciate all comments and help16:41
Jeffrey4lyeah16:41
spsurya__duonghq: i will start for nova and swift16:41
*** egonzalez has quit IRC16:41
duonghqspsurya__, I pushed 2 patchsets for nova16:41
duonghqwill add you to reviewers list16:41
spsurya__duonghq: ok16:42
*** beekneemech is now known as bnemec16:42
duonghqso, can we move to the next topic from me?16:43
Jeffrey4lsure16:43
duonghq#link https://blueprints.launchpad.net/kolla-ansible/+spec/ansible-specific-task-become16:43
duonghqlast week I posted this bp status to meeting16:43
duonghqso if nobody has any comments on it, can we mark it as finished?16:44
Jeffrey4lduonghq, should we use "become" for kolla_docker modules?16:44
Jeffrey4las normally user can not connect docker.sock16:45
Jeffrey4lit's permission is "root:docker"16:45
*** egonzalez has joined #openstack-meeting-416:46
duonghqlet me recheck it tomorrow16:46
Jeffrey4lokay16:46
yankcrimeyeah thanks again to Jeffrey4l and pbourke for being patient with my change also :)16:46
duonghqor we just need to add the user to docker group?16:46
duonghqwhich option do your prefer?16:47
Jeffrey4lduonghq, no. become should be better.16:47
Jeffrey4lwe can not ensure the user is a member of docker group.16:47
duonghqI think the real question is which is better: we tried to add the user to the docker group, or just leave the user as it and apply "become" on it16:48
Jeffrey4li prefer to use "become" like other tasks.16:48
duonghqok, but how about you, pbourke, spsurya__ ....16:49
duonghq"become" seems more secure16:49
pbourkebecome is probably most consistent as there are some operations outside docker that need root regardless16:50
spsurya__duonghq: i also see *become* is there for other task16:50
spsurya__ans that should be fine16:51
duonghqok, thank you16:51
duonghqsorry for rush but I have one more topic, if we can finish on it, I'll  move to the next, about 8mins left16:51
duonghqthank Jeffrey4l, pbourke, spsurya__ for comment about ansible-become16:52
Jeffrey4lnp. next?16:53
duonghqmy next topic is about kolla-cli, do you want to discuss in this week or push to next meeting?16:53
pbourkewe can start now and continue next meeting if needed16:54
bmacei don't know how much else is on the agenda or how long you expect the discussion to take.  we can talk in the kolla channel after also if you want16:54
Jeffrey4lor continue in kolla channel ;D16:54
duonghqas we have kolla-cli in official repository, so I think we should make the commands in kolla-cli more usable, for example, add node and remove node16:54
duonghqcurrently, it just manipulate the inventory file16:55
bmaceso just a nomenclature thing? node instead of host?16:55
pbourkemaybe we should get a state of the union type thing for kollacli before we discuss changing commands etc?16:55
duonghqyeah, node, due to I'm opeing the Jeffrey4l's bp https://blueprints.launchpad.net/kolla-ansible/+spec/remove-node16:55
pbourkei.e. is it usable yet with current kolla code right now, what tasks are currently high priority?16:56
duonghqpbourke, my point is deployment "topo" can be changed in production, as it real requirement (e.g. remove node, remove service,....)16:56
duonghqbut remove node is more than just remove the node from inventory file16:56
bmacei can add some kolla-cli bp, but right now there are still some "oracleisms" in it that i'm working on removing.  my goal is to have it working in the kolla-ansible vagrant dev environment asap16:57
pbourkeduonghq: ah I see16:57
pbourkebmace: sounds good :)16:57
bmacefor other stuff, i think we can add kolla-cli blueprints as well, duonghq, and discuss those then?16:57
duonghqbmace, thank for it, but in the mean time, should we implement the lacking logic in kolla-ansible?16:57
Jeffrey4lduonghq, even though that pb is mine. what i want is just improve current destroy logical.16:57
Jeffrey4lremove service or node need more tasks16:58
duonghqbmace, sure, we have project kolla-cli in launchpad, just add something there and link back to the related-one in kolla-ansible16:58
duonghqJeffrey4l, that's my point16:58
duonghqbut it's real requirements from operator16:58
*** egonzalez has quit IRC16:58
duonghqshould we try to do something in this cycle, but I don't want to overload our pending bp list16:59
Jeffrey4lmostly , shutdown the node works lol16:59
duonghqif we can shutdown the node, it's the best case16:59
Jeffrey4lat least i'd like to improve current destroy action.17:00
duonghqbut if the node is turn on accidently, some ghost will walk in our life17:00
Jeffrey4lok. time is up. let us back to openstack-kolla channel.17:00
duonghqkk, thanks17:00
Jeffrey4lthanks for comming,17:00
Jeffrey4lhave a nice day&night17:00
Jeffrey4l#endmeeting17:00
spsurya__thanks17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Wed Apr  4 17:00:41 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-04-04-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-04-04-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-04-04-16.00.log.html17:00
*** sadasu has quit IRC17:00
*** bmace has left #openstack-meeting-417:00
caoyuangood bye17:00
caoyuan:)17:01
*** mgoddard has quit IRC17:03
*** Kevin_Zheng has quit IRC17:07
*** links has quit IRC17:08
*** salmankhan has quit IRC17:13
*** david-lyle has quit IRC17:16
*** mgiles has left #openstack-meeting-417:23
*** Guest44505 has quit IRC17:32
*** Guest44505 has joined #openstack-meeting-417:33
*** duonghq has quit IRC17:33
*** anilvenkata has quit IRC17:40
*** d0ugal has quit IRC17:42
*** alexchadin has joined #openstack-meeting-417:44
*** hongbin_ has quit IRC17:45
*** caoyuan has quit IRC17:52
*** abhishekk has joined #openstack-meeting-417:52
*** hongbin_ has joined #openstack-meeting-417:52
*** yamamoto_ has quit IRC17:58
*** yamamoto has joined #openstack-meeting-417:59
*** yamamoto_ has joined #openstack-meeting-418:06
*** paken has joined #openstack-meeting-418:09
*** yamamoto has quit IRC18:10
*** d0ugal has joined #openstack-meeting-418:12
*** arcolife has joined #openstack-meeting-418:14
*** shaohe_feng has quit IRC18:15
*** shaohe_feng has joined #openstack-meeting-418:15
*** spiette has quit IRC18:16
*** alexchadin has quit IRC18:18
*** spiette has joined #openstack-meeting-418:19
*** salv-orlando has quit IRC18:24
*** zhubingbing has joined #openstack-meeting-418:26
*** zhubingbing has quit IRC18:30
*** Sukhdev has joined #openstack-meeting-418:36
*** Sukhdev has quit IRC18:41
*** gcheresh has joined #openstack-meeting-418:44
*** VW has joined #openstack-meeting-418:50
*** VW_ has quit IRC18:52
*** gkadam has quit IRC19:00
*** gcheresh has quit IRC19:05
*** harlowja has joined #openstack-meeting-419:10
*** salv-orlando has joined #openstack-meeting-419:18
*** gkadam has joined #openstack-meeting-419:42
*** david-lyle has joined #openstack-meeting-419:42
*** seajay has quit IRC19:46
*** gcheresh has joined #openstack-meeting-419:47
*** yankcrime has left #openstack-meeting-419:56
*** VW has quit IRC20:08
*** VW has joined #openstack-meeting-420:09
*** VW has quit IRC20:14
*** VW has joined #openstack-meeting-420:15
*** seajay has joined #openstack-meeting-420:16
*** snapiri has quit IRC20:28
*** Sukhdev has joined #openstack-meeting-420:29
*** snapiri has joined #openstack-meeting-420:30
*** yamamoto_ has quit IRC20:31
*** snapiri has quit IRC20:33
*** snapiri has joined #openstack-meeting-420:33
*** paken has quit IRC20:42
*** julim has quit IRC20:42
*** gcheresh has quit IRC20:48
*** abhishekk has quit IRC20:49
*** Sukhdev has quit IRC21:04
*** seajay has joined #openstack-meeting-421:14
*** iyamahat has quit IRC21:15
*** yamahata has quit IRC21:19
*** d0ugal has quit IRC21:21
*** arcolife has quit IRC21:21
*** zhubingbing has joined #openstack-meeting-421:28
*** yamamoto has joined #openstack-meeting-421:28
*** iyamahat has joined #openstack-meeting-421:29
*** zhubingbing has quit IRC21:33
*** yamamoto has quit IRC21:33
*** gkadam has quit IRC21:36
*** julim has joined #openstack-meeting-421:37
*** ktibi_ has quit IRC21:41
*** yamahata has joined #openstack-meeting-421:50
*** d0ugal has joined #openstack-meeting-421:50
*** cjloader has quit IRC22:03
*** xgerman_ has quit IRC22:15
*** xgerman_ has joined #openstack-meeting-422:15
*** yamamoto has joined #openstack-meeting-422:30
*** seajay has quit IRC22:34
*** yamamoto has quit IRC22:36
*** seajay has joined #openstack-meeting-422:43
*** bobh has quit IRC22:57
*** d0ugal has quit IRC23:03
*** hongbin_ has quit IRC23:06
*** pmesserli has quit IRC23:10
*** pmesserl_ has joined #openstack-meeting-423:10
*** pmesserl_ has quit IRC23:26
*** chyka has quit IRC23:30
*** Guest98296 has joined #openstack-meeting-423:31
*** edleafe- has joined #openstack-meeting-423:32
*** yamamoto has joined #openstack-meeting-423:32
*** edleafe has quit IRC23:33
*** edleafe- is now known as edleafe23:33
*** yamamoto has quit IRC23:38
*** yamahata has quit IRC23:42
*** seajay has quit IRC23:42
*** iyamahat has quit IRC23:44

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