20:00:41 <mattgriffin> #startmeeting ha-guide
20:00:42 <openstack> Meeting started Thu Jul 30 20:00:41 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:46 <openstack> The meeting name has been set to 'ha_guide'
20:00:53 <mattgriffin> hi megm
20:01:01 <mattgriffin> anyone else here for the HA Guide meeting?
20:01:12 <megm> Hi, Matt!
20:01:30 <mattgriffin> here's the agenda:
20:01:32 <mattgriffin> #link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting
20:02:00 <mattgriffin> just a quick update on things today and then any other items to discuss
20:02:25 <mattgriffin> megm, how are you?
20:02:39 <megm> Hanging in there -- how are you?
20:03:11 <mattgriffin> megm, lots of meetings today. looking forward to actually doing some work... eventually
20:03:15 <mattgriffin> :)
20:03:23 <megm> Good luck with that ;-)
20:03:30 <mattgriffin> hehe
20:04:02 <megm> I just started reading the ha-guide as it is...  An interesting endeavor...
20:04:24 <mattgriffin> yeah. i was going to start doing that as well
20:04:41 <mattgriffin> one of the action items from last week was to "look into how to call out bugs for the HA Guide sections"
20:05:00 <mattgriffin> so i made a note at https://docs.google.com/spreadsheets/d/17EApMTVzCgddR62ZYJC4qAs9imdZWDcSy81UNEae8WY/edit#gid=0
20:05:23 <mattgriffin> basically i propose that all reviewers of the draft HA Guide that are filing bugs should tag their issue with ha-guide
20:05:34 <megm> Do we need to file a bug for each CR now?  Andrew B asked me and I admit that I hadn't thought about that...
20:06:15 <mattgriffin> yeah. for everyone in column E i think that's the best way to do it
20:06:28 <megm> +1 -- then we can search for ha-guide and get the current list.
20:06:30 <mattgriffin> s/everyone/everything
20:06:36 <mattgriffin> megm, aye
20:07:00 <mattgriffin> all issues go into the openstack-manuals LP project so we need a way to easily filter
20:07:17 <mattgriffin> cool
20:07:24 <megm> Who can triage these bugs then?
20:07:37 <mattgriffin> i can keep a look out for them
20:07:57 <megm> We need to keep this process moving, I think, so that people who come on to help don't get discouraged.
20:08:14 <mattgriffin> i was going to email a bunch of the contributors to the various openstack services and ask them to review the content that most applies to them
20:08:19 <megm> Do you know when/if clouddon will be back with us?
20:08:37 <mattgriffin> i do not. i'll try to ping him
20:08:46 <mattgriffin> #action mattgriffin find clouddon
20:09:01 <megm> Are you getting responses from them?  I tried putting them on the reviewer list and sending emai for a couple of the pieces and got bupkas
20:09:17 <mattgriffin> i haven't sent any yet
20:09:19 <megm> It may have gotten lost in the noise, of course.
20:09:55 <megm> Perhaps a formal request will help us get on their respective radars.
20:10:04 <mattgriffin> med_, responded to the swift one. thanks med_ !!!
20:10:30 <mattgriffin> give ya' a shoutout
20:11:17 <megm> It seems that Pacemaker is in good hands -- I touched base with Radek (who has been busy with other things but still plans to work on this).
20:11:22 <mattgriffin> so i'll take that as an action item... email a bunch of contributors and try to get some reviews going for the draft guide and bug filing
20:11:37 <megm> He says that Andrew B who joined us last week is a big contributor to Pacemaker so he's thrilled to have his involvement.
20:11:42 <mattgriffin> #action mattgriffin email a bunch of contributors and try to get some reviews going for the draft guide and bug filing
20:12:01 <mattgriffin> megm, cool
20:12:13 <megm> I wonder if we should consider holding this meeting at an "eastern hemisphere" hour every other week.
20:13:08 <mattgriffin> that's a good idea
20:13:21 <megm> Once we have bugs, how do we get people to contribute some content?
20:13:47 <mattgriffin> megm, ideally the person who filed the bug would either provide the content or advise
20:13:53 <megm> Some may just put the info we need into the bug so I can grab it and write it up.
20:14:04 <mattgriffin> if needed we can add their content on their behalf
20:14:11 <mattgriffin> yup yup
20:14:11 <megm> That will be terrific if it works.
20:14:33 <megm> You'll be explaining all this in the mail you send out, correct?
20:14:39 <mattgriffin> yeah
20:14:46 <mattgriffin> i'll cc you on all messages
20:14:57 <megm> Any luck with Percona people and the MySQL piece?
20:15:30 <mattgriffin> not yet. need to ping them again
20:15:37 <mattgriffin> might have to find another source
20:15:43 <med_> Oh, ha-guide time is now?
20:15:48 * med_ thought it was at 8am this morning
20:15:53 <med_> no wonder I haven't been seeing them.
20:15:55 <mattgriffin> med_, :)
20:16:08 <med_> every week or two weeks?
20:16:41 <mattgriffin> med_, every week
20:16:47 <med_> adding
20:16:57 <mattgriffin> but only 30 min (hopefully)
20:17:40 <mattgriffin> ok. back to Percona... i'll contact some old consulting colleagues directly as well as ping their boss (again)
20:19:06 <megm> Have you spoken to nchase lately?  Mirantis has some good MySQL people, too, at least for the basics.
20:19:50 <megm> med_, you represent Swift?
20:19:51 <mattgriffin> i haven't. i'll try him too
20:20:27 <megm> I see that his boss has a new job, not at Mirantis...  May be some upheaval...
20:21:17 <mattgriffin> interesting
20:21:33 <mattgriffin> ok. need to run soon....
20:21:42 <megm> Is _med still here?
20:21:48 <mattgriffin> i have a couple of action items and need to track down a few people
20:22:05 <megm> Sounds good.  I guess I should read and file bugs.
20:22:08 <mattgriffin> and we should start to read/review the HA Guide draft from beginning to end and file bugs
20:22:12 <mattgriffin> hehe... yes
20:22:44 <megm> It seems that the NEXT/PREVIOUS buttons have disappeared...  Really hard to read this thing!
20:24:25 <megm> I think a new CSS is being released soon -- it sounds like it may have better navagation.
20:24:36 <med_> megm, erm, no.
20:24:46 * med_ is here
20:24:54 <med_> (called away IRL briefly)
20:25:05 <megm> med_, excellent!
20:25:18 <megm> So you represent swift?
20:25:29 <med_> megm, not in the slightest.
20:25:51 <med_> I work for Time Warner Cable. Ie, I'm an operator with a lot of openstack background
20:26:01 * med_ has 4.5 years of openstack now
20:26:08 <megm> Ah, very cool!
20:26:10 <med_> maybe 4.3
20:26:21 <megm> Wow -- 4.5 years!
20:26:22 <med_> I'm sure that's not helpful, but it is accurate.
20:26:42 <megm> ;-)  .2 of a year can be significant...
20:27:25 <med_> mattgriffin, do you have a roll call setup for this meeting. If I can be added that would be helpful. I have pulled in the ICS.
20:27:31 <med_> (which is also helpful)
20:27:38 <megm> Are you a writer and comfortable with RST?  If not, I am here to serve as your scribe if you can contribute content.
20:27:52 <mattgriffin> med_, i do not. where can i find docs to set that up?
20:28:19 <mattgriffin> med_, er... i'll look into setting it up :)
20:28:19 <med_> in the nova meetings, they just have a list on the wiki you can edit to be notified at meeting start time.
20:28:30 <mattgriffin> ah cool.
20:28:31 <med_> It' just a list of nics anyone can paste into the channel
20:28:56 <megm> Very cool!
20:29:02 <mattgriffin> #action mattgriffin set up a roll call (like those guys on nova) and include med_
20:29:05 <med_> hmm, the ICS I just added for this meeting has set it at 3pm
20:29:18 <med_> per the eavesdrop listing
20:29:23 <med_> so maybe the eavesdrop listing needs an update
20:30:43 <med_> http://eavesdrop.openstack.org/#Documentation_HA_Guide_update_Meeting
20:30:53 <med_> so is it at 2100 UTC or is it at some other time?
20:31:04 <med_> dmbp:~ dmedberry$ TZ=UTC date
20:31:04 <med_> Thu Jul 30 20:30:57 UTC 2015
20:31:19 <med_> the meeting appears to be starting in 30 minutes mattgriffin
20:32:06 <mattgriffin> hmm...
20:32:22 <megm> Ah, that's the old time.  when we went to DST, this time slot was hard for people so we moved it.
20:32:40 <mattgriffin> need to update
20:34:27 <med_> the infra project needs an update then
20:35:15 <med_> i cna update it
20:36:23 <mattgriffin> med_, thanks!
20:37:16 <med_> https://review.openstack.org/207614
20:37:27 <med_> feel free to add yoursleves as reviewer and look at it.
20:38:42 <mattgriffin> cool
20:40:31 * med_ is kind of amazed he hadn't been cluebatted about this months ago
20:40:55 <med_> megm, did you have anymore questions for me? I think this room is idle until top of the hour
20:41:15 <med_> or until mattgriffin does a closemeeting action...
20:41:21 <mattgriffin> :)
20:41:28 <megm> Nothing specific unless you want to work on something in real time ;-)
20:41:47 <med_> i've got minutes right now... I'm not an RST guy as you've clearly picked up on.
20:42:02 <med_> and I've got nothing that needs to go into ha-guide at the moment either.
20:42:28 <megm> I had not picked up that you are not an RST guy.
20:42:47 <megm> Ah, if you don't have changes, then you must not have read the draft ;-)
20:42:59 <med_> I would appreciate someone looking at:
20:43:00 <med_> https://review.openstack.org/#/c/206261/
20:43:24 * med_ doesn't have a draft horse, a draft beer, nor a cool breeze, so apparently not
20:43:55 <med_> I see three in process ha-guide reviews and I've looked at all of those but not any "draft" so to speak.
20:44:22 <megm> http://docs.openstack.org/draft/ha-guide/
20:44:33 <med_> cool I'll review
20:44:42 * med_ wonders wehre the text/code is...
20:44:57 <med_> I'll have comments later then @megm.
20:45:02 <megm> Ah, you you made some updates to the docbooks cinder section.
20:45:17 <med_> That I did do.
20:45:22 <megm> Where are you for getting that merged?  I will pick up these changes and add them to the RST version.
20:45:24 * med_ knows much more about cinder than about Swift
20:45:29 <med_> and much more about Nova than about Swift
20:46:04 <megm> ;-)
20:46:21 <megm> I suspect you know more about almost all the OpenStack components than I do!
20:46:28 <med_> I really don't see the "draft" git repo
20:46:44 <med_> not sure where that is. If you can point me at it megm, I'd be forever grateful.
20:47:14 <megm> Ah, the git repo is not "draft" -- that is coming from Jenkins.
20:47:32 <med_> gotcha
20:47:46 <med_> so I have the main repo for ha-guid, cinder, security-doc, nova, etc.
20:48:00 <med_> and I've made changes in most of those and proposed in another.
20:48:07 <megm> The git repo is the same one as the docbook repo -- the docbook source is under high-availability and the new RST guide is under ha-guide
20:49:13 <megm> Could you email me the CR numbers for all those?  DreidelLhasa@yahoo.com or meg.mcroberts@yahoo.com
20:51:02 <megm> It looks like your changes, at least in the CR I'm looking at, are related to new components.  Do you know which OpenStack release first supports this stuff?
20:52:13 <megm> Matt, what is our plan?  Changes that affect Juno and earlier can go into the docbook version?  Anything that is for Liberty and forward only should only go into the RST version?
20:52:22 <med_> the one I referenced above (with the added Py3 line) is as of Kilo. The older way (original mysql://) is since the beginning of time.
20:52:50 <med_> and so I've been told any changes I make, make to both the xml and the RST
20:53:10 <med_> I've done no changes that are "Liberty" changes.
20:53:20 <megm> Sounds like a plan.  Except, if you like, I can do the RST pieces.
20:53:41 <megm> Good -- that's what I wanted to check.  It sounds like you are on top of thigs.
20:53:44 <med_> I just hate using and seeing out of date documentation (or worse, so out of date it's just plain wrong.)
20:53:48 <med_> coolio.
20:54:06 <mattgriffin> sorry.. had to step away.
20:54:09 * mattgriffin is back
20:54:24 <megm> Oh, me too!  What I really prefer is documentation that specifies the release when something is added.
20:54:30 <mattgriffin> y'all all good
20:54:32 <mattgriffin> ?
20:54:39 <mattgriffin> ^ that's some Texan
20:54:45 <megm> That way, it's clear, even if the maintenance process falls apart.
20:55:22 <megm> So perhaps this doc should say, "Alternatively, for Kilo and later releases, you can switch to pymysql...."
20:56:17 <megm> matt, are you a native Texan?
20:56:26 <mattgriffin> yes sir
20:56:40 <megm> Cool!
20:57:18 <mattgriffin> ok. nearing the top of the hour. cool to endmeeting?
20:57:47 <megm> med_, are we agreed that I'll do the RST for your docbook modifications?  I'll make you a reviewer, of course?
20:58:01 <med_> uh, that's fine. Not necessary, but fine.
20:58:03 <megm> You have my email?  Write to me and then matt can end this meeting...
20:58:11 <med_> go for it, endmeet
20:58:22 <megm> med_, it's up to you-- I'm just trying to be helpful ;-)
20:58:54 <megm> Have a great week, everyone!
21:01:00 <mattgriffin> Thanks!
21:01:02 <mattgriffin> #endmeeting