| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2024-09-05 | |||
| 18:56:55 | sean-k-mooney | so its not entirly strange to say if we are moving it allow the scheduer hits to optionally be updated | |
| 18:57:20 | sean-k-mooney | im less sure if that should be member or admin policy wiese | |
| 18:57:26 | sean-k-mooney | but i could see the argument either way | |
| 18:57:33 | melwitt | yeah, agree | |
| 18:58:46 | sean-k-mooney | the one nice thing about policy is as long as we are secure by default operator can always define there own | |
| 18:59:36 | melwitt | I think regardless we need the nova-manage command. afaik everyone is +1 about it and it could be backported for older versions | |
| 19:00:30 | sean-k-mooney | im slowly coming to the view that nova manage (witin reason) shoudl have more tooling to help operator get out of messes like this | |
| 19:00:46 | melwitt | same | |
| 19:01:18 | sean-k-mooney | i.e. i kind of want a flavor refesh command in nova-manage to check if the host is still valide and update the embded flavor with the latest verion of that flavor | |
| 19:01:38 | sean-k-mooney | or allwo you to also update the embded flavor extra spec liek the image properties | |
| 19:01:57 | sean-k-mooney | that does not change teh advice of never modify flavor once they are in use | |
| 19:02:13 | sean-k-mooney | but it give you an escape hatch if you did without forceing resizes | |
| 19:02:23 | melwitt | why not resize? oh | |
| 19:03:17 | sean-k-mooney | sometimes people pin thing to hosts :) the other reason i have heard is mano integration | |
| 19:03:30 | sean-k-mooney | i.e. there is a system on top that created the worklaod | |
| 19:03:42 | sean-k-mooney | and changing the flavor id is not trivial as a result | |
| 19:04:22 | sean-k-mooney | for example if it was deployed with heat or somethign like that | |
| 19:04:37 | melwitt | hm | |
| 19:04:43 | sean-k-mooney | i soudl argure that you shoudl stop doing it wrong | |
| 19:05:08 | sean-k-mooney | but customer sometimes dont like that | |
| 19:05:12 | sean-k-mooney | not sure why :) | |
| 19:06:05 | sean-k-mooney | anyway if you or they were to propsoe an extention to nova-mange for there usecase | |
| 19:06:17 | sean-k-mooney | or even the addtion of scheduler hits to the move ops | |
| 19:06:25 | sean-k-mooney | i would not really be against that | |
| 19:06:26 | melwitt | yeah.. it's a balance of "how painful is it to do the right thing" | |
| 19:07:05 | sean-k-mooney | do you remmber how horizon used to work ? | |
| 19:07:29 | sean-k-mooney | nova has had imutable flavors for as long as i have worked on openstck | |
| 19:07:39 | melwitt | oh, the "edit" flavor thing? | |
| 19:07:51 | sean-k-mooney | old version of hroizon use to allwo you to update the cpu ram and disk by deleteing and recreatin gthe flavor | |
| 19:07:53 | sean-k-mooney | ya | |
| 19:07:55 | sean-k-mooney | that | |
| 19:08:07 | melwitt | yeah, I remember. I take it that means it no longer does that? | |
| 19:08:35 | sean-k-mooney | no that was removed about 6 year ago after we kept gettting bug and telling them it a hroizon issue | |
| 19:08:49 | melwitt | oh hah | |
| 19:09:15 | sean-k-mooney | melwitt: so keyston also does nto allow you to update role asignment in trusts (a way of delegation access) | |
| 19:09:20 | melwitt | I use horizon sometimes but not for changing flavors | |
| 19:09:27 | sean-k-mooney | tripleo did the delete and recreat thing | |
| 19:09:52 | sean-k-mooney | and it causes similar bugs to this day | |
| 19:10:23 | sean-k-mooney | i use horizon more then i shoudl | |
| 19:10:51 | sean-k-mooney | i have not tried skyline yet | |
| 19:11:10 | sean-k-mooney | its been on my todolist but not high enough to take the time to do it | |
| 19:12:23 | melwitt | and I just finally realized why it's named skyline | |
| 19:12:25 | melwitt | 😝 | |
| 19:13:19 | sean-k-mooney | why? | |
| 19:13:30 | sean-k-mooney | oh.. | |
| 19:13:41 | melwitt | lol | |
| 19:13:42 | sean-k-mooney | its a horizon pun | |
| 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 | |