Monday, 2017-03-27

*** markvoelker has joined #openstack-meeting-501:01
*** HelenYao has joined #openstack-meeting-501:53
*** ricolin has joined #openstack-meeting-503:20
*** joanna has quit IRC03:37
*** ralonsoh has joined #openstack-meeting-506:55
*** makowals has quit IRC08:03
*** makowals has joined #openstack-meeting-508:04
*** matrohon has joined #openstack-meeting-508:04
*** rarcea has joined #openstack-meeting-508:09
*** irenab has left #openstack-meeting-508:17
*** ricolin has quit IRC09:12
*** ricolin has joined #openstack-meeting-511:42
*** markvoelker has quit IRC12:47
*** yankcrime has joined #openstack-meeting-513:50
*** markvoelker has joined #openstack-meeting-514:00
mrhillsmananyone here for osops meeting?14:01
mrhillsman#startmeeting osops14:02
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: osops)"14:02
openstackThe meeting name has been set to 'osops'14:02
mrhillsman#topic RollCall14:02
*** openstack changes topic to "RollCall (Meeting topic: osops)"14:02
yankcrimehi mrhillsman14:03
*** simon-AS559 has joined #openstack-meeting-514:05
mrhillsmanhey14:06
mrhillsmanlost interwebs for a moment :(14:06
mrhillsman#topic Previous Agenda14:07
*** openstack changes topic to "Previous Agenda (Meeting topic: osops)"14:07
mrhillsman#link https://etherpad.openstack.org/p/osops-meeting14:07
mrhillsmani think we covered most of this stuff previously14:07
mrhillsmanrobputt you around?14:08
mrhillsmanguess not hehe, will have to check with him on that monitoring matrix idea14:09
izaakko/ sorry for being late14:10
mrhillsmanno worries14:10
mrhillsmangoing to change topic because previous items are old except one14:11
mrhillsman#topic Ops Midcycle Review14:11
*** shananigans has joined #openstack-meeting-514:11
*** openstack changes topic to "Ops Midcycle Review (Meeting topic: osops)"14:11
mrhillsmanone of the things from the midcycle was around new projects14:11
mrhillsman#link https://github.com/openstack-infra/project-config/blob/master/gerrit/projects.yaml14:12
mrhillsmanthat link was provided as a way to find out about new projects14:12
mrhillsmanalong this same line there was discussion about the project team guide14:12
mrhillsman#link https://etherpad.openstack.org/p/MIL-ops-osops14:12
mrhillsmanwondering if anyone has any ideas about what could be added to the project team guide to potentially address some operational items14:13
mrhillsman#link https://docs.openstack.org/project-team-guide/14:14
* yankcrime reads14:15
mrhillsman#action mrhillsman start a thread on the ML around ops content for project team guide14:15
mrhillsmanyankcrime hehe, you will need some time :)14:15
izaakkProbably some "operational requirements" kind of section?14:15
*** simon-AS559 has quit IRC14:16
yankcrimeyup14:16
*** raddaoui has joined #openstack-meeting-514:16
mrhillsmanrequirements is a hard case to make14:16
*** simon-AS559 has joined #openstack-meeting-514:16
yankcrimeoperational considerations perhaps14:16
izaakkThings that Operators look at a project before adopting it14:16
mrhillsmanyeah14:16
mrhillsmansomething like that14:16
izaakknot as a strict requirement but lique a guide14:16
yankcrimeat least some kind of "engage operators early to ensure their concerns are captured" or something14:16
mrhillsmansome guidelines14:16
mrhillsmanagreed14:16
mrhillsmanwe also have the ops tags14:16
mrhillsmanwhich we need some more visibility into14:17
yankcrimethere's an issue of awareness that needs to be thought through really14:17
yankcrimehow should operators / interested parties be made aware14:17
mrhillsmanbut that could be a way to ensure "requirements"14:17
yankcrimeshould the onus be on the project team14:17
mrhillsmani think so14:17
mrhillsmancannot say for sure14:17
yankcrimeor should it be up to the operators community to organise and interact14:17
izaakkYeah operational minimal viable product14:17
yankcrimeprobably a bit of both14:17
mrhillsmanbut if there is already say an email that goes to openstack-dev14:17
mrhillsmanshould probably go to openstack-operators as well14:17
yankcrimeyeah, i think that should be the minimum tbh mrhillsman14:18
mrhillsmanprobably a combination as you suggest yankcrime14:18
yankcrimeeven just some notional "try and canvas operatos opinions via an email"14:18
izaakkthis links to logging standardization as an example I think14:18
mrhillsmandefinitely a notification at least14:18
yankcrimegood shout izaakk14:18
mrhillsmanyeah14:18
mrhillsmani'll start a thread on the ML14:19
izaakkCool14:19
yankcrimesounds good14:19
mrhillsmanwill probably need quite a bit of input and perspectives on this one14:19
mrhillsmanat least to get started14:19
yankcrimeand some delicate moderation no doubt ;)14:20
mrhillsmanhehe14:20
mrhillsmanwe also discussed at the midcycle addressing the larger needs of operators versus just tooling14:21
mrhillsmanthis is going to be quite an undertaking as i was reviewing the wiki14:21
mrhillsmanwhich definitely gives way for that14:21
mrhillsmanas it has operations and then ops tooling14:22
mrhillsmani wonder how can we get buy-in14:22
izaakkBuy-in in what?14:22
mrhillsmani think we need to consider amongst many things that are a concern for operators14:22
mrhillsmanwhat are the top 314:22
mrhillsmanizaakk participation14:23
mrhillsmanlooking at the operations wiki14:23
mrhillsman#link https://docs.openstack.org/project-team-guide/14:23
mrhillsmanbah14:23
mrhillsman#link https://wiki.openstack.org/wiki/Operations14:23
mrhillsmanthere are quite a few areas14:24
mrhillsmani was looking at the use cases one for example14:24
mrhillsmanand it has stuff there from 201214:24
mrhillsmanso i think addressing the larger needs of operators warrants a few folks taking a step back and thinking about this at large14:25
mrhillsmani think a good starting place is getting a group together who can14:25
mrhillsmanwithin osic our group is focused primarily on the tooling14:25
mrhillsmanbranching outside of this subset is probably too much for us to take on14:26
mrhillsmanalone :)14:26
mrhillsmanright now we have i can say in terms of working groups/teams as noted on the wiki14:26
mrhillsmanops meetups and tooling14:26
mrhillsmanpersonally i do not know how to tackle it and need some guidance on it14:27
izaakkYes, 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
mrhillsmanagreed14:28
mrhillsmanso it is something i think we need to hash out in terms of expectation/purpose/motive/etc and get some feedback14:29
izaakkBecause 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 contribute14:29
mrhillsmanso if we are more than just tooling14:29
mrhillsmanwhat are we <- this needs to get structured14:29
izaakkQuestion: is Operators Tools and Monitoring the same as OSOps WG?14:30
mrhillsmangood question :)14:31
mrhillsmani do not have the answer :)14:32
yankcrimei think addressing the wider needs of 'operators' is going to be a case of asking what people expect from the ops community14:32
mrhillsmani would say no in terms of the definition14:32
mrhillsmanbecause a working group is temporary14:32
yankcrimewhich is basically what you're saying by "thinkinbg about this at large" mrhillsman14:32
mrhillsmangood point yankcrime14:32
mrhillsmanyep14:32
mrhillsmanso i think possibly an email is in order for this14:33
yankcrimethere's different levels of interaction - what are our inputs (experience, developer / project lifecycle interaction), what are our outputs (code, docs), and how to get involved14:33
mrhillsmansomething like we are streamlining what we do, what we are, and are requesting help in defining that14:33
mrhillsmanmaybe an etherpad instead yankcrime ?14:34
mrhillsmanflushing out those in/outs and how to get involved14:35
mrhillsmanallow folks to comment/discuss14:35
yankcrimegood idea, at the very least just a grab-bag of ideas to discuss and formalise for a session in boston14:36
mrhillsmanok cool14:36
mrhillsmanso it sounds like we have a couple of things to tackle14:37
izaakk+114:37
mrhillsman#action work on getting the repos to a place where they are relevant to ATC/AUC14:38
mrhillsman#action setup etherpad for brainstorming around ops community ins/outs/involvement14:38
mrhillsmanlast thing and then we can drop :)14:39
mrhillsman#topic Ops Hangout Sessions14:39
*** openstack changes topic to "Ops Hangout Sessions (Meeting topic: osops)"14:39
mrhillsmanthese were discussed in NYC or BCN i know and someone said they were doing them but i have not seen anything on the mailing list14:39
mrhillsmani think an etherpad for ideas is a good way to start this14:40
mrhillsmanthoughts?14:40
yankcrimenot seen anything about this tbh14:40
mrhillsmansame here14:41
mrhillsmani think there is potential value here14:41
mrhillsmanwould depend on the sessions14:41
izaakkGoogle Hangouts?14:41
mrhillsmanyeah14:41
mrhillsmanlike 30-40 minute workshop/walk-through/how-to/etc14:42
izaakkThe problem can be people from china14:42
mrhillsmanis there any other option they can use?14:42
mrhillsmani think a pool of session ideas14:42
mrhillsmanand shared content is best approach14:42
izaakkNemat is exploring different services that are also available in chaina, I can provide more input on this. Need to talk to him14:42
mrhillsmanthis way it does not have to be all english #1 :)14:42
mrhillsmanand could address your concern as well14:43
izaakkcool14:44
mrhillsmanyankcrime thoughts?14:44
yankcrimehmm, could be good - needs some proposals and a pool of ideas like you say14:45
mrhillsmanok cool14:45
mrhillsman#action create etherpad for capturing ops hangout sessions14:46
yankcrimebe nice to tease out some "ops best practices" and then have demos / sessions14:46
mrhillsman+114:46
mrhillsmanwell, if there is nothing else, i'll end the meeting and give y'all back some time14:46
yankcrimefor 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 more14:46
mrhillsmantrue14:47
mrhillsman#action scour ops etherpads for potential hangout sessions14:47
mrhillsmananything else genglemen14:47
yankcrimenothing from me14:48
izaakkI'm good14:48
mrhillsman#endmeeting14:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:49
openstackMeeting ended Mon Mar 27 14:49:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-03-27-14.02.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-03-27-14.02.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-03-27-14.02.log.html14:49
yankcrimethanks all14:49
mrhillsmanthanks for making it14:49
mrhillsmannext time i'll send a reminder out via email :)14:49
mrhillsmanwill send a summary in a little bit14:50
yankcrimecheers mrhillsman14:51
*** simon-AS559 has left #openstack-meeting-514:54
*** yankcrime has left #openstack-meeting-514:56
*** joanna has joined #openstack-meeting-515:10
*** benj_ has quit IRC15:51
*** matrohon has quit IRC16:23
*** markvoelker has quit IRC17:23
*** serverascode has joined #openstack-meeting-517:28
*** ricolin has quit IRC17:53
*** ralonsoh has quit IRC18:11
*** aimeeu__ has joined #openstack-meeting-519:41
*** aimeeu has quit IRC19:41
*** aimeeu__ is now known as aimeeu19:41
*** joanna has quit IRC19:49
*** markvoelker has joined #openstack-meeting-520:09
*** markvoelker has quit IRC20:22
*** matrohon has joined #openstack-meeting-520:24
*** joanna has joined #openstack-meeting-520:49
*** matrohon has quit IRC21:23
*** cwolferh has quit IRC22:40
*** rarcea has quit IRC22:43
*** cwolferh has joined #openstack-meeting-522:52
*** markvoelker has joined #openstack-meeting-522:52
*** cwolferh has quit IRC23:00
*** benj_ has joined #openstack-meeting-523:25
*** joanna has quit IRC23:48

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!