14:01:35 #startmeeting kayobe 14:01:36 Meeting started Mon May 13 14:01:35 2019 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:39 The meeting name has been set to 'kayobe' 14:01:45 #topic rollcall 14:01:50 Hello o/ 14:02:19 Hi \o 14:03:26 dougsz? 14:04:04 hey there 14:04:44 hi there \o 14:04:51 hi radeks :) 14:04:58 #topic agenda 14:05:07 * Roll-call 14:05:10 * Announcements 14:05:12 * Review actions from last meeting 14:05:14 * Kayobe whiteboard https://etherpad.openstack.org/p/kayobe-whiteboard 14:05:16 * Discussion 14:05:18 ** Stein release planning https://etherpad.openstack.org/p/kayobe-stein-release 14:05:20 ** Train summit summary 14:05:22 ** Kayobe seeking official status 14:05:24 ** Github repo mirroring 14:05:26 ** Bug review & squash 14:05:28 * Open Discussion 14:05:30 No announcements today, unless someone has any 14:06:46 hi 14:06:48 hi jovial[m] 14:07:04 have we started? 14:07:13 yeah 14:07:22 Also no action items to review 14:07:29 #topic Kayobe dashboard 14:07:37 #link https://etherpad.openstack.org/p/kayobe-whiteboard 14:07:49 s/dashboard/whiteboard/ 14:08:04 We have a CI failure on master currently in the seed upgrade job 14:08:17 It appears to be something to do with mariadb in bifrost 14:08:39 jovial[m]: has kindly offered to look into it 14:08:53 #action jovial[m] to investigate seed upgrade job failure 14:09:16 moving onto review priorities 14:09:23 I wish there was an easy way to run a zuul playbook to recreate :( 14:09:47 does everyone else just run the stuff manually? or am I doing something wrong? 14:10:01 the same question here 14:10:02 jovial[m]: there aren't too many commands to run thanks to the scripts in dev/ 14:10:18 I believe the zuul team are adding that feature 14:11:01 upgrades are a bit more challenging to run 14:11:15 Ok, I will proceed manually and eagerly await that feature :) 14:11:48 it's a good opportunity to get to know what the CI tests are doing :) 14:14:40 #topic Stein release 14:15:05 IIRC there was a problem with bifrost last time I looked at this 14:15:37 It needs a bit of time spent to work out what's going on. Hopefully otherwise it's close 14:16:06 We have a few patches open now, I guess we need to decide what makes the release soon 14:16:22 always the bifrost ;-) 14:16:28 yeah :( 14:17:07 I am afraid I haven't had time to look again at my Cumulus patch :( 14:17:40 Hopefully there will be time before release 14:18:07 #topic Train summit summary 14:18:21 #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005924.html 14:18:27 I sent that to the list 14:18:36 #link https://etherpad.openstack.org/p/DEN-19-kayobe-feedback-roadmap 14:18:47 that's the Etherpad from the feedback session 14:19:15 we had quite a few people involved, and the main concerns seemed to be around documentation 14:19:24 Nice to see Cody was there 14:20:08 I think at that stage of the summit I was a little fried, so perhaps didn't get the most out of the crowd 14:20:21 still, some good points in there 14:20:43 The workshop went well, and the room was packed 14:21:01 Some familiar faces, and some new 14:21:17 Hopefully we planted a seed for some people 14:21:25 (pun not intended) 14:21:37 Any questions? 14:22:43 #topic Kayobe seeking official status 14:23:05 I think its time for us as a project to seek official status 14:23:25 we're pretty stable, and have a good user base 14:23:42 there are a few options 14:23:57 1. a new deliverable of the kolla project 14:24:10 2. an official OpenStack project 14:24:25 3. a top level OpenStack foundation project 14:24:46 the first requires buy in from the kolla team 14:24:53 The third option, is this like Airship? 14:25:04 priteau: yes 14:25:25 it's not clear to me that there's enough overlap with kolla contributors right now for 1., but we could propose it 14:26:04 2 vs 3 would probably be a question for OpenStack TC/board folk 14:26:30 The 2nd option is well documented. Not sure how people end up in the 3rd. 14:26:32 we're fairly tied to OpenStack right now, so it seems a logical association 14:26:59 I suppose 1. might be awkward for the potential OSA support that was hinted at 14:27:14 OSA? 14:27:16 1 is easiest - kolla team votes, similar to Tenks 14:27:21 (if it ever gets implemented) 14:27:30 OpenStack Ansible 14:27:51 dougsz: its a fair point. It was just an idea but might be worth keeping in mind 14:28:15 it didn't have any immediate interest so probably won't happen right now 14:28:42 Personally, it would be nice to remove some of the boiler plate with closer integration of Kayobe with KA 14:29:03 dougsz: got an example? 14:29:09 the double templating? 14:29:11 Inventory files, config 14:29:23 yeah 14:30:32 would be nice 14:30:32 I think there will always be those who want a separate kolla-ansible though 14:30:44 Agreed 14:31:23 we could consider other ways of adding kayobe's config knowledge into a more vanilla kolla config 14:32:06 ideas on a postcard please 14:32:10 :) 14:32:29 I think we've drifted a bit. Good topic though 14:32:39 #topic Github mirroring 14:33:07 Github mirroring to https://github.com/openstack/kayobe was broken by the switch to opendev, since kayobe is now x/kayobe 14:33:17 this means we have a stale mirror 14:33:25 and it will only get more stale 14:33:30 kill with fire? 14:34:05 Infra offer to archive the repo, although I assume you'd still be able to clone it so that might not help that much 14:34:19 They can also move it to another org, e.g. kayobe/kayobe 14:34:47 I've hesitated with this due to the official project bid, which could move us back to openstack/kayobe :) 14:35:10 do you own the kayobe namespace? 14:35:14 nope 14:35:30 It could take a while to become official, IIRC there's a discussion with the TC which could take time to schedule. 14:35:32 apparently someone else does 14:35:39 https://github.com/kayobe 14:35:51 if they haven't used it in ages you can ask github to transfer it 14:36:17 maybe we can even keep the logo ;-) 14:36:21 Joined GitHub on May 23, 2017 14:36:21 lol 14:36:28 No public activity since 14:37:11 what should we do? 14:37:18 we have updated docs to use opendev 14:37:23 for reference on the TC discussions: https://governance.openstack.org/tc/reference/new-projects-requirements.html 14:37:31 https://github.community/t5/How-to-use-Git-and-GitHub/Taking-the-name-of-an-old-unused-account/m-p/2485#M801 14:38:40 mgoddard: I think it's worth asking GitHub about the kayobe username. It might not take long and then people who want to use GitHub will still be able to do so. 14:39:04 Until we move back to openstack/kayobe if the official project process is successful 14:39:08 how would we keep the mirror in sync? 14:39:20 priteau: true. There's probably a bit of work in setting up a mirror sync job 14:39:47 hopefully openstack/kayobe would redirect to kayobe/kayobe, and then support removing the redirection 14:40:06 FWIW, there seemed to be lots of folks saying, I want kolla but I wish it did the base install the triple-o can 14:40:43 I think that's a good argument for being part of kolla 14:40:52 if you move a repository on github the old link redirects to the new one - so, does that mean github.com/openstack/kayobe would still work? 14:41:11 we have the PTG on 28th & 29th May, I'm going to bring it up then 14:41:21 I wonder if its worth having a vote, noting that the failure means you consider being a top level openstack project under the TC? 14:41:37 cool 14:42:00 johnthetubaguy: vote on what, and by who? 14:42:36 oops, I meant kolla core voting on kayboe joining kolla, a bit like tenks 14:43:53 right, thats what we would have to do. Want to test the water first though 14:44:00 makes sense 14:45:13 I'm getting the impression people think we should try to grab the kayobe org, is that right? 14:46:29 #action mgoddard to enquire about kayobe org on github 14:46:44 #topic Bug review & squash 14:46:45 I quite like our slick new x/kayobe branding 14:47:07 I was thinking we ought to have a bug review & squash session 14:47:42 perhaps an hour or two to review open bugs, then some more time spent on sharing some out and squashing them 14:47:45 any takers? 14:48:44 just me then :) 14:48:58 I'll be up for squashing some :D 14:48:59 Sounds like a good idea, at least making sure all the bugs on Storyboard are still valid 14:49:26 yeah 14:49:50 it's not the most exciting job, but it is important 14:50:12 #action mgoddard to schedule bug review and squash session 14:50:27 #topic open discussion 14:50:33 Anyone have anything? 14:50:37 kayobe-seed-upgrade-centos http://logs.openstack.org/06/658806/1/check/kayobe-seed-upgrade-centos/01a3739/ : SUCCESS in 1h 01m 34s 14:50:57 Either the seed upgrade job is just flakey, or it is now fixed... 14:52:08 Thanks for attending everyone 14:52:14 #endmeeting