Tuesday, 2023-03-21

kaloyankmorning Ironic07:06
dtantsurJayF: 17:00 UTC is problematic for me, but I can make it, I guess08:59
dtantsurJayF: otherwise, the schedule looks good to me09:03
rpittaugood morning ironic! o/09:05
kaloyankgeneric question, is this https://docs.openstack.org/ironic/latest/contributor/contributing.html#feature-submission-process still valid? I want to submit an RFE for saving local disk deployments to images09:14
dtantsurkaloyank: this is more or less up-to-date, yes09:18
dtantsurhave you seen the previous attempt on snapshots in ironic?09:19
kaloyanknope, it'd be interesting if you can share some links :)09:19
kaloyankI found this: https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/snapshot-support.html09:33
opendevreviewDmitry Tantsur proposed openstack/ironic-specs master: [WIP] Merge Inspector into Ironic  https://review.opendev.org/c/openstack/ironic-specs/+/87800109:36
dtantsurkaloyank: yeah, I meant that09:36
kaloyankif I understand correctly, the spec just needs to be implemented?09:40
opendevreviewRiccardo Pittau proposed openstack/sushy stable/zed: Exclude all files starting with . from flake8 tests  https://review.opendev.org/c/openstack/sushy/+/87801810:17
opendevreviewRiccardo Pittau proposed openstack/sushy stable/yoga: Exclude all files starting with . from flake8 tests  https://review.opendev.org/c/openstack/sushy/+/87801910:17
opendevreviewRiccardo Pittau proposed openstack/sushy stable/xena: Exclude all files starting with . from flake8 tests  https://review.opendev.org/c/openstack/sushy/+/87802010:18
opendevreviewRiccardo Pittau proposed openstack/ironic master: Use main branch of metal3-dev-env to run metal3 integration job  https://review.opendev.org/c/openstack/ironic/+/87760011:05
opendevreviewRiccardo Pittau proposed openstack/ironic master: Use main branch of metal3-dev-env to run metal3 integration job  https://review.opendev.org/c/openstack/ironic/+/87760011:07
iurygregorygood morning Ironic11:19
opendevreviewMerged openstack/ironic-python-agent-builder master: Add DIB_IPA_HARDWARE_RDO to define repo behaviour  https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/87756712:41
TheJuliagood morning13:01
TheJuliakaloyank: yes, but going down that road, it doesn't have to be an exact match to the spec. you may learn things along the way!13:04
TheJuliaWe can also change the spec if new ideas surface13:04
TheJuliaSome aspects have changed since that was written, we might be able to find a way to get authentication data out of the agent13:06
dtantsurmorning TheJulia 13:27
dtantsurTheJulia, JayF, arne_wiebalck, 2023Q2 is around the corner, who is going to schedule the next BM SIG meetup?13:32
TheJuliaI guess the question which comes to mind is what would we like to present/engage in regards to? Would this be an opportunity to present some of the under-discussion ideas (as long as we preface them as such)?14:00
JayFdtantsur: if you have specific suggestions how I can shift things around to make your life easier; please let me know (re: vPTG)14:08
dtantsurJayF: nothing specific. If we manage to finish by 16:30 UTC, it will be much better for me, but it's fine.14:09
dtantsurTheJulia: "Things I learned by first creating ironic-inspector and then destroying it again" :D14:10
sschmittI've got a question about this spec: https://specs.openstack.org/openstack/ironic-specs/specs/9.0/physical-network-awareness.html14:26
sschmittit seems to be fully implemented, but there are some usecases it seems like it doesn't support. For one this seems to work only for vlan networks. We'd like to do it with vxlan networks (assuming we have some ml2 mechanism to setup the vxlan vteps on the top of rack switches)14:28
dtantsurI'm not sure anything on the ironic side is actually preventing vxlan from working? Or even: I've heard people confidently saying "it works if the ML2 driver and the switch do the right thing".14:29
sschmittSecondly, as far as im aware you must specify these physical networks in your ml2 conf file. Which means if you want to add one (like if you got a new bm node that has 8 interfaces but you only configured 6 physnets), you have to restart neutron14:29
sschmitti think this also means that they are implicitly provider networks, which isnt ideal from an RBAC perspective14:30
sschmitt@dtantsur you might be right, i know its hard coded in NGS for vlan. It also might on the neutron side as vxlan provider networks claim to be supported, but i can find almost no info on them14:32
dtantsurI'll tag hjensas and mgoddard who know much more about these things14:32
TheJuliasschmitt: I think the model was largely for where you had distinct networking fabrics and to scope the fabric based and help map port->fabric->neutron's connectivity for neutron15:46
TheJuliaunfortunately the term fabric has other means15:48
TheJuliameanings15:48
* TheJulia can't type today15:48
TheJuliadtantsur: That sounds like a whorthwhile presentation15:48
TheJuliadtantsur: I think talking about RBAC would actually be a good idea. I've been on the scientific-sig slack a few rbac related questions have come up (besides, I have a talk on this subject too..)15:49
sschmittyeah i think that works for some, but i think "put this network on this baremetal interface, otherwise fail" is also important15:49
sschmittespecially when you want mixed vm and baremetal topologies15:50
TheJuliasschmitt: yeah, If you want to implicitly direct it yeah. The physnet awareness was always intended so the humans didn't have to be concious of it15:50
sschmittwe get around this today by scheduling a bunch of dummy networks until we get the right network on the right interface, which is less than ideal15:52
TheJuliaouch :(15:53
hjensassschmitt: In neutron "physical_network" is only a thing for provider networks. (provider:physical_network)16:01
hjensassschmitt: I think if don't intend to use provider networks there is a gap in functionality.16:03
hjensassschmitt: also, reading backlog - In theory using vxlan should work if the is an ML2 that can configure vtep on the switch. (But I'm not aware of any plug-in that does)16:05
sschmittso it sounds like a new spec for functionality to explicitly hook up a neutron tenant network to a baremetal port would be needed16:07
hjensassschmitt: yes, I think this would be an RFE, ideas: 1. additional field in the binding-profile 2. a tag on the neutron port (I think binding-profile would be preffered)16:12
sschmittyeah i think binding profile would be the best as well16:14
opendevreviewDmitry Tantsur proposed openstack/ironic-specs master: [WIP] Merge Inspector into Ironic  https://review.opendev.org/c/openstack/ironic-specs/+/87800116:54
dtantsurThis is becoming an interesting document ^^^. Essentially, the whole Inspector (except for the introspection rules) explained as a text :D16:54
rpittauI'm too tired to read that now, but wow!16:58
TheJuliaI'm almost afraid?!17:00
dtantsurC'mon, I tried to keep it easy and entertaining!17:06
dtantsurdon't make me regret even starting a spec :D17:06
JayFMy eyes are glazed over and all I've read is the url ;) 17:06
JayFseriously, thanks for writing that up and I'll open it up and read it today at some point :D 17:07
dtantsurThanks! It's WIP but it's actually almost-almost complete.17:07
rpittaugood night! o/17:10
* TheJulia hears of virtualization inside of firmware levels of code interaction utilizing linux running on cards in firmware on cards before the main host OS boots and wonders how many levels of nesting is taking place.17:23
dtantsur"We need to go deeper" (c)17:26
TheJuliaI suspect that is always the pattern. The substrate is often hidden as you can only observe the floor (for lack of a better word)17:36
kubajjdtantsur: am I safe to quote this in my dissertation? This seems kind of relevant18:32

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