Friday, 2019-05-31

*** markvoelker has quit IRC00:09
*** markvoelker has joined #openstack-operators00:10
*** markvoelker has quit IRC00:14
*** mriedem_away has quit IRC00:57
*** gyee has quit IRC01:42
*** ekcs has quit IRC01:47
*** markvoelker has joined #openstack-operators02:10
*** markvoelker has quit IRC02:14
*** ekcs has joined #openstack-operators03:49
*** pcaruana has joined #openstack-operators05:03
*** rcernin has quit IRC05:07
*** ekcs has quit IRC05:16
*** rcernin has joined #openstack-operators06:10
*** simon-AS559 has quit IRC06:56
*** simon-AS5591 has joined #openstack-operators07:11
*** tesseract has joined #openstack-operators07:12
*** rcernin has quit IRC07:52
*** derekh has joined #openstack-operators08:40
*** electrofelix has joined #openstack-operators09:38
*** VW_ has quit IRC11:33
openstackgerritMohammed Naser proposed x/osops-tools-contrib master: osa: add tool to cleanup host  https://review.opendev.org/66243611:48
*** logan- has quit IRC12:07
*** logan- has joined #openstack-operators12:07
*** openstack has joined #openstack-operators12:27
*** ChanServ sets mode: +o openstack12:27
*** bgmccollum has quit IRC12:28
*** yankcrime has joined #openstack-operators12:28
*** bgmccollum has joined #openstack-operators12:31
*** mriedem has joined #openstack-operators13:05
smcginnismihalis68_, emccormick, and others - there's a mailing list thread on openstack-discuss (see "[tc][ops] reviving osops- repos") that I think could use some input from actual operators.13:27
smcginnisI haven't replied to the thread, but am curious if my take from here (http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-05-30.log.html#t2019-05-30T20:00:26) is legitimate or not with your experience.13:28
emccormicksmcginnis I have a reply in progress13:28
smcginnisemccormick: Great! Thanks Eric.13:28
smcginnis*s/c/k/13:29
smcginnis:)13:29
emccormickThat IRC thread is interesting. I personally am unconcerned with appearances given by the location of a repo. I'm more concerned with the visibility of what's in it so it provides the most utility to the most people.13:32
emccormickI don't see a good train for it *not* to be under ipenstack/ though13:33
emccormickopenstack/ too13:33
smcginnisGreat input then. I think it ultimately doesn't matter as long as we have a way to promote it and make it visible and useful.13:34
* mnaser doesn't really care either13:34
mnaserjust unsure on how this can be under openstack/13:34
smcginnisIf it's community supported work that's owned by a SIG, then I think the namespace should be fine.13:35
smcginnisPersonally I kind of like the -ops to make it more clear what type of content can be found there, but meh.13:35
emccormickIt's already technically owned by a WG13:39
mnasersmcginnis: right but is there an 'operators' sig or something? I couldn't find a reasonable 'home'13:39
emccormickA dormant one mind you, but it's there13:39
smcginnisWe could probably morph the ops-docs one to be more general if there isn't something set up already, but I thought like emccormick there was something existing.13:40
mnaserhttps://governance.openstack.org/sigs/13:40
mnaserdidn't see any 'ops' or something13:40
emccormickhttps://wiki.openstack.org/wiki/Osops13:40
emccormickIt predates any such formal organization13:41
*** electrofelix has quit IRC13:43
mnaserright. now I'm not sure what to do (and frankly, I can't imagine how even more painful this might be for someone who's new to this)13:44
mnasermost people would have probably thrown it on a git repo and called it a day by now (because of all this 'extra work')13:45
emccormickThere's a mix of formality in there to accommodate scared newbies or overly busy Ops (who isn't??)13:45
emccormickSome repos are curated. Some are wild west. Throw it in there with now warranty13:46
mnaseryeah, like I can't imagine someone would have actually pushed through to go through all of this :p13:46
emccormickmnaser The idea was that, if a contributor didn't want to commit to maintaining a tool and putting in a little bit of testing, it could just live in the -contrib repos (the uncurated place)13:57
emccormickessentially that was meant to be no more work than sticking it in one's own git repo13:57
emccormickThe process on that wiki page was meant to be handled by the "SIG" team.13:58
emccormickLots of ops have been through Upstream Institute or are otherwise competent enough to deal with Gerrit though, so likely it wouldn't be a huge issue for people to follow normal workflow13:59
emccormickWe do need a Quickstart sort of doc so people could figure out what they needed to do just to push something up without having to read 20 pages of goo though.14:01
*** macza has joined #openstack-operators15:28
*** gyee has joined #openstack-operators15:50
*** mriedem is now known as mriedem_hangry16:14
*** simon-AS5591 has quit IRC16:41
*** derekh has quit IRC17:00
*** khyr0n_ has joined #openstack-operators17:57
*** tesseract has quit IRC18:04
*** mattia has quit IRC18:38
*** mattia has joined #openstack-operators18:38
*** mriedem_hangry is now known as mriedem18:44
*** openstackgerrit has quit IRC19:01
*** dtrainor has quit IRC19:10
*** simon-AS559 has joined #openstack-operators19:31
*** dtrainor has joined #openstack-operators19:33
*** slaweq has quit IRC19:48
*** slaweq has joined #openstack-operators19:53
*** slaweq has quit IRC19:58
*** khyr0n has quit IRC20:53
*** khyr0n_ has quit IRC20:53
*** khyr0n has joined #openstack-operators20:53
*** pcaruana has quit IRC21:54
*** simon-AS559 has quit IRC22:00
*** openstackgerrit has joined #openstack-operators22:42
openstackgerritMerged x/osops-tools-contrib master: heat: add cleanup_stacks  https://review.opendev.org/66227722:42
openstackgerritMerged x/osops-tools-contrib master: osa: add tool to cleanup host  https://review.opendev.org/66243622:42
*** macza has quit IRC23:06
*** VW_ has joined #openstack-operators23:17
*** VW_ has quit IRC23:34
*** gyee has quit IRC23:44

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