17:00:55 <tinwood> #startmeeting charms
17:00:55 <openstack> Meeting started Mon Oct 17 17:00:55 2016 UTC and is due to finish in 60 minutes.  The chair is tinwood. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:56 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:59 <openstack> The meeting name has been set to 'charms'
17:01:05 <icey> o/
17:01:13 <tinwood> Welcome all!
17:01:29 <tinwood> So the first topic on the agenda (at https://etherpad.openstack.org/p/openstack-charms-weekly-meeting-20160317) is:
17:01:41 <thedac> is it just me or is the date bit on that link wonky?
17:01:54 <tinwood> #topic Review ACTION points from previous meeting
17:01:57 <cargonza> o/
17:01:58 <thedac> shouldn't it be 20161017
17:02:09 <gnuoy> yeah, thats my fault
17:02:09 <tinwood> thedac, yes it should.
17:02:10 <cargonza> ack on the date
17:02:20 <thedac> cool, we can fix it after the meeting
17:02:37 <tinwood> #action tinwood to fix the date on the agenda for this meeting after the meeting.
17:03:07 <tinwood> is beisner around or still travelling?
17:03:24 <gnuoy> swap day
17:03:40 <tinwood> okay, we'll carry over his action.
17:03:54 <tinwood> next up is action: tinwood Bug #1629624
17:03:56 <openstack> bug 1629624 in OpenStack Barbican SoftHSM Charm "amulet test fails with barbican-softhsm blocking on 'Charm installed and token store configured'" [High,Fix committed] https://launchpad.net/bugs/1629624 - Assigned to Alex Kavanagh (ajkavanagh)
17:04:11 <tinwood> This was fixed committed and so we can close it.
17:04:36 <tinwood> The next two actions are for jamespage but I don't think he is present?
17:05:01 <tinwood> I'll take that as a no.
17:05:16 <tinwood> next action is: gnuoy update charm guide with refactored charms_openstack bits (carried forward)
17:05:20 <gnuoy> https://review.openstack.org/#/c/387238/
17:05:35 <gnuoy> ^ the more eyes the better. english is hard
17:05:49 <thedac> I'll take a read through today
17:05:50 <tinwood> I agree.  I'll take another look at it.
17:05:56 <gnuoy> thanks
17:06:05 <tinwood> Shall we carry the action over to the next meeting just to top and tail it?
17:06:18 <gnuoy> no, Ithink we can close it tbh
17:06:30 <tinwood> okay, that's good.
17:06:45 <tinwood> #topic State of Development for next Charm Release
17:06:53 <tinwood> So we released!
17:06:55 <jamespage> o/
17:06:58 <gnuoy> 17.01 ftw!
17:07:15 <jamespage> apologies for tardyness
17:07:30 <tinwood> jamespage, we skipped over some of your actions.  Does the meeting mind if we go back?
17:07:41 <icey> +1
17:07:44 <thedac> go for it
17:07:44 <jamespage> pls
17:07:45 <gnuoy> #link http://docs.openstack.org/developer/charm-guide/1610.html
17:07:57 <gnuoy> fine by me
17:07:59 <tinwood> #topic re-review action points ...
17:08:11 <tinwood> so we have: jamespage review current newton specs against plan (carried forward)
17:08:16 <jamespage> done
17:08:34 <jamespage> http://specs.openstack.org/openstack/charm-specs/
17:08:36 <jamespage> ^^
17:08:47 <tinwood> That's great!
17:08:48 <jamespage> I pushed anything incomplete to ocata
17:09:02 <gnuoy> tip top
17:09:21 <tinwood> Are there any actions we should be taking from those specs (in general)?
17:09:50 <jamespage> the backlog ones for ocata need a look
17:09:57 <jamespage> federation and charm charm layering
17:10:06 <gnuoy> I can take look
17:10:39 <jamespage> ta
17:10:45 <tinwood> how about a general action for all to read through the specs before the next meeting and add comments to the next agenda?
17:10:54 <tinwood> Or is that too formal?
17:10:56 <jamespage> tinwood, I think thats  good idea
17:11:04 <jamespage> we're bound to have some stuff coming out of the summit next week
17:11:20 <jamespage> some of the cross charm initiatives will need specs methinks
17:11:39 <tinwood> #action all to read through the charm specs: http://specs.openstack.org/openstack/charm-specs/
17:11:41 <cargonza> ack on cross charm initiatives
17:12:17 <cargonza> do we need to account the review queue also?
17:12:21 <tinwood> how do we want to collect comments?
17:12:33 <tinwood> let's take cargonza question first.
17:13:38 <tinwood> thoughts on review queue?
17:13:52 <jamespage> I'm not quite sure on the context of the question?
17:13:55 <gnuoy> I don;t think the review queue needs a spec if I've ubndersttod the question correctly
17:14:06 <tinwood> cargonza, ?
17:14:07 <jamespage> ^^ like gnuoy if that's the case
17:14:08 <cargonza> no spec needed for the review queue
17:14:21 <jamespage> specs are for new features of significant changes ot the charms
17:14:24 <jamespage> or new charms
17:14:25 <cargonza> lets go back to the spec - capturing comments
17:14:37 <cargonza> review queue is another topic - apologize
17:14:47 <wolsen> gerrit is used for charm-specs comments as well right?
17:14:55 <tinwood> cargonza, I'll add it to the topics list
17:14:56 <jamespage> wolsen, yes - for a proposed change
17:15:02 <tinwood> (review queue)
17:15:04 <cargonza> ack tx
17:15:10 <wolsen> jamespage: ah the issue is for carry over? getting comments on that?
17:15:38 <jamespage> not sure - cargonza would you like to frame your questions specifically?
17:16:14 <gnuoy> I think tinwood was asking how we should collect comments relating to our review of the specs for next time
17:16:14 <cargonza> we're asked to put effort on the charm review queue...
17:16:28 <jamespage> sorry we're jumping around here
17:16:28 * cargonza finding link
17:16:31 <tinwood> To clarify: topic is charm-specs; comments welcome; where should we collect them?
17:16:42 <tinwood> (sorry for bad chairing there for a minute)
17:16:46 <cargonza> ack lets finish this one
17:17:19 <cargonza> collect them via google doc?
17:17:20 <gnuoy> Just propose changes for anything that jumps out at us
17:17:24 <gnuoy> ?
17:17:28 <jamespage> gnuoy, +1
17:17:30 <wolsen> gnuoy, +1
17:17:35 <tinwood> via gerrit: +1
17:17:37 <jamespage> if you think a change is appropriate propose a change
17:17:51 <jamespage> or just ask in irc
17:17:53 <jamespage> or on the ML
17:18:00 <jamespage> but lets not start using gdocs pls
17:18:05 <wolsen> +1
17:18:09 <tinwood> +1
17:18:21 <jamespage> tinwood, shall we move on
17:18:22 <jamespage> ?
17:18:24 <tinwood> yes
17:18:40 <tinwood> other action: jamespage to identity alternate week slot and get scheduled (carried forward)
17:18:48 <jamespage> carried forward (again)
17:18:51 <jamespage> sorry apac
17:18:56 <tinwood> np
17:18:56 <jamespage> I will get this sorted out
17:19:01 <jamespage> might be for nov tho
17:19:21 <tinwood> okay, next up:
17:19:29 <tinwood> #topic State of Development for next Charm Release
17:19:43 <gnuoy> We're bright eyed and bushy tailed
17:20:16 <jamespage> indeed
17:20:56 <tinwood> So next up is 17.01
17:20:56 <jamespage> master branches are open
17:20:57 <gnuoy> Its the start of a new cycle probably not too much else to say
17:21:13 <jamespage> time to get those carried over features landed early
17:21:15 <thedac> Worth noting there will be lots of discussion at ODS about this
17:21:15 <gnuoy> yep, end of Jan I assume we'll go for
17:21:17 <jamespage> so they don't miss the next freeze
17:21:35 <jamespage> bearing in mind it will be just after new year, and christmas always gets in the way :-)
17:21:44 <jamespage> so its really 2 months of devtime max
17:21:51 <tinwood> Not long.
17:21:52 <gnuoy> thedac, lots of discussion about what?
17:22:03 <thedac> the next charms release
17:22:03 <jamespage> assuming we're doing a 17.01 which I think is the case until for now
17:22:11 <gnuoy> thedac, ack, yes
17:22:18 <jamespage> thedac, yes - we have session wed pm at the end of day
17:22:24 <tinwood> How soon after 17.01 is the 'developer' ODS conf?
17:23:05 <jamespage> its in fedb
17:23:08 <jamespage> openstack.org/ptg
17:23:12 <tinwood> Also is there a cfgmgmtcamp in feb?
17:23:15 <jamespage> yes
17:23:30 <jamespage> actually as a team we need to decided whether we're doing the PTG
17:23:41 <jamespage> my feel is that we should - but maybe only the first couple of days
17:23:48 <tinwood> What does PTG stand for?
17:23:51 <jamespage> which is horizontal rather than vertical
17:23:56 <jamespage> tinwood, go read :)
17:23:59 <thedac> project teams gathering
17:24:08 <tinwood> (it was for the meeting!)
17:24:11 <jamespage> tinwood, lets move on shall we?
17:24:17 <tinwood> yes.
17:24:25 <tinwood> #topic High Priority Bugs
17:24:49 <jamespage> https://bugs.launchpad.net/charms/+source/ceph/+bug/1424771
17:24:50 <openstack> Launchpad bug 1424771 in nova-compute (Juju Charms Collection) "Excessive caps for CephX users glance, cinder, nova-compute" [Medium,Triaged]
17:25:13 <tinwood> Also maybe: https://launchpad.net/openstack-charms
17:25:29 <jamespage> cholchombe has the acl part of that inflight; icey and I landed some supporting changes today to restrict things better
17:25:55 <jamespage> just raising as needs focus asap - sensing frustration from original reporter and it is a security concern
17:26:24 <tinwood> ok
17:26:30 <wolsen> jamespage: from inflight, is there a review pending?
17:26:53 <jamespage> wolsen, not at the moment - the original acl design proposed has some awkward limitations
17:26:59 <wolsen> ack
17:27:11 <tinwood> (for the minutes) there are 26 outstanding bugs with 2 marked as critical.
17:27:14 <jamespage> wolsen, cholchombe and I have one that works, but it needs re-implemening
17:27:31 <wolsen> jamespage: I look forward to seeing the new version :-)
17:27:43 <jamespage> tinwood, ack - keep focussed on bugs all
17:27:50 <jamespage> maybe we should have another bug day?
17:27:57 <gnuoy> +lots
17:27:58 <tinwood> I like bug days
17:28:03 <thedac> yes
17:28:10 <jamespage> I think one or two a month would be good
17:28:13 <gnuoy> I think I'm going to don my bug trousers at ODS
17:28:23 * tinwood gasp
17:28:26 <jamespage> tinwood, can you action me with that
17:28:35 <jamespage> ok we're tight on time
17:28:47 <jamespage> tinwood, what's left on the agenda
17:28:49 <tinwood> #action jamespage allocate days in month for bug squashing.
17:28:49 <jamespage> ?
17:28:58 <tinwood> #topic Openstack Events
17:29:03 <gnuoy> ODS!
17:29:16 <jamespage> indeed next week be there
17:29:18 <jamespage> \o/
17:29:23 <jamespage> (if you can)
17:29:35 <tinwood> okay and finally
17:29:44 <tinwood> #topic Open Discussion
17:29:51 <tinwood> cargonza, review queue?
17:30:19 <cargonza> ignore tinwood..
17:30:25 <cargonza> I was corrected already
17:30:29 <tinwood> thanks everybody
17:30:32 <thedac> :)
17:30:33 <cargonza> please and thank you
17:30:38 <jamespage> thanks tinwood
17:30:41 <tinwood> #endmeeting