| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2024-09-05 | |||
| 19:14:08 | sean-k-mooney | of couse it is why would anything in ptyhon ever not be a pun | |
| 19:14:25 | melwitt | quite clever really. I liked the name just didn't get it | |
| 19:15:50 | sean-k-mooney | ill begrudgingly admit its pretty good | |
| 19:16:23 | melwitt | :) | |
| 19:16:37 | sean-k-mooney | so you know https://instructlab.ai/ | |
| 19:16:53 | melwitt | labrador | |
| 19:16:54 | sean-k-mooney | the dog logo is apprently russel brants dog | |
| 19:17:13 | JayF | using ipxe as the rescue image is the most brilliant thing I've read today | |
| 19:17:18 | melwitt | oh, that's pretty cute. wears corrective lenses | |
| 19:17:30 | sean-k-mooney | ya i also wonder if its a lab | |
| 19:18:20 | sean-k-mooney | JayF: so one of the things i have wanted to be able to do is have a way to expose glace images over ipxe to vms for a long time | |
| 19:18:23 | melwitt | I think it is. I saw it somewhere else in the instructlab docs or something like that | |
| 19:18:37 | sean-k-mooney | basically so you could pxe boot form isos in galnce and boto form bascially a blank disk | |
| 19:19:27 | sean-k-mooney | JayF: today you can use hw:boot_menu to use pxe btu the problem has alwasy been the tftp server and gettign that to work with neutron | |
| 19:19:43 | JayF | sounds familiar | |
| 19:19:56 | sean-k-mooney | we chatted about using netboot.xyz | |
| 19:19:58 | JayF | if only you knew some experts in getting things pxe booted ;) | |
| 19:20:10 | JayF | you know ironic used to support this first class and dropped the feature, right? | |
| 19:20:27 | sean-k-mooney | netboot.xyz? | |
| 19:20:28 | JayF | so people didn't have to manage local bootloaders, we'd pxe into the OS on disk | |
| 19:20:34 | JayF | so many of the moving parts may already be in place | |
| 19:20:47 | JayF | no, netboot.xyz *does* power my personal homelab though :D (+cockpit to spin up the VMs) | |
| 19:20:57 | sean-k-mooney | ya so what missing is being able to set the relevent dhcp option in the neturon subnet | |
| 19:21:22 | sean-k-mooney | then you could jsut trivially set a netron nic as the boot device | |
| 19:21:39 | sean-k-mooney | and if you wanted you could just run your own pxe server on another nova vm | |
| 19:21:39 | JayF | That works though, is what I'm saying | |
| 19:21:47 | JayF | Ironic does that today, tells neutron dhcp agent to serve up pxe | |
| 19:21:50 | sean-k-mooney | JayF: it works for horizon | |
| 19:21:53 | sean-k-mooney | *ironic | |
| 19:21:53 | JayF | so the moving parts are likely there? | |
| 19:22:04 | sean-k-mooney | but i think you might not be able to do this as a normal user | |
| 19:22:21 | sean-k-mooney | i.e. i dont know if you can do this without being admin | |
| 19:22:30 | JayF | oooh, that's a good point | |
| 19:22:49 | sean-k-mooney | i thikn 99% of it is there however | |
| 19:24:08 | sean-k-mooney | oh https://docs.openstack.org/api-ref/network/v2/index.html#extra-dhcp-option-extra-dhcp-opt-extension | |
| 19:24:18 | sean-k-mooney | so this is what ironic is using | |
| 19:24:30 | sean-k-mooney | oh... | |
| 19:24:41 | sean-k-mooney | JayF: its on the port i always looked for this on the subnet | |
| 19:24:52 | sean-k-mooney | because you defien extra routs and the dns servers on the subnet | |
| 19:25:04 | sean-k-mooney | so i was expect the dhcp option ot also be on the subnet | |
| 19:25:23 | sean-k-mooney | JayF: so ya i dont see why you could not do pxe boot today | |
| 19:25:45 | sean-k-mooney | and it woudl be simple enough to add another port extention that nova could read to allow it to be used as the boot device | |
| 19:27:57 | sean-k-mooney | i should try doing this someday and write a doc... | |
| 19:29:08 | sean-k-mooney | JayF: there is even openstack client support for this | |
| 19:30:29 | JayF | yeah like, I don't want this feature personally | |
| 19:30:39 | JayF | but I figured ironic might be a model for doing it (or at least pointing in a direction) | |
| 19:30:53 | JayF | hint: this also could be used to enable UEFI HTTPBoot, which is superior to pxe in every way | |
| 19:31:15 | JayF | this being said: Ironic-Conductor spins up and manages the tftp server. There is no neutron answer to that aiui. | |
| 19:31:21 | sean-k-mooney | JayF: well since you say that if the ovmf file that wemu is using support that | |
| 19:31:28 | sean-k-mooney | then that woudl also already work today | |
| 19:32:14 | sean-k-mooney | enableing the boot memu allow you to use any of the facilites in teh uefi firmware provide by your host ovmf uefi image | |
| 19:33:01 | sean-k-mooney | is its really a question of does qemu/ovmf supprot http boot if so you could in thory use it | |
| 19:37:02 | JayF | I guess that's kinda true, it still comes over dhcp information | |
| 19:37:14 | JayF | so from a nova perspective, especially if you don't own the tftp/http/whatever server, it doesn't matter | |
| 19:37:15 | sean-k-mooney | yep i have it up locally | |
| 19:37:35 | sean-k-mooney | so my ovmf firmware supprot uefi and pxe boot | |
| 19:37:44 | sean-k-mooney | *http and pxe boot | |
| 19:38:22 | sean-k-mooney | i dont have dhcp confirued on my local libvirt to provide the dhcp options | |
| 19:38:32 | sean-k-mooney | but i dont see why you could not make this work today | |
| 19:39:06 | sean-k-mooney | it would be a lot cleaner however to have a neturon prot extion to just lable the port a boot souce | |
| 19:39:27 | sean-k-mooney | then we could add the libvirt xml to make it boot form that first and then fallback to the local disk | |
| 19:40:26 | sean-k-mooney | anywya i should finish for the day | |
| 19:40:49 | sean-k-mooney | JayF: before i go did ye get the auto lessee suff finished on the ironic side | |
| 19:41:07 | JayF | It's got one +2, waiting review, basically paused since we got CVE patches in the gate | |
| 19:41:13 | JayF | it'll be in this release, we don't FF like nova does :) | |
| 19:41:36 | sean-k-mooney | good to know and ya i saw the maile yesterday | |
| 19:41:40 | JayF | only piece missing that I promised, that frankly I forgot about until I looked at the BP yesterday is the migration script | |
| 19:42:06 | JayF | that'll be trivial to write and document :) | |
| 19:42:35 | JayF | although TBH I am extremely skeptical any operators will actually want to backfill lessee | |
| 19:49:46 | sean-k-mooney | ya it might be nice to put that in an ironic-manage command or similar | |
| 19:49:58 | sean-k-mooney | but it does not sound like its a blocker for the feature ot be used | |
| 19:50:15 | sean-k-mooney | jsut a nice to have for consitency | |
| 19:50:45 | sean-k-mooney | JayF: i assume an admin could just manually set the lessee on the ironic node if they wanted too | |
| 19:51:59 | JayF | We do not have an ironic-manage command, I was just going to add something to our tools/ directory | |
| 19:52:24 | JayF | basically just for each ironic node with non-null instance_uuid, check nova for instance owner, and set it on the node | |
| 19:52:44 | JayF | with probably an option for shard (so you can do N processes to parallelize) | |
| 19:53:06 | sean-k-mooney | JayF: oh really so you dont have an ironic-manage db_sync? | |
| 19:53:16 | sean-k-mooney | how do ye manage db upgrade in ironic? | |
| 19:53:19 | JayF | I thought it was ironic-dbsync? | |
| 19:53:20 | JayF | IMBW | |
| 19:53:58 | sean-k-mooney | yep https://opendev.org/openstack/ironic/src/branch/master/setup.cfg#L49 | |
| 19:54:23 | sean-k-mooney | ok i tought <project>-manage was the normal convention for that tool | |
| 19:54:34 | sean-k-mooney | but i ugess there is no really reason not to call it something else | |
| 19:54:56 | sean-k-mooney | ok actully stoping for today this time o/ | |
| 19:54:58 | JayF | yeah and TBH, with my operator hat on, I prefer tools like this not to require the whole app | |
| 19:55:19 | JayF | (pip install nova to get nova-manage just feels overkill, even if it's not, really) | |
| 19:55:53 | sean-k-mooney | well its internally using the same oslo version object and db fucntion ectra | |
| 19:56:06 | sean-k-mooney | but ya we normally intend it to be run form where the conductor is | |
| 19:56:17 | JayF | yeah, in this case though, I want to write a tool that's 100% API-shaped, no db magic needed | |
| 19:56:23 | sean-k-mooney | it can be run remotely but that not what we expect peopel to do | |
| 19:56:32 | JayF | I can tell you I've worked zero places that ran it, at upgrade time, from a nova-anything :) | |
| 19:56:34 | sean-k-mooney | right makes sense | |
| 19:57:15 | sean-k-mooney | well its normally ran form yoru openstack contoler nodes | |
| 19:57:44 | sean-k-mooney | in contaieriesed installer yousually the nova-conductor container just because it already had the correct configs | |
| 19:58:23 | sean-k-mooney | we have discussed having the conductore be able to just do it automatically in teh past when its starts | |
| 19:58:36 | sean-k-mooney | but that alway felt a little too much out fo scope | |
| 20:01:25 | JayF | yeah most places I worked did "N" version upgrades at once, so we'd just have someone spin up a dedicated machine that we'd upgrade through the intermediate versions to do all the migrations | |
| 20:01:52 | JayF | we went O->U at one place using that kinda model | |
| 23:08:58 | opendevreview | melanie witt proposed openstack/nova master: docs: Change note:: to warning:: for service user token https://review.opendev.org/c/openstack/nova/+/928308 | |
| #openstack-nova - 2024-09-06 | |||
| 00:27:02 | opendevreview | melanie witt proposed openstack/nova master: docs: Show the recommended way to PXE boot an instance https://review.opendev.org/c/openstack/nova/+/928309 | |