Tuesday, 2025-01-21

opendevreviewsuiong ng proposed openstack/nova master: Fix parameter order in add_instance_info_to_node  https://review.opendev.org/c/openstack/nova/+/93941100:52
opendevreviewMasahito Muroi proposed openstack/nova master: Fix parameter order in add_instance_info_to_node  https://review.opendev.org/c/openstack/nova/+/93941101:07
opendevreviewMasahito Muroi proposed openstack/nova master: Use defaultdict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/93965801:09
opendevreviewMasahito Muroi proposed openstack/nova master: Add ServersViewBuilderTestV296 unit test class  https://review.opendev.org/c/openstack/nova/+/93967301:09
opendevreviewsuiong ng proposed openstack/nova master: Fix parameter order in add_instance_info_to_node  https://review.opendev.org/c/openstack/nova/+/93941101:21
opendevreviewsuiong ng proposed openstack/nova master: Fix parameter order in add_instance_info_to_node  https://review.opendev.org/c/openstack/nova/+/93941102:42
opendevreviewRajesh Tailor proposed openstack/nova master: Add support for showing image properties in server show response  https://review.opendev.org/c/openstack/nova/+/93964907:01
opendevreviewMichael Still proposed openstack/nova master: libvirt: direct SPICE console object changes  https://review.opendev.org/c/openstack/nova/+/92687608:34
opendevreviewMichael Still proposed openstack/nova master: libvirt: direct SPICE console database changes  https://review.opendev.org/c/openstack/nova/+/92687708:34
opendevreviewMichael Still proposed openstack/nova master: libvirt: allow direct SPICE connections to qemu  https://review.opendev.org/c/openstack/nova/+/92484408:34
opendevreviewMichael Still proposed openstack/nova master: libvirt: Add extra spec for sound device.  https://review.opendev.org/c/openstack/nova/+/92612608:34
opendevreviewMichael Still proposed openstack/nova master: libvirt: Add extra specs for USB redirection.  https://review.opendev.org/c/openstack/nova/+/92735408:34
opendevreviewPierre Riteau proposed openstack/nova stable/2024.1: libvirt: Wrap un-proxied listDevices() and listAllDevices()  https://review.opendev.org/c/openstack/nova/+/93969508:44
lucadelmontehello, not sure if this is the right channel to ask some clarificatin about ironic node console integration with nova, i am having some issue to make it work, following the documentation i setup a node with ipmitool-socat console driver, and issuing the baremetal command i am able to get the socat connection working, when i issue the command from nova (openstack console url show --debug  --serial <SERVERID>) i rece11:03
lucadelmonte"unexpected exception in api method: attributeerror: 'node' object has no attribute 'get_node_console", does someone have some ideas on how to fix it?11:03
sean-k-mooneygibi: fyi https://review.opendev.org/c/openstack/devstack/+/922846 merged if you want to try updating https://review.opendev.org/c/openstack/nova/+/937275 again13:02
opendevreviewBalazs Gibizer proposed openstack/nova master: [CI][nova-next]test with placement ac breadth-first  https://review.opendev.org/c/openstack/nova/+/93727513:39
gibisean-k-mooney: thanks for the headsup. Trying in ^^13:40
sean-k-mooneycool lets check back in an hour or two and hopefully that passes13:41
*** gaudenz__ is now known as gaudenz13:59
*** ykarel_ is now known as ykarel14:33
opendevreviewJames Page proposed openstack/nova master: Switch to using oslo.utils secretutils  https://review.opendev.org/c/openstack/nova/+/93972115:21
opendevreviewJames Page proposed openstack/nova master: Correctly patch get_by_flavor_id  https://review.opendev.org/c/openstack/nova/+/93972215:21
opendevreviewMerged openstack/placement stable/2024.2: Add a global limit on the number of allocation candidates  https://review.opendev.org/c/openstack/placement/+/93893915:54
gibisean-k-mooney: no luck, now it fails at https://github.com/openstack/devstack/blob/3cddf9f8832328c17be3644ddd7be5a7dcbedda8/inc/meta-config#L19215:56
gibisean-k-mooney: I will dig a bit later15:56
sean-k-mooneyoh i see15:58
sean-k-mooneywe are now creatign the dir in merge_config_file 15:58
sean-k-mooneyso we can remove that if15:58
sean-k-mooneyhttps://github.com/openstack/devstack/blob/3cddf9f8832328c17be3644ddd7be5a7dcbedda8/inc/meta-config#L189-L19315:58
elodillesgibi: btw, the placement patches are on gate now, was it too early to merge them? :-o15:59
elodillesgibi: i mean the backports on stable/2024.216:00
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Jan 21 16:00:34 2025 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
bauzashey folks16:00
gibielodilles: don't worry :)16:00
elodilles:)16:00
elodilleso/16:00
fwieselo/16:00
masahitoo/16:00
opendevreviewMerged openstack/placement stable/2024.2: Factor out allocation candidate generation strategy  https://review.opendev.org/c/openstack/placement/+/93894016:01
opendevreviewMerged openstack/placement stable/2024.2: Add round-robin candidate generation strategy  https://review.opendev.org/c/openstack/placement/+/93894116:01
gibielodilles: this is just figthing with devstack to configure placement to use the new config options in nova-next 16:01
elodillesgibi: ACK (merged meanwhile ^^^)16:01
gibielodilles: thanks16:01
bauzasokay let's start the meeting16:01
bauzasI'll be clear, packed day with meetings, so I had no time to update the agenda16:02
bauzasso let's do it live16:02
bauzas#topic Bugs (stuck/critical) 16:02
bauzas#info No Critical bug16:02
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:03
bauzasanything about bugs ?16:03
Ugglao/16:03
bauzaslooks not16:03
bauzas#topic Gate status 16:03
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:04
bauzas#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:04
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status16:04
bauzas#info Please look at the gate failures and file a bug report with the gate-failure tag.16:04
bauzas#info Please try to provide meaningful comment when you recheck16:04
bauzas(still waiting for the periodic runs check to be done)16:04
bauzasanything about the gate ?16:04
bauzasI'll be honest, this week I was mostly away from upstream CI16:05
bauzasokay, all periodics are green-ish (one is on RETRY)16:05
bauzasI guess we can move on16:05
bauzasthen, let's move on16:06
bauzas#topic Release Planning 16:07
bauzas#link https://releases.openstack.org/epoxy/schedule.html16:07
bauzas#info Nova deadlines are set in the above schedule16:07
bauzas#info 5 weeks before Feature Freeze16:07
bauzastick tock...16:07
bauzasas a reminder from last week :16:07
bauzas#info we'll try to create as os-traits release next 2 week, please provide your os-traits patches sooner than later.16:08
bauzaswe already merged one trait proposal, so feel free to propose the ones you need for your series16:08
bauzas#undo16:08
opendevmeetRemoving item from minutes: #info we'll try to create as os-traits release next 2 week, please provide your os-traits patches sooner than later.16:08
bauzas#info we'll try to create as os-traits release next week, please provide your os-traits patches sooner than later.16:08
bauzas(bad copy paste)16:08
bauzasthis is said16:09
bauzasany question ?16:09
UgglaWe need to bump the LIBVIRT / QEMU version too.16:09
bauzaswe'll discuss that in the open discussion section16:10
Ugglaok16:10
bauzasmoving on then16:10
bauzas#topic Review priorities 16:10
bauzas#link https://etherpad.opendev.org/p/nova-2025.1-status16:10
bauzashemanth: I've seen your review request on  https://review.opendev.org/c/openstack/nova/+/93904416:11
bauzasI'll make sure that your patch is in the above etherpad16:11
bauzasoh it's there already16:11
bauzashemanth: given the patch, we'll discuss that in the open discussion section to see whether it's a specless blueprint or not and whether we can accept it as an feature exception for this cycle16:12
bauzasmoving on then16:13
bauzas#topic Stable Branches 16:13
bauzaselodilles: your time :)16:13
elodillesACK16:13
elodillesi should be quick:16:13
elodilles#info nothing to report, stable gates seem to be healthy16:13
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:13
elodillesthis is all16:14
elodillesfrom me16:14
bauzas++16:14
bauzasthanks16:14
elodillesnp16:14
bauzas#topic vmwareapi 3rd-party CI efforts Highlights 16:14
bauzasfwiesel: anything to mention ?16:15
fwieselNothing to report from my side16:15
bauzascool16:15
bauzas#topic Open discussion 16:15
bauzaspretty large agenda for today16:15
bauzaslet's be productive16:15
bauzas(sean-k-mooney) disable the heal instance info cache periodic16:15
bauzasaround ?16:16
bauzasif not, we can leave that item for next week, no worries16:16
bauzasnext item16:16
bauzas (bauzas) Updating our QEMU/libvirt min versions ?16:16
bauzasso, when working with Uggla on the VFIO-pci series for live-migration, we discussed about the minimum versions we have16:17
bauzasthe context is that in libvirt we do support our minimums from Focal, AFAICT :)16:18
bauzasbut now, our tested runtimes are clear, we only need to support Jammy 16:18
bauzas#link https://governance.openstack.org/tc/reference/runtimes/2025.1.html16:19
bauzasduring the Caracal PTG, we agreed on upgrading our min versions as soon as we were able to bump them, and I'd prefer honestly to bump our mins on that SLURP release rather than on a non-SLURP16:19
gibi+116:20
bauzas(which would mean that we need to forward-port the relnotes to G* which would be the next SLURP if we bump during Flamingo)16:20
Uggla+116:20
bauzasare we okay to bump our mins to be the existing the next mins ?16:20
bauzaswhich are Jammy ones16:20
bauzaswe could define the next mins to be the Noble versions for QEMU and libvirt16:21
gibi+1 on making the current next_min our new min, and set next_min to whatever in Noble16:21
bauzas#link https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L215-L22416:21
* gibi does not feel the quorum 16:22
Ugglasounds good, are there docs to update too ?16:22
bauzasthat's OK, we can provide a patch and people will review it anyway16:22
bauzasUggla: yes, there are, see the big fat comment on top of the code, by the link I passed16:23
bauzasUggla: fancy proposing the bump ?16:23
gibifeel free to ping me for review16:23
bauzasthanks gibi 16:24
Ugglayep I can provide the patch early next week.16:24
gibiUggla: thanks for taking this16:24
bauzas#agreed Uggla will propose the QEMU/libvirt versions bump this cycle so people may review the proposal16:24
bauzasmoving on16:24
bauzasa procedural note,16:25
bauzas(bauzas) This is my last PTL term16:25
UgglaI will also propose the release for trait if that's ok for you ?16:25
bauzasUggla: which trait ?16:25
gibiUggla: sure go ahead16:25
sean-k-mooneybauzas: oh sorry16:25
sean-k-mooneyi was distracted16:25
bauzasoh you meant the os-trait release patch ? sure, but please wait until next week as said before16:26
gibiif in the meantime we get the patches for the vTPM traits the we can hold the release a bit but I suggest to just do one more release if needed16:26
Ugglabauzas, yes16:26
bauzassean-k-mooney: no worries, we'll get back to you in a sec16:26
gibireleases are quick an cheap16:26
bauzasso, about the PTL seat, I'll leave it16:26
bauzasas a reminder, elections start on Feb 516:27
bauzasvoilĂ , it was mostly a FYI16:27
gibibauzas: thank you for your service16:27
bauzas(as you've seen, my upstream involvment on Nova decreased a bit so I need to give me more time to do real work)16:27
elodillesindeed, thanks so far bauzas o/16:28
Ugglathx bauzas for the PRL service.16:28
fwieselbauzas: Thanks a lot!16:28
UgglaI think I will be a candidate for the PTL seat. bauzas almost convinced me. :)16:28
bauzasthanks, I appreciated that seat but now the cushion has my bottom nearly printed on it *on it since I seated too long16:29
bauzasI don't want to convince anyone, it's an election16:29
bauzasbut I appreciate people volunteering for that service16:29
UgglaOf course.16:29
bauzasas a reminder, I won't disappear and I'll of course help the new PTL 16:30
bauzaswhoever is elected16:30
bauzasanyway, that reminds me I have to start to draft next PTG agenda16:31
bauzasof course, I won't run it but the next person will appreciate to have it ready16:31
bauzasanyway, done on that procedural note16:31
bauzasmoving on16:32
bauzasback to sean-k-mooney's point16:32
bauzas(sean-k-mooney) disable the heal instance info cache periodic16:32
bauzassean-k-mooney: around now ?16:32
sean-k-mooneyya so context16:32
sean-k-mooneyabout 2-3 years ago the neturon folks started seeing higher then expecte background load the neutorn server api in bug reports form upstream/downstream custoemrs16:33
sean-k-mooneyafter some invstatiation thaty raised the topic of our periodic heal action in a neutron nova cross project session and asked is it really needed16:34
bauzasindeed16:34
sean-k-mooneyat the time we determined that it should not be but it kind of fell off our radar16:34
bauzasI do also remember some OpenInfra talks about that16:34
sean-k-mooneyrecently this has come up again down stream and i wanted to bring th topic back upstrem16:34
sean-k-mooneyso there are two patches related to this in flight16:35
sean-k-mooneythe first just test disabling the perodic in nova next16:35
sean-k-mooneyi belive tha that has already merged16:35
sean-k-mooneythe second which is what i wanted to dicuss16:35
sean-k-mooneyis how do we feel about finally disbaling the perodic by default16:35
bauzasgiven the operator feedback I heard, I'm pro-this 16:36
sean-k-mooneyi would like to propose doign it this cycle but if we want to leave it back in the nova-next job to get more data that also a path forward16:36
bauzassean-k-mooney: here's my proposal, 16:36
bauzassend a thread to openstack-discuss by notifying the ops that we plan to do it this cycle16:37
bauzaslink to the proposed patch16:37
bauzasand if nobody argues by the next weeks, then we can merge it16:37
bauzasmy bet is that operators will appreciate the default disabling 16:37
sean-k-mooneyok i can do that16:37
sean-k-mooneyshal we set a date to check back. say 2 weeks?16:38
sean-k-mooneyi would prefer not to wiat rith to FF to change the default16:38
sean-k-mooneyin case we decied we need to revert it16:38
bauzasgood point16:38
bauzasyeah, 2 weeks seems a reasonable trade-off16:39
masahitoI agree the default change as a large scale OpenStack operator. it's nice update.16:39
bauzaswe have 5 weeks to FF16:39
bauzasthat would leave 3 weeks with the change running in CI16:39
sean-k-mooneyack ill send a mail to the list later today16:40
gibiI'm OK with the 2 weeks notice16:40
sean-k-mooneythe proceedign patch https://review.opendev.org/c/openstack/nova/+/939453/116:40
sean-k-mooneyhasnet actully merge yet16:40
sean-k-mooneythat is just testing disabling it in nova-next only16:41
sean-k-mooneyif there is no objection ill recheck that16:41
sean-k-mooneyand that gives ues 2 addtional weeks fo feedback in the nova-next job while we wait16:41
bauzasindeed16:41
bauzassounds a plan16:41
bauzas#agreed sean-k-mooney will notify openstack-discuss about disabling by default the instance info cache and give a 2-week notice for disagreements16:42
bauzascool16:42
bauzasmoving on16:42
bauzas(hemanth) Request for review - Compute memory monitor16:43
bauzasis hemanth here?16:43
bauzaslooks not16:44
sean-k-mooneyso we have said no to extenind that inteface to coolect memory stats in the past16:44
sean-k-mooneythis would be a spec or specless blueprint too right16:45
bauzasand this is a feature request, which would require an approval exception 16:45
bauzasgiven we're past the Feature Approval Freeze deadline16:45
sean-k-mooneyhttps://docs.openstack.org/nova/latest/contributor/policies.html#metrics-gathering16:45
gibiyeah put it on the next PTG agenda16:45
sean-k-mooneythat speicficly stats that we wont implement new monditors16:46
bauzasI'm particularly not against discussing that feature with the owner but not this cycle16:46
sean-k-mooneythat was added after intel propeosed extending this for numa/memory metrics16:46
sean-k-mooneyso we can revisit this but it would be a direct revsersal fo that proabition on new monitors16:46
bauzasagreed, this is a broad discussion16:47
bauzasand I'd want to have it done with a quorum16:47
bauzasI agree with gibi, we could add it tothe PTG (provided I create the PTG agenda)16:48
sean-k-mooneyyep ptg disccsion woudl be good16:48
gibiyeah so give the discussion a space and time but set expectation with hemanth that this is not an easy one due to the policy in place16:49
bauzastbc, one of the options being "continue to disregard any other monitors" or even "deprecate the CPU one"16:49
sean-k-mooneyso the exisitn inteface is currently frozen16:50
bauzasgibi: 100% agreed, we would need to understand the usecase and why this is crucial to have Nova supporting such monitors16:50
sean-k-mooneyand we partly reverted the merged numa code16:50
sean-k-mooneybecause of the perfoamce impact on the rpc bus16:50
sean-k-mooneyhowever i do know that peopel use the existing cpu monitor16:50
sean-k-mooneynamely our internal redhat cloud uses it16:50
sean-k-mooneyand it massivly helped them with there workload schdduleing16:51
bauzasperhaps, but there are limitations that people need to understand16:51
sean-k-mooneythe specificly use the host cpu load metric via the metrics weigher to avoid hevlilly loaded hosts when placing new instnaces16:51
bauzasI know, that's the most common usecase16:52
bauzasas I said, there are usecases but also limitations16:52
bauzaslike, the timewindow is pretty large and if you rely your cloud capacity on such timewindow, you're a fool16:53
sean-k-mooneyyep we dont need to preempt the ptg topic16:53
sean-k-mooneywell i disagre with that statement but anyway there are lots of dragons here16:53
sean-k-mooneythe metrics are sent as aprt fo each schduelr report16:54
sean-k-mooneyanywya i think we can move on16:55
bauzas#agreed as the current design policy explicitely avoiding new monitors, this feature requires a quorum and a long discussion to evaluate a policy revision, hence the Nova community proposing to revisit that topic at the PTG16:55
bauzassean-k-mooney: every 60 secs, right ? :)16:56
bauzas(by default of course)16:56
bauzasI'm just saying that planning your cloud capacity on a 60-sec time window is nice but not helpful 16:56
bauzasanyway, we're mostly at time16:57
bauzasanything else ?16:57
gibi-16:57
bauzasthanks all16:57
bauzas#endmeeting16:57
opendevmeetMeeting ended Tue Jan 21 16:57:46 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2025/nova.2025-01-21-16.00.html16:57
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-01-21-16.00.txt16:57
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2025/nova.2025-01-21-16.00.log.html16:57
elodillesthanks o/16:57
masahitothank you16:58
gibithanks16:58
*** eandersson0 is now known as eandersson17:51
opendevreviewMark Goddard proposed openstack/nova master: ironic: Let Ironic handle deployment cleanup actions during destroy  https://review.opendev.org/c/openstack/nova/+/88341118:20
mikalsean-k-mooney: are you still around?18:37
sean-k-mooneymikal: kind of 18:50
sean-k-mooneyi will be for the next 20-30 mins or so18:50
sean-k-mooneymikal: you updated your spcie patches in the last few days correct18:50
sean-k-mooneyi asume you woudl like to make progress on https://review.opendev.org/c/openstack/nova/+/927354/13 and the proceedign ones18:52
mikalsean-k-mooney: yeah, the code didn't change, I just figured if I pushed again I'd get a newer CI run. I figure I'll do that weekly from now on.20:06
mikalsean-k-mooney: but yeah, I'm just after some advice about what I need to do next. I think I'm just waiting on reviews, but maybe I missed something?20:06
mikalsean-k-mooney: (also sorry for the slow reply, I was off having my pre-work ablutions).20:06
sean-k-mooneyno worries20:07
sean-k-mooneyim still here but going to finish shortly20:07
mikalThat's cool. You don't have to reply now or anything.20:07
sean-k-mooneymelwitt: you started looking at mikal's serise last cycle can you take anotoehr pass this cycle?20:07
mikalI would like to get these landed so I don't have to keep rebasing them, but I understand there are competing priorities.20:07
sean-k-mooneymy +2 is still there on the first 2 patches ill see if i can load context and look at the remaining 3 this week20:08
mikalThanks. Let me know if you need anything from me. There is an outstanding question on the final patch that I need to reload the state for and address. I'll try to get that one done after work tonight.20:09
sean-k-mooneyis it this one https://review.opendev.org/c/openstack/nova/+/927354/8/nova/virt/libvirt/driver.py#679020:09
sean-k-mooneyi have not read it but seems to be the only open comment20:09
sean-k-mooneyoh its askign what happens if the requeted number fo usb prots is larger the the model supprot20:10
sean-k-mooneymy guess is livbirt will complain and we will fail to define the domain20:10
mikalYeah, that's the one.20:10
mikalI need to do some testing there.20:11
sean-k-mooneyif we knwo or cna detect the limit perhaps via virsh domcapablities20:11
sean-k-mooneywe coudl add some validation but i think without tha tthe only real option are put the vm in error and log a relevent error20:12
mikalI think I'd be tempted to just put in a smallish constant upper bound for now and see if people really care?20:12
mikalLike... How many USB devices are you really passing through? Shouldn't it mostly just be mass storage or a smartcard reader or something?20:12
sean-k-mooneythat or have a cofnig option that default to the same value20:12
mikalIt shouldn't be dozens of devices I wouldn't think.20:12
mikalYeah.20:13
sean-k-mooneyya so 8-10 proably 20:13
mikalI think I'd rather land something simple, and then iterate based on feedback. Solving all possible issues seems like premature optimisation to me.20:13
sean-k-mooneyyep20:13
mikal(As long as the simple thing is compatible with whatever we think might be a valid future thing)20:13
mikalNoting as well that for this to be really useful I need to land code in the clients and at least one deployer. So at this rate I think this is at least two releases away from being usable in the real world.20:14
sean-k-mooneyyou coudl likely set a limit here         'hw_redirected_usb_ports': fields.IntegerField(),20:14
sean-k-mooneyof like 1020:14
sean-k-mooneybut it would proably be better to do that in the driver then the object20:14
mikalI can do some reading on the capabilities of the various USB controllers in libvirt today.20:15
sean-k-mooneythis is perhaps somethin that could be a followup patch on top by the way20:16
mikalYeah, that would be my preference. Happy to work on it, don't really want to block on it though.20:17
mikalAnyways, I'll take a look today / tonight and should let you go. I have to go learn how shoes work before I miss my bus.20:17
sean-k-mooneyhttps://libvirt.org/formatdomain.html#controllers the libvirt docs just say "    USB controllers accept a ports attribute to configure how many devices can be connected to the controller."20:18
sean-k-mooneybut they dont document the limtis so i feel like this will be a qemu limit20:18
mikalHerm. That sounds like "read the qemu code" territory...20:18
sean-k-mooneyi think the usb sepc allwos somehting like 256 device but i highly doubt qemu supprots that20:19
sean-k-mooneyok ill chat to you tomorrow o/20:19
mikalThanks Sean, sorry if I made you late for anything. I appreciate the chat.20:20
sean-k-mooneyhttps://qemu-project.gitlab.io/qemu/system/devices/usb.html#physical-port-addressing20:21
sean-k-mooney UHCI has two root ports (1,2). EHCI has six root ports (1-6), and the emulated (1.1) USB hub has eight ports.20:21
sean-k-mooneyso 8 unless you use hubs so ya i would limit to 8 for now20:22
mikalYeah, I'm going to be honest and say I don't immediately know the difference between a "root port" and whatever other types of ports there are.20:22
sean-k-mooneyusb can have a tree for device below the root port up to 8 level deep i belive20:23
sean-k-mooneylinius tech tips did a video tyring to reach the limit pluging usb hubs into usb hubs a few months ago20:23
sean-k-mooneyhttps://www.youtube.com/watch?v=hiwaxlttWow20:24
mikalHeh. Actionable advice right here.20:25
mikals/here/there/20:25

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