21:32:42 <ShillaSaebi> #startmeeting arch-ops-guide 21:32:42 <openstack> Meeting started Thu Jun 2 21:32:42 2016 UTC and is due to finish in 60 minutes. The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:32:42 <njohnston> #endmeeting 21:32:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:32:45 <openstack> The meeting name has been set to 'arch_ops_guide' 21:32:53 <ShillaSaebi> hello all 21:33:00 <njohnston> oh good, glad that worked, since the last meeting had not ended properly 21:33:06 <ShillaSaebi> can we get a roll call for the ops/arch guide meeting: 21:33:10 <ShillaSaebi> oh good! 21:33:22 <njohnston> o/ 21:33:34 <darrenc> do you need to end it first? 21:33:39 <darrenc> o/ 21:33:43 <ShillaSaebi> i think were ok 21:34:00 <darrenc> cool 21:34:11 <ShillaSaebi> so just the 3 of us aye? 21:34:25 <darrenc> I guess so :) 21:34:27 <ShillaSaebi> ok 21:34:32 <ShillaSaebi> well lets go ahead and get started 21:34:40 <ShillaSaebi> #topic Ops Guide 21:34:40 <darrenc> I think Shaun is moving countries 21:34:47 <ShillaSaebi> oh wow really 21:35:03 <darrenc> South Africa -> Germany 21:35:26 <ShillaSaebi> oh right i remember he said he was going to Germany 21:35:49 <ShillaSaebi> So we still need more people to find and look for content that needs to be updated #link https://etherpad.openstack.org/p/ops-guide-reorg 21:36:14 <darrenc> yeah so far it's just be me and tom 21:36:21 <darrenc> been* 21:36:47 <darrenc> I'm thinking of pushing up a patch with those changes 21:37:01 <darrenc> and hopefully that will get some response 21:37:18 <ShillaSaebi> ok 21:37:36 <darrenc> but yeah, some ops ppl to pick a chapter or section and review it would be great 21:37:55 <ShillaSaebi> Devon and Vic are interested in working on this too 21:38:00 <ShillaSaebi> Devon may be joining us later today 21:38:09 <ShillaSaebi> I can poke them tomorrow 21:38:13 <njohnston> Vic sends his regrets, but is at a doctor's appointment 21:38:33 <darrenc> that would be great, thanks 21:40:27 <ShillaSaebi> ok 21:40:44 <darrenc> so any thoughts on getting more ops ppl to help? 21:40:55 <ShillaSaebi> i think maybe start joining their meetings 21:40:58 <ShillaSaebi> we've tried ML 21:41:12 <ShillaSaebi> we've tried other methods that didn't seem to make much traction 21:41:20 <njohnston> perhaps talking about docs in meetings like the ansible and puppet meetings 21:41:29 <darrenc> mailing lists only seems good for informing 21:41:33 <njohnston> those are very ops-dominated 21:42:12 <ShillaSaebi> thats a good idea 21:42:15 <njohnston> "Hey you're working on a puppet module update to configure haproxy, would you mind also checking the ops guide chapter XX to make sure it's up to date?" 21:42:24 <ShillaSaebi> thats a great idea 21:42:38 <darrenc> +1 21:42:46 <katomo> +1 21:42:51 <ShillaSaebi> hi katomo 21:43:07 <katomo> hi ShillaSaebi 21:43:21 <darrenc> Need to checking ops meeting times, but I think they are held when I'm asleep 21:44:16 <ShillaSaebi> i wonder if there is an APAC one? 21:44:37 <darrenc> Perhap we can coordinate as a team who will go to what meeting 21:45:34 <ShillaSaebi> that works 21:45:45 <ShillaSaebi> does someone want to maybe gather the list of meetings first that are ops centric 21:45:48 <njohnston> +1 coordination 21:45:54 <ShillaSaebi> then we can look at the times and see who can go to what 21:46:38 <darrenc> I can do it 21:46:41 <njohnston> perhaps that can be collated and arranged via email 21:46:52 <darrenc> Yep, I'll send out an email 21:46:52 <ShillaSaebi> yeah email works 21:47:15 <ShillaSaebi> ok next thing 21:47:20 <ShillaSaebi> Sourcing enterprise ops documentation 21:47:27 <ShillaSaebi> so we have a wiki filled with docs 21:47:32 <ShillaSaebi> not really cleaned up 21:47:52 <ShillaSaebi> i can dump them somewhere as long as we don't put them up as official docs or anything. We need to really revise them and clean them up before putting them anywhere 21:48:37 <darrenc> I assume it has enterprise specific information in it? 21:49:13 <njohnston> be sure to look at wiki docs with the coming reorganization in mind: http://lists.openstack.org/pipermail/openstack-dev/2016-June/096481.html 21:51:58 <ShillaSaebi> ok 21:52:05 <ShillaSaebi> yeah enterprise specific info 21:52:11 <ShillaSaebi> but we can clean that up 21:52:16 <darrenc> I'm ok with it being dumped somewhere secure as long there is not company sensitive information in it 21:52:23 <darrenc> no* 21:52:31 <ShillaSaebi> ok 21:52:38 <ShillaSaebi> i can do google docs or something 21:52:41 <ShillaSaebi> ill work on that tomorrow 21:52:47 <darrenc> especially if there are other team members from other companies 21:53:02 <darrenc> *cough* 21:53:17 <darrenc> :) 21:53:19 <katomo> good 21:53:22 <ShillaSaebi> ok :D 21:53:26 <ShillaSaebi> yeah sounds good to me 21:53:41 <darrenc> thanks, that would be great 21:53:42 <ShillaSaebi> ok next thing to bring up 21:53:45 <ShillaSaebi> Revise Ops Guide spec with proposed content structure? 21:55:09 <ShillaSaebi> i think we already pretty much touched on this 21:55:15 <ShillaSaebi> with the new content structure that needs to be worked on 21:55:53 <darrenc> Well I think the earlier point is removing old content 21:56:56 <darrenc> after that, looking at the content structure with the arch guide in mind 21:57:16 <darrenc> so atm, I'm migrating the arch content in the ops guide to the arch guide 21:58:09 <darrenc> so content in each guide is segregated by what you want to do, rather than persona 21:59:06 <darrenc> arch guide -> design a cloud 21:59:21 <ShillaSaebi> right 21:59:23 <darrenc> ops guide -> deployment, maintain and trouble 21:59:28 <ShillaSaebi> and operate 21:59:29 <ShillaSaebi> :D 21:59:34 <darrenc> yep 21:59:35 <katomo> sounds reasonable to me 21:59:38 <ShillaSaebi> makes sense 21:59:54 <darrenc> troubleshoot* 22:01:58 <ShillaSaebi> ok 22:02:06 <ShillaSaebi> #topic Arch Guide 22:02:13 <ShillaSaebi> Work items wiki page #link https://wiki.openstack.org/wiki/Architecture_Design_Guide_restructure_work_items 22:02:49 <ShillaSaebi> for this section: migrate #link http://docs.openstack.org/ops-guide/architecture.htm content to the Arch Guide under the relevant sections 22:02:57 <ShillaSaebi> the link should be updated 22:03:10 <darrenc> ok, that was me 22:03:34 <darrenc> I've asked shaun to help populate the wiki page 22:03:39 <ShillaSaebi> great! 22:03:45 <ShillaSaebi> lgtm 22:04:14 <darrenc> and I'll some things to migrate the mitaka arch guide content as well 22:04:28 <darrenc> so some help with migration would be appreciated 22:04:58 <ShillaSaebi> noted 22:05:06 <darrenc> So I'm done one patch already https://review.openstack.org/#/c/324179/ 22:05:38 <ShillaSaebi> awesome! 22:05:40 <darrenc> I've* 22:05:49 <katomo> G! 22:06:00 <darrenc> progress! :P 22:07:26 <ShillaSaebi> nice thank you darrenc 22:07:44 <ShillaSaebi> ok lets move along 22:07:46 <ShillaSaebi> #topic Open discussion 22:08:00 <ShillaSaebi> volunteers volunteers volunteers! 22:08:14 <katomo> yeah! 22:08:32 <ShillaSaebi> So we need volunteers to attend ops meetings and volunteers to identify outdated content or content to be removed #https://etherpad.openstack.org/p/ops-guide-reorg 22:08:39 <ShillaSaebi> are there any other topics anyone wants to bring up 22:10:14 <katomo> nothing from me 22:10:30 <darrenc> oh, anyone hear anything about the ops midcycle? 22:11:05 <ShillaSaebi> Seattle? 22:11:09 <ShillaSaebi> I think 22:11:15 <darrenc> oh really? 22:11:18 <darrenc> when? 22:11:24 <ShillaSaebi> I think so but Im not 100% sure yet 22:11:30 <ShillaSaebi> not sure of the date either 22:11:38 <ShillaSaebi> theres a planning meeting though that goes on 22:11:43 <ShillaSaebi> we could probably eavesdrop it 22:12:29 <darrenc> ok cool 22:13:28 <darrenc> sorry, coming back to the arch guide 22:13:44 <ShillaSaebi> sure 22:14:09 <darrenc> once we have some work item to do, it might be useful to coordinate a chunk of time to focus on it 22:14:24 <darrenc> shaun suggested a series of one day sprints 22:14:25 <ShillaSaebi> ok 22:14:45 <katomo> good 22:14:49 <ShillaSaebi> yeah would rather see one day than 2-3 day allocations 22:14:57 <ShillaSaebi> i think it would work better that way 22:15:04 <ShillaSaebi> agreed 22:15:05 <darrenc> which I thought is easier than a 2-3 day sprint 22:15:10 <darrenc> snap 22:15:10 <ShillaSaebi> true eys 22:15:12 <ShillaSaebi> yes* 22:15:13 <ShillaSaebi> hah 22:15:24 <ShillaSaebi> oh as far as the ops mid cycle goes: the next meeting is on: ==> Tuesday, 14 of Jun at 1400 UTC[1] in #openstack-operators 22:15:31 <ShillaSaebi> for the planning 22:15:40 <ShillaSaebi> in case :) 22:15:55 <darrenc> ah ok 22:16:01 <darrenc> thanks 22:16:03 <ShillaSaebi> yw 22:16:12 <ShillaSaebi> anything else anyone wants to bring up? 22:16:25 <darrenc> it would be great to have another ops guide working session at the midcycle 22:16:31 <ShillaSaebi> yes 22:16:39 <darrenc> like at the Design Summit but longer 22:16:46 <ShillaSaebi> yeah 22:16:57 <ShillaSaebi> we can plan around it once we know dates and location 22:16:58 <darrenc> 40 minutes wasn't a lot of time 22:17:10 <ShillaSaebi> Devon from our team, is also part of the team for the ops midcycle planning 22:17:28 <ShillaSaebi> Ill sync with her on when the actual event is so we can plan something 22:17:36 <darrenc> well the sooner it's planned, the greater the chance of international contributors attending 22:17:45 <ShillaSaebi> yep! 22:18:08 <darrenc> oh great, thanks! 22:18:22 <ShillaSaebi> ok awesome, anything else? 22:18:38 <darrenc> that's all from me 22:18:45 <ShillaSaebi> ok then! meeting adjourned 22:18:50 <ShillaSaebi> have a good one! 22:18:53 <ShillaSaebi> #endmeeting