10:02:03 #startmeeting charms 10:02:04 Meeting started Mon Feb 11 10:02:03 2019 UTC and is due to finish in 60 minutes. The chair is tinwood. Information about MeetBot at http://wiki.debian.org/MeetBot. 10:02:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 10:02:08 The meeting name has been set to 'charms' 10:02:12 Hi everybody 10:02:20 Morning 10:02:31 So, first topic 10:02:39 #topic Review ACTION points from previous meeting 10:02:50 I don't think there is anything on this one? 10:02:59 Not that I am aware of 10:03:16 Okay, in that case, let's move on 10:03:23 #topic State of Development for next Charm Release 10:05:37 The charm-specs for the current cycle are at https://github.com/openstack/charm-specs/tree/master/specs/stein and they should be viewable on openstack.org but I'm not sure where 10:06:25 So we are progressing ceph-rdb mirroing, keystone-goal-state and radosgw multisite 10:07:04 We're also pushing ahead with renaming the lxd subordinate charm to nova-lxd to free the lxd name up for more interesting (but potentially not openstack) usage. 10:07:13 anyone want to add anything else? 10:08:23 okay, in that case: 10:08:26 Progress is being made on codifying the OpenStack Security Guide in the charms 10:08:34 ah good 10:08:55 #topic High Priority Bugs 10:09:18 https://bugs.launchpad.net/openstack-charms/+bugs 10:09:18 Use stable-backport tag for bugs http://tinyurl.com/charm-stable-backports 10:09:18 Critical bugs: https://tinyurl.com/osc-critical-bugs 10:09:18 High priority bugs: https://tinyurl.com/osc-high-priority 10:09:48 No criticals, however, quite a few highs. 10:09:55 But many of them are old. 10:10:17 It begs the question; if a bug is 3 years old, is it really a 'high'? 10:11:01 Good point, I guess some cleaning up is due 10:11:57 Yes, I'm wondering if a bug discussion is needed to come up with some policies about de-prioritising bugs that sit around for a long time. i.e. it can't actually be high if it's 3 years old -- or maybe it is. 10:12:17 'High' means "fix soon" 10:13:05 anyway, I guess we should have a think and come back at that this topic when more people have had a chance to think about it. 10:13:14 Any more on bugs? 10:13:54 Not from me 10:13:58 Okay, then we go to: 10:13:58 pass 10:13:59 #topic Openstack Events 10:14:11 I don't know of any upcoming ones? fnordahl? 10:14:18 There's an Ops Meetup coming to Berlin soon, but I don't think we'll have anybody there 10:14:31 And berlin is such a nice place! 10:14:47 indeed! 10:14:53 We were present on the Config Mgmt camp in Ghent last week 10:15:01 Good point fnordahl 10:15:17 Unfortunately, gnuoy isn't with us today to let us know what happened. 10:15:23 And I guess the next big event is Open Infrastructure Summit in April, followed by the PTG 10:15:24 https://etherpad.openstack.org/p/BER-ops-meetup 10:15:35 thanks icey 10:16:09 Shall we move to Open Discussion? 10:16:14 Go for it 10:16:22 #topic Open Discussion 10:16:26 The floor is open 10:16:49 I want to bring up the OpenStack Infra GitHub integration 10:17:00 sure 10:17:30 We want to use that since it fits nicely with our new functional test workflow with Zaza and the actual functional tests living in GitHub 10:17:59 However, it has proven a bit brittle, I brought it up in the #openstack-infra channel last week and at least we got a confirmation that it is a WIP 10:18:32 If everyone could take a moment to think about how we should attack this and chime in on the ML thread that would be great http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002488.html 10:18:34 For the uninitiated, is this around using github hooks to do tests? or something else 10:18:50 Depends-On: 10:19:37 fnordahl, oh, I didn't know that was a feature 10:20:32 It is, but it has some issues. Would be great to have it work 100% 10:20:55 that might mean we need to delve into zuul code? :) 10:21:39 okay, but action to think about how to do it and chime back to ML thread 10:22:14 #action all read http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002488.html (zaza, zuul and depends-on: github url) and consider a response. 10:22:28 thx tinwood 10:22:41 np 10:22:49 anything else for this topic? 10:23:13 Not from me 10:23:31 okay, then let's finish up 10:23:45 #topic Next Chair 10:23:52 and it's fnordahl 10:23:55 \o/ 10:23:58 party time! 10:24:10 Are you around in 2 weeks. Actually, aren't we all in Malta? 10:24:36 may be worth having anyways, as we'll have almost the entire core team present 10:24:51 Okay, 2 weeks it is. 10:25:01 #endmeeting