| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-12-14 | |||
| 16:15:41 | gmann | gibi: thanks | |
| 16:16:25 | bauzas | gibi: I marked the nova and placement ones with the R-P flag | |
| 16:16:33 | gmann | sean-k-mooney: that was for RBAC one, and we have BP also for that #link https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh-2 | |
| 16:16:50 | bauzas | sean-k-mooney: we said on a meeting yes for a specless BP approval | |
| 16:16:54 | gmann | yeah | |
| 16:16:56 | bauzas | (for the policy thing) | |
| 16:17:01 | sean-k-mooney | bauzas: ok | |
| 16:17:16 | sean-k-mooney | normally i think we shoudl treath policy like an api change | |
| 16:17:31 | sean-k-mooney | and use a spec for it but we can proceed without one for now | |
| 16:17:46 | bauzas | this is the defaults, but meh | |
| 16:17:47 | gmann | I have pushed SYSTEM reader->system admin on top of dansmith server policy changes. and I will be pushing more changes this week | |
| 16:17:58 | sean-k-mooney | bauzas: well to me policy change are interop issues | |
| 16:18:09 | bauzas | sean-k-mooney: I don't disagree | |
| 16:18:13 | sean-k-mooney | so change default is a breaking change but lest not repoen that | |
| 16:18:27 | bauzas | but for users, those are transparent if defaults correctly scoped | |
| 16:18:36 | gmann | well policy change does not require spec always. we have fixed (new or default change) many as bug also | |
| 16:19:09 | gmann | yeah, as it is overall change in RBAC, and as described in goal we have way that users will be broken by default | |
| 16:19:23 | gmann | and migration path and plan for them to new policy in next release | |
| 16:19:45 | gmann | *user will not be broken | |
| 16:19:53 | gmann | sorry for typo. :) | |
| 16:20:11 | sean-k-mooney | just to not consume all the time on this is the plan this cycle to walk back the work we had done and focus on identifying the work need with most of the new work happing next cycle | |
| 16:20:20 | sean-k-mooney | i will review the wiki you provided offline | |
| 16:20:40 | gmann | yeah, specially we are isloating the system form project resource and no system reader in yoga | |
| 16:20:52 | sean-k-mooney | ack | |
| 16:21:11 | gmann | sean-k-mooney: thanks, wiki audit will be helpful | |
| 16:21:48 | bauzas | I think we also said that the TC would document this | |
| 16:22:02 | bauzas | the policy changes, I mean | |
| 16:22:14 | bauzas | I even wrote this in the BP when I approved | |
| 16:22:14 | sean-k-mooney | its in the tc spec to some degree | |
| 16:22:20 | gmann | basically this is what we will do (phase1 ) in nova in yoga #link https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#phase-1 | |
| 16:22:22 | bauzas | that's my point | |
| 16:22:24 | sean-k-mooney | i would like to see a nova game plan for how to aling to that | |
| 16:22:35 | sean-k-mooney | which is why i ask about a nova spec | |
| 16:22:57 | sean-k-mooney | but if most of that work will happen next cycle im fine with the wiki and specless blueprint for this cycle | |
| 16:22:59 | bauzas | that's why we said we can start to digest and see whether we need to document more the changes in the spec | |
| 16:23:03 | bauzas | right | |
| 16:23:08 | bauzas | moving on ? | |
| 16:23:12 | sean-k-mooney | +1 | |
| 16:23:16 | gmann | yeah, its there in TC goal | |
| 16:23:41 | bauzas | #topic Stable Branches | |
| 16:23:46 | bauzas | stable gates are not blocked | |
| 16:23:49 | bauzas | shit | |
| 16:23:56 | bauzas | elodilles: it's you who should tell it | |
| 16:24:06 | elodilles | :) | |
| 16:24:12 | elodilles | so they are not blocked | |
| 16:24:16 | gibi | :D | |
| 16:24:18 | elodilles | (as far as I've seen it before the meeting with a quick double-check) | |
| 16:24:28 | gmann | i thought it is very blocked and bauzas typo :) | |
| 16:24:30 | elodilles | though on some branches (wallaby, victoria?) patches need many rechecks to be able to merge | |
| 16:24:58 | bauzas | interesting dystopîa | |
| 16:25:05 | bauzas | between gmann and elodilles | |
| 16:25:05 | elodilles | gmann: hopefully not o:) | |
| 16:25:16 | gmann | \o/ | |
| 16:25:42 | elodilles | or are they? :-o | |
| 16:27:50 | bauzas | so, what to say ? I guess we need to double check | |
| 16:27:51 | bauzas | :) | |
| 16:28:32 | elodilles | i haven't seen any blocking issue, but i'm now confused :) | |
| 16:28:58 | elodilles | gmann: did i miss something? | |
| 16:29:16 | gmann | ah no, I have not seen too. I think recheck is more needed that is uit | |
| 16:29:18 | gmann | it | |
| 16:29:44 | gmann | I saw in other project stable/train but not nova | |
| 16:30:17 | elodilles | oh, thanks | |
| 16:30:43 | elodilles | cool for nova then | |
| 16:30:55 | bauzas | I guess we can reasonable move on as nothing will change during those days I guess | |
| 16:31:00 | bauzas | nothing actionable I mean, | |
| 16:31:05 | bauzas | but who knows | |
| 16:31:07 | elodilles | ++ | |
| 16:31:28 | bauzas | #topic Sub/related team Highlights | |
| 16:31:42 | bauzas | skipping libvirt's point, as lyarwood is on PTO | |
| 16:31:55 | bauzas | #topic Open discussion | |
| 16:32:09 | bauzas | aaaand that's it, we consumed all the items | |
| 16:32:29 | bauzas | last call for anything anyone | |
| 16:32:46 | gibi | happy PTO everyone! :D | |
| 16:32:56 | sean-k-mooney | o/ | |
| 16:33:18 | gibi | I hope I will be bored at the end of my PTO | |
| 16:33:23 | gmann | \o | |
| 16:34:02 | gmann | gibi: more beer can company you :) | |
| 16:34:11 | gibi | :) | |
| 16:35:34 | bauzas | happy new year for everyone indeed | |
| 16:35:51 | bauzas | safe travels for those who visit family or do leisure | |
| 16:36:01 | bauzas | safe beers for those who stay at home | |
| 16:36:33 | gmann | you too. thanks | |
| 16:36:41 | bauzas | and hopefully, make a wish for 2022 eventually be the time for seeing us together :) | |
| 16:37:40 | bauzas | that being said, let's call it a year. | |
| 16:37:43 | gibi | \o/ | |
| 16:37:46 | bauzas | thanks | |
| 16:37:53 | bauzas | #endmeeting | |
| 16:37:53 | opendevmeet | Meeting ended Tue Dec 14 16:37:53 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:37:53 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2021/nova.2021-12-14-16.00.html | |
| 16:37:53 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2021/nova.2021-12-14-16.00.txt | |
| 16:37:53 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2021/nova.2021-12-14-16.00.log.html | |
| 16:37:55 | opendevreview | mitya-eremeev-2 proposed openstack/nova master: Delete bogus attachments. https://review.opendev.org/c/openstack/nova/+/820935 | |
| 16:40:41 | elodilles | bauzas: thanks \o/ & same to you :) & sorry :S | |
| 16:44:25 | opendevreview | Martin Kopec proposed openstack/nova master: Add check job for FIPS https://review.opendev.org/c/openstack/nova/+/790519 | |
| #openstack-nova - 2021-12-15 | |||
| 04:14:10 | hungnt1 | i have 1 openstack cluster run on production. | |
| 04:14:14 | hungnt1 | i have 1 openstack cluster run on production. | |
| 04:14:18 | hungnt1 | all compute run CPU Intel Xeon Gold 6126 and fixed CPU model for VM is Skylake-Server | |
| 04:14:38 | hungnt1 | now i have 10 new server run CPU Intel Xeon Gold 6330 | |
| 04:14:54 | hungnt1 | How can I check the new CPU compatibility with SkyLake-Server for migration VM ? | |
| 04:14:59 | hungnt1 | can anyone help me ? | |