| *** bauzas_ is now known as bauzas | 00:19 | |
| *** __ministry is now known as Guest2547 | 01:36 | |
| *** bauzas_ is now known as bauzas | 01:40 | |
| *** dtantsur_ is now known as dtantsur | 02:13 | |
| *** __ministry is now known as Guest2554 | 02:38 | |
| *** bauzas_ is now known as bauzas | 03:51 | |
| *** bauzas_ is now known as bauzas | 04:11 | |
| *** bauzas_ is now known as bauzas | 05:04 | |
| *** bauzas_ is now known as bauzas | 05:45 | |
| *** bauzas_ is now known as bauzas | 07:06 | |
| *** bauzas_ is now known as bauzas | 07:44 | |
| *** bauzas_ is now known as bauzas | 07:52 | |
| *** bauzas_ is now known as bauzas | 08:00 | |
| opendevreview | zhou zhong proposed openstack/nova master: nova-manage: modify image properties in request_spec https://review.opendev.org/c/openstack/nova/+/924319 | 08:51 |
|---|---|---|
| opendevreview | zhou zhong proposed openstack/nova master: nova-manage: modify image properties in request_spec https://review.opendev.org/c/openstack/nova/+/924319 | 08:52 |
| opendevreview | zhou zhong proposed openstack/nova master: nova-manage: modify image properties in request_spec https://review.opendev.org/c/openstack/nova/+/924319 | 08:56 |
| opendevreview | zhou zhong proposed openstack/nova master: nova-manage: modify image properties in request_spec https://review.opendev.org/c/openstack/nova/+/924319 | 08:59 |
| *** bauzas_ is now known as bauzas | 09:11 | |
| stan | sean-k-mooney is there any work being done on using Shared security group during an instance launch? | 09:54 |
| stan | We have a common security rule that allows access to our backup server, so I would really be handy if we can attach this during instance creation. | 09:55 |
| sean-k-mooney | stan: yes, there is a patch for it but its been worked on inconsitently | 09:57 |
| sean-k-mooney | im expecting we will merge in in the next 3-4 weeks shortly after rc1 is released | 09:57 |
| stan | sean-k-mooney Thanks, that is great news. :) | 09:58 |
| sean-k-mooney | stan: the issue is that when that feature was orgianlly added to neutron it was not even discussed with us let alone propsoed as an enhanemnet | 09:58 |
| sean-k-mooney | the gap is not being closed but its a feature not a bug | 09:59 |
| sean-k-mooney | so we wont be backporting it | 09:59 |
| sean-k-mooney | with that said its pretty trivial so you could do that downstream if you really wanted | 10:00 |
| sean-k-mooney | stan: https://review.opendev.org/c/openstack/nova/+/811521 | 10:00 |
| stan | yeah, I think I will merge it at our downstream. I'm trying to move off of VMware in our company, so I will also try to help as much I can, to contribute back. | 10:01 |
| stan | Thanks again for the prompt response :) | 10:01 |
| *** bauzas_ is now known as bauzas | 10:21 | |
| *** bauzas_ is now known as bauzas | 11:18 | |
| *** bauzas_ is now known as bauzas | 12:04 | |
| opendevreview | Merged openstack/nova stable/2023.1: libvirt: call get_capabilities() with all CPUs online https://review.opendev.org/c/openstack/nova/+/927558 | 12:07 |
| *** __ministry is now known as Guest2605 | 12:50 | |
| *** bauzas_ is now known as bauzas | 12:57 | |
| *** bauzas_ is now known as bauzas | 13:13 | |
| *** bauzas_ is now known as bauzas | 13:50 | |
| opendevreview | Brian Haley proposed openstack/nova master: Support creating servers with RBAC SGs https://review.opendev.org/c/openstack/nova/+/811521 | 14:46 |
| chris218 | Hi guys is there a reason this patch never got merged or it just wasn't ever proposed? https://opendev.org/openstack/openstack-virtual-baremetal/src/branch/stable/2.0/patches/nova/nova-pxe-boot-pike.patch | 15:01 |
| JayF | I don't know the history of that patch specifically, but the repository it's in has been archived for a couple years. Also the pike release of openstack was something in the neighborhood of 8 years ago? So I suspect that patch is old, too | 15:10 |
| JayF | You might have better results asking a question related to what you're trying to do | 15:10 |
| chris218 | Well i'm interested in letting nova boot directly from pxe which is what that patch provided | 15:58 |
| melwitt | I used this gerrit search "project:openstack/nova message:pxe" to find https://review.opendev.org/c/openstack/nova/+/434549 | 16:02 |
| opendevreview | Merged openstack/nova master: doc: Fix markup syntax and typo https://review.opendev.org/c/openstack/nova/+/906379 | 16:04 |
| chris218 | melwitt: awesome thanks, my gerrit-fu is unfortunately very bad and I didn't find it myself. | 16:05 |
| chris218 | So in theory if somebody implemented it as a flavor extra spec it could get accepted? | 16:06 |
| melwitt | from what I can tell, if someone proposed this with a proper flavor extra spec or image property then it could be considered mergeable.. but obvs would need to run it by other people too in case there is some other concern about the idea | 16:06 |
| sean-k-mooney | we discussee this in the past | 16:18 |
| sean-k-mooney | you can actully do it already today | 16:18 |
| sean-k-mooney | its a littel hacky today and it woudl be nice to make it work more seamlessly | 16:18 |
| sean-k-mooney | chris218: to do this today you need to enabel the boot menu using hw:boot_menu=true | 16:18 |
| sean-k-mooney | and from there you can do a pxe boot | 16:19 |
| sean-k-mooney | but it woudl be nice to have a way to do that more cleanly | 16:19 |
| *** bauzas_ is now known as bauzas | 16:30 | |
| melwitt | ah, so this is the spec that shows why the effort was abandoned https://review.opendev.org/c/openstack/nova-specs/+/435052 | 16:44 |
| melwitt | chris218: ^ | 16:45 |
| chris218 | Oh wow using rescue with ipxe sounds like a great solution thanks a lot! | 16:51 |
| *** bauzas_ is now known as bauzas | 16:54 | |
| melwitt | elodilles: I was re-reading the most recent release countdown email and wanted to clarify, it says "In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings." does that mean it's only for UI components or it's for everything including nova docs? | 17:41 |
| *** bauzas_ is now known as bauzas | 17:42 | |
| sean-k-mooney | melwitt: technially the string freeze applies to nova and others but we dont really follow that or at least have not for many years | 17:44 |
| sean-k-mooney | we dont go out of our way to not follow it either but realsiticlly if a bug is found we are are not going to hold it because it updates some doc text or add a release note | 17:45 |
| sean-k-mooney | we have https://releases.openstack.org/dalmatian/schedule.html#soft-stringfreeze and https://releases.openstack.org/dalmatian/schedule.html#hard-stringfreeze | 17:46 |
| melwitt | thanks. I approved a tiny docs only change earlier and afterward realized about string freeze and wondered if I should make sure I don't do anymore | 17:46 |
| melwitt | yeah, I was looking at that but 1) the email said horizon and friends and 2) over the years the scope of translated things has shrunk so I wasn't 100% what all it applies to these days | 17:46 |
| sean-k-mooney | i think its fine. this was here to help with localisation efforts | 17:46 |
| sean-k-mooney | melwitt: personally i would argure it time to remove the sting freeze milestones form teh schdule | 17:48 |
| sean-k-mooney | with that said the hard string freeze only come into effect at RC1 | 17:48 |
| sean-k-mooney | so it only applies to the stable branch until the actual release and not to master | 17:49 |
| sean-k-mooney | the soft string freeze is for master between FF and rc1 | 17:49 |
| sean-k-mooney | melwitt: for what its worth im not sure why sphinx lint did not bitch about the syntax issues i added it to catch and prevent those | 17:53 |
| melwitt | +1 on removing the milestones ... but at the very least at least I would appreciate some clarity from the i8n team side what is done nowadays regarding freezes. the i8n efforts used to be visible back in the day at design summits and stuff but it hasn't seemed that visible to me in more recent years | 17:53 |
| sean-k-mooney | maybe it does not detec of handel the unblanced case well | 17:53 |
| sean-k-mooney | " The file is read once at `nova-compute`` " | 17:53 |
| melwitt | sean-k-mooney: the patch was proposed before you added that stuff (it was from january) I've been going through some review dashboards and that's why I saw it | 17:54 |
| sean-k-mooney | i belive the currnt process is they do the changfes on a seperate server we dont look at and peropdically we get a gerrit review that we are jsut ment to appove | 17:54 |
| sean-k-mooney | which i kind of hate | 17:54 |
| sean-k-mooney | melwitt: oh what i ment was when i proposed the sphix-lint thing i fixed a bunch of these | 17:55 |
| sean-k-mooney | so im not sure why i didnt have to fix that one | 17:55 |
| melwitt | right.. I remember the bot changes but I'm not sure if they still do that? and if so, what impact does it have. it's like a black box for me | 17:56 |
| melwitt | sean-k-mooney: you did fix the `` things. the only remaining fix from the january patch was a it's => its grammar thing so it was technically 1/3 valid still 😛 | 17:56 |
| sean-k-mooney | ah ok | 17:57 |
| melwitt | when I looked at it I was like, "this looks really familiar" so I pulled up your patch and linked it in a comment, just for informational purposes | 17:58 |
| melwitt | I've been looking through review dashboards and launchpad bugs seeing what things I could clear out | 18:00 |
| melwitt | which reminds me, I replied to an issue someone opened yesterday about the inability to force live migration destinations that I thought was interesting https://bugs.launchpad.net/nova/+bug/2078932 | 18:01 |
| melwitt | I'm not sure if we have an official recommendation on how to do that given the "force" flags removal from the API | 18:02 |
| melwitt | if we do, I'd like to add it to the docs somewhere bc it seems like a common use case | 18:03 |
| *** bauzas_ is now known as bauzas | 18:14 | |
| *** bauzas_ is now known as bauzas | 18:31 | |
| sean-k-mooney | melwitt: well you can always use the old microversion but ya that kind of by desing | 18:46 |
| sean-k-mooney | schduler hint are not ment to be changeable for the lifetime of an instance | 18:46 |
| melwitt | right | 18:46 |
| sean-k-mooney | you can specify a host | 18:46 |
| sean-k-mooney | and provide that host passes all filters we will use it | 18:47 |
| sean-k-mooney | the jsonfilter is off by default as its kind of a security problem | 18:47 |
| sean-k-mooney | but obvioulsy if it has been used and used to selct based on host name then that vm is effectivly pinned and needs to be upgraded in place with downtime | 18:47 |
| melwitt | that doesn't work for them because they have a jsonfilter that filters on specific hostnames (I know) but they have some kind of numa pinning requirements and I dunno enough about that to know a better way | 18:48 |
| sean-k-mooney | they have this jsonfilter https://github.com/openstack/nova/blob/master/nova/scheduler/filters/json_filter.py#L24 | 18:48 |
| melwitt | I would like to document what is the right way to do this if possible because I think it will come up a lot | 18:49 |
| sean-k-mooney | that allows you to match on anyting in the host state object | 18:49 |
| melwitt | right | 18:49 |
| sean-k-mooney | well the write way is to not live migrate it | 18:49 |
| melwitt | :D | 18:49 |
| sean-k-mooney | what they want to do is intentially not supported | 18:49 |
| melwitt | they said it was a host evacuate situation though | 18:50 |
| sean-k-mooney | the could shelve and unhevle the host but there is no way to move the instance without recreating it | 18:50 |
| melwitt | which seems reasonable to me | 18:50 |
| sean-k-mooney | so how i woudl fix this | 18:50 |
| melwitt | ok. that's what I thought but I wasn't sure if there were more things I didn't know about | 18:50 |
| sean-k-mooney | is implemnt the recreat api i wanted to add a few years ago | 18:50 |
| sean-k-mooney | recreate is ment to be like resize and rebuild combined. one api that by defautl moves the isntance to another host alloing the embded flavor and image property to optionaly be udeated or for either to be chanaged | 18:51 |
| sean-k-mooney | as part of a request it woudl be reasonabel to update the schdeuler hits | 18:52 |
| sean-k-mooney | melwitt: in the short term a nova-mange command to update the reqest spec is proably what we should do | 18:52 |
| melwitt | sean-k-mooney: ok, good. cause that's what I told them :) | 18:53 |
| sean-k-mooney | long them an single api call that is "recreate this vm, keepign its data unless i ask for the image, and optionally changing the flavor" would avoid a lot of user/operator pain | 18:53 |
| sean-k-mooney | s/the image/the image to be changed/ | 18:54 |
| melwitt | but yeah, re: the recreate API for the longterm solution, if the nova-manage command isn't good enough, I think it would be helpful | 18:54 |
| sean-k-mooney | i want recreate for like 10 diffent usecase this just beign one of them | 18:54 |
| sean-k-mooney | another short term soltuion woudl be allow schduler hints to be passed to move ops | 18:55 |
| sean-k-mooney | so to migrate (cold/live) resize, unshleve, evacuate | 18:55 |
| melwitt | yeah, I could see that | 18:56 |
| sean-k-mooney | we allow doing thing like chainging the keypair i think for rebuild | 18:56 |
| melwitt | yes, we do | 18:56 |
| sean-k-mooney | so its not entirly strange to say if we are moving it allow the scheduer hits to optionally be updated | 18:56 |
| sean-k-mooney | im less sure if that should be member or admin policy wiese | 18:57 |
| sean-k-mooney | but i could see the argument either way | 18:57 |
| melwitt | yeah, agree | 18:57 |
| 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:58 |
| melwitt | I think regardless we need the nova-manage command. afaik everyone is +1 about it and it could be backported for older versions | 18:59 |
| *** bauzas_ is now known as bauzas | 19:00 | |
| 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 |
| melwitt | same | 19:00 |
| 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 |
| sean-k-mooney | or allwo you to also update the embded flavor extra spec liek the image properties | 19:01 |
| sean-k-mooney | that does not change teh advice of never modify flavor once they are in use | 19:01 |
| sean-k-mooney | but it give you an escape hatch if you did without forceing resizes | 19:02 |
| melwitt | why not resize? oh | 19:02 |
| sean-k-mooney | sometimes people pin thing to hosts :) the other reason i have heard is mano integration | 19:03 |
| sean-k-mooney | i.e. there is a system on top that created the worklaod | 19:03 |
| sean-k-mooney | and changing the flavor id is not trivial as a result | 19:03 |
| sean-k-mooney | for example if it was deployed with heat or somethign like that | 19:04 |
| melwitt | hm | 19:04 |
| sean-k-mooney | i soudl argure that you shoudl stop doing it wrong | 19:04 |
| sean-k-mooney | but customer sometimes dont like that | 19:05 |
| sean-k-mooney | not sure why :) | 19:05 |
| sean-k-mooney | anyway if you or they were to propsoe an extention to nova-mange for there usecase | 19:06 |
| sean-k-mooney | or even the addtion of scheduler hits to the move ops | 19:06 |
| sean-k-mooney | i would not really be against that | 19:06 |
| melwitt | yeah.. it's a balance of "how painful is it to do the right thing" | 19:06 |
| sean-k-mooney | do you remmber how horizon used to work ? | 19:07 |
| sean-k-mooney | nova has had imutable flavors for as long as i have worked on openstck | 19:07 |
| melwitt | oh, the "edit" flavor thing? | 19:07 |
| 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 |
| sean-k-mooney | ya | 19:07 |
| sean-k-mooney | that | 19:07 |
| melwitt | yeah, I remember. I take it that means it no longer does that? | 19:08 |
| 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 |
| melwitt | oh hah | 19:08 |
| sean-k-mooney | melwitt: so keyston also does nto allow you to update role asignment in trusts (a way of delegation access) | 19:09 |
| melwitt | I use horizon sometimes but not for changing flavors | 19:09 |
| sean-k-mooney | tripleo did the delete and recreat thing | 19:09 |
| sean-k-mooney | and it causes similar bugs to this day | 19:09 |
| sean-k-mooney | i use horizon more then i shoudl | 19:10 |
| sean-k-mooney | i have not tried skyline yet | 19:10 |
| sean-k-mooney | its been on my todolist but not high enough to take the time to do it | 19:11 |
| melwitt | and I just finally realized why it's named skyline | 19:12 |
| melwitt | 😝 | 19:12 |
| sean-k-mooney | why? | 19:13 |
| sean-k-mooney | oh.. | 19:13 |
| melwitt | lol | 19:13 |
| sean-k-mooney | its a horizon pun | 19:13 |
| sean-k-mooney | of couse it is why would anything in ptyhon ever not be a pun | 19:14 |
| melwitt | quite clever really. I liked the name just didn't get it | 19:14 |
| sean-k-mooney | ill begrudgingly admit its pretty good | 19:15 |
| melwitt | :) | 19:16 |
| sean-k-mooney | so you know https://instructlab.ai/ | 19:16 |
| melwitt | labrador | 19:16 |
| sean-k-mooney | the dog logo is apprently russel brants dog | 19:16 |
| JayF | using ipxe as the rescue image is the most brilliant thing I've read today | 19:17 |
| melwitt | oh, that's pretty cute. wears corrective lenses | 19:17 |
| sean-k-mooney | ya i also wonder if its a lab | 19:17 |
| 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 |
| melwitt | I think it is. I saw it somewhere else in the instructlab docs or something like that | 19:18 |
| sean-k-mooney | basically so you could pxe boot form isos in galnce and boto form bascially a blank disk | 19:18 |
| 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 |
| JayF | sounds familiar | 19:19 |
| sean-k-mooney | we chatted about using netboot.xyz | 19:19 |
| JayF | if only you knew some experts in getting things pxe booted ;) | 19:19 |
| JayF | you know ironic used to support this first class and dropped the feature, right? | 19:20 |
| sean-k-mooney | netboot.xyz? | 19:20 |
| JayF | so people didn't have to manage local bootloaders, we'd pxe into the OS on disk | 19:20 |
| JayF | so many of the moving parts may already be in place | 19:20 |
| JayF | no, netboot.xyz *does* power my personal homelab though :D (+cockpit to spin up the VMs) | 19:20 |
| sean-k-mooney | ya so what missing is being able to set the relevent dhcp option in the neturon subnet | 19:20 |
| sean-k-mooney | then you could jsut trivially set a netron nic as the boot device | 19:21 |
| JayF | That works though, is what I'm saying | 19:21 |
| sean-k-mooney | and if you wanted you could just run your own pxe server on another nova vm | 19:21 |
| JayF | Ironic does that today, tells neutron dhcp agent to serve up pxe | 19:21 |
| sean-k-mooney | JayF: it works for horizon | 19:21 |
| JayF | so the moving parts are likely there? | 19:21 |
| sean-k-mooney | *ironic | 19:21 |
| sean-k-mooney | but i think you might not be able to do this as a normal user | 19:22 |
| sean-k-mooney | i.e. i dont know if you can do this without being admin | 19:22 |
| JayF | oooh, that's a good point | 19:22 |
| sean-k-mooney | i thikn 99% of it is there however | 19:22 |
| sean-k-mooney | oh https://docs.openstack.org/api-ref/network/v2/index.html#extra-dhcp-option-extra-dhcp-opt-extension | 19:24 |
| sean-k-mooney | so this is what ironic is using | 19:24 |
| sean-k-mooney | oh... | 19:24 |
| sean-k-mooney | JayF: its on the port i always looked for this on the subnet | 19:24 |
| sean-k-mooney | because you defien extra routs and the dns servers on the subnet | 19:24 |
| sean-k-mooney | so i was expect the dhcp option ot also be on the subnet | 19:25 |
| sean-k-mooney | JayF: so ya i dont see why you could not do pxe boot today | 19:25 |
| 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:25 |
| sean-k-mooney | i should try doing this someday and write a doc... | 19:27 |
| *** bauzas_ is now known as bauzas | 19:28 | |
| sean-k-mooney | JayF: there is even openstack client support for this | 19:29 |
| JayF | yeah like, I don't want this feature personally | 19:30 |
| JayF | but I figured ironic might be a model for doing it (or at least pointing in a direction) | 19:30 |
| JayF | hint: this also could be used to enable UEFI HTTPBoot, which is superior to pxe in every way | 19:30 |
| JayF | this being said: Ironic-Conductor spins up and manages the tftp server. There is no neutron answer to that aiui. | 19:31 |
| sean-k-mooney | JayF: well since you say that if the ovmf file that wemu is using support that | 19:31 |
| sean-k-mooney | then that woudl also already work today | 19:31 |
| 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:32 |
| sean-k-mooney | is its really a question of does qemu/ovmf supprot http boot if so you could in thory use it | 19:33 |
| JayF | I guess that's kinda true, it still comes over dhcp information | 19:37 |
| JayF | so from a nova perspective, especially if you don't own the tftp/http/whatever server, it doesn't matter | 19:37 |
| sean-k-mooney | yep i have it up locally | 19:37 |
| sean-k-mooney | so my ovmf firmware supprot uefi and pxe boot | 19:37 |
| sean-k-mooney | *http and pxe boot | 19:37 |
| sean-k-mooney | i dont have dhcp confirued on my local libvirt to provide the dhcp options | 19:38 |
| sean-k-mooney | but i dont see why you could not make this work today | 19:38 |
| 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 |
| 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:39 |
| sean-k-mooney | anywya i should finish for the day | 19:40 |
| sean-k-mooney | JayF: before i go did ye get the auto lessee suff finished on the ironic side | 19:40 |
| JayF | It's got one +2, waiting review, basically paused since we got CVE patches in the gate | 19:41 |
| JayF | it'll be in this release, we don't FF like nova does :) | 19:41 |
| sean-k-mooney | good to know and ya i saw the maile yesterday | 19:41 |
| JayF | only piece missing that I promised, that frankly I forgot about until I looked at the BP yesterday is the migration script | 19:41 |
| JayF | that'll be trivial to write and document :) | 19:42 |
| JayF | although TBH I am extremely skeptical any operators will actually want to backfill lessee | 19:42 |
| sean-k-mooney | ya it might be nice to put that in an ironic-manage command or similar | 19:49 |
| sean-k-mooney | but it does not sound like its a blocker for the feature ot be used | 19:49 |
| sean-k-mooney | jsut a nice to have for consitency | 19:50 |
| sean-k-mooney | JayF: i assume an admin could just manually set the lessee on the ironic node if they wanted too | 19:50 |
| JayF | We do not have an ironic-manage command, I was just going to add something to our tools/ directory | 19:51 |
| 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 |
| JayF | with probably an option for shard (so you can do N processes to parallelize) | 19:52 |
| sean-k-mooney | JayF: oh really so you dont have an ironic-manage db_sync? | 19:53 |
| sean-k-mooney | how do ye manage db upgrade in ironic? | 19:53 |
| JayF | I thought it was ironic-dbsync? | 19:53 |
| JayF | IMBW | 19:53 |
| sean-k-mooney | yep https://opendev.org/openstack/ironic/src/branch/master/setup.cfg#L49 | 19:53 |
| sean-k-mooney | ok i tought <project>-manage was the normal convention for that tool | 19:54 |
| sean-k-mooney | but i ugess there is no really reason not to call it something else | 19:54 |
| sean-k-mooney | ok actully stoping for today this time o/ | 19:54 |
| JayF | yeah and TBH, with my operator hat on, I prefer tools like this not to require the whole app | 19:54 |
| JayF | (pip install nova to get nova-manage just feels overkill, even if it's not, really) | 19:55 |
| sean-k-mooney | well its internally using the same oslo version object and db fucntion ectra | 19:55 |
| sean-k-mooney | but ya we normally intend it to be run form where the conductor is | 19:56 |
| JayF | yeah, in this case though, I want to write a tool that's 100% API-shaped, no db magic needed | 19:56 |
| sean-k-mooney | it can be run remotely but that not what we expect peopel to do | 19:56 |
| JayF | I can tell you I've worked zero places that ran it, at upgrade time, from a nova-anything :) | 19:56 |
| sean-k-mooney | right makes sense | 19:56 |
| sean-k-mooney | well its normally ran form yoru openstack contoler nodes | 19:57 |
| sean-k-mooney | in contaieriesed installer yousually the nova-conductor container just because it already had the correct configs | 19:57 |
| sean-k-mooney | we have discussed having the conductore be able to just do it automatically in teh past when its starts | 19:58 |
| sean-k-mooney | but that alway felt a little too much out fo scope | 19:58 |
| 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 |
| JayF | we went O->U at one place using that kinda model | 20:01 |
| *** bauzas_ is now known as bauzas | 22:05 | |
| *** bauzas_ is now known as bauzas | 22:42 | |
| *** bauzas_ is now known as bauzas | 22: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 | 23:08 |
| *** bauzas_ is now known as bauzas | 23:10 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!