Earlier  
Posted Nick Remark
#openstack-nova - 2026-04-02
19:02:41 gmaan slot booking?
19:02:57 sean-k-mooney ut im goign to try and see of i can aovid to many conflicts between the nova watcher and cybrog tracks
19:03:10 sean-k-mooney gmaan: ya the session request was a whiel ago
19:03:31 sean-k-mooney but i have not recived the email fro bookign specific slot yet for cybrog
19:03:59 sean-k-mooney but im expecting that to happen in the next week or so
19:04:06 gmaan it is open, I am not sure there will be separate email for that?
19:04:37 gmaan you can see booking happening in #openinfra-events
19:04:44 sean-k-mooney i was told to expect one by sylvian but i guess i can check with allison
19:05:08 sean-k-mooney ok i was waiting for a notifiction i gues i can figure that out next week then
19:05:20 gmaan afaik, once team PTG booking is confirmed, you can book slot anytime
19:05:52 sean-k-mooney ok i need to chnage the ether pad linkes that were auto created
19:06:03 gmaan https://ptg.opendev.org/ptg.html
19:06:03 gmaan many projects already booked
19:06:55 sean-k-mooney ok i was specificly under the impression that the modeerators for each session would be notifed when we can start doing that
19:07:56 sean-k-mooney looks like nova is not there yet ill sync with Uggla next week
19:08:09 gmaan yeah
19:12:35 Uggla sean-k-mooney, I'll book the slot tomorrow, because I'll be on PTO next wwek
19:13:00 sean-k-mooney Uggla: what days were we thinking for the ptg
19:13:34 sean-k-mooney i may have missed it but i was not sure that was dicsussed in the recent irc metting
19:13:52 Uggla I thought about Tue --> Fri
19:14:23 sean-k-mooney ack im condierign doing the actul cyborg ptg on monday or tudesday
19:14:48 sean-k-mooney we coudl do the corss rpoejct session on one of the nova days
19:15:06 sean-k-mooney wathcer is wednesday-friday
19:15:52 sean-k-mooney althoguh firday is shorter due to the tc sessions
19:16:19 Uggla yep expecting to close a bit earlier on friday.
19:16:49 sean-k-mooney ok we can figure it out when your back form pto
19:17:30 sean-k-mooney ill put in some temp cybrog slot on monday and tuesday for now and we can see fi there is a good slot free for the cross project when your back
19:17:42 Uggla sure we will have 1 week to prepare. Right now we have few topics, but I'm pretty sure it will grow next week.
19:18:00 sean-k-mooney i still ned to find time to prepare a small number fo high priroty topics
19:18:54 sean-k-mooney just an fyi one of the things im goign to do is propse a very target spec to chate 2 things in the schduler one fo which si optional to maybe enabel cybrog to do numa in placment before nova does
19:19:36 Uggla ok
19:19:39 sean-k-mooney but i need ot find time to write that up but that was oging to be one of the topci i brought up
19:20:16 sean-k-mooney the other would be the chagne needed to compelte vgpus with cybrog and how nova and cybrog talk to each other
19:20:28 sean-k-mooney those are the 3 general teeme at least
19:20:42 sean-k-mooney we might decied to push the numa topic to a future cycel btu we can see
19:21:46 Uggla btw I don't know if we have requirments to set cross team session ? (beginning of the week ?)
19:22:05 sean-k-mooney we dont but its often better to do
19:22:07 Uggla maybe gouthamr knows about iy ^
19:22:21 sean-k-mooney historically trhey happend on monday
19:22:45 gouthamr yes, monday and tuesday
19:22:50 sean-k-mooney so we coudl do monday between 13-1500
19:23:00 Uggla yeah so maybe I'll book the full week and adapt later.
19:23:00 sean-k-mooney before the tc session start
19:23:44 gmaan Monday 15 - 18 UTC is I see the leader interaction sessions booked
19:24:03 gouthamr we can't get all of it, but, will be good to coordinate and attempt
19:24:03 gouthamr we'll have to email blast this info: "Please try and schedule all cross project meetings at the beginning of the week, preferably by avoiding project-only sessions at the beginning of the week"
19:24:14 sean-k-mooney gmaan: ya the last 3 hours of that slot are the tc ones
19:24:20 gmaan yeah
19:24:43 Uggla gmaan got it, i'll avoid TC of course
19:25:28 sean-k-mooney gouthamr: so taht can be a litte togh if you wnat to try and attend all or as much as possibel fo cybrog nova, watcher and tc seesions
19:26:38 gouthamr always :( but we can try our best.. i think Monday for the TC will also be "forum" style - so we'll def address cross project stuff, even if all of it isn't "governance". I'm going to try to get some TC buy in for this
19:26:47 Uggla sean-k-mooney, I see that as a trend to book x session first.
19:27:46 sean-k-mooney gouthamr: im also tryign to decied if i want to bug a 00UTC slot or not
19:27:51 sean-k-mooney for cybrog.
19:27:53 gouthamr the "community leaders" session will likely be followed by an operators forum.. the specifics are tbd.. i'll also work with hberaud to get the "eventlet-removal" discussion scheduled, likely on tuesday for 1 hour instead of two
19:27:55 opendevreview Clif Houck proposed openstack/nova master: perf(ironic): eliminate O(N²) ProviderTree deepcopy at startup (B6) https://review.opendev.org/c/openstack/nova/+/980676
19:28:20 gouthamr sean-k-mooney: ah you might have some interest since past contributors have been from APAC
19:28:50 sean-k-mooney gouthamr:right that why i was thinking of doing that on monday night and having the main seesion on tuesday
19:29:19 gmaan gouthamr: i think monday 3 hrs is too much for cross projects in TC? unless you are accommodating eventlet kind of topics also
19:30:11 gmaan bcz these 3 hrs will take most of the Monday slots so other cross projects things will be difficult to avoid conflict
19:30:44 gouthamr gmaan: hmm, fair, i could cut that down to two hours if we don't have "cross project" impact. can i take until our next TC meeting (Tuesday) to decide?
19:31:08 gouthamr if that happens, you folks get an extra hour.. if not, i'll promise it'll still be something you'll want to join and participate in
19:32:15 gmaan ++, sure I mean, keeping it for TC is ok, but it will be helpful to know which hrs (out of these 3 hrs) hrs cross projects interaction/topic will be and which hrs TC specific
19:35:27 gouthamr i'll push TC/governance-only discussions to Friday as much as possible
19:36:41 sean-k-mooney well its ok for them ot be on moday
19:37:12 sean-k-mooney its just we have a 2 hour widnow in the eu timeslot but htat a bit early for NA folks
19:37:28 sean-k-mooney so most corss project stuff woudl have to happenon tueday or durign the week
19:37:43 sean-k-mooney unless we do them in the na slots on monday
21:56:38 JayF sean-k-mooney: clif: I'll get https://review.opendev.org/c/openstack/ironic/+/983251 mergable tomorrow or next week, but it should be good enough to get started. Ironic+Nova services start with it enabled. There's a zuul job in there with a devstack config.
21:57:04 clif nice
21:57:40 sean-k-mooney[m] Cool just got to the ironc part of the openinfra live
21:57:53 JayF it's mainly just an ad for the full one next week
22:20:45 sean-k-mooney[m] [JayF_](https://matrix.to/#/@_oftc_JayF_:matrix.org) https://4a2cc9e4719053545829-344a6ad21c722e33f9112420ebbef28e.ssl.cf2.rackcdn.com/openstack/0127c1b07a614bf59b7652d259434573/controller/logs/local_conf.txt will be useful especially with the patch
22:49:09 JayF sean-k-mooney[m]: feel free to give review feedback if it's on my change specifically; if it's an overall pattern then LOOK OVER THERE [/me runs]
22:51:40 sean-k-mooney[m] Some telephone communication vibes.
22:55:52 sean-k-mooney[m] Like instead of CUSTOM_GOLD trait I would expect you to use a CUSTOM_BEARMETAL_GOLD resource class so you can use unified limits of per sku quota and simpler billing
23:28:02 JayF sean-k-mooney[m]: there's no doubt in my mind that some nontrivial % of that is carryover, if there are concrete improvements we can make in the devstack setup that'd be cool
23:28:23 JayF sean-k-mooney[m]: I don't know as much as I should about the nova setup side of Ironic as I should, despite the work I've done on the virt driver, maybe could kill both those birds with one stone
#openstack-nova - 2026-04-03
07:28:14 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: stop using _get_mem_encryption_config() for SEV checks https://review.opendev.org/c/openstack/nova/+/967970
07:28:15 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: make RP creation independent of specific encryption models https://review.opendev.org/c/openstack/nova/+/967972
07:28:15 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: refactor memory encryption trait logic for extensibility https://review.opendev.org/c/openstack/nova/+/967971
07:28:16 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: adjust requirement checks for mem_encryption guests https://review.opendev.org/c/openstack/nova/+/967974
07:28:16 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: refactor _guest_configure_mem_encryption() for extensibility https://review.opendev.org/c/openstack/nova/+/967973
07:28:17 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: address minor issues pointed out in the review https://review.opendev.org/c/openstack/nova/+/983278
07:28:17 opendevreview Taketani Ryo proposed openstack/nova master: mem-enc: introduce a check between mem_encryption and locked_memory https://review.opendev.org/c/openstack/nova/+/971300
13:24:46 TheJulia then the direct tie to op-ex of use. Unfortunately, the venn diagram of the topic has never really yielded solid consensus from the baremetal heavy operators that I've spoken to. :(
13:24:46 TheJulia sean-k-mooney[m]: quick comment looking at the back scroll, there is an interesting and confusing shift we've seen when the topic of billing baremetal has come up, in that I think most take entirely different views on approaches at that cross-over to whole hosts, likely rooted in the shift from op-ex accounting of expenditures and already sunk cost against the prior cap-ex versus the sunk cap-ex cost of just the gear and
13:28:23 sean-k-mooney TheJulia: :) ist more that we recommend encoding model sepcific informationin resouce classes rathre then traits if the reosuce shoudl not be consider interchangable. i.e. if you have 2 dell server skus and form a billing/perfoamce/consumtion point of view you treat them the same because objectivly an end user would not care whic of the two host they got then its ok to share
13:28:25 sean-k-mooney a resouce class but if they are not interchangable they should use diffent resouce classes
13:28:45 sean-k-mooney so the Standard baremental one shoudl really only be used if you only have 1 type of server.
13:28:58 sean-k-mooney or one tyep in a given AZ or regions for example
13:29:02 TheJulia oh, yeah, absolutely, I guess what I'm trying to get across, is people seem to really stop caring about billing baremetal at some point and its weeeeeird.
13:29:14 sean-k-mooney oh ya
13:29:23 sean-k-mooney well at some pont it just power cost as well right
13:29:33 TheJulia OR, they have entirely different models built into their budgets and just roll with that
13:29:39 sean-k-mooney i.e. you run them till they die or you run out of power/rack space
13:29:48 sean-k-mooney ya that too
13:29:50 TheJulia well, power + licenses + support on some level, but yeah
13:30:06 TheJulia oh, and cooling
13:30:53 TheJulia when I ran data centers, getting leadership to accept budgetting for cooling repairs or even improvements was quite literally the hardest problem even with temp sensors, load graphs, power curve and usage calculations

Earlier   Later