Thursday, 2021-04-22

*** mlavalle has quit IRC00:39
*** sapd1 has quit IRC01:12
*** luksky has joined #openstack-nova01:16
*** farice has joined #openstack-nova01:19
*** luksky has quit IRC01:22
*** luksky has joined #openstack-nova01:22
*** luksky has quit IRC01:29
*** k_mouza has joined #openstack-nova02:21
*** k_mouza has quit IRC02:25
*** mkrai has joined #openstack-nova03:45
*** ratailor has joined #openstack-nova04:19
*** rcernin has quit IRC04:22
*** rcernin has joined #openstack-nova04:28
*** k_mouza has joined #openstack-nova04:33
*** k_mouza has quit IRC04:37
*** mkrai_ has joined #openstack-nova04:40
*** mkrai has quit IRC04:42
*** ralonsoh has joined #openstack-nova05:20
*** xinranwang has joined #openstack-nova05:59
*** slaweq has joined #openstack-nova06:12
*** mkrai_ has quit IRC06:13
*** StevenK has quit IRC06:13
*** rcernin has quit IRC06:29
*** StevenK has joined #openstack-nova06:35
*** lpetrut has joined #openstack-nova06:36
gibigood morning06:37
*** dklyle has quit IRC06:48
*** whoami-rajat_ has joined #openstack-nova06:50
*** rcernin has joined #openstack-nova06:59
*** luksky has joined #openstack-nova07:01
*** rcernin has quit IRC07:08
*** rcernin has joined #openstack-nova07:09
*** andrewbonney has joined #openstack-nova07:17
*** macz_ has joined #openstack-nova07:34
*** gokhani has joined #openstack-nova07:34
*** rpittau|afk is now known as rpittau07:34
*** macz_ has quit IRC07:39
*** rcernin has quit IRC07:40
*** tosky has joined #openstack-nova07:49
*** mgoddard has joined #openstack-nova07:49
*** lucasagomes has joined #openstack-nova08:01
*** derekh has joined #openstack-nova08:03
lyarwoodMorning08:04
*** StevenK has quit IRC08:04
sean-k-mooneygibi: im going to go create the plament periodic job now want me to also create patches for the review pirority lable for the nova deliverables while im at it.08:12
*** rcernin has joined #openstack-nova08:14
gibisean-k-mooney: if you know how to do it then please propose it08:16
sean-k-mooneycool ya i do ill propose the patch to project-config repo and add you to the review list08:17
sean-k-mooneythey will want the ptl to sign off on those kind of changes anyway08:17
gibisure, thanks08:18
openstackgerritliuzhuangzhuang proposed openstack/nova master: Fix RBD timeout  https://review.opendev.org/c/openstack/nova/+/78658808:44
*** mkrai has joined #openstack-nova08:45
*** sapd1 has joined #openstack-nova08:58
stephenfinlyarwood: Real easy doc follow-up here for you if you've 2 mins https://review.opendev.org/c/openstack/nova/+/78383008:59
openstackgerritsean mooney proposed openstack/placement master: Add weekly jobs  https://review.opendev.org/c/openstack/placement/+/78750808:59
*** dtantsur|afk is now known as dtantsur09:02
lyarwoodstephenfin: ack'd09:04
stephenfin \o/09:04
stephenfinthanks09:04
gibistephenfin: hi! there are two followups for the device detach series that would need a second set of eyes https://review.opendev.org/c/openstack/nova/+/77891809:15
* stephenfin looks09:15
*** tesseract has joined #openstack-nova09:23
*** tesseract has quit IRC09:28
*** tesseract has joined #openstack-nova09:28
*** k_mouza has joined #openstack-nova09:42
*** avolkov has joined #openstack-nova09:47
stephenfingibi: comments on https://review.opendev.org/c/openstack/nova/+/77891809:54
gibistephenfin: thanks, will look in a bit09:56
openstackgerritStephen Finucane proposed openstack/nova master: network: Remove 'kwargs' from 'get_instance_nw_info'  https://review.opendev.org/c/openstack/nova/+/74487209:58
openstackgerritStephen Finucane proposed openstack/nova master: network: Remove unused 'affect_auto_assigned' parameter  https://review.opendev.org/c/openstack/nova/+/74487109:58
openstackgerritStephen Finucane proposed openstack/nova master: network: Add type hints for various allocate functions  https://review.opendev.org/c/openstack/nova/+/74487009:58
openstackgerritStephen Finucane proposed openstack/nova master: network: Add type hints for deallocate functions  https://review.opendev.org/c/openstack/nova/+/78751609:58
openstackgerritStephen Finucane proposed openstack/nova master: network: More allocate, deallocate type hints  https://review.opendev.org/c/openstack/nova/+/78751709:58
openstackgerritStephen Finucane proposed openstack/nova master: network: Add type hints for attach, detach functions  https://review.opendev.org/c/openstack/nova/+/78751809:58
*** mgoddard has quit IRC10:01
sean-k-mooneygibi: just added you to https://review.opendev.org/q/topic:%22review-priority%22+(status:open%20OR%20status:merged)10:21
sean-k-mooneysome of the placement repos do not have the correct acls defiend so i added those  as a copy of the placment repos config in the second patch10:21
*** rcernin has quit IRC10:22
openstackgerritBalazs Gibizer proposed openstack/placement stable/wallaby: Add a reproduction test for bug story/2008831  https://review.opendev.org/c/openstack/placement/+/78752510:28
openstackgerritBalazs Gibizer proposed openstack/placement stable/wallaby: Make sure the policy upgrade check get a valid config  https://review.opendev.org/c/openstack/placement/+/78752610:28
*** ratailor_ has joined #openstack-nova10:30
*** ratailor has quit IRC10:31
*** k_mouza has quit IRC10:45
*** k_mouza has joined #openstack-nova10:47
gibistephenfin: replied in https://review.opendev.org/c/openstack/nova/+/778918 I agree with your comment. I will respin10:47
*** mkrai has quit IRC10:50
*** rcernin has joined #openstack-nova11:03
*** rcernin has quit IRC11:08
*** sapd1 has quit IRC11:15
openstackgerritBalazs Gibizer proposed openstack/nova master: Move instance power state check to _detach_with_retry  https://review.opendev.org/c/openstack/nova/+/77891811:27
openstackgerritBalazs Gibizer proposed openstack/nova master: Consolidate device detach error handling  https://review.opendev.org/c/openstack/nova/+/77897811:27
gibistephenfin: fixed your comments ^^11:28
gibisean-k-mooney: thanks, I will check them11:28
*** rcernin has joined #openstack-nova11:28
*** rcernin has quit IRC11:33
openstackgerritMerged openstack/nova-specs master: trivial: Fix spelling, formatting of vDPA spec  https://review.opendev.org/c/openstack/nova-specs/+/78126011:40
Dmitrii-Sho/ Looking for some input on a spec: https://review.opendev.org/c/openstack/nova-specs/+/787458. If there is interest, I am open for discussion during the remaining PTG time (via meetpad.opendev.org or other means) or afterwards via gerrit/IRC/email etc. Any feedback would be much appreciated. I added this as a topic to the Nova etherpad11:40
Dmitrii-Shhttps://etherpad.opendev.org/p/nova-xena-ptg - hopefully there will be some time left to discuss it.11:40
openstackgerritMerged openstack/nova master: docs: Follow up for SEV doc  https://review.opendev.org/c/openstack/nova/+/78383011:41
sean-k-mooneylooking at it quickly but form the title this sound complex11:42
*** mkrai has joined #openstack-nova11:44
openstackgerritMerged openstack/nova master: docs: Correct typos in 'nova-manage db' docs  https://review.opendev.org/c/openstack/nova/+/78406711:45
sean-k-mooneyDmitrii-Sh: we are planning to discuss tracking pci device in placement but im not  conviced that what you are suggestign is compatiable with the direction we wanted to take11:46
sean-k-mooneyDmitrii-Sh: you have clearly put a lot of tought into this by the way form the lenght of the spec so this will take some time to digest11:47
Dmitrii-Shsean-k-mooney: I see, I could find ways to adjust it such that it is compatible with the effort to track pci devices in the placement DB.11:48
Dmitrii-ShAs such, part of what I am suggesting for the Nova DB is only there to build the Placement DB state.11:48
sean-k-mooneywe were going to suggest tracking each PF as an RP and having inventories of VF,PF and pci devices11:50
Dmitrii-ShSo I could place the right state into the Placement DB right away but that's to be seen11:50
sean-k-mooneythe pci_devices tabel would still be used to track the slecect of the specific pci device11:50
sean-k-mooneywe dont want to actully have placment select a specifc VF for example11:51
artomDmitrii-Sh, I saw you post the spec last night. I think your biggest problem is that only youself and sean-k-mooney understand any of the hardware bits :P11:52
Dmitrii-Shsean-k-mooney: I see. Do you plan to replace InstancePCIRequests with placement resource requests?11:53
artomDmitrii-Sh, I think a sort of "smartnic for dummies" paragraph (or section) might be useful, just to give the rest of use context on what this thing even is11:53
Dmitrii-Shartom: ty. I tried to make it largely agnostic of a specific vendor and target a class of devices: off-path SmartNICs with a separate (mostly ARM) CPU. There are several vendors out there that follow this pattern.11:55
Dmitrii-Shbut I can add a paragraph discussing it, or even better, a reference to an overview about those11:55
artomI don't want to speak for everyone here, but you have a whole bunch of vocabulary there that isn't accessible to most of us ("switchdev-capable", "off-path")11:55
Dmitrii-ShI guess I should link this then https://netdevconf.info/0x14/pub/slides/39/Netdev%200x14%20--%20Taking%20Control%20of%20your%20SmartNIC%20v1.pdf11:56
sean-k-mooneyDmitrii-Sh: not replace them no but we would also claime resouces in placment for them11:56
artomDmitrii-Sh, yeah, any kind of introduction or reference to what this hardware is and how it's different from the PCI devices that we're used to would be very useful. For me, at least.11:56
artomHopefully for other non-sean-mooney reviewers too11:56
sean-k-mooneyDmitrii-Sh: im not really trielled with nova calling neutron as part fo vif plugging as a clinet11:57
Dmitrii-Shartom: ack, will do. I understand that it's a lot of info to process11:57
sean-k-mooneyeven if that was doen via os-vif11:57
sean-k-mooneyDmitrii-Sh: have you spoken to the cyborg team about this by the way11:58
sean-k-mooneythey were tryign to enable reprogrambel smart nics via a different approch11:58
Dmitrii-Shsean-k-mooney: I've seen their specs but they seem to be targeting FPGA-based on-path NICs (Intel IIRC)11:58
Dmitrii-Shand the approach there is to program NICs from the hypervisor host itself11:59
sean-k-mooneyDmitrii-Sh: primarally11:59
sean-k-mooneyi just wanted to make sure you were aware of it11:59
Dmitrii-Shwhere as here there is a security boundary between the hypervisor host and the SmartNIC host11:59
Dmitrii-Shsean-k-mooney: ack, I am. I wish it addressed the things needed for off-path NICs to avoid fragmentation12:00
sean-k-mooneyso there was an effort to allow the neutron agent to manage remote host in the past12:00
sean-k-mooneywhat you are proposing is closer to that12:00
*** farice has quit IRC12:00
sean-k-mooneyi think we would still want to keep the binding host the same at the ml2 level12:00
sean-k-mooneythe host on which the vm resides12:00
Dmitrii-ShThere was some work in Ironic in the past https://specs.openstack.org/openstack/ironic-specs/specs/approved/support-smart-nic.html12:00
sean-k-mooneybut we may need to have other information that woudl be use to corralate that to the chassis in ovn12:01
Dmitrii-Shas a result neutron-openvswitch-agent started using os-vif to plug representors (but that's not usable outside ironic at the moment)12:01
Dmitrii-Shsean-k-mooney: yes, I think there has to be a mapping table somewhere but I haven't quite decided where yet12:02
sean-k-mooneyDmitrii-Sh: in neutron12:03
sean-k-mooneyi dont think nova should need to know what network backend is being used in this code12:03
Dmitrii-Shsean-k-mooney: this makes sense. Otherwise Nova becomes too aware of a particular ML2 mechanism driver12:03
sean-k-mooneyyep12:03
*** brinzhang has quit IRC12:04
sean-k-mooneyi have only skimmed the spec so i really need to set some time aside to digest it12:04
*** brinzhang has joined #openstack-nova12:04
Dmitrii-Shsean-k-mooney: ok, np, thanks for the early and quick feedback - much appreciated12:04
Dmitrii-Shsean-k-mooney: I am happy to make adjustments to make it work with the ongoing efforts in Nova12:04
*** mkrai has quit IRC12:05
sean-k-mooneyill try and do that relitively soon. if we dont have time in the ptg we coudl set up a call afterward next week or the week after and see who is interested12:05
sean-k-mooneyDmitrii-Sh: have you discussed this with the neutron folks yet?12:05
Dmitrii-Shsean-k-mooney: ty. I think I'm going to hop in during the PCI device tracking in the Placement service discussion (added a note to ping me to the etherpad just in case).12:06
Dmitrii-Shsean-k-mooney: I am working on a Neutron spec at the moment12:06
sean-k-mooneycool12:06
Dmitrii-Shsean-k-mooney: There is some cross-project work to do in Neutron OVN mechanism driver and OVN itself12:06
sean-k-mooneyby the way one hack for the differnt hostname thing you could look at is changhing the [DEFAULT]/host value in the neutronl.conf for the ovs agent of the hostname value in the ovsdb for ovn12:07
sean-k-mooneybasically you could change those values so that you are declaring that you are manaing the network on behalf of host XYZ even if its not running on it12:08
Dmitrii-Shsean-k-mooney: there's a possibility that there will be 2 SmartNICs in one physical host12:09
sean-k-mooneyso assuming the agent/ovn would be runnign on the smart nic you could use the servers hostname for those values12:09
Dmitrii-Shwhich creates an issue with this - I considered it as an initial hack12:09
sean-k-mooneyah right12:09
sean-k-mooneyya that does make things harder12:09
Dmitrii-Shsean-k-mooney: hence the dances with PCI VPD serial numbers12:09
Dmitrii-Shas we don't have another way of tracking which functions belong where on both sides12:10
sean-k-mooneystill i think we coudl encode some info in ovn or the agent config such that the ml2 driver could maintain the mapping12:10
sean-k-mooneyit just wont be as simple12:10
sean-k-mooneyi see one other issue potentaillyu12:10
sean-k-mooneythe pci address will it always be the same form the host vs smartnic perspecitve12:11
Dmitrii-ShDidn't quite catch that. The SmartNIC host sees a different PCIe topology from the hypervisor host12:12
Dmitrii-Shdifferent addresses too12:12
Dmitrii-Shbasically each host does its own PCIe topology enumeration12:12
Dmitrii-Shit's kind of like with blades and non-transparent bridging or managed PCIe switches that hide certain parts of the overall topology12:13
sean-k-mooneyright12:14
sean-k-mooneyso the only thing that we currently pass to neturon to tell it which device we selected is the pci address12:14
sean-k-mooneyfrom the nova-compute agents point of view12:14
Dmitrii-Shyes, and that's the problem in this case12:15
Dmitrii-Shthe ARM host doens't know how the hypervisor host enumerated its topology12:15
sean-k-mooneywe cannot use macs and other info like vendor id and project id are not applicable12:15
Dmitrii-Shdoesn't*12:15
Dmitrii-Shsean-k-mooney: yes12:15
sean-k-mooneyyep so we would need the neuron ml2 driver to translate12:15
sean-k-mooneywe could optionally add some addtional info to the binding profile which i assuem is what you were suggesting12:16
Dmitrii-Shsean-k-mooney: yes, the PCIe VPD serial number could be it. Additionally, we need a way to send a logical number of a VF12:16
Dmitrii-Shto pick the right representor on the other side12:16
Dmitrii-Shthe logical numbers are maintained in the NIC firmware, so presumably they are stable12:16
sean-k-mooneyi think we can discuover both of those statically and put them in the extra_info column12:17
sean-k-mooneythen we can include that in the port update12:17
sean-k-mooneyDmitrii-Sh: i think we can avoid the need for any db schema changes on the nova side12:17
Dmitrii-Shsean-k-mooney: that's one way to do it. I was planning to do the translation based on the relationship of "transport node" RPs (name == VPD serial) and OVN chassis RPs (name == smartnic_hostname).12:18
sean-k-mooneycurrently we only use the extra_info column to store nic features. i was going to store vdpa device paths in them but we removed it12:18
Dmitrii-ShSo, in essence, the Nova schema changes are there to build the Placement state ("transport node" RPs)12:19
Dmitrii-ShI could build this info as devices are discovered and push it to the Placement DB right away12:19
sean-k-mooneywell what we are going to discsus later is create rp for each PCI device as a chiled of the compute node rp with the pci address as the RP name12:20
sean-k-mooneythoguh we were not going to suggest havign an rp per vf just per PF12:20
sean-k-mooneyso the pci device would be in the sub tree of the compute node RP not under the neutron RPs12:21
gibido I understand correctly from above that one VF from this smartnic can be made available to more than one compute node / hypervisor?12:22
Dmitrii-Shsean-k-mooney: *thinking*12:22
sean-k-mooneygibi: ish basiably ovs and either ovn/neutron-l2 agent woudl be running on a smartnic isntalled in a server12:23
sean-k-mooneygibi: on the arm cores runnign linux12:23
gibiso from other perspective do we need to represent this smartnic as a sharing RP in placement or can it be under a given compute RP?12:24
Dmitrii-Shgibi: there is some IO virtualization sharing tech to allow VFs of one device to be selectively shared across different compute nodes (e.g. in a blade). I have some links in the spec to people describing it.12:24
*** brinzhang has quit IRC12:24
gibiDmitrii-Sh: OK, so it is possible12:24
*** brinzhang has joined #openstack-nova12:24
Dmitrii-Shhence I am going for shared resource providers when it comes to representing SmartNICS12:24
Dmitrii-Shmuch like with shared storage12:25
sean-k-mooneyDmitrii-Sh: i think the simpelst thing to do is as follows. 0 do not modify placment for this specifically. 1 add the extra identifiesr to the pci_device extra info column, 2. add that info the the prot profile. 3 modify the ml2 drivers to sotre the coallation beween the ovn chassi name and the device and have it use that value instead12:25
gibiDmitrii-Sh: thanks, I get it12:25
*** sorrison has quit IRC12:26
sean-k-mooneygibi: yep you can do it with connectx-6 cards i think intel were working on it at one point too but no idea if its still a thing they are planning on12:26
*** sorrison has joined #openstack-nova12:26
sean-k-mooneygibi: one of the things i was investigating in the past was  could we move nova-compute to the smart nic too12:26
*** lpetrut_ has joined #openstack-nova12:27
gibithis is crazy talk :D12:27
gibisorry, my brain failed12:27
sean-k-mooneyidea bing you would jsut grab a stanarcd server and install libvirt on it then you would just install an OpenstackPowerd smarntic that rann all the openstack servics in the server and its an instance compute node after some config updates12:27
*** tobias-urdin has joined #openstack-nova12:28
*** tesseract-RH has joined #openstack-nova12:28
sean-k-mooneygibi: in this case they are jsut trying to move the networkign contol plane to the smarnic and not all the contol plane12:28
*** tesseract has quit IRC12:28
gibi... and then at some point that smartnic is connected to two hypervisors and we are back to the one compute host multiple compute node situation :)12:28
sean-k-mooneysame basic idea however just run less stuff on the hypervior host12:28
sean-k-mooneygibi: hehe lol lets hope this and rack scale design never have a baby12:29
*** lpetrut has quit IRC12:29
sean-k-mooneyDmitrii-Sh: by the way os-vif can connect to ovs over tcp to do the pluggin fo the interface into the ovs bridge12:30
Dmitrii-Shsean-k-mooney: I see.  (1) ok, there will be some more info stored per pci_device but that's not too bad (2) ok, this can be done during the port update (3) yes, Neutron would need to look up a hostname of a chassis based on the serial number.12:30
Dmitrii-Shsean-k-mooney: I think os-vif can only use one OVS endpoint12:30
sean-k-mooneyDmitrii-Sh: so we can have os-vif running in the compute agent talk to ovs on the smart nic if it has an ip12:30
Dmitrii-Shsean-k-mooney: comes back to the dual-NIC case12:30
sean-k-mooneyDmitrii-Sh: corrrect today. but you could tell use what endpoitn to connecto to in the binding:detail from the ml2 driver12:31
sean-k-mooneyif we need that12:31
sean-k-mooneye.g. make the config value the defualt and allow it to change per port if needed12:31
sean-k-mooneyDmitrii-Sh: yep so if we take this approch we can still track pci device in placment as a seperat effort without having to take account of the network backend in use12:32
gibihm does this whole thing also suggest that a single neutron-ovs-agent will handle more than on OVS instance (one per smartnic)?12:32
gibis/on OVS/one OVS/12:33
sean-k-mooneyno but we might have multipel ovs agents on the same physical server one running on each smart nic12:33
*** zoharm has joined #openstack-nova12:33
gibiwait, not just the OVS runs on the smartnic but also the neutron agent?12:33
sean-k-mooneygibi: unless we revisit the scaleable ovs agent spec whic intended to od that12:33
sean-k-mooneygibi: well in teh case of ovn theere would be a seperate ovn contoler per smartnic form what i understand12:34
sean-k-mooneyso if we are talking about ml2/ovs i would assume we would have 1 agent per smartnic Dmitrii-Sh is that correct?12:34
Dmitrii-Shsean-k-mooney: ok, I'll have a look at whether something falls over with that approach. One challenge is NIC resource allocation when multiple compute nodes are involved but let's see.12:35
sean-k-mooneygibi: the neturon l2 agent and ovn southd are basically equvlent12:35
Dmitrii-Shsean-k-mooney: yes, 1 per nic12:35
*** belmoreira has joined #openstack-nova12:35
Dmitrii-Shsean-k-mooney: I considered having something crazy that had 1 ARM host but 2 NICs12:35
sean-k-mooneyDmitrii-Sh: can we declare multi host nics out of scope of the inital proposal12:35
Dmitrii-Shbut I haven't seen hw like that12:35
sean-k-mooneyits not crazy i have seen hardware that was designed to work that way12:36
sean-k-mooneyit was a top of rack swtich that had a pcie card that plugged into your servers12:36
sean-k-mooneyeach server tought it was getting a nic but actully it all the nic hardware was on the switch12:36
Dmitrii-ShI guess that would be similar to 1 SmartNIC with PCIe bifurcation? Some lanes go to one CPU, some to another?12:37
sean-k-mooneykind of yes12:37
Dmitrii-Shso, in this case, there would be 2 PFs exposed to the hypervisor host under different root complexes12:38
*** happyhemant has joined #openstack-nova12:38
Dmitrii-Shand the NUMA node association of PFs (and their VFs) would be based on that too12:38
sean-k-mooneybasically it was a ginant pcie switch on one end that connectd to multiple hosts and then a ether net switch on the other12:38
sean-k-mooneyDmitrii-Sh: ya you can do the pci biforcation with mellonox connetx5 today12:39
*** hamalq has joined #openstack-nova12:39
sean-k-mooneythey have a 200G sku that has 2x 16 connectors that can connect to 2 different cpus12:39
sean-k-mooneyit get 2 PFs and the VF can float between them12:39
Dmitrii-Shsean-k-mooney: yes, there's a special connector on the NIC and an add-in card that plugs to a different topology12:40
Dmitrii-Shand the NIC is smart enough to use 2 sets of lanes differently12:40
sean-k-mooneyyep hardware vendors make software enginers look sane12:40
Dmitrii-Shsean-k-mooney: :^D12:41
gibilol12:41
Dmitrii-Shsean-k-mooney: ok, I am aiming to make the design extensible such that those things can be supported but I will avoid focusing on it for the initial proposal then12:42
Dmitrii-Shit's just very difficult to extend it later as I see it12:42
sean-k-mooneyi spent quite a lot of my time at intel dealing with topic like this which is why this seam like a realitvly normal request to me12:42
sean-k-mooneyDmitrii-Sh: ya i think that multi host nics proably need cyborg to manage well12:43
Dmitrii-Shsean-k-mooney: good thing you did, otherwise my requests would look insane12:43
sean-k-mooneyDmitrii-Sh: same as remove nic over a pcie fabric12:43
sean-k-mooneyDmitrii-Sh: we were looking at this problem space when we were looking at how to integrate a rackscale design composeable server with nova12:44
sean-k-mooneyDmitrii-Sh: basicaly i wanted to allow create a composable physical server form disaggreated devices (nics, storage, gpus, fpga) via a new nova virt driver12:45
sean-k-mooneyso it would be like creating a vm but with realy hardware using a pcie/rdma based frabric12:45
Dmitrii-Shsean-k-mooney: right, I've seen some hw like this with 1U PCIe switches and composable topologies12:46
sean-k-mooney:( we never pushed it publically. i thought it was on https://github.com/intel-orchestration-software but we did boot a node with a poc virt driver internally12:48
Dmitrii-Shsean-k-mooney: I think I came across this (but haven't had this in a lab): https://gigaio.com/products/12:50
sean-k-mooneyDmitrii-Sh: i think we both have a lot to digest. can you add the topic to the end of https://etherpad.opendev.org/p/nova-xena-ptg12:51
sean-k-mooneyas i said if we dont get to it im happy to review and we could set up a call or somehting in a week or too if needed12:51
sean-k-mooneyoh its already there12:52
sean-k-mooneyTransport Node bp/spec RFC and this topic dont really seam realted to me12:52
sean-k-mooneybut i see where you were comign form12:52
gibiDmitrii-Sh: thanks for the well written spec, I forwarded it to my downstream counterparts to see if my company is also interested in solving these use case. I agree with Sean about trying to get to this on the PTG but it might not fit into the timeframe.12:56
Dmitrii-Shsean-k-mooney: yes, added it a little earlier to the etherpad13:01
Dmitrii-Shsean-k-mooney: the gigaio stuff is unrelated, yes, just sharing what I've seen :^)13:01
Dmitrii-Shgibi: thanks a lot, much appreciated13:02
sean-k-mooneyDmitrii-Sh: im adding a summery of what i think the problem statemnt is and a sumamry of what i was propsing as an alternitve desing.13:02
sean-k-mooneyfeel free to extend of correct eitehr13:02
*** ratailor_ has quit IRC13:03
sean-k-mooneyim also addig a link to the irc logs of this conversation if peopel want to review it13:03
*** avolkov has quit IRC13:04
*** artom has quit IRC13:04
*** avolkov has joined #openstack-nova13:05
*** artom has joined #openstack-nova13:05
Dmitrii-Shsean-k-mooney: hmm, all the colors are gone from the etherpad13:06
Dmitrii-Shat least for me13:06
sean-k-mooneydont press contol shift c13:06
sean-k-mooneyyep i had the wrong window slected and ctrl-shift-c is apparently clear all colors13:07
sean-k-mooneyi contol z it and it dissconnected me13:07
sean-k-mooneyso ya i cant revert it it seams13:07
sean-k-mooneythey are here https://etherpad.opendev.org/p/nova-xena-ptg/timeslider#2463513:08
*** Luzi has joined #openstack-nova13:09
*** mgoddard has joined #openstack-nova13:09
Dmitrii-Shsean-k-mooney: right, haven't found a way to revert yet13:10
sean-k-mooneyi think the only way would be contrl z but i dont think that will work now13:10
sean-k-mooneywhich suck but ya13:11
sean-k-mooneyim going to add that as a warning to the top of the doc13:11
sean-k-mooneyits a really bad keyboard shortcut to choose13:11
*** luksky has quit IRC13:14
*** luksky has joined #openstack-nova13:14
*** brinzhang_ has joined #openstack-nova13:14
*** sapd1 has joined #openstack-nova13:16
*** k_mouza has quit IRC13:22
*** k_mouza_ has joined #openstack-nova13:22
*** k_mouza_ has quit IRC13:22
*** ratailor has joined #openstack-nova13:22
*** k_mouza has joined #openstack-nova13:23
sean-k-mooneyDmitrii-Sh: ok im done summerising it. im goingt to go take a walk and clear my head before the ptg resumes. o/13:25
Dmitrii-Shsean-k-mooney: tyvm, I'll have a look in 20-30 mins and adjust if needed13:25
*** avolkov has quit IRC13:26
*** rcernin has joined #openstack-nova13:29
*** k_mouza has quit IRC13:30
*** k_mouza has joined #openstack-nova13:31
*** k_mouza has quit IRC13:31
*** k_mouza has joined #openstack-nova13:32
openstackgerritMerged openstack/nova master: glance: Improve [glance]enable_rbd_download and associated options help text  https://review.opendev.org/c/openstack/nova/+/78565613:32
*** rcernin has quit IRC13:34
*** k_mouza_ has joined #openstack-nova13:37
*** k_mouza has quit IRC13:40
*** lpetrut_ has quit IRC13:45
*** brinzhang_ has quit IRC13:50
* bauzas definitely needs a coffee13:53
*** priteau has quit IRC13:53
*** k_mouza has joined #openstack-nova13:55
*** k_mouza has quit IRC13:56
*** k_mouza has joined #openstack-nova13:56
stephenfingibi: Might be a few minutes late. Having internet woes :-(13:58
*** k_mouza_ has quit IRC13:58
gibistephenfin: ack13:58
*** k_mouza has quit IRC14:01
*** k_mouza has joined #openstack-nova14:02
*** mgoddard has quit IRC14:06
gibibelmoreira: we are talking about emulating guest archs14:07
gibiin the nova room now14:07
*** tesseract-RH has quit IRC14:07
belmoreirathanks gibi. Unfortunately, I can't join right now (I'm in the TC meeting).14:08
gibibelmoreira: OK, I think I'm aware of your viewpoint so I can represent it14:09
belmoreirathanks gibi14:09
*** tesseract has joined #openstack-nova14:10
*** k_mouza_ has joined #openstack-nova14:11
*** k_mouza_ has quit IRC14:12
*** k_mouza_ has joined #openstack-nova14:13
*** k_mouza has quit IRC14:14
*** k_mouza_ has quit IRC14:19
*** k_mouza has joined #openstack-nova14:20
stephenfinralonsoh: we'll be talking about networking-related stuff in nova shortly, if you can join. If not, we can skip them and come back when you're free?14:21
*** k_mouza_ has joined #openstack-nova14:22
ralonsohstephenfin, thanks! joining now14:22
*** k_mouza has quit IRC14:25
*** mkrai has joined #openstack-nova14:34
stephenfinDmitrii-Sh: fwiw, we'll be talking about PCI device tracking in placement in 5-10 minutes if you're not already on the meeting14:38
gibistephenfin: thanks for pinging people :)14:38
Dmitrii-Shstephenfin: ty for the ping, I'll try to sneak out and join for that14:39
*** ratailor has quit IRC14:39
*** k_mouza_ has quit IRC14:46
*** k_mouza has joined #openstack-nova14:47
*** macz_ has joined #openstack-nova14:50
*** macz_ has quit IRC14:51
*** macz_ has joined #openstack-nova14:51
*** dklyle has joined #openstack-nova14:52
slaweqgibi: lbragstad: hi, will the session about RBAC and system scope tokens be in Keystone or Nova's room?14:57
slaweqI see in the https://etherpad.opendev.org/p/policy-popup-xena-ptg that it's in Mitaka which seems to be Keystone session14:57
slaweqbut on the ptg.openstack.org I see that it may also be in the Nova's room14:58
*** xinranwang has quit IRC14:59
gibi:/14:59
gibigood question14:59
gibilets have it in the Mitaka room14:59
slaweqgibi: great15:00
gibiI will push the people from the nova room to the keystone one15:00
slaweqthat's what I told in the Neutron session few minutes ago :)15:00
slaweqgibi++15:00
lbragstadslaweq keystone i think15:03
*** mkrai has quit IRC15:10
*** __ministry1 has joined #openstack-nova15:11
*** k_mouza has quit IRC15:13
*** k_mouza_ has joined #openstack-nova15:13
*** k_mouza has joined #openstack-nova15:21
*** mgoddard has joined #openstack-nova15:22
*** k_mouza_ has quit IRC15:25
*** happyhemant has quit IRC15:26
*** rcernin has joined #openstack-nova15:30
*** mkrai has joined #openstack-nova15:30
*** rcernin has quit IRC15:35
*** __ministry1 has quit IRC15:36
*** mgoddard has quit IRC15:49
*** brinzhang_ has joined #openstack-nova15:55
*** brinzhang has quit IRC15:58
openstackgerritLee Yarwood proposed openstack/nova master: zuul: Replace grenade and nova-grenade-multinode with grenade-multinode  https://review.opendev.org/c/openstack/nova/+/77888515:58
openstackgerritLee Yarwood proposed openstack/nova master: zuul: Remove nova-dsvm-multinode-base  https://review.opendev.org/c/openstack/nova/+/77890815:58
*** mkrai has quit IRC16:01
*** tesseract has quit IRC16:02
*** gokhani has quit IRC16:03
*** hamalq has quit IRC16:06
*** lucasagomes has quit IRC16:09
*** Luzi has quit IRC16:15
*** gyee has joined #openstack-nova16:17
bauzasgibi: back on the nova room when it's 16:25pm UTC, right ?16:18
* bauzas feels lost in translation16:18
dansmithwhat is the next nova topic?16:18
gibiright16:19
gibidansmith: 18:17 < gibi> #nova next pci device attach/detach api?16:19
dansmithgibi: ah, sorry, but thanks :)16:19
*** slaweq_ has joined #openstack-nova16:20
gibiI'm trying to keep http://ptg.openstack.org/ptg.html up to date via the ptgbot16:20
dansmithgibi: ah yeah I hadn't seen the coming up next section used yet, that's nice16:21
openstackgerritMerged openstack/nova master: libvirt: Remove dead error handling code  https://review.opendev.org/c/openstack/nova/+/77970416:30
*** derekh has quit IRC17:02
*** andrewbonney has quit IRC17:04
*** aarents has quit IRC17:06
*** ralonsoh has quit IRC17:08
*** k-s-dean has quit IRC17:11
*** zoharm has quit IRC17:21
*** dtantsur is now known as dtantsur|afk17:22
*** rpittau is now known as rpittau|afk17:24
*** boxiang_ has joined #openstack-nova17:39
*** k_mouza has quit IRC17:39
*** k_mouza has joined #openstack-nova17:40
*** elod_ has joined #openstack-nova17:43
*** smcginni1 has joined #openstack-nova17:44
*** sapd1 has quit IRC17:48
*** elod has quit IRC17:48
*** mgariepy has quit IRC17:48
*** smcginnis has quit IRC17:48
*** boxiang has quit IRC17:48
*** kopecmartin has quit IRC17:48
*** eharney has quit IRC17:49
*** k_mouza has quit IRC17:49
*** k_mouza has joined #openstack-nova17:49
*** sapd1 has joined #openstack-nova17:54
*** eharney has joined #openstack-nova17:55
*** mgariepy has joined #openstack-nova17:55
*** lbragstad_ has joined #openstack-nova18:29
*** lbragstad has quit IRC18:32
*** k_mouza_ has joined #openstack-nova18:32
*** k_mouza_ has quit IRC18:34
*** k_mouza_ has joined #openstack-nova18:34
*** k_mouza has quit IRC18:35
*** dklyle has quit IRC18:36
*** mgoddard has joined #openstack-nova18:41
*** elod_ is now known as elod18:44
*** dklyle has joined #openstack-nova18:45
*** k_mouza has joined #openstack-nova18:49
*** k_mouza_ has quit IRC18:53
*** mgoddard has quit IRC18:56
*** k_mouza has quit IRC19:00
*** k_mouza has joined #openstack-nova19:01
*** k_mouza has quit IRC19:03
*** k_mouza has joined #openstack-nova19:04
*** k_mouza_ has joined #openstack-nova19:18
*** k_mouza has quit IRC19:22
*** belmoreira has quit IRC19:25
*** slaweq_ has quit IRC19:30
*** rcernin has joined #openstack-nova19:31
*** whoami-rajat_ is now known as whoami-rajat19:33
*** k_mouza_ has quit IRC19:36
*** rcernin has quit IRC19:36
*** k_mouza has joined #openstack-nova19:36
*** k_mouza_ has joined #openstack-nova19:37
*** k_mouza has quit IRC19:41
*** k_mouza_ has quit IRC19:48
*** arne_wiebalck has quit IRC19:51
*** yonglihe has quit IRC19:51
*** lbragstad_ is now known as lbragstad19:56
*** yonglihe has joined #openstack-nova19:57
*** arne_wiebalck has joined #openstack-nova19:57
*** iurygregory has quit IRC19:59
*** hamalq has joined #openstack-nova20:10
*** k-s-dean has joined #openstack-nova20:36
*** slaweq has quit IRC20:44
*** rcernin has joined #openstack-nova20:45
*** k_mouza has joined #openstack-nova20:45
*** k_mouza has quit IRC20:45
*** k-s-dean has quit IRC20:46
*** k_mouza has joined #openstack-nova20:46
*** k-s-dean has joined #openstack-nova20:46
*** k_mouza has quit IRC20:49
*** k-s-dean has quit IRC20:56
*** k-s-dean has joined #openstack-nova20:57
*** rcernin has quit IRC21:00
*** rcernin has joined #openstack-nova21:00
*** rcernin has quit IRC21:25
*** mlavalle has joined #openstack-nova21:27
*** macz_ has quit IRC21:29
*** rcernin has joined #openstack-nova21:36
*** rcernin has quit IRC21:41
*** rcernin has joined #openstack-nova21:41
*** k_mouza has joined #openstack-nova21:46
*** k_mouza has quit IRC21:46
*** k_mouza has joined #openstack-nova21:47
*** rcernin has quit IRC21:50
*** irclogbot_1 has quit IRC21:50
*** whoami-rajat has quit IRC21:50
*** zzzeek has quit IRC21:51
*** k_mouza has quit IRC21:52
*** zzzeek has joined #openstack-nova21:53
*** irclogbot_1 has joined #openstack-nova21:54
*** lemko has quit IRC22:07
*** lemko has joined #openstack-nova22:08
*** rcernin has joined #openstack-nova22:15
*** luksky has quit IRC22:18
*** rcernin has quit IRC22:20
*** k_mouza has joined #openstack-nova22:21
*** k_mouza has quit IRC22:21
*** k_mouza has joined #openstack-nova22:22
*** k_mouza has quit IRC22:30
*** rcernin has joined #openstack-nova22:34
*** rcernin has quit IRC22:38
*** rcernin has joined #openstack-nova22:42
*** rcernin has quit IRC22:42
*** rcernin has joined #openstack-nova22:43
*** k_mouza has joined #openstack-nova23:09
*** k_mouza has quit IRC23:09
*** k_mouza has joined #openstack-nova23:09
*** k_mouza has quit IRC23:15
*** tosky has quit IRC23:17
*** mlavalle has quit IRC23:59

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!