15:59:58 #startmeeting kolla 15:59:59 Meeting started Wed Jun 14 15:59:58 2017 UTC and is due to finish in 60 minutes. The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:04 The meeting name has been set to 'kolla' 16:00:12 #topic rollcall, w00t! 16:00:22 w00t 16:00:22 a bit WOOT today please 16:00:29 WOOT 16:00:34 w00t 16:00:50 w00t! 16:01:34 w00t! 16:01:48 WOOT 16:02:48 woot 16:02:57 0/ aka woot 16:03:46 w00t! 16:04:05 w00t 16:04:21 WOOT 16:04:40 that's the spirit:) let's get with meeting 16:04:46 #topic Announcements 16:05:06 I started voting for spsurya_ core team addition, cores, please cast your votes 16:05:51 I will start separate vote for Surya to add him to kolla-kubernetes core team too 16:06:10 but since these core teams are separate, consider this a separate vote 16:06:25 another announcement 16:06:38 We released 5.0.0b2, so images are now tagged 5.0 in master 16:06:48 Jeffrey4l: how are we looking in terms of 4.0.2? 16:07:13 need collect info today. if no other issue, should be release today 16:07:43 cool, if there are any outstanding bugs left, let us know. And everyone, please prioritize these 16:07:54 ok, that's it from me, any community announcements? 16:08:57 guess not 16:09:00 let's get to agenda 16:09:12 #topic Bump min Ansible version to 2.2.0 (duonghq) https://review.openstack.org/#/c/452067/ 16:09:17 duonghq: you have the floor 16:09:23 roger 16:09:40 As you can see, the ps is merged (for a few hours) 16:09:53 so we should start working on remove all warning of Ansible 16:10:02 good point 16:10:10 lots of thigns will break on 2.4 16:10:29 the original intend of the topic is I want to know if we want to bump the Ansible to 2.2.0, but the ps is merged, so the point is as above 16:10:41 duonghq: can you create bp for that? and let's start gathering warnings that needs fixing 16:10:49 inc0, sure 16:10:52 thanks 16:11:06 we need to distribute this work 16:11:22 but first we need to figure out what types of changes need to be made 16:11:30 as in "remove all when: {{..." 16:11:41 then we can distribute work across roles 16:11:41 #link https://launchpad.net/bugs/1695142 16:11:43 Launchpad bug 1695142 in kolla-ansible "In Ansible 2.3, when statement should not contain delimiters" [Medium,In progress] - Assigned to Duong Ha-Quang (duonghq) 16:11:54 gate is a good place to collect all warnings. 16:12:38 Jeffrey4l, yes, I'll collect warning in tomorrow 16:12:43 thanks 16:12:45 cool. thanks. 16:13:05 btw, this patch need to be merge in ocata. 16:13:08 https://review.openstack.org/473206 16:13:21 which is break by ansible 2.3. 16:13:37 it's merged 16:13:39 now it is block by its parent patchq https://review.openstack.org/473205 :) 16:13:42 hmm, egonzalez did w+1, but why is not merged? 16:13:51 ah ok 16:13:55 parent patch ;) 16:14:08 I'll review this after meeting, thanks Jeffrey4l 16:14:16 thanks. 16:14:41 anything else on the topic duonghq ? 16:14:56 inc0, no, thanks 16:15:01 cool, moving on 16:15:04 #topic remove kolla-k8s related code (jeffrey4l) 16:15:08 Jeffrey4l: go ahead 16:15:19 hrm, actually this is mainly for you inc0 ;) 16:15:29 lol 16:15:36 yeah, I guess 16:15:36 before kolla-k8s is depends on kolla-ansible genconfig tools 16:15:45 now it doesn't I know;) 16:15:58 but now, seem you have implement configuration generate in kolla-k8s' side. 16:16:04 I was thinking of doing this but it slipped my mind :( 16:16:19 and i have confirmed with kolla-k8s guys. 16:16:33 anyway, yes, we can get rid of k8s code from kolla-ansible conf 16:17:37 so, if anyone feels like helping with that, it would be appreciated:) 16:18:13 inc0: sure 16:18:13 seems we can move on? 16:18:38 yeah 16:18:49 #topic bug triaged this week (spsurya) 16:18:55 go ahead Surya 16:19:02 yes 16:19:25 #link https://etherpad.openstack.org/p/kolla-bug-triage-week 16:19:28 so this week i was triaging these bugs 16:19:29 let's gather all bugs here 16:19:36 https://www.irccloud.com/pastebin/l9sp8WM3/ 16:20:06 inc0: you can find here too 16:20:19 some of them are in progress 16:20:23 cool, I copied it to ehterpad so we can have one list 16:20:27 for reporter response 16:20:41 cool. it will be more clearly for kolla-ansible. 16:20:44 btw, here is the kolla-k8s' implementation link https://github.com/openstack/kolla-kubernetes/tree/master/ansible 16:20:44 one of them i found invalid 16:21:12 I will be trying more to triage from upcoming weeks 16:21:15 ( network issue, ignore mine ;( ) 16:21:17 spsurya_: can you please use etherpad and list out bugs which are ready to fix? 16:21:33 that would be super useful for anyone who looks for contribution opportunity 16:21:38 that is all from my side 16:21:46 inc0: sure 16:22:15 and if someone ever asks for "how to contribute" or we ourselves want to do something with our free time, it would be good list to take from 16:22:56 inc0: you may continue 16:23:01 that's it 16:23:05 #topic open discussion 16:23:11 I will keep adding in the same link 16:23:13 anyone wants to share anything?:) 16:23:18 great Surya, thank you 16:23:20 i have one. 16:23:21 which are ready to fix 16:23:22 about https://review.openstack.org/473168 16:23:34 about 16:23:35 Flatten neutron_* variables 16:23:57 o/ (sorry for the delay.. I'm one person attending 3 meetings ;)) 16:23:58 we have already move all container variable into default/main.yml file. 16:24:28 but it is a big dict now. and it is hard for end-user to do some customization. 16:24:46 for example. add a environment variable into neutron_server container. 16:24:52 yeah, maybe we should do that across the board 16:24:55 it's good idea. 16:25:10 flatten the neutron_servers will be helpful for this kinda case. 16:25:13 +1 16:25:34 but if we do it here, we need to do it everywhere 16:25:40 yep. 16:25:46 so customization logic will be consistent 16:26:10 +1 16:26:19 this is a example modificaiton. need change other roles if this change is necessary. 16:26:46 another related thought is: move config.json into default/main.yml, then end-user could add whatever config file into container by simple change a dict. 16:27:40 that's gonna be harder 16:27:47 well 16:27:54 i.e. config.json is render base on default/main.yml file. 16:27:55 ansible still needs to render .json 16:28:16 we need to keep ABI consistent, but yes, that's doable 16:28:24 yes. config.json is still required. but it is render base on default/main.yml configration. 16:28:29 we can have one template for config.json and render it all from vars 16:28:42 yeah, +2 from me 16:28:43 yes. 16:28:47 thanks. 16:29:05 should we have one bp about this? 16:29:19 if we're doing this, yes 16:29:23 i think so. 16:29:24 to organize work 16:29:30 and add work items for all the roles 16:29:36 so we can distribute 16:29:38 we have many roles now ;( 16:29:47 yeah 16:29:54 I think we can categorize by alphabetic order 16:30:05 that's why distribution of work is crucial, and for that we need to keep track what's done what is not 16:30:12 and distribute task by range 16:30:22 yes. use work item to track each role. 16:30:31 or etherpad 16:30:33 as daidv did in his bp 16:30:52 work for me. 16:30:56 cool 16:31:13 anything else Jeffrey4l ? 16:31:25 i have another new about hub.docker.com. 16:31:34 one in China?:) 16:31:52 seem docker company are trying work with aliyun ( one china company ) to provide docker iamges service. 16:31:53 yep. 16:32:06 cool 16:32:06 but i searched news, seem it is not ready now. 16:32:14 oh I see 16:32:27 well, we will have publisher code hopefully soon 16:32:28 inc0: update the triaged bugs link https://etherpad.openstack.org/p/kolla-bug-triage-week one is ready to fix, two of them are under review and one of the bug is invalid 16:32:34 anyway, once it is ready. we can push image into it . 16:32:35 it would be good to have Chinese mirror somewhere 16:32:40 yes. 16:33:04 I have one topic too 16:33:06 https://review.openstack.org/#/c/466815/ 16:33:15 so last few weeks I was working with gates 16:33:30 just so you see, adding new gate scenerio will be super easy after this merges 16:33:40 let say we want to add designate to scenerio 16:33:53 i checked the logs. seems the nova-compute in subnodes report errors. 16:33:57 o/ 16:34:20 you create gate-kolla-ansible-dsvm-deploy-designate-centos-binary-centos-7-2-node-nv job in infra 16:34:30 (notice deploy-designate) 16:34:51 then $ACTION in gates will have value "deploy-designate" 16:35:25 and you can add change to config template https://review.openstack.org/#/c/466815/13/tests/templates/globals-default.j2 like this 16:35:53 {% if 'designate' in action %}enable_designate: "yes"{% endif %} 16:35:56 that's it 16:36:10 is it possible to use "deploy-heat-magnum-senlin" in jobs name? 16:36:26 yeah 16:36:36 cool. 16:37:22 nice 16:37:23 it's gonna need infra patch and that's kinda tricky to find all required places to add this 16:37:26 aha, you even didn't change project-config. nice idea. 16:37:26 but I can help with that 16:37:36 no, you need, project-config 16:37:51 i mean the magic ACTION. 16:39:11 https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/projects.yaml#L6370 you'll need to add another option for this action 16:39:36 yes 16:39:48 but that's arguably hardest part of adding new scenerio 16:40:10 and if you do it this way, as in heat-magnum-senlin 16:40:30 you can modify globals in a way that if heat in action: enable heatr 16:40:48 so if we ever add heat-ceilometer-aodh, that will just work 16:41:23 but let's be prudent with this, every new gate consumes resources and makes contribution harder 16:41:32 should we use some test scenario like puppet does? like scenario 1 for heat related , and scenario for ceph related. 16:41:50 so let's focus on covering common use cases, we can have slew of experimental gates for more...exotic ones 16:42:01 yeah, that was my thinking 16:42:10 then we may use 2-3 scenrio to cover all roles. 16:42:12 coo. 16:42:14 It's better if we can gate only related-change 16:42:36 but it's required dependency tree between service 16:42:37 well change to kolla-ansible will be super simple now 16:42:51 duonghq, yes. 16:43:08 also I'd like to not add new aio gates 16:43:15 let's do everything multinode from now on 16:43:25 inc0, +1 16:43:36 +1 16:43:51 cool, that's it from me 16:44:01 keep an eye on this change 16:44:47 anyone else? 16:45:04 yep, i have one topic regarding gnocchi 16:45:08 go ahead 16:45:28 as most may know, gnocchi has been retired from openstack and now is an independent project 16:45:46 this means, there is no more tarballs to download/install in source images 16:46:04 uhh that's a good point 16:46:09 git clone from github? 16:46:59 we can just change default in build (just for master because I assume ocata tarballs will stay on) 16:47:29 not sure about how backports will work 16:47:39 probably wont... 16:48:02 seem the gnocchi in releases project is still updated https://github.com/openstack/releases/blob/master/deliverables/_independent/gnocchi.yaml 16:48:41 when gnocchi is retired? 16:49:02 we should ask release team how gnocci is handled 16:49:09 hrm, ok. ignore me. gnocchi is release 4.0 already. 16:49:16 ah 16:49:21 I guess git clone then? 16:49:34 whole repo was removed, just missing removal from gobernance https://review.openstack.org/#/c/466320/ 16:49:55 here is the new repo: https://github.com/gnocchixyz/gnocchi/ 16:50:18 i think it will now follow global-requirements.txt too. 16:50:43 git clone should be best solution now. 16:51:02 let's just do git clone->pip install 16:51:18 how about master? 16:51:18 we already have plumbing for tha 16:51:20 t 16:51:30 gnocci master github 16:51:32 ? 16:52:29 another question is which version should we use when pike is released ;( 16:52:50 we can ask gnocci community:) 16:53:12 yep 16:54:07 ok, are we done?:) 16:54:25 thats all from me 16:54:33 anyone else? 16:55:10 guess not:) 16:55:17 thank you all for coming! 16:55:20 #endmeeting kolla