17:03:01 <gnuoy> #startmeeting charms
17:03:01 <openstack> Meeting started Mon Oct 31 17:03:01 2016 UTC and is due to finish in 60 minutes.  The chair is gnuoy. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:03:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:03:04 <openstack> The meeting name has been set to 'charms'
17:03:22 <gnuoy> I'm guessing beisner and jamespage aren't here ?
17:03:36 <beisner> o/
17:03:41 <gnuoy> \o
17:04:05 <gnuoy> From last time : ACTION: beisner regular upgrade tests
17:04:17 <gnuoy> should I carry that forward?
17:04:44 <gnuoy> #topic Review ACTION points from previous meeting
17:04:50 <beisner> we have charm upgrade mojo specs running daily, and openstack package upgrade mojo specs running at the same frequency
17:05:29 <gnuoy> was that action supposed to cover multi release upgrades as well or not?
17:05:39 <gnuoy> L-M->N
17:05:43 <beisner> gnuoy, i'm lost in the context of that action though.  was that for the multi-upgrade path?  ie. i -> j -> k -> l -> m -> n
17:05:48 <gnuoy> haha
17:05:55 <gnuoy> not sure, let me check
17:06:48 <gnuoy> beisner, err I don't see it in the previous meeting summary tb h
17:06:53 <gnuoy> lets move on
17:07:06 <beisner> ok, let's call it multi-step upgrade and carry that forward
17:07:17 <gnuoy> ack
17:07:29 <gnuoy> #action beisner mutli-step upgrades
17:07:40 <gnuoy> #topic State of Development for next Charm Release
17:07:49 <gnuoy> tinwood, hows the manilla charm?
17:08:34 <tinwood> getting very close now.  Now handling multiple conversations in the interface, and needing to write tests, but it was basically working until I split it up.
17:08:54 <gnuoy> tinwood, kk, theres a cephfs charm too right?
17:09:15 <tinwood> gnuoy, wrt to manila, no, but now very easy to add one.
17:09:25 <gnuoy> kk
17:09:28 <tinwood> or as a separate cephfs charm?
17:09:46 <gnuoy> I think there is a seperate cephfs charm but I may be making that up
17:10:03 <tinwood> We need to check with the storage charm folks.
17:10:14 <tinwood> I'll take an action if you'd like?
17:10:37 <gnuoy> #action tinwood update at the next meeting wrt manilla and cephfs charms
17:10:41 <gnuoy> tinwood, thanks
17:10:48 <tinwood> np
17:11:29 <gnuoy> Theres been some requests for openstack dashboard integration which I'll try and take a look soon
17:11:56 <gnuoy> anything else anyone wants to point at for 17.01 ?
17:12:14 <gnuoy> ...
17:12:20 <gnuoy> #topic High Priority Bugs
17:12:40 <gnuoy> So, I think rabbit + DNS has raised its head again
17:12:49 <gnuoy> I mean: Rabbit - ~DNS
17:13:36 <gnuoy> https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1584902
17:13:37 <openstack> Launchpad bug 1584902 in rabbitmq-server (Juju Charms Collection) "Setting RabbitMQ NODENAME to non-FQDN breaks on MaaS 2.0" [High,New] - Assigned to James Page (james-page)
17:13:41 <gnuoy> I think
17:13:49 <gnuoy> anything else?
17:14:37 <gnuoy> ok then
17:14:41 <gnuoy> #topic Openstack Events
17:14:51 <gnuoy> Well ODS was just a thing
17:15:14 <tinwood> How was it
17:15:19 <gnuoy> good thanks
17:15:36 <gnuoy> the fishbowls and working session on the friday were really good
17:16:07 <gnuoy> thedac and I are going to work up a spec for the single API haproxy solution
17:16:30 <tinwood> sounds good.
17:16:56 <gnuoy> #action gnuoy Loadbalancer spec
17:17:30 <beisner> food for thought: i believe rmq can now cluster with nodenames being IP address, if we stop using sname (ie. use long name).  i'd like to see us try that.  ultimately, until we get consistent dns records from the underlying tooling, i think anything we do will be brittle.
17:17:39 <gnuoy> I'm going to plough on unless anyone has anything else for events?
17:17:47 <gnuoy> #topic Open Discussion
17:17:48 <tinwood> nope, I'm good.
17:18:36 <gnuoy> Anything to openly discuss?
17:18:53 <gnuoy> ...
17:19:00 <tinwood> no, I'm good.
17:19:28 <gnuoy> Ok, next meeting is two weeks time same time (17:00 UTC) and thedac is chairing!
17:19:31 <gnuoy> #endmeeting