Earlier  
Posted Nick Remark
#openstack-nova - 2022-05-25
15:49:23 opendevreview Ghanshyam proposed openstack/nova stable/victoria: DNM: testing Tempest pin in stable/victoria https://review.opendev.org/c/openstack/nova/+/843301
16:14:35 opendevreview Merged openstack/nova stable/xena: Fix pre_live_migration rollback https://review.opendev.org/c/openstack/nova/+/836015
16:33:37 stephenfin gibi: +2 on the PCI spec. Nice work
17:15:36 sean-k-mooney melwitt: im doing a fully review fo the pci spec which is why its taking a while not just the detals
17:15:42 sean-k-mooney so far all good
17:16:11 sean-k-mooney but do you want me to levae the +w to you or will i send it on its way assuming im happy with it when i get to the end
17:16:45 melwitt sean-k-mooney: no feel free to +W :)
17:26:00 sean-k-mooney ack it shoudl be sitting in the zuul pipeline now
17:28:45 sean-k-mooney ok im going to swap to my personal laptop and work on some minor patch updates so ill be off irc for the rest or the day. ill leave my client open but ill chat to people tomrrow
17:32:06 opendevreview Miguel Lavalle proposed openstack/os-vif master: Delete trunk bridges to avoid race with Neutron https://review.opendev.org/c/openstack/os-vif/+/841499
17:33:09 opendevreview Erlon R. Cruz proposed openstack/nova stable/wallaby: Adds regression test for bug LP#1944619 https://review.opendev.org/c/openstack/nova/+/838332
17:36:10 opendevreview Erlon R. Cruz proposed openstack/nova stable/wallaby: Adds regression test for bug LP#1944619 https://review.opendev.org/c/openstack/nova/+/838332
17:38:04 opendevreview Merged openstack/nova-specs master: PCI device tracking in Placement https://review.opendev.org/c/openstack/nova-specs/+/791047
18:12:56 opendevreview Ghanshyam proposed openstack/nova stable/ussuri: DNM: Testing stable/ussuri with tempest fix for constraints mismatch https://review.opendev.org/c/openstack/nova/+/843046
18:51:51 opendevreview Artom Lifshitz proposed openstack/nova stable/xena: Reproduce live migration rollback w/o multi port bindings error https://review.opendev.org/c/openstack/nova/+/843336
18:52:01 opendevreview Artom Lifshitz proposed openstack/nova stable/xena: Fix LM rollback w/o multi port bindings extension https://review.opendev.org/c/openstack/nova/+/843337
18:52:37 opendevreview Artom Lifshitz proposed openstack/nova stable/wallaby: Reproduce live migration rollback w/o multi port bindings error https://review.opendev.org/c/openstack/nova/+/843338
18:52:38 opendevreview Artom Lifshitz proposed openstack/nova stable/wallaby: Fix LM rollback w/o multi port bindings extension https://review.opendev.org/c/openstack/nova/+/843339
21:33:11 opendevreview Miguel Lavalle proposed openstack/os-vif master: Delete trunk bridges to avoid race with Neutron https://review.opendev.org/c/openstack/os-vif/+/841499
#openstack-nova - 2022-05-26
07:56:11 songwenping_ sean-k-mooney:can we support multi-create vgpu vms?
09:35:02 gibi kashyap: I played with a fedora36 container but I cannot reproduce the slow pip resolving issue either there
09:35:45 gibi so I think you might have extra python3- packages installed that creates some version confusion
09:35:59 gibi it should now do it
09:36:04 gibi as venv is separate
09:36:08 gibi but I have no other ideas
09:40:46 sean-k-mooney songwenping: no that is not supported
09:41:00 sean-k-mooney songwenping: we do not suppport multi create with nested resouce providres
09:42:01 sean-k-mooney songwenping: https://bugs.launchpad.net/nova/+bug/1874664
09:42:49 sean-k-mooney songwenping: actully it looks like the patches are merged
09:43:01 sean-k-mooney https://review.opendev.org/c/openstack/nova/+/723884/ and https://review.opendev.org/c/openstack/nova/+/723858/
09:45:20 sean-k-mooney songwenping: i dont think this fully resolves the issue bauzas ^
09:46:28 sean-k-mooney songwenping: ya reading them we only added documentation and test to show that it does not work in some cases
09:46:44 sean-k-mooney so form the comit
09:46:47 sean-k-mooney - you can ask for a flavor with 2 VGPU with --max 2
09:46:49 sean-k-mooney - but you can't ask for a flavor with 4 VGPU and --max 2
09:47:23 kashyap gibi: Hey, thanks a ton for trying! Also, what do you mean by "it should now do it as venv is separate"? I can't quite parse it :)
09:47:31 kashyap Pls rephrase it
09:47:55 gibi tox should build a new virtual env that is sealed off from python packages on the host
09:49:02 kashyap Yeap; thanks!
09:49:18 gibi interestingly the dockerfile in the bugreport shows the issue to me but my dockerfile doesn't
09:49:24 gibi craxy
09:53:03 opendevreview Rajat Dhasmana proposed openstack/nova-specs master: Repropose volume backed server rebuild spec https://review.opendev.org/c/openstack/nova-specs/+/840155
09:54:09 whoami-rajat sean-k-mooney, ^^ updated the spec
09:57:34 sean-k-mooney whoami-rajat: thanks ill review it shortly
09:57:52 whoami-rajat thanks!
10:28:07 songwenping sean-k-mooney: no, not this bug.
10:28:54 sean-k-mooney songwenping: are you refering to creating a vm with multipel vgpus?
10:28:57 songwenping i create two vms with flavor that has 1 vgpu metadata
10:29:09 sean-k-mooney ok
10:29:44 songwenping libvirt allocate the same vgpu for these two vms
10:29:47 sean-k-mooney we only support doing that via 2 differnt api request today
10:30:12 sean-k-mooney we do not supprot creating 2 vms that use vgpus in the same api request
10:30:37 songwenping does the api check the request?
10:30:44 sean-k-mooney no
10:30:54 sean-k-mooney we will not block it at the api
10:31:20 sean-k-mooney we docuement it in the api as part of the previous bug
10:31:57 songwenping why donot we block it at api?
10:31:59 sean-k-mooney gibi: speaking of which if you use pci device in placment for now at least multi create will not work for the same reason
10:32:12 sean-k-mooney songwenping: becuase at the api we dont know fi it uses nested resouce provder or not
10:32:27 sean-k-mooney so we documented the limistaion
10:32:57 songwenping could you please find the doc?
10:35:18 sean-k-mooney songwenping: https://docs.openstack.org/nova/yoga/admin/virtual-gpu.html#caveats
10:36:59 sean-k-mooney we added this section https://review.opendev.org/c/openstack/nova/+/723884/6/doc/source/admin/virtual-gpu.rst
10:37:19 sean-k-mooney we coud make that more clear that we do not support multi creat a all but that is our current stnace
10:37:35 sean-k-mooney if a server uses neste reseouce proverder we do not support multi create
10:38:13 sean-k-mooney this applys to vgpu, cyborg, neuton bandwith or packet per second qos or any other usage of resouce form nested resouce providers
10:38:25 sean-k-mooney like pmem
10:50:54 opendevreview Rajesh Tailor proposed openstack/nova master: Fix typos https://review.opendev.org/c/openstack/nova/+/843127
10:50:54 songwenping sean-k-mooney: i see, thanks.
10:59:38 gibi sean-k-mooney: I don't have the context why the multi create fail on nested allocations but I can take a look later
11:00:19 sean-k-mooney gibi: we just dont have any code for it to handel mappign the allcoation to the differnt instance properly
11:00:55 sean-k-mooney we woudl need to do multipel placment queries and orchstrate that in the schduler
11:00:56 gibi hm, I thought that normal multicreate uses the alternatives from the scheduler
11:01:47 sean-k-mooney it does i think but apprently that is not enough
11:02:21 sean-k-mooney this has basicaly never worked if you have nested rps
11:02:25 sean-k-mooney it work fine if you dont
11:04:54 kevko Hi nova team !
11:05:15 kevko I would like to ask if there is any chance to do something as i will describe below :
11:06:01 kevko I really would like to schedule 2 instances in server group with anti-affinity policy to be scheduled to different host but also in different datacentre (or az)
11:06:35 kevko something similar as it is here
11:06:45 kevko https://specs.openstack.org/openstack/nova-specs/specs/rocky/implemented/complex-anti-affinity-policies.html
11:07:06 kevko instead of max_server_per_host key should be something as max_server_per_az
11:07:20 sean-k-mooney kevko: that is not currently possibel or trivial to do
11:07:39 kevko yeah, i was checking code :/
11:07:44 sean-k-mooney the request spec currently modles an az requst as a string
11:07:56 kevko it's mainly because of octavia and two datacentres ..
11:08:02 sean-k-mooney it cant accpet a list of stings so you cant do that in a singel request
11:08:22 sean-k-mooney kevko: in the past we have declared this out of scope of nova
11:08:36 sean-k-mooney kevko: as somethign a higher level orchestrator shoudl mange
11:08:48 kevko hmm
11:09:14 kevko it's mainly because of octavia loadbalancers ..
11:09:30 sean-k-mooney yep so octavia coudl orchestrate this
11:09:54 sean-k-mooney they already mange the vm creation
11:09:59 sean-k-mooney via calling nova
11:10:09 sean-k-mooney so they could make requsts with differnt AZs
11:11:04 sean-k-mooney i woudl have ot refresh my memory of server goups but i cant recall if you can add more server to the group in later request or not
11:11:21 sean-k-mooney if you can you could just group the loadbalnce request per AZ
11:12:01 kevko i am not sure if I understand
11:13:08 sean-k-mooney i was trying to recall if you needed to populate the server group in one go or coudl you make multiple server create request and resuse the same server group
11:13:12 sean-k-mooney i think its the latter

Earlier   Later