17:01:53 <thedac> #startmeeting charms
17:01:54 <openstack> Meeting started Mon May 15 17:01:53 2017 UTC and is due to finish in 60 minutes.  The chair is thedac. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:57 <openstack> The meeting name has been set to 'charms'
17:02:16 <thedac> #topic
17:02:22 <thedac> #topic Review ACTION points from previous meeting
17:02:41 <thedac> Not sure if Dmitrii-Sh is here but he had: "
17:02:43 <thedac> Dmitrii-Sh track the network-binding not being able to be changed after deploy/add-unit."
17:02:56 <thedac> Anyone with an update for that?
17:03:08 <coreycb> o/
17:03:35 <thedac> ok, moving on
17:03:38 <thedac> #topic State of Development for next Charm Release
17:03:50 <thedac> tinwood: any update on next Ubuntu release will be an 'a' (coming after z) -- still landing the alpha comparison changes to the charms.
17:03:58 <thedac> How many are left?
17:04:07 <tinwood> thedac, so ...
17:04:15 <tinwood> all of the non-reactive charms are done.
17:04:30 <tinwood> ... and charms.openstack is done.
17:04:37 <jamespage> o/
17:04:40 <tinwood> ... so in theory, all of the reactive charms are done too!
17:04:46 <jamespage> sorry I'm late
17:04:47 <thedac> So we just need rebuilds of the reactive charms?
17:04:51 <thedac> hey, jamespage
17:05:17 <tinwood> thedac, yup.  I've checked them all, and they don't do anything weird, so they should be okay.
17:05:33 <tinwood> I figured they would be picked up with any new changes./
17:05:39 <thedac> Great so we can remove that one from the list
17:05:45 <thedac> I have 3 remaining zesty amulet changes to go that have unique snoflake issues: https://review.openstack.org/#/q/topic:zesty-ocata+is:open
17:05:51 <wolsen> o/
17:06:02 <thedac> Hi wolsen
17:06:11 <wolsen> hi thedac, apologies for the tardiness
17:06:15 <thedac> wolsen: want to give us an update on the DNS progress?
17:06:15 <tinwood> the 'a' is 'artful' AFAIK
17:06:23 <jamespage> it is
17:07:19 <wolsen> thedac: the code has been tested and there are several reviews ready for input - https://review.openstack.org/#/q/topic:charms-internal-dns
17:07:33 <thedac> great, thank you
17:07:36 <wolsen> todo are still mojo specs and amulet tests
17:08:05 <thedac> The other point for state of development is our focus on getting snap deployed openstack into the charms
17:08:19 <thedac> Any other updates for State of development?
17:08:45 <jamespage> prob worth updating on specs
17:09:08 <jamespage> we don't currently have anyone working on the openstack loadbalancer implementation
17:09:26 <wolsen> boy that sure would be a great feature to have as well
17:09:50 <jamespage> wolsen: yeah - kinda the problem here - its all high, higher, highest :-)
17:09:57 <wolsen> jamespage: I'm aware :)
17:10:01 <jamespage> lol
17:10:18 <tinwood> (got to give the cat a tablet - back in 2 mins)
17:10:23 <thedac> ok moving onto bugs
17:10:26 <thedac> #topic High Priority Bugs
17:10:34 <thedac> #link https://bugs.launchpad.net/openstack-charms/+bugs
17:10:42 <thedac> Any particular bugs to highlight?
17:11:13 <wolsen> I'm ill prepared to list the specific ones, but I know there's a couple that are key for some stable backports
17:11:58 * tinwood is back
17:12:21 <thedac> jamespages has prepeared a tag for backports http://tinyurl.com/charm-stable-backports
17:12:27 <thedac> jamespage even
17:12:48 <thedac> wolsen: pleas add any bugs you are aware of with that tag
17:12:53 <wolsen> yes, will visit bugs and apply them appropriately
17:13:07 <jamespage> yes - as we're going to release a little less frequently, please tag anything targetted for stable-backport with the tag of the same name
17:13:33 <thedac> Moving on
17:13:40 <thedac> #topic OpenStack Events
17:13:46 <thedac> Any events on the horizon?
17:14:15 <tinwood> Is there going to be a PTG?
17:14:41 <thedac> Yes, in September if I am not mistaken
17:15:26 <thedac> no info on the web page that I can find
17:15:36 <thedac> Other events?
17:15:48 <thedac> ...
17:15:57 <thedac> Ok moving on
17:15:59 <thedac> #topic Open Discussion
17:16:07 <thedac> The floor is open
17:16:21 <tinwood> moving mocks: may I?
17:16:44 <thedac> +1 to optimizing mocks
17:16:48 <wolsen> +1
17:16:55 <tinwood> So, I'd like to move mocks from reactive charm's unit_tests/__init__.py to charms.reactive to centralise them
17:17:38 <wolsen> so the mock is moved away from the actual test?
17:17:40 <tinwood> Which means 'testy code' in the library (but there's already test code in the published library)
17:18:03 <tinwood> wolsen, you'd still have to import them, (probably in the __init__.py)
17:18:23 <tinwood> ... but updates to them could be central for code in charms.openstack that rely on charmhelpers.
17:18:41 <tinwood> And the example is ch.c.o.u.OPENSTACK_RELEASES
17:19:03 <tinwood> which is going to break every reactive charm's unit tests (I've just discovered) that relies on charms.openstack
17:19:15 * tinwood is sorry
17:19:17 <thedac> :)
17:19:20 <wolsen> yeah, I see where the advantages are in doing that
17:19:43 <wolsen> tinwood: you can make it up to all of us with videos of your cat playing on the ipad
17:19:55 <tinwood> :)
17:20:08 <tinwood> I'll raise a bug on the reactive charms I know about, and then get them fixed.
17:20:17 <thedac> Any other open discussion items? non-cat related ;)
17:20:19 <tinwood> assuming we are okay with it.
17:21:04 <wolsen> so question on the designate charm
17:21:12 <wolsen> (maybe this is wrong forum)
17:21:20 <wolsen> but was it intention to not relate to neutron-api?
17:21:51 <thedac> Good question. gnuoy is not here to answer.
17:21:53 <wolsen> I can take over to #openstack-charms if prepared
17:21:58 <wolsen> err if preferred*
17:22:09 <thedac> Yeah, let's have that discussion there
17:22:12 <wolsen> ok
17:22:26 <thedac> Last call for open discussion items?
17:22:41 <tinwood> Not from me
17:22:45 <wolsen> none here
17:22:50 <thedac> ok
17:22:53 <thedac> #topic Next Chair
17:23:06 <thedac> Etherpad says jamespage is up next
17:23:40 <thedac> #endmeeting