21:31:46 <ShillaSaebi> #startmeeting ops_guide
21:31:46 <openstack> Meeting started Thu Jun 30 21:31:46 2016 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:31:47 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:31:50 <openstack> The meeting name has been set to 'ops_guide'
21:32:00 <ShillaSaebi> hello
21:32:08 <ShillaSaebi> roll call for ops/arch guide meeting?
21:32:23 <DevonBoatwright> I'm here!
21:32:29 <ShillaSaebi> hi DevonBoatwright
21:32:34 <DevonBoatwright> Hello!
21:32:45 <ShillaSaebi> anyone else here for the ops/arch guide meeting?
21:33:23 <ShillaSaebi> lets give it a few min
21:34:18 <DevonBoatwright> okie
21:36:55 <darrenc> hello
21:37:07 <DevonBoatwright> Hey darrenc!
21:37:17 <darrenc> sorry, I was caught up doing something else
21:37:21 <ShillaSaebi> hi darrenc
21:37:26 <ShillaSaebi> it looks like its just us 3
21:37:30 <darrenc> hiya
21:37:34 <ShillaSaebi> we were waiting to see if anyone else was joining
21:37:40 <ShillaSaebi> anyone else here for the ops/arch guide meeting?
21:37:42 <darrenc> ahh, ok
21:38:00 <ShillaSaebi> ok
21:38:10 <ShillaSaebi> well we can go ahead and get started
21:38:14 <katomo> hello
21:38:20 <ShillaSaebi> hi katomo!
21:38:22 <darrenc> hi katomo
21:38:25 <DevonBoatwright> Hello!
21:38:41 <ShillaSaebi> #topic action items from last meeting
21:38:53 <ShillaSaebi> Devon has an update, she joined an ops meeting. Vic won't be joining but she can update us on Vic as well
21:39:01 <ShillaSaebi> or tried to join an ops meeting
21:39:09 <ShillaSaebi> I'll let you expand on that DevonBoatwright
21:39:43 <DevonBoatwright> I emailed so people pretty much have the details but I joined the tag meeting but it never actually happened. Turned out they only met once a month (not every other week)
21:39:51 <DevonBoatwright> And then the once a month meetings had not been happening either
21:40:10 <DevonBoatwright> So I will keep an eye out to see if the meeting will happen again. They are trying to communicate and be better organized about meeting
21:40:28 <darrenc> thanks, good to know
21:40:56 <darrenc> I saw Victor's email about the ops meeting
21:41:08 <DevonBoatwright> Vic joined the.. oh, I can't remember the name TELCOM? Was that what it was called? He had one person who said they would join.. but I guess that person isn't here. Hopefully they will check in, or maybe email for more info.
21:41:21 <darrenc> yeah
21:41:53 <DevonBoatwright> I mean, we have his user name.. so we could catch him on irc sometime, right?
21:42:19 <darrenc> sure, we can reach out to him
21:42:51 <ShillaSaebi> great
21:42:53 <ShillaSaebi> thats a start!
21:42:56 <ShillaSaebi> thanks Devon
21:43:16 <DevonBoatwright> No problem. Wish I could have helped a bit more.
21:44:02 <darrenc> Update from me: I submitted some patches to remove irrelevant or duplicated content in the ops guide
21:44:25 <ShillaSaebi> awesome
21:44:30 <ShillaSaebi> do you happen to have the links handy
21:44:36 <darrenc> one sec
21:44:55 <ShillaSaebi> ok
21:46:13 <darrenc> https://review.openstack.org/#/c/331521/ and https://review.openstack.org/#/c/330918/
21:47:16 <ShillaSaebi> great thanks
21:47:19 <ShillaSaebi> we'll take a look
21:47:33 <ShillaSaebi> #topic Bug spotlights
21:47:41 <ShillaSaebi> so we are looking for volunteers for the bugs!
21:47:54 <darrenc> yep, ops guide related bugs
21:48:14 <ShillaSaebi> #link https://bugs.launchpad.net/openstack-manuals/+bug/1375623 - Mention files to backip for horizon/ceilometer/heat
21:48:14 <openstack> Launchpad bug 1375623 in openstack-manuals "Chapter 14. Backup and Recovery in OpenStack Operations Guide - missing: Horizon Celiometer Swift Heat " [Medium,Confirmed]
21:48:25 <ShillaSaebi> #link https://bugs.launchpad.net/openstack-manuals/+bug/1580424 - fix architecture diagram
21:48:26 <openstack> Launchpad bug 1580424 in openstack-manuals "error in OpenStack architecture picture" [Medium,Confirmed] - Assigned to Pallavi (pallavi-s)
21:48:32 <ShillaSaebi> #link https://bugs.launchpad.net/openstack-manuals/+bug/1457767 - Improve logging/monitoring content
21:48:32 <openstack> Launchpad bug 1457767 in openstack-manuals "Chapter 13. Logging and Monitoring in OpenStack Operations Guide" [Wishlist,Confirmed]
21:48:41 <ShillaSaebi> #link https://bugs.launchpad.net/openstack-manuals/+bug/1457770 - Improve logging/monitoring content
21:48:42 <openstack> Launchpad bug 1457770 in openstack-manuals "Chapter 13. Logging and Monitoring in OpenStack Operations Guide" [Wishlist,Confirmed]
21:48:50 <ShillaSaebi> #link https://bugs.launchpad.net/openstack-manuals/+bug/1457768 - Improve logging/monitoring content
21:48:51 <openstack> Launchpad bug 1457768 in openstack-manuals "Chapter 13. Logging and Monitoring in OpenStack Operations Guide" [Wishlist,Confirmed]
21:49:00 <ShillaSaebi> #link https://bugs.launchpad.net/openstack-manuals/+bug/1499114 - Networking troubleshooting tools
21:49:00 <openstack> Launchpad bug 1499114 in openstack-manuals "Document tools for Network Troubleshooting" [Undecided,Confirmed] - Assigned to Richard (csravelar)
21:49:18 <ShillaSaebi> so 2 of them are assigned
21:49:45 <darrenc> yeah, I contacted the assignees to see if they are still working on them
21:49:53 <ShillaSaebi> yeah just saw that
21:49:58 <ShillaSaebi> ok great
21:50:10 <darrenc> no response so far
21:50:11 <ShillaSaebi> DevonBoatwright we can look through these and see if theres anything we can help with
21:50:16 <darrenc> and I messaged them as well
21:50:22 <ShillaSaebi> awesome ok
21:50:28 <DevonBoatwright> Sounds like a plan to me ShillaSaebi
21:50:37 <ShillaSaebi> lets wait till the next meeting and if no response, maybe reassign
21:50:45 <darrenc> I can tackle the arch diagram but need to know what else needs changing
21:51:12 <darrenc> katomo: you mentioned in the bug there were other changes required?
21:51:18 <katomo> good
21:51:32 <darrenc> can you specify those changes?
21:52:11 <katomo> darrenc: Yeah, but I can't remember...
21:52:20 <katomo> I will write later.
21:52:31 <darrenc> no worries, thanks katomo :)
21:53:12 <ShillaSaebi> cool
21:53:24 <ShillaSaebi> #topic Enterprise ops documentation
21:53:26 <katomo> remove EC2 API... and so one :)
21:53:46 <darrenc> ok
21:54:12 <darrenc> So, did anyone take at look at the doc?
21:55:29 <darrenc> can I ask what is mcollective?
21:56:23 <darrenc> It's all through the doc
21:56:49 <ShillaSaebi> yeah its a framework for building orchestration on servers...
21:56:50 <darrenc> I think there is some good troubleshooting in there
21:57:01 <ShillaSaebi> yeah i would think we should take the troubleshooting out and use that for the guide
21:58:02 <ShillaSaebi> katomo i got your request for access to the google docs
21:58:09 <ShillaSaebi> ill approve it as soon as this meeting is over
21:58:30 <katomo> ShillaSaebi: thanks
21:58:42 <darrenc> The "Operationalizing OpenStack" process coule also be useful
21:58:53 <darrenc> s/coule/could
21:58:58 <darrenc> but make it more generic
22:00:10 <ShillaSaebi> ok
22:01:04 <darrenc> so next steps: work out where this content could go
22:01:40 <darrenc> We can edit the doc and make suggestions
22:01:49 <darrenc> and I can push up a patch with this infor
22:01:58 <darrenc> /infor/info
22:02:03 <ShillaSaebi> sounds good
22:02:12 <ShillaSaebi> yeah if we can find a home for it i can help push it up too
22:02:34 <darrenc> cool, thanks
22:02:35 <ShillaSaebi> and ill bring more docs too once were finished with this batch
22:02:38 <katomo> good
22:02:42 <darrenc> sounds good
22:02:47 <ShillaSaebi> :D
22:02:56 <ShillaSaebi> #topic Arch Guide
22:03:08 <ShillaSaebi> Work items wiki page #link https://wiki.openstack.org/wiki/Architecture_Design_Guide_restructure_work_items
22:04:04 <darrenc> Erm, so not much happening with the Arch Guide atm
22:04:42 <darrenc> Shaun will take a look at the Design chapter this week
22:05:18 <darrenc> but the reality is we need more people with technical knowledge on this project
22:05:51 <katomo> yeah
22:05:52 <ShillaSaebi> +1
22:06:06 <darrenc> I've reached out the new Architecture Working Group on the dev ML
22:06:18 <darrenc> to*
22:06:28 <DevonBoatwright> agreed
22:06:53 <darrenc> We're not going to get far with just docs ppl doing this
22:07:08 <ShillaSaebi> yeah agreed
22:07:33 <darrenc> anyway, it would be great if this working group can get involved or even take some ownership of it
22:07:40 <ShillaSaebi> well reaching out to the arch wg is a great start
22:07:56 <ShillaSaebi> hopefully youll get some feedback or an update soon
22:08:33 <katomo> +1
22:08:33 <darrenc> yeah, in the meantime I look at reworking mitaka changes in the new structure
22:09:50 <ShillaSaebi> awesome
22:09:55 <ShillaSaebi> cool anything else on this topic?
22:11:05 <ShillaSaebi> ok #topic open discussion
22:11:12 <ShillaSaebi> anything anyone would like to bring up?
22:11:24 <darrenc> yeah
22:11:41 <katomo> nothing from me
22:12:10 <darrenc> so I'm wondering how effective it is to restructure a guide over a whole release cycle
22:13:01 <darrenc> so we have planned to restructure the arch guide and potentially the ops guide this cycle
22:13:45 <ShillaSaebi> so do you think that it's something we should break apart into chunks
22:13:50 <darrenc> but not many people have bandwidth to contribute to that scale of work
22:13:56 <ShillaSaebi> agreed
22:14:04 <ShillaSaebi> maybe we can break it up
22:14:23 <darrenc> yeah, I'm just concerned we'll hit the same issue last cycle with the arch guide
22:14:54 <darrenc> arrange some content here and there, but no real contributions from SMEs
22:15:04 <ShillaSaebi> right
22:15:32 <ShillaSaebi> how awesome would it be if the arch wg could give a huge helping hand in this effort
22:15:42 <ShillaSaebi> specially if its a team full of architects :D
22:15:49 <darrenc> true!
22:15:59 <darrenc> I think we need to reconsider our approach
22:16:30 <katomo> agree
22:17:28 <darrenc> We really architects providing guidance to the arch guide, and ops for the ops guide
22:18:04 <darrenc> and working alongside docs to drive those changes
22:18:39 <ShillaSaebi> yeah
22:18:41 <darrenc> I mean we used to do the book sprint thing
22:18:45 <ShillaSaebi> i couldnt agree with that more
22:19:12 <darrenc> pile a bunch of people in a room for a week and churn out a book
22:19:25 <ShillaSaebi> is that easier for people to do
22:19:35 <ShillaSaebi> since they don't have to allocate time on a weekly basis, steadily
22:19:40 <ShillaSaebi> and just hammer it out in a week?
22:19:53 <darrenc> Yeah, there are pluses and minuses
22:20:16 <darrenc> pluses, you get a book
22:20:47 <ShillaSaebi> minus, stuck in a conf room
22:20:55 <darrenc> minuses, book content and structure is limited to the people in the room
22:21:28 <darrenc> You need the right mix of SMEs and docs
22:21:32 <ShillaSaebi> is anyone going to the ops mid cycle?
22:21:38 <ShillaSaebi> thats another great place to find SMEs
22:23:05 <darrenc> I don't think I will be
22:23:13 <darrenc> Nice location, though
22:25:42 <ShillaSaebi> i wont be either
22:25:48 <ShillaSaebi> but we have a few folks from Comcast going
22:25:55 <ShillaSaebi> I will make sure to let them know to look for contributors
22:27:17 <ShillaSaebi> ok anything else anyone wants to bring up?
22:27:29 <darrenc> If I remember correctly, I *think* Lana was looking at appointing an Ops docs liason
22:27:47 <ShillaSaebi> was that on the ML
22:27:54 <ShillaSaebi> sounds somewhat familiar
22:29:29 <ShillaSaebi> looks like were out of time
22:29:36 <ShillaSaebi> can we continue that on the ML DarenC?
22:29:39 <ShillaSaebi> DarrenC
22:29:52 <darrenc> yep, you read my mind :)
22:30:28 <ShillaSaebi> ok everyone
22:30:30 <ShillaSaebi> thank you so much for joining
22:30:36 <DevonBoatwright> yw
22:30:39 <ShillaSaebi> have a good one!!
22:30:40 <katomo> thanks, good day.
22:30:47 <ShillaSaebi> see ya next time, good day/evening/night all!
22:30:48 <DevonBoatwright> See ya Shilla
22:30:49 <darrenc> thanks everyone!
22:30:53 <ShillaSaebi> #endmeeting