= Agenda = * Review ACTION points from previous meeting 1. gnuoy move meeting to openstack-meeting channel * State of Development for next Charm Release * High Priority Bugs * Openstack talk submissions for ODS * What does the chair of this meeting do after the meeting? * workload status messages, max 20 chars and proper case? * Openstack Events * Open Discussion * Announce next meeting date, time and chair * ACTION: meeting chair (of this meeting, not the next one) to carry out post-meeting procedure (minutes, etc) documented at https://wiki.ubuntu.com/ServerTeam/OpenStackCharmsChairActions == Minutes == === Review ACTION points from previous meeting === The meeting location and time was discussed. It's desired to move the meeting to #openstack-meeting, but finding a slot has been difficult. gnuoy proposed to try to book openstack-meeting-4 biweekly-even on a Monday (which is 17.00UTC). gnuoy action to book openstack-meeting-4 on a Monday. === State of Development for next Charm Release === * Keystone v3 support in the dashboard has landed * Apparmor for nova-compute is close. * Designate and designate bind should land this week. * Barbican is very close, but has a bug upstream * There are a number of deploy from source reviews ready for review, which should cover the bulk of getting DFS into shape. * Charmhelpers syncs "as-a-module" are progressing to help with the licensing change as part of the move of charms to official openstack project status. * All charm interfaces and layers are now in Git/Gerrit * Feature freeze is Thursday 14th July (next week). === High Priority Bugs === Nothing came up === Openstack talk submissions for ODS === General discussion about importance of getting talks into ODS. Key points: * talk about things openstack-ish that are really interesting to the general community * deploying openstack talks * talks on testing are good. Also discussion around a charm school at ODS. cargonza took an action to coordinate the logistics for a charm school. === What does the chair of this meeting do after the meeting? === With the proposed move to #openstack-meeting gnuoy proposed that the process that the chair should follow should be reviewed. i.e. how the agenda is raised, the meeting notified to potential participants, the agenda circulated, and post-meeting processes. action: gnuoy & jamespage to review the chair's post meeting process and amend as required === workload status messages, max 20 chars and proper case? === Rough summary: the status messages could be enforced to 20 chars + Proper case. Currently OpenStack charms can generate very long status messages which result in users having to scroll their (narrow?) terminals, or have ugly wraps in the status screen. No action was raised, but all authors are asked to consider a 20 char limit & case when writing status message. === Openstack Events === Nothing new here, but see ODS above. === Open Discussion === * email thread about hosting third party OS charms. See logs below for general discussion. jamespage took an action to: "document procedure for setup of sub-charm group ownership for SDN/storage vendors etc..." === Announce next meeting date, time and chair === Same time, same place (maybe) and thedac is set to chair. Note that the meeting may move to #openstack-meeting. gnuoy to advise if this happens. === Meeting Actions === * gnuoy action to book openstack-meeting-4 on a Monday. * cargonza took an action to coordinate the logistics for a charm school. * gnuoy & jamespage to review the chair's post meeting process and amend as required * jamespage took an action to: "document procedure for setup of sub-charm group ownership for SDN/storage vendors etc..." == Log == {{{ == Meeting information == * #ubuntu-meeting: openstack-charms-meeting, 06 Jul at 17:00 — 17:52 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-07-06-17.00.log.html]] == Meeting summary == === Review ACTION points from previous meeting === The discussion about "Review ACTION points from previous meeting" started at 17:01. * ''ACTION:'' gnuoy to try to book first slot from http://paste.ubuntu.com/18635394/ === State of Development for next Charm Release === The discussion about "State of Development for next Charm Release" started at 17:07. === Release Bugs === The discussion about "Release Bugs" started at 17:14. === Openstack Events === The discussion about "Openstack Events" started at 17:19. === Openstack talk submissions for ODS === The discussion about "Openstack talk submissions for ODS" started at 17:21. * ''ACTION:'' cargonza to sync with sales team re charm school at ODS Barcelona === What does the chair of this meeting do after the meeting? === The discussion about "What does the chair of this meeting do after the meeting?" started at 17:27. * ''ACTION:'' gnuoy & jamespage to review the chair's post meeting process and amend as required. === workload status messages, max 20 chars and proper case? === The discussion about "workload status messages, max 20 chars and proper case?" started at 17:32. === Openstack Events === The discussion about "Openstack Events" started at 17:42. === Open Discussion === The discussion about "Open Discussion" started at 17:43. * ''ACTION:'' jamespage document procedure for setup of sub-charm group ownership for SDN/storage vendors etc... * ''ACTION:'' Announce next meeting date, time and chair == Vote results == == Action items, by person == * cargonza * cargonza to sync with sales team re charm school at ODS Barcelona * gnuoy * gnuoy to try to book first slot from http://paste.ubuntu.com/18635394/ * gnuoy & jamespage to review the chair's post meeting process and amend as required. * **UNASSIGNED** * jamespage document procedure for setup of sub-charm group ownership for SDN/storage vendors etc... * Announce next meeting date, time and chair == Done items == * (none) == People present (lines said) == * tinwood (80) * gnuoy (78) * jamespage_shadow (23) * thedac (17) * coreycb (15) * meetingology (8) * cargonza (2) == Full Log == 17:00 #startmeeting openstack-charms-meeting 17:00 Meeting started Wed Jul 6 17:00:48 2016 UTC. The chair is tinwood. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:00 17:00 Available commands: action commands idea info link nick 17:00 welcome all! 17:01 thanks 17:01 The first topic is: 17:01 #topic Review ACTION points from previous meeting 17:01 Looking at the last minutes, gnuoy, it's about moving this meeting!? 17:01 sure, I've done a subtopic for each action in the past 17:02 but I'm guessing you're looking at me for moving this meeting... 17:02 Not sure I follow. 17:02 #subtopic gnuoy to move this meeting 17:02 ^ that sort of thing 17:02 anyway 17:02 I have a gerrit request up for scheduling the meeting 17:03 but we can't have this slot 17:03 (Still new at this) I guess I have to do that? 17:03 we can have: http://paste.ubuntu.com/18635394/ 17:03 And those map to times, I'm guessing. 17:04 tinwood, good point they are all 17:00 UTC 17:04 so, I propose openstack-meeting-4 biweekly-even 17:04 on a Monday 17:05 works for me 17:05 biweekly means we can have another meeting if we need for apac 17:05 We'd have to move our charms catchup? 17:05 1 week in USA friendly time, one week in apac friendly 17:05 Or is that earlier? (UTC vs BST). 17:06 not everyone would attend both 17:06 tinwood: that is one hour earlier 17:06 Sounds okay then. 17:06 this meeting is 17:00 UTC 17:06 Yes, I like those slots 17:06 that time sounds good to me 17:06 ok, I will book that first slot, thanks 17:06 Okay, sounds like an action - is that okay for you to do gnuoy as you're running with it. 17:07 yep 17:07 #action gnuoy to try to book first slot from http://paste.ubuntu.com/18635394/ 17:07 * meetingology gnuoy to try to book first slot from http://paste.ubuntu.com/18635394/ 17:07 thanks gnuoy 17:07 #topic State of Development for next Charm Release 17:08 Any comments on this topic, please? 17:08 Keystone v3 support in the dashboard has landed 17:08 \o/ 17:08 Apparmor for nova-compute is close. I am fighting an amulet race condition at the moment. 17:09 A few caveats though. The dashboard now has to have a db relation if you want to use keystone v3 17:09 Designate and designate bind should land this week. 17:09 barbican is very close, but has a bug upstream :( 17:09 I have a number of deploy from source reviews ready for review, which should cover the bulk of getting DFS into shape. the corresponding c-h changes have landed for the current reviews. 17:10 \o/ 17:10 coreycb, hopefully you should get your charmhelper syncs for free 17:10 with jamespages ch sync for licensing changes 17:10 So it looks like it's all heading in the right direction. 17:11 one more thing 17:11 Any more before we move on? 17:11 all interfaces and layers are in Git/Gerrit now 17:11 ^ Repoint reviews if you need to! 17:11 gnuoy, very nice 17:11 jamespages work but am happy to take the credit 17:12 :) 17:12 Oh, at the feature freeze day is next week. 17:12 yea! good point 17:12 coreycb++ 17:13 Thursday next week to be precise 17:13 So anything that has to make the release needs to be done by next Thursday. 17:13 tinwood, feature-wise, at least 17:13 yes 17:14 next: 17:14 #topic Release Bugs 17:14 gnuoy, would you have your link handy? 17:15 I'm guessing: #link https://goo.gl/HJjORI 17:15 yep 17:15 Yes, there are 32 bugs on the list. 17:16 ...and we still seem to making little progress 17:16 that seems to be like 32 too many 17:16 Do they need to be shifted by 16.07? 17:17 bearing in mind some of them are quite 'old'. 17:17 I'm not sure, I think James does something about retargeting bus 17:17 * bugs 17:17 so long as our run rate on bugs is stable, I think we're ok - we need to focus on high priority bugs first 17:17 (of coursE) 17:18 I would encourage you all to take some time over the next week and spend an hour on the bug queue 17:18 please :-) 17:18 I'll be focussing on reviews, landing and bugs in the next 8 days in the runup to final freeze 17:18 okay, that sounds like a good plan. 17:19 #topic Openstack Events 17:19 I noticed an email that said there was a week to go for submitting talk abstracts for ODS? Did I read that right? 17:20 tinwood, I think your looking at an out of data agends 17:20 * agenda 17:20 I have next agenda item as "Openstack talk submissions for ODS 17:20 " 17:20 ... 17:20 indeed. sorry. 17:20 np, they were adds 17:21 #topic Openstack talk submissions for ODS 17:21 So, hands up if you've submitted one! 17:21 * gnuoy keeps his hand down 17:21 * tinwood knows nothing :( 17:21 I plan to submit one, not sure what yet though 17:21 aparently ONE talk has been submitted so far. 17:22 according to the email I saw. 17:22 gnuoy: we talked about a Openstack charms development talk we could co-author 17:22 yes, agreed 17:23 I'd love to collaborate as I enjoy talking. 17:23 but not if you've already got a partner! 17:23 sounds good we can discuss offline 17:23 and lets talk to markbaker about getting a charm school workshop as well 17:24 some general guidance - talk about things openstack-ish that are really interesting to the general community 17:24 we're (almost) and openstack project, so this is a great change to let the world know about us! 17:24 deploying openstack talks +1000 17:25 beisner, testing stuff good as well - maybe some s390-ish? 17:25 Anything else on ODS? 17:25 Any actions? 17:26 wrt to charm school, I need to sync with the sales team to field the attendance... 17:26 #action cargonza to sync with sales team re charm school at ODS Barcelona 17:26 * meetingology cargonza to sync with sales team re charm school at ODS Barcelona 17:26 I'll coordinate logistics with the admins (ie. rooms, av, etc.) 17:26 awesome 17:27 excellent. 17:27 Okay, next topic looks a bit strange. 17:27 #topic What does the chair of this meeting do after the meeting? 17:27 ok, this one is mine 17:28 The chair of this meeting doesn't always seem to be following the actions outlined in the wiki 17:28 drinks a beer and goes to bed? 17:28 * tinwood lol 17:28 So, can we review the process and amend accordingly 17:29 My first time so .. 17:29 tinwood, I think thats an action for jamespage and I 17:29 agreed - 17:29 once we move under #openstack for meetings we get automated minutes; but I'd like for us to announce the meeting prior to it happening 17:30 and summarize on the openstack-dev ML afterwards 17:30 #action gnuoy & jamespage to review the chair's post meeting process and amend as required. 17:30 * meetingology gnuoy & jamespage to review the chair's post meeting process and amend as required. 17:30 which is not as documented on the ubuntu wiki, but that's where we came from , not where we want to be 17:30 lets get that sorted out between now and next week 17:31 tinwood, sorry, I meant previous chairs not you 17:31 what I really meant was: 17:31 okay, that sounds good. I'm hoping one of you is a chair for the first openstack-meetings meeting. 17:31 We have a process documented and I don;t think its clear to everyone so lets review that 17:32 Right, so there's an action for that. okay to move on? 17:32 sounds good to me 17:32 #topic workload status messages, max 20 chars and proper case? 17:32 ok, so, thats me as weel 17:32 * well 17:32 I think I'm guilty here. 17:33 * thedac hides 17:33 There was a suggestion that we are consistent accross all charms and use proper caps and limit them to 20 chars 17:33 When you say 'Proper Caps', what do you mean? 17:33 I'm not convinced tbh. I think we'll loose valuable info 17:33 Like this 17:33 rather than 17:33 like this 17:34 Okay, that's good. 17:34 What's the driver? 17:34 for 20 chars only? 17:34 I agree a max 20 chars will lose valuable information 17:34 I think its useful to say: all these interfaces are missing... 17:34 thats more that 20chars right there 17:35 that is fairly limiting, 20 chars 17:35 perhaps the requester will negotiate 17:35 Unless it's "'mysql', 'hsm', is miss..." 17:36 okies - so I think working some examples might be useful 17:36 then we can review appropriately and see what works well 17:36 jamespage, +1 17:36 It sounds like we need to pull together all of the workload statuses we set, put them down somewhere, and review it? Or is that too much? 17:37 or gnuoy ^ 17:37 Maybe aim for nice caps and succint message but not limit chars 17:37 coreycb, haha that was jamespage 17:37 lol 17:37 tinwood, I think that's a good idea 17:38 at least a subset of the common messages 17:38 This sounds like an action. Who's not here today? 17:39 Seriously, do we need this as a minuted action? 17:39 tinwood, I don't think so. Maybe lets all keep in mind the formatting of thos stauses 17:39 * those 17:40 Can I ask where the '20' came from? 17:40 it was a suggestion floating around for people with limited terminal width 17:40 --format yaml FTW 17:41 haha yeah 17:42 okay, so no action, but try to keep them short and snappy. assess_status() is a repeat offender as it concatenates missing interfaces ... a lot. 17:42 #topic Openstack Events 17:42 We may have covered this, but any more events? 17:42 Well ODS but I think we've covered that 17:43 Ok, moving on to: 17:43 #topic Open Discussion 17:43 The floor is yours. 17:44 I have nothing to openly discuss :-) 17:44 * tinwood chuckles 17:44 Do we want to discuss the email thread about hosting third party OS charms? 17:44 fire away. 17:44 congress and charm partner charms 17:45 Should all charms go upstream or is there a selection criteria? 17:45 there are no 3rd party os charms 17:46 as a project, openstack charms should be embracing anyone who wants to charm their part of openstack 17:46 agreed. I am aksing if the charm partner SDN charms should also be in this category 17:46 publication of such charms to the juju charm store is dependent on them meeting the criteria as set out by the juju charm team 17:47 thedac, +1 absoluletey 17:47 thedac, plumgrid already asked, onos want to be 17:47 I think the model of charms-core + charms--core will work well here 17:47 ok, so if we could document the procedure that would be helpful 17:47 sure - I'll put something in the charm-guide 17:48 great 17:48 #action jamespage document procedure for setup of sub-charm group ownership for SDN/storage vendors etc... 17:48 * meetingology jamespage document procedure for setup of sub-charm group ownership for SDN/storage vendors etc... 17:48 jamespage, beat me to it. 17:49 thanks jamespage 17:49 Anything more for Open Discussion? 17:49 not from me 17:49 or from jamespage 17:49 I am good 17:49 I'm good as well 17:49 Great. 17:50 #action Announce next meeting date, time and chair 17:50 * meetingology Announce next meeting date, time and chair 17:50 So the chair rotates; who's up for it next? 17:50 tinwood, it's in the wiki, one sec 17:50 tinwood, thedac is the winner 17:50 \o/ 17:51 At the moment, we're assuming next Wednesday at 17.00UTC here again? 17:51 tinwood, yes, I hope its elsewhere but will post a redirect here if needs be 17:51 ok 17:52 okay, then. With no further ado, thanks everybody and ... 17:52 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology) }}}