| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-04-08 | |||
| 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 ? | |
| 13:37:32 | sean-k-mooney | the capabliteis are only sotred in memory from what i can see in the dirver | |
| 13:37:52 | sean-k-mooney | last line of https://paste.openstack.org/show/bj273VR3I4dh787TCSV6/ | |
| 13:38:03 | sean-k-mooney | but you can also get that from the api | |
| 13:38:15 | sean-k-mooney | using openstack client if you need too with the osc-placement plugin | |
| 13:39:04 | sean-k-mooney | anyway your code is correctly reporting to placment that the host ia capable of supportign virtio fs | |
| 13:43:44 | Uggla | https://paste.openstack.org/show/b9aK9NbdS1ja4hxwmP8E/ | |
| 13:43:51 | Uggla | from osc | |
| 13:47:00 | artom | Yeah, looks good, congrats :) | |
| 13:48:17 | Uggla | I'm gonna try to activate fileback memory | |
| 13:48:35 | Uggla | to see if it is reported... | |
| 13:51:31 | Uggla | sean-k-mooney, is it normal to have COMPUTE_ACCELERATORS reported ? | |
| 13:54:19 | sean-k-mooney | yes | |
| 13:54:30 | sean-k-mooney | the traits are what nova can do not what the host can do | |
| 13:54:59 | sean-k-mooney | COMPUTE traits are not about hardware they are about nova/libvirts capablities | |
| 13:56:08 | artom | ... which is sometimes about hardware ;) | |
| 14:00:07 | elodilles | heads up from me: i can't attend the nova session today (at least the 1st hour or so) as i need to be at the release mgmt session o:) | |
| 14:01:33 | bauzas | nova-neutron meeting | |
| 14:01:36 | bauzas | by now | |
| 14:02:00 | bauzas | Nova PTG sessions start now https://www.openstack.org/ptg/rooms/newton | |
| 14:02:09 | bauzas | sean-k-mooney: joining ? | |
| 14:04:05 | sean-k-mooney | oh yes one sec | |
| 14:58:55 | whoami-rajat | bauzas, hey, is the nova team ready for the nova-cinder topic? | |
| 14:59:42 | bauzas | whoami-rajat: we're a bit late and ending nova-neutron call | |
| 14:59:54 | bauzas | whoami-rajat: are you ok if we arrive in 5 mins ? | |
| 15:00:25 | whoami-rajat | bauzas, sure, we're on a break as well | |
| 15:00:38 | bauzas | whoami-rajat: cool, I'll ping you once we're done | |
| 15:00:48 | whoami-rajat | bauzas, ack, thanks | |
| 15:06:06 | bauzas | whoami-rajat: in the session :) | |
| 15:24:59 | sean-k-mooney | bauzas: can ye hear me ok by the way | |
| 15:25:14 | bauzas | 5 secs ago yeah | |
| 15:25:21 | sean-k-mooney | ok im not speaking | |
| 15:39:00 | stephenfin | sean-k-mooney: Sorry, should have piped up sooner with the patch. I didn't realise we were meeting again today (or that you were planning to talk about this /o\) | |
| 15:43:18 | sean-k-mooney | no worreis | |
| 15:46:05 | bauzas | folks, hope you still have energy for one last round of nova discussions | |
| 15:47:26 | gibi | make it quick :) | |
| 15:53:28 | bauzas | gibi: we share the same timezone, hence sharing the same concern | |
| 15:53:47 | bauzas | Friday 6pm discussions aren't productive | |
| 15:54:18 | artom | bauzas, so, talking to Uggla earlier 1:1, I did have a question around scheduling virtio-fs-enabled instances, and figured it would be a nice PTG discussion | |
| 15:54:25 | artom | But I'm not forcing anyone :) | |
| 15:54:55 | opendevreview | Stephen Finucane proposed openstack/nova master: db: Narrow down deprecation warning filter https://review.opendev.org/c/openstack/nova/+/837154 | |
| 15:54:55 | opendevreview | Stephen Finucane proposed openstack/nova master: db: Trivial rewrapping of warning filters https://review.opendev.org/c/openstack/nova/+/837155 | |
| 15:54:56 | opendevreview | Stephen Finucane proposed openstack/nova master: db: Replace use of strings in join, defer operations https://review.opendev.org/c/openstack/nova/+/837156 | |
| 15:54:56 | opendevreview | Stephen Finucane proposed openstack/nova master: db: Remove use of empty 'and_()' https://review.opendev.org/c/openstack/nova/+/837157 | |
| 15:54:57 | opendevreview | Stephen Finucane proposed openstack/nova master: db: Replace use of Connection.connect() method https://review.opendev.org/c/openstack/nova/+/837158 | |
| 15:54:57 | opendevreview | Stephen Finucane proposed openstack/nova master: db: Remove inplicit coercion of SELECTs https://review.opendev.org/c/openstack/nova/+/837159 | |