Thursday, 2019-02-14

*** mriedem has quit IRC00:29
*** dangtrinhnt_ has quit IRC01:15
*** whoami-rajat has joined #openstack-release01:20
*** dangtrinhnt has joined #openstack-release01:22
*** ricolin has joined #openstack-release01:30
*** hongbin has joined #openstack-release02:07
*** armax has quit IRC03:24
*** ykarel|away has joined #openstack-release03:40
*** lbragstad has joined #openstack-release03:46
*** ykarel|away is now known as ykarel03:48
openstackgerritMerged openstack/releases master: Switch Solum service to cycle-with-rc
*** diablo_rojo has quit IRC03:53
*** ricolin has quit IRC04:05
*** armax has joined #openstack-release04:13
*** udesale has joined #openstack-release04:36
*** ykarel has quit IRC04:57
*** ricolin has joined #openstack-release05:02
*** ykarel has joined #openstack-release05:11
*** hongbin has quit IRC05:44
*** cfriesen has quit IRC06:21
*** cfriesen has joined #openstack-release06:25
openstackgerritMerged openstack/releases master: Import xstatic-* release history
openstackgerritMerged openstack/releases master: Release xstatic-magic-search
openstackgerritMerged openstack/releases master: xstatic-mdi
openstackgerritMerged openstack/releases master: xstatic-angular-lrdragndrop
openstackgerritMerged openstack/releases master: xstatic-jasmine
openstackgerritMerged openstack/releases master: Release tripleo-common 8.6.7
*** e0ne has joined #openstack-release06:29
*** e0ne has quit IRC06:46
*** aojea has joined #openstack-release07:21
*** jtomasek has joined #openstack-release07:34
*** jtomasek has quit IRC07:39
*** ykarel is now known as ykarel|lunch07:42
*** jtomasek has joined #openstack-release07:44
*** e0ne has joined #openstack-release08:05
*** e0ne has quit IRC08:08
*** cfriesen has quit IRC08:13
*** tesseract has joined #openstack-release08:14
*** e0ne has joined #openstack-release08:18
*** e0ne has quit IRC08:18
*** e0ne has joined #openstack-release08:29
*** ykarel|lunch is now known as ykarel08:29
*** e0ne has quit IRC08:35
*** electrofelix has joined #openstack-release08:43
*** tosky has joined #openstack-release08:47
*** lbragstad has quit IRC08:47
*** jpich has joined #openstack-release08:53
*** nhbinh_ has quit IRC08:57
*** binh___ has joined #openstack-release08:57
openstackgerritJakub Libosvar proposed openstack/releases master: Release THT 8.2.1
*** dtantsur|afk is now known as dtantsur09:20
openstackgerritAkihiro Motoki proposed openstack/releases master: Release horizon plugins under neutron governance
openstackgerritAkihiro Motoki proposed openstack/releases master: Release neutron stadium stein beta deliverables
*** luizbag has joined #openstack-release09:38
openstackgerritMerged openstack/releases master: Update process to account for Stein changes
openstackgerritThierry Carrez proposed openstack/releases master: Release THT 8.3.0
openstackgerritMerged openstack/releases master: Release horizon plugins under neutron governance
*** hberaud is now known as hberaud|afk10:08
openstackgerritMerged openstack/releases master: Release cinderclient 3.1.1
*** whoami-rajat has quit IRC10:19
*** hberaud|afk is now known as hberaud10:21
*** udesale has quit IRC10:58
*** vdrok has joined #openstack-release11:48
*** armstrong has joined #openstack-release12:11
*** hberaud is now known as hberaud|lunch12:38
*** udesale has joined #openstack-release12:45
*** armstrong has quit IRC13:22
*** armstrong has joined #openstack-release13:23
*** dave-mccowan has joined #openstack-release13:36
*** mriedem has joined #openstack-release13:39
*** jaosorior has quit IRC13:47
*** hberaud|lunch is now known as hberaud13:48
*** lbragstad has joined #openstack-release13:50
*** jaosorior has joined #openstack-release13:51
*** ykarel is now known as ykarel|away14:18
*** ykarel|away has quit IRC14:23
*** ykarel|away has joined #openstack-release14:40
*** ykarel|away is now known as ykarel14:45
*** electrofelix has quit IRC14:53
*** mlavalle has joined #openstack-release14:55
openstackgerritJakub Libosvar proposed openstack/releases master: Release puppet-tripleo 8.4.0
*** udesale has quit IRC15:22
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Feb 14 16:00:10 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: releaseteam)"16:00
openstackThe meeting name has been set to 'releaseteam'16:00
smcginnisPing list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong16:00
smcginnis#link Agenda16:00
dhellmannsmcginnis : I'm in a call but lurking.16:00
smcginnisdhellmann: ack16:00
smcginnis#topic Do we want to do the release 'manifest'16:01
*** openstack changes topic to "Do we want to do the release 'manifest' (Meeting topic: releaseteam)"16:01
ttxright so originally we had that idea to reaffirm liaisons toward the end of the cycle16:01
*** diablo_rojo has joined #openstack-release16:01
ttxbut we haven't really been actively implementing that16:02
ttxI guess there is still time, but we need to start socializing that now-ish16:02
ttx(I kept it off the process change since I was not sure we'd do it for this cycle)16:02
smcginnisWith the loss of enforcing 2 milestones, we do need some way to validate what will be in the coordinated release.16:03
smcginnisDid we ever figured out the specifics of how we would do that "manifest"?16:03
ttxI was thinking about a list of names and email addresses, keyed by project team16:03
ttxin deliverables/stein16:04
smcginnismanifest.yaml or similar?16:04
* diablo_rojo waves16:04
ttxyaml would likely break automation16:04
smcginnisYeah, just thinking we probably have too many places that glob on *.yaml16:04
ttxsince we are expected to only have release files ni deliverables/*/*.yaml16:04
evrardjpsorry I am not really sure to understand the point of the manifest16:05
smcginnisSo a manifest.txt where each team would need to add their acknowledgement that they plan to be part of the stein release?16:05
ttxbut could just be manifest.txt or liaisons.txt16:05
smcginnisevrardjp: It's due to the changes with cycle-with-mielstones.16:05
evrardjpI see the email linked there16:05
smcginnisIn the past, we had a requirement that projects needed to do at least two milestone releases.16:06
evrardjpI don't see the direct link between having a manifest file and activity/healthiness16:06
smcginnisThat was used as an indicator to make sure they were active and were planning on being part of the coordinated release.16:06
evrardjpcouldn't reviews be enough?16:06
ttxevrardjp: we'd ask those people to add themselves16:06
ttxso it's a commitment16:06
ttxin advance of actually requiring reviews16:06
smcginnisBut not that we don't require milestones, the idea to make sure we had would be for them to explicitly acknowledge it by adding to a manifest.16:06
ttx(at which point it's too late)16:06
evrardjpttx: what if projects don't write their names?16:07
evrardjp(sorry to play devil's advocate here)16:07
evrardjpfor me releases should be helping projects, not putting burden on them with <insert new procedure> . I am just worried about the attention loss on that eventual file16:08
evrardjpbut maybe I am a dreamer16:08
smcginnisI am a little concerned about having a new "you all must do this or else you are not included" requirement.16:08
evrardjpbut the plan is the plan right now, sorry for that interruption -- please continue16:08
evrardjpsmcginnis: I am glad I am not the only one :)16:09
ttxevrardjp: the manifest process, done early enough, gives us a chance to chase people down16:09
smcginnisIt was a plan we talked about in Denver. I think it's a question now of whether it really is something we need and want to do.16:09
ttxIt's extra painful to do that in the release weeks16:09
evrardjpcan't we assume that if people have done an RC and branching, they are following our processes?16:10
smcginnisI guess the question (or a question) is if it is "early enough" now or if we've missed that window.16:10
evrardjp(that's the dreamer part)16:10
ttxyeah, we could also skip it this time and see how it goes16:10
ttxevrardjp: so most of the branching and RC is now automatic16:11
evrardjpyeah I meant a review on it16:11
ttxThe big question is... is there anyone actually making sure that what we automatically ship is actually working16:11
ttxthe manifest was a way to close that loophole16:11
smcginnisI'm wondering if that might be better this first time around. I feel like we've been introducing a lot of new things for teams to have to be aware of that are really distractions from their main focus. I'd be concerned introducing another thing they have to keep track of doing might be pushing things.16:12
ttxif nobody abswers for a full month, let's not ship it at all16:12
smcginnisHonestly, I'm wondering now if it was really worth switching from the milestone model.16:12
smcginnisI would be very interested to hear feedback from teams on how they felt this has worked for them this cycle vs past ones.16:13
evrardjpthat sounds like a good PTG topic16:13
ttxI there was certainly less boilerplate activity as a result16:13
smcginnisevrardjp: Good point.16:13
*** ricolin_ has joined #openstack-release16:14
ttxbut maybe that removed a lot of responsibility as well16:14
evrardjpttx: less work for teams is good16:14
ttxa good way to assess that is to run the stein process without the manifest16:14
evrardjpttx: responsibilities don't have to be in code16:14
smcginnisLess boilerplate, but my project perspective is that milestone activity kind of helped to add a little sense of urgency to getting some things done in time where now it's kind of like "oh yeah, milestone-x was last week'/16:14
ttxand see how screwed we end up16:14
evrardjpttx: :)16:14
evrardjpsmcginnis: I feel that too on my side of the pond16:15
ttxok, so... no manifest, revisit in Denver16:16
smcginnisProposal then: no manifest this time around and we see how it goes. We try to do some sort of retrospective at the PTG to evaluate how things went on our end AND try to get PTLs and teams involved to give feedback on how it worked for them.16:16
evrardjpttx: smcginnis +116:16
*** dtantsur is now known as dtantsur|afk16:16
*** ricolin has quit IRC16:16
ttxIt's tricky because with less resources we want to avoid useless work... but at the same time with less activity people are more likely to be lulled into sleep in absence of forced milestones16:17
diablo_rojoWorks for me16:17
ttxI still think it was the right move though. We just need to make extra release noise16:17
evrardjpttx: you're right, and I think that should be into the elements of the PTG conversation16:17
ttxto wake people up16:18
smcginnisI think since it is mostly boilerplate, the amount of work is low versus the level of engagement it promotes.16:18
evrardjpttx: I agree on the noise and communication16:18
ttxstarting next week(s) with library stuff16:18
smcginnisBut happy either way if we can get feedback that we are helping teams and not causing friction.16:18
ttxmanifest is adding some bureaucratic procedure to make sure we actually have people caring. But we could also do that by making a lot of release noise16:18
ttx(our classic dilemma of getting acknowledgement for our messaging)16:19
smcginnisI wonder if we could do the two milestone thing by having them add to the manifest at T-1 and some sort of confirmation at T-2.16:19
ttxaka no way to put a big dialog box in front of all teams and know for sure16:20
evrardjpI think using noise would be good -- as we can use that to say "don't forget highlights " anyway16:20
smcginnisLess work than doing a milestone release but still something to trigger them to be aware of the release progress.16:20
ttxsmcginnis: could be a way to do it16:20
evrardjpwho said spam on the channels and ML? :p16:20
smcginnisWell, too late anyway at this point for something like that, so I think I like the plan to skip a manifest for now and reevaluate in Denver.16:21
ttxso with stein we've pushed the pendulum far in the "less of useless work" direction. For train we might need to get a bit more insurance16:21
ttxok next topic16:21
smcginnis#topic Cycle-with-rc transitions in absence of PTL answer16:22
*** openstack changes topic to "Cycle-with-rc transitions in absence of PTL answer (Meeting topic: releaseteam)"16:22
ttxspeaking of...16:22
smcginnisLooks like we have Watcher and Tacker still out there.16:22
ttxTacker had some response16:22
ttxfrom not-the-PTL16:23
ttxmaybe he's the manifest person16:23
ttxhe is a tacker core16:24
ttxI'm fine with that as confirmation16:24
evrardjphe was manifesting his presence as liaison?16:24
ttxtoo soon?16:24
evrardjptoo soon16:24
evrardjpsorry, please continue.16:25
ttxSo I'm fine with the confirmation we got on the TAcker one. More concerned with Watcher16:25
smcginnisI think we've published this as the plan. We've had the review out there for a week(ish) for feedback. I'm OK approving it without an official ack.16:25
ttxare those the only two left ? Not so bad I guess16:25
ttxoh we have a Watcher ack16:26
ttx6 hours ago16:26
smcginnisProblem solved.16:26
ttxall is good16:26
ttxpush the W+116:26
smcginnisNothing to see here, move along.16:26
ttxoh I guess I will16:26
smcginnisThanks :)16:27
smcginnis#topic puppet-aodh failure16:27
*** openstack changes topic to "puppet-aodh failure (Meeting topic: releaseteam)"16:27
smcginnisYeah, weird.16:27
smcginnisIt's gotta be some kind of test of a new release job or something.16:27
smcginnisfungi: Any insight on this one?16:27
ttxfungi: was there some infra re-enqueueing?16:27
ttxdhellmann: have you been sleepwalking again?16:28
fungiwe're continuing to work through problems with the publication to puppetforge16:28
fungiso that same release has been retriggered several times over the past month16:28
ttxok, so safe to ignore?16:28
fungiyeah, currently it seems to be failing on credentials, and i'm hoping to get time today to manually decrypt and compare them to make sure it's not an encoding issue16:29
smcginnisProblem solved again. :)16:29
ttxfungi: feel free to quick-respond to the thread on openstack-discuss to close it for reference16:29
fungiif only16:29
fungiwill do16:29
fungionce i climb out of today's meeting hole16:29
ttxwe are killing it today16:29
smcginnisfungi: Well, our problem solved. Not yours. :D16:30
fungiheh ;)16:30
ttxsmcginnis: maybe we should assign next week tasks ?16:30
smcginnis#topic Assigning tasks16:30
*** openstack changes topic to "Assigning tasks (Meeting topic: releaseteam)"16:30
ttx(coincidentally i won't be around)16:30
smcginnisttx: Are you snowboarding again?!16:30
ttxno, visiting NYC with family16:31
ttxso, yes.16:31
smcginnisOh, fun.16:31
smcginnisFreeze reminder will be in my countdown email.16:31
fungihave fun. i enjoy manhattan immensely16:31
smcginnisI was surprised by how much I liked NYC. Actually didn't think I would.16:32
diablo_rojofungi, actually? Or is that sarcasm? lol16:32
evrardjpdiablo_rojo: I was wondering the same :D16:32
smcginnisstable-maint groups is another one for the countdown email.16:32
smcginnisfungi: Do you want to take the task to notify infra to generate an artifact signing key? Or should someone else do that?16:33
smcginnisNot sure if that last one is an issue yet with our changes.16:34
fungidiablo_rojo: i genuinely enjoy manhattan16:34
smcginnisI suppose there are a few.16:34
fungiit's a fun town16:34
fungismcginnis: i'll take it, yes16:34
smcginnisfungi: Thanks16:34
fungi(and probably just do it unless i get an eager volunteer)16:34
smcginnisttx or dhellmann: Do either of you want to take checking on c-w-i projects that have not been released?16:35
smcginnisEveryone's gone planning vacations now. :)16:36
ttxlet me see16:36
smcginnisDoesn't have to be right now, but Monday I guess.16:37
ttxsmcginnis: I feel like that would be a good exercise for our new recruits :)16:37
ttxan area they have not been touching on that much16:37
diablo_rojoWhat needs to be done?16:38
ttxdiablo_rojo: it's described in PROCESS I think16:38
diablo_rojoJust go poke them and get them to do one if they haven't already?16:38
diablo_rojoOh, convenient lol16:38
*** hberaud is now known as hberaud|school-r16:38
evrardjpttx: is it clearly defined in process page?16:38
ttxdiablo_rojo: I think the idea is just to establish the list, for smcginnis to include in his weekly email16:38
evrardjpI guess diablo_rojo and I we can have a look at come back to you?16:39
ttxevrardjp: touché16:39
smcginnisMight be a good exercise to go through to find the script to run to get the list.16:39
diablo_rojoMaking a list is definitely doable :)16:39
diablo_rojoI love lists.16:39
smcginnisevrardjp, diablo_rojo: Should I put your names on the task in the etherpad?16:39
diablo_rojosmcginnis, sure!16:40
openstackgerritMerged openstack/releases master: Switch Watcher service to cycle-with-rc
* diablo_rojo signs up evrardjp to do work with her :) 16:40
smcginnisevrardjp: OK with you?16:40
evrardjpafter today though, it's a special day....16:40
smcginnisIt's technically a task for next week, so plenty of time?16:41
evrardjp(not mine)16:41
evrardjpyeah everything good16:41
diablo_rojoevrardjp, Cecile?16:41
smcginnis#topic Open discussion16:42
*** openstack changes topic to "Open discussion (Meeting topic: releaseteam)"16:42
evrardjpwow that's not for meetings!16:42
evrardjplet's discuss tomorrow diablo_rojo about your love of lists16:42
evrardjpand make that thing16:42
smcginnisJust wanted to point out to folks that I put up a proposed schedule for train16:42
diablo_rojoevrardjp, I'll bea headed to MN tomorrow, but in the morning before I head to the airport we can :)16:42
evrardjpdiablo_rojo: let's sync in a different chan :)16:43
smcginnisUpdate coming, but take a look and see if milestones land on any important dates or anything liek that.16:43
diablo_rojoevrardjp, sounds good :)16:43
smcginnisOK, anybody have anything else?16:45
diablo_rojoDon't think so.16:45
smcginnisThanks everyone.16:45
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"16:45
openstackMeeting ended Thu Feb 14 16:45:58 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:46
openstackMinutes (text):
diablo_rojoThanks smcginnis!16:46
ttxthanks smcginnis16:46
evrardjpthanks indeed16:46
*** hberaud|school-r is now known as hberaud16:46
* dhellmann was less successful at paying attention that he hoped16:48
dhellmannsmcginnis, ttx: I thought we had a detailed plan worked out for handling liaison acks for the manifest, but now I don't remember it. Is it not in the PTG meeting notes?16:49
dhellmannadd it to the series .rst file maybe?16:49
ttxdhellmann: we had that but did not really follow up on it16:50
smcginnisdhellmann: I think we had discussed some options, but I don't remember having a concrete plan.16:50
dhellmannah, ok. I thought we'd worked it out, but maybe not16:51
dhellmannseems reasonable to revisit it at the next ptg16:51
ttx"Before milestone 2: announce the "choose your model" moment at milestone-2 for intermediary things that haven't released yet + the final release liaison designation plan"16:52
* diablo_rojo is excited to be in the release room at the PTG with all the cool kids16:52
ttx    team.yml file where each team needs to have one person add their name as the person responsible for completing that release16:52
ttx    Can't add until around m-3, control/enforce by flag in schedule.yml16:52
ttx    2-3 weeks before RC deadline16:53
ttx    Explain that the person is responsible for making sure we have a working deliverable by the end + cycle-hightlight collection16:53
ttxdhellmann: we did work it out after all16:53
openstackgerritMerged openstack/releases master: Switch Tacker service to cycle-with-rc
smcginnisHuh, good thing for taking notes.16:55
dhellmannand having a vague memory16:59
diablo_rojoThose two things will get you very far in life I've found16:59
*** hberaud is now known as hberaud|gone17:02
*** ianychoi has joined #openstack-release17:06
*** jpich has quit IRC17:08
openstackgerritDoug Hellmann proposed openstack/releases master: Add Cycle-Highlights to process.rst
openstackgerritDoug Hellmann proposed openstack/releases master: fix nits from previous patch
*** armstrong has quit IRC17:21
openstackgerritSean McGinnis proposed openstack/releases master: Add Cycle-Highlights to process.rst
*** aojea has quit IRC17:31
openstackgerritSean McGinnis proposed openstack/releases master: Add Cycle-Highlights to process.rst
*** luizbag has quit IRC17:47
*** ykarel is now known as ykarel|away17:54
*** ykarel|away has quit IRC18:00
openstackgerritMerged openstack/releases master: Release oslo.versionedobjects 1.35.0
*** ricolin_ has quit IRC18:19
*** ricolin_ has joined #openstack-release18:20
*** mlavalle has quit IRC18:25
*** ricolin_ has quit IRC18:25
*** mlavalle has joined #openstack-release18:32
*** shardy has quit IRC18:40
*** dims has quit IRC18:47
*** dave-mccowan has quit IRC19:42
*** dave-mccowan has joined #openstack-release20:06
*** e0ne has joined #openstack-release20:21
*** dave-mccowan has quit IRC20:28
*** dave-mccowan has joined #openstack-release20:35
*** jtomasek has quit IRC21:23
*** jtomasek has joined #openstack-release21:31
-openstackstatus- NOTICE: Jobs are failing due to ssh host key mismatches caused by duplicate IPs in a test cloud region. We are disabling the region and will let you know when jobs can be rechecked.21:32
*** whoami-rajat has joined #openstack-release21:41
*** e0ne has quit IRC21:48
*** dave-mccowan has quit IRC21:49
*** jtomasek has quit IRC21:54
*** tosky has quit IRC22:05
*** tosky has joined #openstack-release22:05
-openstackstatus- NOTICE: The test cloud region using duplicate IPs has been removed from nodepool. Jobs can be rechecked now.22:14
*** dave-mccowan has joined #openstack-release22:22
*** armax has quit IRC22:30
*** tesseract has quit IRC22:42
*** tosky has quit IRC23:51

Generated by 2.15.3 by Marius Gedminas - find it at!