| cardoe | jrosser, TheJulia: part of this is why I think an engine like what NetBox/Nautobot do makes sense. They take datasets as context and use them to merge with your templates what the expected switch config should be. Then they generate the operations which need to be run to get the switch to that state. Something like that would allow users to more flexibility make those setups. | 01:38 |
|---|---|---|
| cardoe | I think the initial approach is good to land and kick the tires on as a conversation starter. | 01:39 |
| cardoe | Just hiked down the mountain in Kauai so I’ll try to review the series again tonight when I’m relaxing. | 01:40 |
| TheJulia | There is a whole other challenge, where is the boundary layer then… as in should lower levels have all that extra detail/context when it might be an attribute in relation to the scheduling | 01:40 |
| TheJulia | Airport time? | 01:41 |
| TheJulia | It’s cold at jfk | 01:43 |
| TheJulia | Oh, just saw the hiking comment :) enjoy | 01:51 |
| opendevreview | Verification of a change to openstack/ironic master failed: Address remaining review comments for rpc methods https://review.opendev.org/c/openstack/ironic/+/971184 | 01:51 |
| TheJulia | I do think everyone is going to have slightly different style and shape tires to be kicked. Wait for the wheels which are wheels of wheels which dynamically reshape! | 01:53 |
| TheJulia | A lack of sleep and a sum of bad sleep may be kicking in combined with metal tubes. | 02:14 |
| cardoe | TheJulia: well that's the point. I'm looking to refactor our plugin to have a config of "port" or "physical-network". If its set to "port" then it gathers up all the data about the port. VNI, VLAN, trunk, and sub-ports and builds it into a JSON payload which would be documented explicitly. If its "physical-network", it would do all that but for every port on that physical-network. You'd then configure an endpoint where it | 04:57 |
| cardoe | would POST that contents. | 04:57 |
| cardoe | network-generic-switch could be a consumer of that data in the "port" mode | 04:58 |
| TheJulia | It absolutely could, however I’m thinking the higher level. Specifically what is the signal to pivot major differences on, for example entirely different routing configuration. That’s not a Lower level detail on the port or node itself. It’s a behavior or a trait required. Also greetings from the cabin of an aircraft where the lights won’t turn off. | 05:05 |
| TheJulia | Even worse, we’re stuck with the blue accent lights as well. | 05:05 |
| TheJulia | Gasp! They just went out | 05:06 |
| * TheJulia tris to become one with the uncomfortable tiny pillow | 05:06 | |
| opendevreview | Merged openstack/ironic master: Address remaining review comments for rpc methods https://review.opendev.org/c/openstack/ironic/+/971184 | 05:09 |
| cardoe | TheJulia: yeah I just don't think we'll be able to address everyone's needs in 1 plugin. | 05:35 |
| cardoe | TheJulia: what kind of plane ya flying? | 05:35 |
| cardoe | TheJulia: you wanna do the l2vni stuff as a follow on? Like the import of socket nested in a function? | 05:39 |
| opendevreview | Merged openstack/ironic master: Add an ordering method for TBN traits https://review.opendev.org/c/openstack/ironic/+/974519 | 06:30 |
| *** dmellado47 is now known as dmellado4 | 21:01 | |
| opendevreview | Merged openstack/ironic-prometheus-exporter master: Fix resource management in ipmi.py parser https://review.opendev.org/c/openstack/ironic-prometheus-exporter/+/975892 | 22:00 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!