Tuesday, 2017-09-19

*** chlong has joined #openstack-operators00:20
*** ChiTo has quit IRC00:55
*** Apoorva_ has joined #openstack-operators01:17
*** Apoorva has quit IRC01:20
*** rtjure has quit IRC01:21
*** Apoorva_ has quit IRC01:21
*** liverpooler has quit IRC01:24
*** rtjure has joined #openstack-operators01:26
*** rebase_ has joined #openstack-operators01:29
*** rebase_ has quit IRC01:33
*** chyka_ has joined #openstack-operators01:43
*** chyka has quit IRC01:43
*** chlong has quit IRC02:03
*** rebase_ has joined #openstack-operators02:23
*** rebase_ has quit IRC02:27
*** chyka_ has quit IRC02:40
*** rebase_ has joined #openstack-operators03:17
*** rebase_ has quit IRC03:21
*** dbecker has quit IRC03:54
*** dbecker has joined #openstack-operators04:07
*** simon-AS559 has joined #openstack-operators04:33
*** benj_ has quit IRC04:34
*** TuanLA has joined #openstack-operators04:44
*** cnf has joined #openstack-operators04:45
*** aojea has joined #openstack-operators04:48
*** aojea has quit IRC04:53
*** benj_ has joined #openstack-operators04:55
*** gyee has quit IRC04:58
*** rebase_ has joined #openstack-operators05:05
*** rebase_ has quit IRC05:09
*** aojea has joined #openstack-operators05:46
*** aojea has quit IRC05:52
*** aojea has joined #openstack-operators05:56
*** rebase_ has joined #openstack-operators05:59
*** rebase_ has quit IRC06:04
*** aojea has quit IRC06:05
*** mriedem has quit IRC06:05
*** arnewiebalck has quit IRC06:05
*** harlowja has quit IRC06:05
*** tdasilva has quit IRC06:05
*** Dmitrii-Sh has quit IRC06:05
*** Oku_OS-away has quit IRC06:05
*** melwitt has quit IRC06:05
*** melwitt has joined #openstack-operators06:05
*** melwitt is now known as Guest3664106:06
*** Dmitrii-Sh has joined #openstack-operators06:06
*** trw[m] has quit IRC06:09
*** aspiers[m] has quit IRC06:09
*** retr0h has quit IRC06:09
*** aojea has joined #openstack-operators06:10
*** mriedem has joined #openstack-operators06:10
*** arnewiebalck has joined #openstack-operators06:10
*** tdasilva has joined #openstack-operators06:10
*** Oku_OS-away has joined #openstack-operators06:10
*** mnaser has quit IRC06:12
*** Oku_OS-away is now known as Oku_OS06:15
*** dmibrid_ has quit IRC06:19
*** mriedem has quit IRC06:25
*** mnaser has joined #openstack-operators06:27
*** sticker has quit IRC06:33
*** simon-AS559 has quit IRC06:38
*** chyka has joined #openstack-operators06:44
*** chyka has quit IRC06:48
*** rebase_ has joined #openstack-operators06:53
*** simon-AS559 has joined #openstack-operators06:56
*** rebase_ has quit IRC06:58
*** simon-AS5591 has joined #openstack-operators06:58
*** simon-AS559 has quit IRC07:01
*** yprokule has joined #openstack-operators07:14
*** trw[m] has joined #openstack-operators07:17
*** rcernin has joined #openstack-operators07:18
*** pcaruana has joined #openstack-operators07:22
*** tesseract has joined #openstack-operators07:24
*** retr0h has joined #openstack-operators07:27
*** aspiers[m] has joined #openstack-operators07:27
*** liverpooler has joined #openstack-operators07:31
*** threestrands has quit IRC07:36
*** fandrieu_ has joined #openstack-operators07:39
*** fandrieu has quit IRC07:39
*** fandrieu_ is now known as fandrieu07:39
*** larizmen has joined #openstack-operators07:40
*** Caterpillar has joined #openstack-operators07:41
*** larizmen has quit IRC07:41
*** d0ugal has quit IRC08:01
*** d0ugal has joined #openstack-operators08:09
*** chyka has joined #openstack-operators08:34
*** chyka has quit IRC08:38
*** electrofelix has joined #openstack-operators08:45
*** rebase_ has joined #openstack-operators09:35
*** rebase_ has quit IRC09:40
*** fandrieu has quit IRC09:44
*** fandrieu has joined #openstack-operators10:20
*** fandrieu_ has joined #openstack-operators10:22
*** fandrieu has quit IRC10:25
*** fandrieu_ is now known as fandrieu10:25
*** rebase_ has joined #openstack-operators10:30
*** rebase_ has quit IRC10:34
*** rebase_ has joined #openstack-operators11:02
*** rebase_ has quit IRC11:07
*** rebase_ has joined #openstack-operators11:56
*** rebase_ has quit IRC12:01
*** liverpooler has quit IRC12:06
*** alexpilotti has joined #openstack-operators12:07
*** TuanLA has quit IRC12:08
*** liverpooler has joined #openstack-operators12:08
*** alexpilo_ has quit IRC12:10
*** alexpilo_ has joined #openstack-operators12:11
*** alexpilotti has quit IRC12:13
*** dminer has joined #openstack-operators12:14
*** MVenesio has joined #openstack-operators12:19
*** VW has joined #openstack-operators12:32
*** VW has quit IRC12:33
*** VW has joined #openstack-operators12:33
*** alexpilotti has joined #openstack-operators12:38
*** alexpilo_ has quit IRC12:39
*** catintheroof has joined #openstack-operators12:49
*** mriedem has joined #openstack-operators12:57
*** chlong has joined #openstack-operators13:19
*** markvoelker has joined #openstack-operators13:30
*** smcginnis has joined #openstack-operators13:45
*** medberry2 has joined #openstack-operators14:00
*** medberry2 is now known as medbrry214:00
*** shintaro has joined #openstack-operators14:00
*** chyka has joined #openstack-operators14:00
*** emccormick has joined #openstack-operators14:02
emccormicko/14:03
*** Guest36641 is now known as melwitt14:03
shintarohi14:03
medbrry2hi14:03
*** mihalis68 has joined #openstack-operators14:04
emccormickheya14:04
mihalis68morning14:04
shintarohi mihalis6814:04
mihalis68I didn't make an agenda, we have a big upgrade about to start14:04
mihalis68just three of us today?14:04
* smcginnis sits in the corner and watches14:04
mihalis684...?14:04
*** chyka has quit IRC14:04
mihalis68#startmeeting Ops Meetup Team14:05
openstackMeeting started Tue Sep 19 14:05:27 2017 UTC and is due to finish in 60 minutes.  The chair is mihalis68. Information about MeetBot at http://wiki.debian.org/MeetBot.14:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:05
openstackThe meeting name has been set to 'ops_meetup_team'14:05
emccormick4 looks like14:06
mihalis68#link https://etherpad.openstack.org/p/ops-meetups-team agenda14:06
mihalis68eric you're updating the wrong meeting, scroll up14:08
emccormickoops14:08
emccormick:D14:08
mihalis68sorry14:08
mihalis68but it IS the 19th, pretty sure14:08
mihalis68#topic actions14:08
emccormickThere we go.14:08
mihalis68I have one ongoing activity, to launch the Wiki-fied operators guide14:08
medbrry2#action me to email ops about ptg14:08
mihalis68I have done a little bit of work on that14:08
mihalis68Bloomberg had two people at PTG and one of them (David Desrosiers) is helping me with doc issues. We'll try to pull together the TOC page for the guide this week, so this action continues14:09
smcginnisSounded like the message got across at the PTG that older docs were a necessity.14:09
mihalis68yeah, quite true14:09
mihalis68they seem to have agreed to not delete from Mitaka onwards14:09
VWo/14:09
mihalis68and also there is a plan for how to make that work14:09
mihalis68hi VW14:09
mihalis68they are moving code like parts out of the doc files to a separate place so they can be maintained after the docs are locked for a release14:10
mihalis68we are  upgrading to mitaka soon and then my complaint about vanishing docs will be no more14:10
emccormickawesome14:10
mihalis68I had another action somewhere to spiff up the team wiki reflecting upcoming events : DONE14:10
emccormickI had one from a couple weeks ago to make the etherpad for SYD session planning and send out to the list. That is here. https://etherpad.openstack.org/p/SYD-ops-session-ideas14:11
emccormickIt's got some things in it, but it's pretty light. Need to send another nag.14:11
mihalis68another topic that I was interested in in Mexico City was openstack release cadence and the possibility of long-term support releases of openstack (for example, hypothetically, making every other release maintained for longer)14:13
mihalis68This is an infinitely deep rabbit hole14:13
mihalis68I had discussions on this with David and eventually just had to grind to a halt14:13
mihalis68but I will say that a lot of feedback to the devs amounts to "you are insane"14:13
mihalis68the idea that on day 1 we install a new openstack, run it for 6 months, then install the next one is just not realistic14:13
emccormickYeah there's a lot of opposition to it14:14
smcginnisOn the plus side...14:14
emccormickbut me wants it.14:14
medbrry2 driving but will comment on lts hen i park14:14
smcginnisI think my whining about vendors needing to support LTS is getting a little bit of traction.14:14
mihalis68go ahead smcginnis14:14
smcginnisRed Hat is planning an LTS version.14:14
mihalis68the developers have valid difficulties in making an LTS happen, but I think they can be solved14:14
emccormick*tingle*14:14
smcginnisAnd I think Huawei will follow suite if they listen to our recommendations.14:15
mihalis68for example a lot of openstack depends on python bits and pieces and those don't necessarily have LTS either14:15
smcginnisSo if we have two vendors supporting an LTS release (as long as it's the same release) we may get wider buy in.14:15
emccormickwill that trickle down to RDO or just RHOS?14:15
smcginnisemccormick: Not really sure at this point. I'm guessing RHOS only.14:15
mihalis68yes Maria (representing RH) said she has some customers who want an LTS (even whilst emphasizing some still want the maximum velocity - 2 releases per year or more)14:15
smcginnis++14:16
smcginnisThere's definitely a mix.14:16
mihalis68David is a Canonical employee assigned to Bloomberg and so he gets it that we need an LTS too14:16
smcginnisNFV users seem to want a feature as soon as it's coded. Other's not so much.14:16
mihalis68he's talking to Canonical luminaries such as James Page to get the current picture and thinking about this so far14:16
medbrry2cannical has alway suportd an Lts14:16
medbrry2tied to their LLTS Ubuntu14:16
mihalis68they do, med, but the actual openstack official dev community still only has 2/year as always.14:17
mihalis68maintenance of a release (other than security fixes) stops 6 months and a day14:17
smcginnisI think the key to this will be getting Red Hat, Canonical, SuSE, Huawei, etc. all working towards the same LTS in the open rather than in their own downstream support teams.14:17
medbrry2But the Stable team has no bandwidth or power to o more14:17
mihalis68yes, it is clear from the devs that it's resources, not a lack of interest14:17
medbrry2mihalis68: agreed.Canonical does backport secu to their LTSs14:18
mihalis68or not only the latter :)14:18
medbrry2smcginnis: Im not sure how t effectively influence that.14:18
medbrry2afai n ops oon the tc14:18
*** rebase_ has joined #openstack-operators14:19
smcginnisMe neither, but I'll keep whining about it in public while I can. ;)14:19
emccormickSomeone put this on the etherpad14:19
mihalis68My view is an openstack released today (hypothetically) shouldn't be installed for production for a while even if I had the deployment capability to keep up. Let it get some mileage first14:19
emccormickwe can talk about it at the Forum with a wider group14:19
smcginnisUC has a voice for sure though.14:19
mihalis68so then it dies 6 months later? I DONT GET IT14:19
medbrry2no operators on the TC14:19
admin0mihalis68: it does not die .. you just upgrade it properly14:19
mihalis68I can't "just upgrade it"14:19
emccormickmihalis68 I"m with you on the letting it bake thing14:19
admin0and there are people who are still running icehouse becuse it fits all the needs ..14:20
smcginnisI think the topic should definitely be at the forum. The only way we'll get there is to be very vocal to vendors that can make it happen.14:20
mihalis68if I'm running it in production and it has a bug I need to fix that not just unleash a newer version and possibly break more stuff14:20
emccormick+114:20
mihalis68Unfortunately I cannot make Sydney14:20
mihalis68so people who will be there will need to push this issue14:21
mihalis68med is the TC makeup deficient, not having operators?14:22
mihalis68obviously asking for an opinion14:22
mihalis68understanding that others may have a diff view14:22
mihalis68or anyone else?14:23
emccormickok it's on the etherpad14:23
medbrry2nsorry driving gain14:23
smcginnismihalis68: It's an interesting question.14:23
medbrry2not sure about what it should have14:23
smcginnisCurrent policy is TC needs to be ATC.14:23
medbrry2ill think about it14:23
mihalis68I think that openstack proudly mentions maturity and stability, right>14:23
smcginnisAnd there are some ops that actually do qualify.14:23
mihalis68I think that openstack proudly mentions maturity and stability, right?14:23
medbrry2you cn be ops and atc. i am14:24
smcginnisBut rules would need to be tweaked to open it up to wider ops representation.14:24
mihalis68isn't there a cost to that that isn't being paid?14:24
smcginnismedbrry2: I'll vote for you. ;)14:24
medbrry2restate please mih14:24
emccormickme 2!14:24
mihalis68"it's very stable"14:25
mihalis68"great can I run it for a year"14:25
mihalis68"sorry no can has"14:25
*** ChiTo has joined #openstack-operators14:25
mihalis68is Med willing to be considered?14:25
medbrry2 COST TO WHAT mihalis6814:25
mihalis68as a software project "matures" it has to devote more resources to supporting long-term usage'14:26
medbrry2mihalis68: sure14:26
medbrry2sure to being considered14:26
mihalis68openstack has run on 2/year and nothing else for, what, 7 years?14:26
mihalis68I would support med on TC (huge proviso, not familiar with definitions of UC nor TC as I should be)14:26
mihalis68med on TC, fifield on board14:27
mihalis68but you didn't hear me say this14:27
VWTC governs how things become a project and the rules they must play by14:27
smcginnisSome reference: https://governance.openstack.org/14:28
mihalis68so is release cadence strictly an OS board issue?14:28
VWUC looks after Ops/End users in the community, organizes their events and looks to further engage them into the development lifecycle process14:28
admin0mihalis68: i worked on a production public openstack cloud that went from icehouse to now ocata .. wtih production customers and clients and we love the new releases as it brings up new features14:28
admin0so i do not see why this cycle needs to be changed or different14:28
mihalis68we are running openstack liberty and we have an engineering hill to climb to get off nova-network before we can go to newer releases than mitaka14:29
admin0if you are happy with a release, no one forces you to upgrade it .. it can be your LTS14:29
mihalis68it's not a question of not liking the new releases and new features, we just can't get to them as fast as is assumed by the release cadence14:29
mihalis68with respect, no14:29
mrhillsmanSorry I'm tardy :)14:29
admin0“we just can't get to them as fast as is assumed by the release cadence”  — lack of resources or manpower ?14:30
mihalis68admin0 example the devs deleted liberty docs from the docs website because EOL14:30
mihalis68that's just wrong and is being fixed14:30
mihalis68liberty is *not* EOL for our vendor14:30
medbrry2welcome mrhillsman14:30
emccormickhi mrhillsman14:30
mihalis68it is already established over the past many meetings that there exists an important part of the community that cannot keep up with 2 releases per year14:30
mihalis68hi mrhillsman14:31
admin0mihalis68: its an open source project on best effort by the community  .. we keep a backup of all repo and docs ..  .. yuo can’t blame them for deleting due to lack of resources just because you diddn’t think it was necessary to backup the docs your organization run on ?14:31
mihalis68by the way, the request is not to stop doing the normal releases, it is to support some of them for longer14:31
mihalis68you're lacking some context here I think14:31
admin0i guess i am :)14:31
mihalis68they deleted the docs because they couldn't maintain them any more. After discussion they agreed that was wrong and they are fixing that14:32
admin0yes, but that still does not change that if you should have backed up yourself14:32
mihalis68their previous answer was "you can just build from tag". That is not a good answer, since we tried and reported to them how deficient the result is and how hard it was to do14:32
mihalis68No, i don't accept that for a minute14:33
admin0if you are running something on prod and its not “guaranteed/paid” by vendor, then it should be your organization doing the backup14:33
mihalis68I don't back up openstack.org at all14:33
mihalis68oh we have a paid vendor14:33
* medbrry2 is done driving and reads sb14:33
admin0aha !14:33
mihalis68but we (us+vendor) discussed. Instead of using openstack documents in some Canonical portal, we want a solution which helps the community. That has been agreed14:34
mihalis68the idea that we just get a private openstack from canonical is simplistic and misleading14:34
mihalis68yes sure we do get our apt packages from cloud-archive, but I think the openstack docs should live on openstack.org for the release life of the software it relates to14:35
medbrry2#action med to read tc bylaws and comme t on ops ml14:35
emccormickAnd from what was said here earlier, that is now going to happen.14:35
emccormickper discussion at PTG14:35
mihalis68yep. as I say the context is we have won this debate14:35
smcginnismedbrry2: Next TC election is coming up soon. Just saying... :)14:36
mihalis68the docs team didn't really even fight it. They deleted them for minor reasons to do with branching and javascript security fixes14:36
mihalis68o/ med for tc14:36
mihalis68docs are just one bit though14:36
mihalis68the larger issue of openstack LTSes continues to swirl around14:36
mihalis68it seems the vendors need to unite around it14:37
mihalis68I've typed a lot14:37
mihalis68is there things we need to discuss re: Sydney and/or tokyo that we didn't touch on yet?14:37
mihalis68I think for example Tokyo will mark the start of the foundation officially owning and running even planning for a mid-cycle meet up if mrhillsmans brief update last week is true14:38
emccormickSydney I think we just need to get people putting more sessions in14:38
mihalis68counting on you to be the benevolent dictator for sydney, erik!14:38
mihalis68"event planning" not even planning14:38
emccormickjajaja14:39
mihalis68#agreed emccormick to chivvy along the planning for Sydney ops meetup14:40
*** medbrry2 has quit IRC14:40
emccormickmrhillsman Anything more to add about upcoming foundation support?14:40
mihalis68by the way, backing up the docs was not the issue anyway14:40
mihalis68you can build a set of docs from EOL-LIBERTY tag or whatever it is, but they are broken14:40
mihalis68they are not clean w.r.t. being all relative links etc14:41
mihalis68I actually got the code and built it14:41
mihalis68but probably more than enough about docs for one day14:41
shintaromrhillsman, if we can get Foundtion support for Tokyo, I like to know who to contact. fifieldt?14:41
mihalis68it will not be tom14:42
mihalis68he's moving roles, but I can't say more14:42
shintarooh ok.14:42
* med_ rejoined from desk14:43
VWThe foundation will plug someone in, I'm sure until an official replacement is found14:43
med_so stupid parliamentary procedure question: this is the ops meetup planning meeting not the operators take over the world meeting. I'm happy to find out and report on the #o-o mailing list about TC but it takes more than this meeting's support to make that happen. (fyi)14:43
mihalis68yeah, haven't heard who though14:43
mihalis68quite right14:44
mihalis68(if you have the bylaws please forward :)14:44
med_roger.14:44
mihalis68I believe the right procedure would be to breach the topic of an operator for the TC14:44
mihalis68and mention that Med qualifies by being ATC as well14:44
mihalis68and then perhaps see if anyone else would like to be considered14:44
med_so smcginnis is TC.14:44
mihalis68then announce a vote?14:44
mrhillsmanSorry in a dead spot14:45
mrhillsmanshintaro I will start a thread14:45
shintarothanks mrhillsman14:45
med_mihalis68, probably not going to get an additional vote. Nothing on bylaws other than the tech-committe page. Again, I'll summarize/discuss on ML.14:45
mihalis68a thread about OS foundation contact for event planning?14:45
mrhillsmanyep14:46
*** mdorman has joined #openstack-operators14:46
mihalis68#action med_ to bring up adding an operator to the TC on the operators mailing list14:46
mrhillsmanAnd more specifically structure of the event14:46
med_my atc quals may have expired, I'll make sure I have commits in on Q to re-qual.14:46
mihalis68cool14:46
mrhillsmanI think opendev is a great example of how we can provide value14:46
mrhillsmanPersonally, being realistic, ops midcycle needs to feed back into the ecosystem better14:47
* med_ missed that event14:47
mihalis68another action I had (talking of feedback) is see if the local team has any thoughts about the mexico city event14:47
mrhillsmanSo I would like to start a thread on this in general14:48
mihalis68I sent a list of fairly standard Q.s to the slack channel. Gloria says she will respond. Depending on how that goes there might be another superuser article that could be made from that14:48
mihalis68I think we should somehow send a mid-cycle "digest" back to the community14:49
mihalis68and make it more prominent than "here is the URL of some ether pads"14:49
med_+1 on digest14:49
med_+1 on Superuser. (I think they target very different readers, so both are good)14:49
mrhillsmanWhat i liked about opendev was it being focused14:49
mihalis68#action mrhillsman volunteered to kick off discussion of feedback from mid-cycles back to wider operators community14:50
mrhillsmanI think ops midcycle is too wild west like per se14:50
mihalis68#action mihalis68 to pull together a sample/proposed digest for next meeting14:50
med_mrhillsman, folks I talked to (devs) at PTG had no idea OpenDev was truly an OpenStack event. with that name, it wasn't entirely obvious.14:50
mrhillsmanSo incorporating focus and freedom14:50
mihalis68I had no idea until this very second14:50
mihalis68not having been, I can't comprehend what opendev had that we lack at mid-cycles14:51
VWI'm not saying that mid-cycle meetings for Ops couldn't use more structure, but remember the primary focus of them is to get operators engaged in the community at large14:51
mrhillsmanThat's reasonable assessment, I think that was on purpose14:51
mihalis68can you provide detail?14:51
emccormickI had no idea it was an openstack event either14:52
mihalis68ok we are missing something right here14:52
VWso, we don't want to re-engineer them to be sessions that create copious amounts of blueprints, etc14:52
emccormickI just saw a few people start tweeting about it14:52
VWI have to run to an in person meeting.  Take care all - see you next week14:52
mrhillsmanI'm on my phone, thread I can type more, but pulling out 2-3 things to focus on14:52
mihalis68bye VW thanks!14:52
mrhillsmanI'm not suggesting losing the spirit/mandate14:53
mrhillsmanBut if we are honest, we have the same discussions14:53
*** VW_ has joined #openstack-operators14:53
mrhillsmanAnd we have more than blueprints14:53
mrhillsmanI will create thread ;)14:54
mihalis68just over 5 minutes14:54
mihalis68last week we discussed the possibility of a NE USA meet up before end of year or possibly early next year14:54
mihalis68given that not everyone can get to australia or japan14:55
smcginnisSomeone told me there was going to be an ops meetup in NY in Oct or Nov.14:55
mihalis68and openstack days east was cancelled due to lack of interest14:55
mihalis68anyone know where that came from? or is that my suggestion last week bouncing around and echoing back here?14:55
mrhillsmansmcginnis I heard the same but for next year14:56
mihalis68a meetup in NY in Oct sounds ... surprising?14:56
smcginnisI was surprised.14:56
mrhillsmanI heard Bloomberg, Verizon, and someone else involved14:56
smcginnismrhillsman: Same. Maybe we were both there when the person said it. :D14:56
*** VW has quit IRC14:57
mihalis68heh. Well I haven't seen one of my internal contacts since PTG14:57
mihalis68juan negron14:57
mrhillsmanPossibly :)14:57
mihalis68he might be able to swing some level of backing for such a thing14:57
mihalis68he's in our CTO arm, they have discretionary funds14:57
med_saw juan. Didn't discuss this.14:57
*** VW_ has quit IRC14:57
mihalis68I just run the team that runs the prod openstack stuffs, but no soft money14:58
mrhillsmanI think the guy that said it was from Verizon14:58
mihalis68ok14:58
mihalis682 minutes14:58
mihalis68if someone has a lead on that please share14:58
mihalis68otherwise, any other business?14:58
mrhillsmanI don't know his name but his face I do14:58
emccormickany Tokyo needs / updates shintaro?14:59
mihalis68Ill ask around within Bloomberg14:59
shintaronot for this week. meeting venue people next week14:59
mihalis68excellent14:59
mihalis68so let's meet next week same time same place15:00
med_+115:00
mihalis68but bear in mind mike perez said other similar groups have moved to meeting when there's something to discuss15:00
mihalis68recognizing a fixed schedule is hard for volunteers to make15:00
med_+215:00
mihalis68ok. any last comments?15:00
mrhillsmanHave a great day!15:01
mihalis68#endmeeting15:01
openstackMeeting ended Tue Sep 19 15:01:10 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-09-19-14.05.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-09-19-14.05.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-09-19-14.05.log.html15:01
shintarothanks all15:01
mihalis68thanks everyone15:01
*** smcginnis has left #openstack-operators15:01
*** VW has joined #openstack-operators15:01
mihalis68my team upgraded a 3.2PB ceph cluster partially to jewel during this meeting15:01
emccormickOh, and if anyone is of meager funds such as myself and looking for a hotel for Sydney, I have found myself in possession of a 2 BR apartment 0.2 miles from the conference15:01
mihalis68I wasn't stressed in the least15:01
mihalis68*cough*15:01
emccormickooer15:02
mihalis68monitors done, OSDs under wy15:02
emccormickto Jewel from...Firefly?15:02
mihalis68hammer->jewel15:02
*** shintaro has quit IRC15:02
emccormicknot so bad15:02
mihalis68indeed15:02
mihalis68no reason to panic15:02
mihalis68that doesn't necessarily provide actual peace of mind, however15:02
emccormickremember if you upgrade the clients nothing will be able to attach a new volume until you reboot the instance ;)15:02
mihalis68it's a pure object store cluster15:03
emccormick(learned the hard way)15:03
mihalis68not directly serving openstack15:03
emccormickah that makes it simple15:03
mihalis68but openstack workloads are starting to use S315:03
*** chyka has joined #openstack-operators15:04
*** chyka has quit IRC15:04
*** VW_ has joined #openstack-operators15:05
*** gyee has joined #openstack-operators15:05
*** chyka has joined #openstack-operators15:05
*** VW has quit IRC15:07
*** Oku_OS is now known as Oku_OS-away15:08
*** larizmen has joined #openstack-operators15:09
*** larizmen has quit IRC15:13
*** makowals has quit IRC15:16
*** zhenq has joined #openstack-operators15:26
*** slaweq_ has quit IRC15:27
*** umbSublime has joined #openstack-operators15:27
*** slaweq has joined #openstack-operators15:28
*** emccormick has quit IRC15:30
*** MVenesio has quit IRC15:30
*** ddyer has quit IRC15:32
*** ddyer has joined #openstack-operators15:37
*** fandrieu has quit IRC15:54
*** yprokule has quit IRC16:03
*** rebase_ has quit IRC16:05
*** rebase_ has joined #openstack-operators16:06
*** Apoorva has joined #openstack-operators16:08
*** simon-AS5591 has quit IRC16:32
*** VW_ has quit IRC16:32
*** ddyer has quit IRC16:33
*** VW has joined #openstack-operators16:33
*** pcaruana has quit IRC16:38
*** ddyer has joined #openstack-operators16:40
*** ddyer has quit IRC16:50
*** ddyer has joined #openstack-operators16:51
*** rcernin has quit IRC16:52
*** tesseract has quit IRC16:52
*** saybeano has quit IRC16:52
*** ddyer has quit IRC16:56
*** simon-AS559 has joined #openstack-operators16:57
*** ddyer has joined #openstack-operators17:00
*** ddyer has quit IRC17:00
*** liverpooler has quit IRC17:02
*** ddyer has joined #openstack-operators17:13
*** rtjure has quit IRC17:38
*** dminer has quit IRC17:41
*** rtjure has joined #openstack-operators17:42
*** liverpooler has joined #openstack-operators17:42
*** electrofelix has quit IRC17:48
*** harlowja has joined #openstack-operators17:49
*** MVenesio has joined #openstack-operators17:49
*** mdorman has quit IRC17:51
*** simon-AS559 has quit IRC18:02
*** rebase_ has quit IRC18:07
*** rebase_ has joined #openstack-operators18:08
*** liverpooler has quit IRC18:15
*** ChiTo has quit IRC18:19
*** rtjure has quit IRC18:24
*** liverpooler has joined #openstack-operators18:31
*** larizmen has joined #openstack-operators18:31
*** liverpooler has quit IRC18:31
*** liverpooler has joined #openstack-operators18:32
*** dminer has joined #openstack-operators18:51
*** mdorman has joined #openstack-operators18:56
klindgrenls18:58
*** VW_ has joined #openstack-operators19:02
*** VW_ has quit IRC19:03
*** VW_ has joined #openstack-operators19:04
*** VW has quit IRC19:06
*** simon-AS559 has joined #openstack-operators19:07
*** simon-AS5591 has joined #openstack-operators19:10
*** simon-AS559 has quit IRC19:11
*** slaweq has quit IRC19:14
*** slaweq has joined #openstack-operators19:14
*** slaweq_ has joined #openstack-operators19:33
*** mihalis68 has quit IRC19:33
*** penick has joined #openstack-operators19:35
*** slaweq has quit IRC19:37
*** VW_ has quit IRC20:00
*** VW has joined #openstack-operators20:02
*** VW has quit IRC20:02
*** VW has joined #openstack-operators20:03
*** rebase_ has quit IRC20:07
*** rebase_ has joined #openstack-operators20:08
*** larizmen has quit IRC20:11
*** rcernin has joined #openstack-operators20:14
*** dtrainor has quit IRC20:22
*** dtrainor has joined #openstack-operators20:23
*** catintheroof has quit IRC20:50
*** catintheroof has joined #openstack-operators20:50
*** catintheroof has quit IRC20:51
*** dmibrid_ has joined #openstack-operators20:52
*** dminer has quit IRC21:05
*** mdorman has quit IRC21:28
*** simon-AS5591 has quit IRC21:55
*** WungFu has joined #openstack-operators22:07
*** rebase_ has quit IRC22:07
*** rebase_ has joined #openstack-operators22:09
*** MVenesio has quit IRC22:12
*** VW_ has joined #openstack-operators22:13
*** aojea has quit IRC22:16
*** VW has quit IRC22:16
*** penick has quit IRC22:16
*** VW_ has quit IRC22:18
*** rebase_ has quit IRC22:21
*** chlong has quit IRC22:21
*** penick has joined #openstack-operators22:23
*** slaweq_ has quit IRC22:36
*** catintheroof has joined #openstack-operators22:45
*** openstackgerrit has quit IRC22:47
*** rebase_ has joined #openstack-operators22:48
*** rebase_ has quit IRC22:52
*** zhenq has quit IRC22:57
*** zhenq has joined #openstack-operators22:57
*** slaweq has joined #openstack-operators23:06
*** chyka has quit IRC23:07
*** penick has quit IRC23:11
*** rcernin has quit IRC23:11
*** slaweq has quit IRC23:12
*** penick has joined #openstack-operators23:14
*** penick has quit IRC23:14
*** Caterpillar has quit IRC23:23
*** rebase_ has joined #openstack-operators23:42
*** rebase_ has quit IRC23:48
*** threestrands has joined #openstack-operators23:51
*** chyka has joined #openstack-operators23:54
*** zhenq has joined #openstack-operators23:59

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