| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-04-07 | |||
| 16:07:13 | bauzas | elodilles: ack, you're free to end up early, I bless you :p | |
| 16:07:50 | elodilles | :) | |
| 16:28:40 | bauzas | sean-k-mooney: just sayin', I'll leave the TC room | |
| 16:28:48 | bauzas | and open the nova room | |
| 16:31:26 | sean-k-mooney | ack ok ill swap now | |
| 17:02:42 | bauzas | gibi: ack, no worries, see you tomorrow morning | |
| 17:02:53 | bauzas | as a reminder, we have a cyborg x-p at 8amUTC | |
| 17:03:08 | gibi | ack | |
| 17:03:09 | bauzas | gibi: we'll just wrap the nova sessions tomorrow I think | |
| 17:03:20 | gibi | I will join to the Cyborg session | |
| 17:03:21 | bauzas | just after the neutron topic | |
| 17:03:27 | bauzas | gibi: thanks ! | |
| 17:35:37 | sean-k-mooney | bauzas: i likely will be asleep for the cyborg session. if i am awake ill try and attend but ill read back after most likely. | |
| 17:35:49 | sean-k-mooney | the main topic is just thw owner_ traits | |
| 17:35:50 | sean-k-mooney | right | |
| 17:36:11 | sean-k-mooney | or general topic of how to model some rps are not owned by nova | |
| 17:36:58 | sean-k-mooney | i think we had agreed to add owned_by on all our RPs last cycle but it then never happened | |
| 17:37:31 | sean-k-mooney | we discussed this in relation to generic mdevs | |
| 17:44:15 | sean-k-mooney | https://review.opendev.org/c/openstack/nova-specs/+/836583/3/specs/zed/approved/owner-nova-trait-usage.rst | |
| #openstack-nova - 2022-04-08 | |||
| 01:04:15 | opendevreview | Wenping Song proposed openstack/nova-specs master: Usage of new trait of OWNER_NOVA https://review.opendev.org/c/openstack/nova-specs/+/836583 | |
| 05:45:56 | whoami-rajat | bauzas, hey, we've a topic by sean-k-mooney regarding os-brick rootwrap config , is there a desired time when nova-cinder could meet up? our PTG is conducted 1300-1700 UTC | |
| 07:10:27 | bauzas | whoami-rajat: we can discuss after 14:30UTC I guess, we have a nova-neutron x-p discussion for only one topic at 2pm | |
| 07:45:41 | gibi | morning | |
| 07:58:59 | bauzas | opening the nova-cyborg room | |
| 08:02:24 | bauzas | songwenping__: are you around ? | |
| 08:03:45 | songwenping__ | bauzas: yes | |
| 08:04:21 | bauzas | can you go on https://www.openstack.org/ptg/rooms/newton ? | |
| 08:04:59 | bauzas | songwenping__: ^ | |
| 08:05:00 | songwenping__ | let me try. | |
| 08:09:48 | songwenping__ | bauzas: it's still joining on the website, :( | |
| 08:10:11 | bauzas | songwenping__: ok, are you able to join with the webapp, maybe ? | |
| 08:10:33 | bauzas | you won't then need to install any zoom app | |
| 08:10:34 | songwenping__ | i haven't install the app | |
| 08:53:36 | opendevreview | Takashi Natsume proposed openstack/python-novaclient master: Update pre-commit hook, hacking versions https://review.opendev.org/c/openstack/python-novaclient/+/836768 | |
| 09:03:47 | Uggla | bauzas, only Neutron/nova discussion and the virtiofs point remaining for today ? | |
| 09:04:06 | bauzas | Uggla: and maybe a Cinder discussion too | |
| 09:04:18 | bauzas | I got asked by whoami-rajat | |
| 09:04:39 | Uggla | bauzas, yep I have just seen ^ | |
| 09:11:55 | whoami-rajat | bauzas, I've planned the session for 1430 L#520 https://etherpad.opendev.org/p/zed-ptg-cinder | |
| 09:12:31 | bauzas | whoami-rajat: a bit of warning tho, the session could be a bit late if we can't wrap the neutron discussion after 30 mins | |
| 09:13:04 | whoami-rajat | bauzas, hmm, how about 1500 then? | |
| 09:13:25 | bauzas | whoami-rajat: let's do it | |
| 09:13:55 | bauzas | whoami-rajat: if we're quickier than 1 hour, I have one topic to discuss from Uggla that's left | |
| 09:14:32 | whoami-rajat | bauzas, ack, 1500 makes sense then | |
| 09:14:35 | whoami-rajat | sean-k-mooney, ^^ | |
| 09:15:20 | whoami-rajat | bauzas, I assume the nova team will join the cinder meeting? | |
| 09:16:01 | bauzas | yup | |
| 09:16:44 | bauzas | whoami-rajat: this makes sense, not all nova contributors could be interested in this topic and that's more a cinder stuff | |
| 09:18:14 | whoami-rajat | yeah, that's my understanding as well | |
| 09:18:20 | whoami-rajat | here's the meeting link: meeting link https://bluejeans.com/556681290 | |
| 09:18:28 | whoami-rajat | but i will share again during the discussed time | |
| 09:19:00 | bauzas | whoami-rajat: already setup | |
| 09:19:07 | bauzas | I updated our etherpad | |
| 09:19:49 | whoami-rajat | great | |
| 09:56:54 | sean-k-mooney | bauzas: i have one slight followup form arbiterd | |
| 09:57:20 | sean-k-mooney | bauzas: basically i wanted to ask about hosting it in opendev and or making it a deliverable fo the compute project | |
| 09:59:26 | sean-k-mooney | i.e. if i move it shoudl it be openstack/arbiterd or x/arbiterd the delta woudl be is it under offical governace and a deliverable of the compute team or not. or i could keep it hosted on my github for now where i already have some ci in place for the time being until we have somethign working end to end with openstack and then move it after | |
| 10:00:55 | sean-k-mooney | bauzas: we dont need to make a desission on that today | |
| 10:02:07 | sean-k-mooney | just wanted to know how other feel as there is a non zero amount of wokr i would have to do to make it pti complient amoung other things for move it to openstack/arbiterd even though that is where i eventually would like to see it be in a year or so | |
| 10:04:48 | kashyap | stephenfin: sean-k-mooney: gibi: Don't look at the newer CPU APIs patch yet, I've accidentally undid some changes during rebase. (I'll also splitting the patches once I post the monolithic patch with rebase fixed.) | |
| 10:05:07 | bauzas | sean-k-mooney: ack, we'll see then | |
| 10:05:08 | sean-k-mooney | ack | |
| 10:05:45 | sean-k-mooney | i likely wont look until monday but ill try to review it then | |
| 10:06:11 | sean-k-mooney | if there is a section in partcalar you want me to look at before then jsut ping me | |
| 10:06:20 | kashyap | Yep | |
| 10:12:01 | gibi | kashyap: ack | |
| 12:14:21 | opendevreview | Merged openstack/python-novaclient master: Update pre-commit hook, hacking versions https://review.opendev.org/c/openstack/python-novaclient/+/836768 | |
| 13:05:11 | Uggla | Quick question: anyway to get and see libvirt driver capabilities on a running devstack ? | |
| 13:08:54 | sean-k-mooney | am they get converted to traits in placment | |
| 13:09:07 | sean-k-mooney | i think you could also see them in the db | |
| 13:09:25 | sean-k-mooney | likely on the compute node record in the cell1 db in your case | |
| 13:11:27 | Uggla | sean-k-mooney, I'm gonna have a look | |
| 13:22:34 | Uggla | sean-k-mooney, I find my traits in placement. | |
| 13:23:00 | Uggla | sean-k-mooney, but not in cell1, I may not look at the right place | |
| 13:24:58 | sean-k-mooney | it might just be in memory i belive the resouce tracker has this info in the host state object | |
| 13:25:06 | sean-k-mooney | which its usign for schduling | |
| 13:27:14 | sean-k-mooney | its not in compute nodes and i dont see any other table that would hold it | |
| 13:28:46 | sean-k-mooney | no | |
| 13:28:57 | sean-k-mooney | it looks like its just in memory in the driver | |
| 13:29:06 | sean-k-mooney | and we are usign the traits for schduleing | |
| 13:30:18 | sean-k-mooney | oh | |
| 13:30:19 | sean-k-mooney | https://github.com/openstack/nova/blob/master/nova/scheduler/filters/compute_capabilities_filter.py#L34-L66= | |
| 13:30:30 | sean-k-mooney | so its using the stats field | |
| 13:32:19 | Uggla | sean-k-mooney, https://paste.openstack.org/show/bj273VR3I4dh787TCSV6/ is it the capabilities my compute have currently ? | |
| 13:32:27 | artom | Uggla, we do `self.driver.capabilities.get('blah', False) in a bunch of places, is that what you mean? | |
| 13:33:19 | sean-k-mooney | Uggla: not just capablities | |
| 13:33:54 | sean-k-mooney | teh traits that are reported are a combanition of a few different things | |
| 13:34:34 | Uggla | artom, not really I just would like to know if there is a easy way to display the capabilities. Just to make sure that COMPUTE_STORAGE_VIRTIO_FS is available on my compute. | |
| 13:35:00 | sean-k-mooney | no there is not | |
| 13:35:11 | sean-k-mooney | they are only stored in memmory i think | |
| 13:35:16 | artom | Uggla, as a user (vs Python code)? Then yeah, you want to look at the traits of the corresponding resource provider | |
| 13:35:20 | artom | sean-k-mooney, wait, what? | |
| 13:35:48 | artom | Oh, is the capability not converted into a trait (yet?) | |
| 13:36:10 | sean-k-mooney | in this case likely not sicne we have not merged the standard trait | |
| 13:36:34 | sean-k-mooney | so placement shoudl reject it unless Uggla has used their modified version | |
| 13:36:49 | Uggla | yep I use my modified version | |
| 13:37:00 | Uggla | placement seems happy with it. | |
| 13:37:04 | sean-k-mooney | in which case you shoudl see it in the placment output | |
| 13:37:17 | sean-k-mooney | then ya that is the best you can do | |
| 13:37:32 | Uggla | placement output is log ? | |