| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-09-21 | |||
| 21:26:37 | cdent | dansmith: that’s not how I remember it? I thought it was “shortly after the latest release to get feedback from people”. | |
| 21:27:04 | dansmith | cdent: very few people install the release shortly after the release | |
| 21:27:10 | cdent | I know, but that was the pitch | |
| 21:27:12 | mriedem | http://lists.openstack.org/pipermail/openstack-dev/2017-September/121783.html | |
| 21:27:22 | mriedem | "Sydney marks the start of Rocky's release cycle, where ideas and requirements will be gathered. Users should aim to come armed with feedback from Augusts's Pike release if at all possible." | |
| 21:27:22 | dansmith | there was definitely a "people who need a midcycle could do it during the forum" argument | |
| 21:28:08 | cdent | “on the priorities and 'blue sky' ideas for the next release.” is both terrifying and exciting | |
| 21:28:15 | mriedem | we had some sessions in boston which were "here is a problem, this is what we plan on doing about it, does that work for you opsy people?" | |
| 21:28:32 | mriedem | i don't know what we have like that for queens | |
| 21:28:41 | cdent | huh, I thought ptg was the replacement for the midcycle, not forum for the midcycle | |
| 21:28:56 | cdent | mriedem: is that because the dance card is full? | |
| 21:28:57 | dansmith | the format of the midcycle was moved to ptg | |
| 21:29:06 | dansmith | instead of design summit style | |
| 21:29:10 | mriedem | and the ptg replaced the dev summit at the start of the release | |
| 21:29:12 | dansmith | but they shifted the schedle | |
| 21:29:15 | dansmith | right | |
| 21:29:40 | mriedem | so now it's semi scheduled blocks of things in a midcycle setting with no ops or users | |
| 21:29:55 | mriedem | well, some ops | |
| 21:30:04 | mriedem | cburgess and med_ <3 | |
| 21:30:22 | edleafe | cdent: PTG is supposed to be planning for the upcoming cycle. Forum is supposed to be more like a midcycle | |
| 21:30:42 | mriedem | except midcycles of yore weren't time boxed | |
| 21:30:52 | mriedem | and didn't cost $3000 to go to | |
| 21:30:55 | dansmith | more like a midcycle, meaning scheduling | |
| 21:31:02 | cdent | edleafe: that’s not at all my understanding, and nor does it correspond to the email that mriedem just linked to | |
| 21:31:30 | dansmith | cdent: certainly you've noticed that the early messaging, the late messaging, and the actual intent for changing things are totally disjoint :) | |
| 21:31:34 | mriedem | there are numerous flame wars on what the ptg is and isn't, or supposed to be or not, in the ML, so probably don't need to enumerate those here | |
| 21:31:52 | cdent | dansmith: yes, very true, but I _never_ thought the forum was a midcycle | |
| 21:32:13 | dansmith | right, all I'm saying is I hope that if we need to have discussions for in-progress things, we can do that as that was part of why the midcycle was important.. for rescuing things that were flailing before it was too late | |
| 21:32:33 | mriedem | dansmith: we can, if you can figure out what those things are going to be in the next 8 days :) | |
| 21:32:34 | edleafe | cdent: no, not a midcycle, but that would be the time to make sure you are on course for completing what you set out to do at the PTG | |
| 21:32:51 | edleafe | dansmith: sorta jinx | |
| 21:32:53 | cdent | if that’s an expectation people have, I think they will be disappointed | |
| 21:32:56 | dansmith | edleafe: exactly | |
| 21:33:02 | mriedem | dansmith: and minus a lot of the developers involved | |
| 21:33:05 | cdent | a) there won’t be time, b) there won’t be the people | |
| 21:33:09 | dansmith | mriedem: certainly for this one | |
| 21:33:13 | cdent | b jinx with mriedem | |
| 21:33:28 | cdent | we should treat it as feedback time | |
| 21:33:45 | mriedem | ^ is why i'd rather just sit in on ops sessions | |
| 21:33:49 | edleafe | many developers couldn't get companies to pay for the midcycles, since it wasn't an "official" event | |
| 21:34:10 | cdent | mriedem: maybe just make that so then? state: we’re not gonna do nova-oriented forum sessions, we’re going to go to ops ones | |
| 21:34:37 | mriedem | cdent: that will be the case if we don't have anything to propose | |
| 21:34:42 | mriedem | which might just happen naturally | |
| 21:34:53 | cdent | I suspect most people whould approve of that, especially if you spread the idea around | |
| 21:35:07 | mriedem | ultimately i just don't want to have to propose topics to fill time | |
| 21:35:27 | mriedem | s/i/us/we/everyone/ | |
| 21:35:54 | dansmith | the topics we proposed in boston were pretty well-attended by ops no? | |
| 21:36:56 | mriedem | yeah | |
| 21:37:18 | mriedem | some of the stuff we talked about in boston is just carrying over into queens | |
| 21:37:29 | mriedem | so that's where i'm thinking, this isn't news, this is stuff we're still working on | |
| 21:37:45 | openstackgerrit | Eric Berglund proposed openstack/nova master: Add PowerVM hypervisor configuration doc https://review.openstack.org/505665 | |
| 21:37:50 | dansmith | I think if we don't propose sessions to get specific feedback from ops, we'll be perceived as not caring to gather input, even if the actual goal is to attend other things | |
| 21:38:15 | mriedem | i don't know what specifically we're trying to get feedback on | |
| 21:38:48 | mriedem | and we've done the general ops feedback sessions in the past which weren't well attended | |
| 21:39:37 | mriedem | getting feedback from pike would be great, hell even ocata | |
| 21:39:49 | dansmith | isn't that likely to be the outcome if we just say we're not proposing things and expect everyone else to do it? | |
| 21:40:36 | mriedem | so are you thinking like a pike feedback session? | |
| 21:41:03 | dansmith | I think that by the time that rolls around several of the people we know of as early movers will be on pike already | |
| 21:41:11 | dansmith | cern, vexxhost already being there, etc | |
| 21:42:03 | mriedem | L10 in https://etherpad.openstack.org/p/SYD-ops-session-ideas | |
| 21:42:21 | mriedem | we do have the project update talk for pike | |
| 21:42:47 | dansmith | surely someone has an opinion on the quotas changes by that point | |
| 21:42:50 | mriedem | i'm totally fine with a pike feedback / update session if people are armed with issues/questions | |
| 21:42:52 | melwitt | I think a good topic would be something like "upgrades", how did it go when you upgraded nova and what issues did you run into, what would make it easier | |
| 21:43:08 | mriedem | ok, so, | |
| 21:43:18 | mriedem | you all know you can throw stuff in this etherpad right? | |
| 21:43:20 | openstackgerrit | OpenStack Proposal Bot proposed openstack/os-traits master: Updated from global requirements https://review.openstack.org/503646 | |
| 21:43:26 | melwitt | I know we've covered it before in the past but it's kind of a moving target I think. each release has its own upgrade gotchas | |
| 21:43:30 | melwitt | yes, sorry | |
| 21:43:44 | dansmith | mriedem: sure, but ya'll were arguing about not having anything here | |
| 21:44:31 | mriedem | i'm basically just trolling myself at this point | |
| 21:44:35 | melwitt | in my case, my brain is totally fried from the PTG and the ideas are emerging slowly | |
| 21:44:38 | mriedem | right | |
| 21:44:40 | mriedem | same here | |
| 21:45:04 | dansmith | mriedem: do you want my alternate color up on L20 or to delete your dupes on L37? | |
| 21:45:05 | mriedem | i would love to have ops people come armed with issues/questions for a pike feedback session | |
| 21:45:10 | dansmith | er, 38-39 | |
| 21:45:43 | mriedem | a lot of times i feel like we get a room full of people and then are pushing the topics on them, without much response unless you cattle prod someone | |
| 21:46:01 | dansmith | same goes for us just waiting for other people to propose topics | |
| 21:46:15 | edleafe | mriedem: are you bringing a cattle prod to Sydney? | |
| 21:46:26 | mriedem | edleafe: kangerprod | |
| 21:46:32 | mriedem | i think you can get them at the corner store | |
| 21:46:49 | edleafe | damn you, I was typing that! | |
| 22:05:50 | dansmith | mriedem: did you see this? https://review.openstack.org/#/c/506370/ | |
| 22:06:03 | dansmith | I don't think the bot barfed it into here else I missed it | |
| 22:06:24 | mriedem | ha, no | |
| 22:07:47 | mriedem | http://docs-draft.openstack.org/70/506370/1/check/gate-nova-docs-ubuntu-xenial/08cdb00//doc/build/html/reference/live-migration.html | |
| 22:07:58 | dansmith | I almost have migration_uuid claims working for cold migration | |
| 22:08:13 | dansmith | gibi laid down the gauntlet with his tests | |
| 22:09:51 | mriedem | efried: you're a docs machine | |
| 22:10:13 | efried | mriedem I was waiting for that to build so I could send you the rendered version. But you what, did it locally? | |
| 22:10:24 | mriedem | no looked at the job results | |
| 22:10:28 | efried | oh, you found it before it was done, cool. | |
| 22:10:36 | mriedem | status.openstack.org/zuul | |
| 22:10:37 | melwitt | he probably spied it on the zuul status page | |
| 22:10:39 | efried | So it ain't perfect, but it's not bad. | |
| 22:10:41 | melwitt | dammit | |
| 22:10:55 | mriedem | efried: 1000% better than what we have today, which is nothing | |
| 22:11:14 | mriedem | you'll have to add that new dependency to global-requirements | |
| 22:11:20 | efried | It's already there | |