*** markvoelker has joined #openstack-meeting-5 | 01:01 | |
*** HelenYao has joined #openstack-meeting-5 | 01:53 | |
*** ricolin has joined #openstack-meeting-5 | 03:20 | |
*** joanna has quit IRC | 03:37 | |
*** ralonsoh has joined #openstack-meeting-5 | 06:55 | |
*** makowals has quit IRC | 08:03 | |
*** makowals has joined #openstack-meeting-5 | 08:04 | |
*** matrohon has joined #openstack-meeting-5 | 08:04 | |
*** rarcea has joined #openstack-meeting-5 | 08:09 | |
*** irenab has left #openstack-meeting-5 | 08:17 | |
*** ricolin has quit IRC | 09:12 | |
*** ricolin has joined #openstack-meeting-5 | 11:42 | |
*** markvoelker has quit IRC | 12:47 | |
*** yankcrime has joined #openstack-meeting-5 | 13:50 | |
*** markvoelker has joined #openstack-meeting-5 | 14:00 | |
mrhillsman | anyone here for osops meeting? | 14:01 |
---|---|---|
mrhillsman | #startmeeting osops | 14:02 |
openstack | Meeting started Mon Mar 27 14:02:30 2017 UTC and is due to finish in 60 minutes. The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
*** openstack changes topic to " (Meeting topic: osops)" | 14:02 | |
openstack | The meeting name has been set to 'osops' | 14:02 |
mrhillsman | #topic RollCall | 14:02 |
*** openstack changes topic to "RollCall (Meeting topic: osops)" | 14:02 | |
yankcrime | hi mrhillsman | 14:03 |
*** simon-AS559 has joined #openstack-meeting-5 | 14:05 | |
mrhillsman | hey | 14:06 |
mrhillsman | lost interwebs for a moment :( | 14:06 |
mrhillsman | #topic Previous Agenda | 14:07 |
*** openstack changes topic to "Previous Agenda (Meeting topic: osops)" | 14:07 | |
mrhillsman | #link https://etherpad.openstack.org/p/osops-meeting | 14:07 |
mrhillsman | i think we covered most of this stuff previously | 14:07 |
mrhillsman | robputt you around? | 14:08 |
mrhillsman | guess not hehe, will have to check with him on that monitoring matrix idea | 14:09 |
izaakk | o/ sorry for being late | 14:10 |
mrhillsman | no worries | 14:10 |
mrhillsman | going to change topic because previous items are old except one | 14:11 |
mrhillsman | #topic Ops Midcycle Review | 14:11 |
*** shananigans has joined #openstack-meeting-5 | 14:11 | |
*** openstack changes topic to "Ops Midcycle Review (Meeting topic: osops)" | 14:11 | |
mrhillsman | one of the things from the midcycle was around new projects | 14:11 |
mrhillsman | #link https://github.com/openstack-infra/project-config/blob/master/gerrit/projects.yaml | 14:12 |
mrhillsman | that link was provided as a way to find out about new projects | 14:12 |
mrhillsman | along this same line there was discussion about the project team guide | 14:12 |
mrhillsman | #link https://etherpad.openstack.org/p/MIL-ops-osops | 14:12 |
mrhillsman | wondering if anyone has any ideas about what could be added to the project team guide to potentially address some operational items | 14:13 |
mrhillsman | #link https://docs.openstack.org/project-team-guide/ | 14:14 |
* yankcrime reads | 14:15 | |
mrhillsman | #action mrhillsman start a thread on the ML around ops content for project team guide | 14:15 |
mrhillsman | yankcrime hehe, you will need some time :) | 14:15 |
izaakk | Probably some "operational requirements" kind of section? | 14:15 |
*** simon-AS559 has quit IRC | 14:16 | |
yankcrime | yup | 14:16 |
*** raddaoui has joined #openstack-meeting-5 | 14:16 | |
mrhillsman | requirements is a hard case to make | 14:16 |
*** simon-AS559 has joined #openstack-meeting-5 | 14:16 | |
yankcrime | operational considerations perhaps | 14:16 |
izaakk | Things that Operators look at a project before adopting it | 14:16 |
mrhillsman | yeah | 14:16 |
mrhillsman | something like that | 14:16 |
izaakk | not as a strict requirement but lique a guide | 14:16 |
yankcrime | at least some kind of "engage operators early to ensure their concerns are captured" or something | 14:16 |
mrhillsman | some guidelines | 14:16 |
mrhillsman | agreed | 14:16 |
mrhillsman | we also have the ops tags | 14:16 |
mrhillsman | which we need some more visibility into | 14:17 |
yankcrime | there's an issue of awareness that needs to be thought through really | 14:17 |
yankcrime | how should operators / interested parties be made aware | 14:17 |
mrhillsman | but that could be a way to ensure "requirements" | 14:17 |
yankcrime | should the onus be on the project team | 14:17 |
mrhillsman | i think so | 14:17 |
mrhillsman | cannot say for sure | 14:17 |
yankcrime | or should it be up to the operators community to organise and interact | 14:17 |
izaakk | Yeah operational minimal viable product | 14:17 |
yankcrime | probably a bit of both | 14:17 |
mrhillsman | but if there is already say an email that goes to openstack-dev | 14:17 |
mrhillsman | should probably go to openstack-operators as well | 14:17 |
yankcrime | yeah, i think that should be the minimum tbh mrhillsman | 14:18 |
mrhillsman | probably a combination as you suggest yankcrime | 14:18 |
yankcrime | even just some notional "try and canvas operatos opinions via an email" | 14:18 |
izaakk | this links to logging standardization as an example I think | 14:18 |
mrhillsman | definitely a notification at least | 14:18 |
yankcrime | good shout izaakk | 14:18 |
mrhillsman | yeah | 14:18 |
mrhillsman | i'll start a thread on the ML | 14:19 |
izaakk | Cool | 14:19 |
yankcrime | sounds good | 14:19 |
mrhillsman | will probably need quite a bit of input and perspectives on this one | 14:19 |
mrhillsman | at least to get started | 14:19 |
yankcrime | and some delicate moderation no doubt ;) | 14:20 |
mrhillsman | hehe | 14:20 |
mrhillsman | we also discussed at the midcycle addressing the larger needs of operators versus just tooling | 14:21 |
mrhillsman | this is going to be quite an undertaking as i was reviewing the wiki | 14:21 |
mrhillsman | which definitely gives way for that | 14:21 |
mrhillsman | as it has operations and then ops tooling | 14:22 |
mrhillsman | i wonder how can we get buy-in | 14:22 |
izaakk | Buy-in in what? | 14:22 |
mrhillsman | i think we need to consider amongst many things that are a concern for operators | 14:22 |
mrhillsman | what are the top 3 | 14:22 |
mrhillsman | izaakk participation | 14:23 |
mrhillsman | looking at the operations wiki | 14:23 |
mrhillsman | #link https://docs.openstack.org/project-team-guide/ | 14:23 |
mrhillsman | bah | 14:23 |
mrhillsman | #link https://wiki.openstack.org/wiki/Operations | 14:23 |
mrhillsman | there are quite a few areas | 14:24 |
mrhillsman | i was looking at the use cases one for example | 14:24 |
mrhillsman | and it has stuff there from 2012 | 14:24 |
mrhillsman | so i think addressing the larger needs of operators warrants a few folks taking a step back and thinking about this at large | 14:25 |
mrhillsman | i think a good starting place is getting a group together who can | 14:25 |
mrhillsman | within osic our group is focused primarily on the tooling | 14:25 |
mrhillsman | branching outside of this subset is probably too much for us to take on | 14:26 |
mrhillsman | alone :) | 14:26 |
mrhillsman | right now we have i can say in terms of working groups/teams as noted on the wiki | 14:26 |
mrhillsman | ops meetups and tooling | 14:26 |
mrhillsman | personally i do not know how to tackle it and need some guidance on it | 14:27 |
izaakk | Yes, also, Monty made a good point on the repo. I think a good framework that allow the operators community to have the opportunity to get ATCs. Probably help from docs people to unify all this concepts? | 14:28 |
mrhillsman | agreed | 14:28 |
mrhillsman | so it is something i think we need to hash out in terms of expectation/purpose/motive/etc and get some feedback | 14:29 |
izaakk | Because from the docs session, a lot of people doesn't even look at this guide, either is not updated or is not clear how to even start to contribute | 14:29 |
mrhillsman | so if we are more than just tooling | 14:29 |
mrhillsman | what are we <- this needs to get structured | 14:29 |
izaakk | Question: is Operators Tools and Monitoring the same as OSOps WG? | 14:30 |
mrhillsman | good question :) | 14:31 |
mrhillsman | i do not have the answer :) | 14:32 |
yankcrime | i think addressing the wider needs of 'operators' is going to be a case of asking what people expect from the ops community | 14:32 |
mrhillsman | i would say no in terms of the definition | 14:32 |
mrhillsman | because a working group is temporary | 14:32 |
yankcrime | which is basically what you're saying by "thinkinbg about this at large" mrhillsman | 14:32 |
mrhillsman | good point yankcrime | 14:32 |
mrhillsman | yep | 14:32 |
mrhillsman | so i think possibly an email is in order for this | 14:33 |
yankcrime | there's different levels of interaction - what are our inputs (experience, developer / project lifecycle interaction), what are our outputs (code, docs), and how to get involved | 14:33 |
mrhillsman | something like we are streamlining what we do, what we are, and are requesting help in defining that | 14:33 |
mrhillsman | maybe an etherpad instead yankcrime ? | 14:34 |
mrhillsman | flushing out those in/outs and how to get involved | 14:35 |
mrhillsman | allow folks to comment/discuss | 14:35 |
yankcrime | good idea, at the very least just a grab-bag of ideas to discuss and formalise for a session in boston | 14:36 |
mrhillsman | ok cool | 14:36 |
mrhillsman | so it sounds like we have a couple of things to tackle | 14:37 |
izaakk | +1 | 14:37 |
mrhillsman | #action work on getting the repos to a place where they are relevant to ATC/AUC | 14:38 |
mrhillsman | #action setup etherpad for brainstorming around ops community ins/outs/involvement | 14:38 |
mrhillsman | last thing and then we can drop :) | 14:39 |
mrhillsman | #topic Ops Hangout Sessions | 14:39 |
*** openstack changes topic to "Ops Hangout Sessions (Meeting topic: osops)" | 14:39 | |
mrhillsman | these were discussed in NYC or BCN i know and someone said they were doing them but i have not seen anything on the mailing list | 14:39 |
mrhillsman | i think an etherpad for ideas is a good way to start this | 14:40 |
mrhillsman | thoughts? | 14:40 |
yankcrime | not seen anything about this tbh | 14:40 |
mrhillsman | same here | 14:41 |
mrhillsman | i think there is potential value here | 14:41 |
mrhillsman | would depend on the sessions | 14:41 |
izaakk | Google Hangouts? | 14:41 |
mrhillsman | yeah | 14:41 |
mrhillsman | like 30-40 minute workshop/walk-through/how-to/etc | 14:42 |
izaakk | The problem can be people from china | 14:42 |
mrhillsman | is there any other option they can use? | 14:42 |
mrhillsman | i think a pool of session ideas | 14:42 |
mrhillsman | and shared content is best approach | 14:42 |
izaakk | Nemat is exploring different services that are also available in chaina, I can provide more input on this. Need to talk to him | 14:42 |
mrhillsman | this way it does not have to be all english #1 :) | 14:42 |
mrhillsman | and could address your concern as well | 14:43 |
izaakk | cool | 14:44 |
mrhillsman | yankcrime thoughts? | 14:44 |
yankcrime | hmm, could be good - needs some proposals and a pool of ideas like you say | 14:45 |
mrhillsman | ok cool | 14:45 |
mrhillsman | #action create etherpad for capturing ops hangout sessions | 14:46 |
yankcrime | be nice to tease out some "ops best practices" and then have demos / sessions | 14:46 |
mrhillsman | +1 | 14:46 |
mrhillsman | well, if there is nothing else, i'll end the meeting and give y'all back some time | 14:46 |
yankcrime | for every ops midcycle there's usually at least a couple of things that someone mentions and then a load of people pipe up and say they're interested in knowing more | 14:46 |
mrhillsman | true | 14:47 |
mrhillsman | #action scour ops etherpads for potential hangout sessions | 14:47 |
mrhillsman | anything else genglemen | 14:47 |
yankcrime | nothing from me | 14:48 |
izaakk | I'm good | 14:48 |
mrhillsman | #endmeeting | 14:49 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:49 | |
openstack | Meeting ended Mon Mar 27 14:49:00 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:49 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-03-27-14.02.html | 14:49 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-03-27-14.02.txt | 14:49 |
openstack | Log: http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-03-27-14.02.log.html | 14:49 |
yankcrime | thanks all | 14:49 |
mrhillsman | thanks for making it | 14:49 |
mrhillsman | next time i'll send a reminder out via email :) | 14:49 |
mrhillsman | will send a summary in a little bit | 14:50 |
yankcrime | cheers mrhillsman | 14:51 |
*** simon-AS559 has left #openstack-meeting-5 | 14:54 | |
*** yankcrime has left #openstack-meeting-5 | 14:56 | |
*** joanna has joined #openstack-meeting-5 | 15:10 | |
*** benj_ has quit IRC | 15:51 | |
*** matrohon has quit IRC | 16:23 | |
*** markvoelker has quit IRC | 17:23 | |
*** serverascode has joined #openstack-meeting-5 | 17:28 | |
*** ricolin has quit IRC | 17:53 | |
*** ralonsoh has quit IRC | 18:11 | |
*** aimeeu__ has joined #openstack-meeting-5 | 19:41 | |
*** aimeeu has quit IRC | 19:41 | |
*** aimeeu__ is now known as aimeeu | 19:41 | |
*** joanna has quit IRC | 19:49 | |
*** markvoelker has joined #openstack-meeting-5 | 20:09 | |
*** markvoelker has quit IRC | 20:22 | |
*** matrohon has joined #openstack-meeting-5 | 20:24 | |
*** joanna has joined #openstack-meeting-5 | 20:49 | |
*** matrohon has quit IRC | 21:23 | |
*** cwolferh has quit IRC | 22:40 | |
*** rarcea has quit IRC | 22:43 | |
*** cwolferh has joined #openstack-meeting-5 | 22:52 | |
*** markvoelker has joined #openstack-meeting-5 | 22:52 | |
*** cwolferh has quit IRC | 23:00 | |
*** benj_ has joined #openstack-meeting-5 | 23:25 | |
*** joanna has quit IRC | 23:48 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!