Open Stack

On Mon, 2022-07-25 at 18:07 -0400, Laurent Dumont wrote:
> I don't think this is possible. It might be possible to add it to the image
> and then do a rebuild? But that's pretty close to recreating your instances.
thats the only offically supported way to do this yes.

the hack to avoid that is to insert the mising image properties into the db directly then hard reboot
the guest if it does not change schduleing.

the qemu guest agent does not.

for other image properties you might need to cold/live migrate or shelve and unshleve to place it on a valid host
after modifying the db.

rebuild is the prefered approch in this case if the guest agent is requried.
> 
> On Mon, Jul 25, 2022 at 2:59 PM John Ratliff <jdratlif at globalnoc.iu.edu>
> wrote:
> 
> > We forgot to set this property on our image before creating several
> > servers in our openstack cluster. I tried adding this property to the
> > volume of one of the hosts and shutting it down / turning it back on, but
> > it didn’t help.
> > 
> > 
> > 
> > I found this blog post showing one way that worked, but it requires manual
> > database editing. I was hoping for something a bit less typo-prone, like
> > something in the openstack cli.
> > 
> > 
> > https://www.thenoccave.com/2021/07/openstack-qemu-guest-tools-after-creation/
> > 
> > 
> > 
> > I can automate the above with ansible if that’s the only way, but if
> > someone has a better suggestion that doesn’t involve recreating our
> > instances, I would appreciate it.
> > 
> > 
> > 
> > Thanks.
> > 
> > 
> > 
> > --John Ratliff
> > 
> > 
> >