I've got a VM (spi-tools-host-1) that I'm not actively using right now. I could shut it down to release the CPU resources, but I want to be able to start it back up again at some point in the future with the same configuration. On AWS I would just back up all the storage and shut down the VM. Is there some way to do that in this environment?
I suspect the answer may include, "Yo, dummy, you should have used puppet instead of just installing things manually with apt-get". If that's the case, feel free to say that :-)
Or, is the VM so small that it's not worth worrying too much about the resources it's wasting?
On 06/07 08:59, Roy Smith wrote:
I've got a VM (spi-tools-host-1) that I'm not actively using right now. I could shut it down to release the CPU resources, but I want to be able to start it back up again at some point in the future with the same configuration. On AWS I would just back up all the storage and shut down the VM. Is there some way to do that in this environment?
I suspect the answer may include, "Yo, dummy, you should have used puppet instead of just installing things manually with apt-get". If that's the case, feel free to say that :-)
You should be able to just turn it off, and whenever you want, just start it up again, that will preserve the current status of the hard drive.
There's actually several ways: * pause -> will preserve the current running status, with whatever is on ram. It will store the VM ram info on the hypervisor RAM, so it will stay on the current hypervisor but will be fast to start. * suspend -> similar as above, but storing the VM ram on disk. * shut off -> will turn the OS on the VM off, same as turning off a bare metal, the VM OS will stop any processes and such, and will have to boot when turning it on (slower, but allows moving the VM easily).
If you don't really care about stopping the current running processes, I'd recommend shutting the VM off, and then whenever you need to, turning it on.
In any case I do recommend though using puppet xd.
Or, is the VM so small that it's not worth worrying too much about the resources it's wasting?
Your VM is quite small, so it's not much of a problem, though if it's not an issue would be nice to save the resources :)
Thanks a lot for being mindful!
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
Looking in https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a63... https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a636839d66f/, I also see "Shelve Instance"; what does that do? I'm actually kind of curious about that last one because in my exploring, I accidentally clicked it, but other than seeing a "shelving" progress bar appear, it doesn't seem to have actually done anything. My instance is still running normally. Fingers crossed :-)
On Jun 7, 2021, at 9:20 AM, David Caro dcaro@wikimedia.org wrote:
There's actually several ways:
- pause -> will preserve the current running status, with whatever is on ram. It will store the VM ram info on the
hypervisor RAM, so it will stay on the current hypervisor but will be fast to start.
- suspend -> similar as above, but storing the VM ram on disk.
- shut off -> will turn the OS on the VM off, same as turning off a bare metal, the VM OS will stop any processes and
such, and will have to boot when turning it on (slower, but allows moving the VM easily).
Shelving is very similar to shutting the VM off, but a bit more complex. The quota for that instance will be deduced from your quota too, and if not unshelved in a specific amount of time, the VM will be removed. When unshelving, you will need to have enough quota to get it back.
Currently your server is in 'shelving' status, so it sholud be waiting for it to shut off, once that happens it will consider it as shelved. If it's still running in a while feel free to open a ticket so we do some debugging.
Cheers!
On 06/07 09:50, Roy Smith wrote:
Looking in https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a63... https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a636839d66f/, I also see "Shelve Instance"; what does that do? I'm actually kind of curious about that last one because in my exploring, I accidentally clicked it, but other than seeing a "shelving" progress bar appear, it doesn't seem to have actually done anything. My instance is still running normally. Fingers crossed :-)
On Jun 7, 2021, at 9:20 AM, David Caro dcaro@wikimedia.org wrote:
There's actually several ways:
- pause -> will preserve the current running status, with whatever is on ram. It will store the VM ram info on the
hypervisor RAM, so it will stay on the current hypervisor but will be fast to start.
- suspend -> similar as above, but storing the VM ram on disk.
- shut off -> will turn the OS on the VM off, same as turning off a bare metal, the VM OS will stop any processes and
such, and will have to boot when turning it on (slower, but allows moving the VM easily).
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
https://phabricator.wikimedia.org/T284461 https://phabricator.wikimedia.org/T284461
Also see https://phabricator.wikimedia.org/T284462 https://phabricator.wikimedia.org/T284462
On Jun 7, 2021, at 10:01 AM, David Caro dcaro@wikimedia.org wrote:
Shelving is very similar to shutting the VM off, but a bit more complex. The quota for that instance will be deduced from your quota too, and if not unshelved in a specific amount of time, the VM will be removed. When unshelving, you will need to have enough quota to get it back.
Currently your server is in 'shelving' status, so it sholud be waiting for it to shut off, once that happens it will consider it as shelved. If it's still running in a while feel free to open a ticket so we do some debugging.
Cheers!
On 06/07 09:50, Roy Smith wrote:
Looking in https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a63... https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a636839d66f/<https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a63... https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a636839d66f/>, I also see "Shelve Instance"; what does that do? I'm actually kind of curious about that last one because in my exploring, I accidentally clicked it, but other than seeing a "shelving" progress bar appear, it doesn't seem to have actually done anything. My instance is still running normally. Fingers crossed :-)
On Jun 7, 2021, at 9:20 AM, David Caro dcaro@wikimedia.org wrote:
There's actually several ways:
- pause -> will preserve the current running status, with whatever is on ram. It will store the VM ram info on the
hypervisor RAM, so it will stay on the current hypervisor but will be fast to start.
- suspend -> similar as above, but storing the VM ram on disk.
- shut off -> will turn the OS on the VM off, same as turning off a bare metal, the VM OS will stop any processes and
such, and will have to boot when turning it on (slower, but allows moving the VM easily).
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
-- David Caro SRE - Cloud Services Wikimedia Foundation <https://wikimediafoundation.org/ https://wikimediafoundation.org/> PGP Signature: 7180 83A2 AC8B 314F B4CE 1171 4071 C7E1 D262 69C3
"Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment." _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org mailto:cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/ https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
I'll have a look at those tasks; it may be that the 'fix' will be to disable the 'shelving' feature.
A couple of things to keep in mind regarding your original question:
- A shut down VM is no longer maintained by puppet, which means it might miss out on security updates and the like while unreachable - A running (but idle) VM doesn't consume a whole lot of resources
For both of the above reasons, just stopping services on the VM and leaving it running is probably your safest/easiest bet. I will nonetheless check out what the story is with shelving.
On 6/7/21 9:24 AM, Roy Smith wrote:
https://phabricator.wikimedia.org/T284461 https://phabricator.wikimedia.org/T284461
Also see https://phabricator.wikimedia.org/T284462 https://phabricator.wikimedia.org/T284462
On Jun 7, 2021, at 10:01 AM, David Caro <dcaro@wikimedia.org mailto:dcaro@wikimedia.org> wrote:
Shelving is very similar to shutting the VM off, but a bit more complex. The quota for that instance will be deduced from your quota too, and if not unshelved in a specific amount of time, the VM will be removed. When unshelving, you will need to have enough quota to get it back.
Currently your server is in 'shelving' status, so it sholud be waiting for it to shut off, once that happens it will consider it as shelved. If it's still running in a while feel free to open a ticket so we do some debugging.
Cheers!
On 06/07 09:50, Roy Smith wrote:
Looking inhttps://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a63... https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a636839d66f/<https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a63... https://horizon.wikimedia.org/project/instances/43d3e9f2-b7d5-4a51-92b6-6a636839d66f/>, I also see "Shelve Instance"; what does that do? I'm actually kind of curious about that last one because in my exploring, I accidentally clicked it, but other than seeing a "shelving" progress bar appear, it doesn't seem to have actually done anything. My instance is still running normally. Fingers crossed :-)
On Jun 7, 2021, at 9:20 AM, David Caro <dcaro@wikimedia.org mailto:dcaro@wikimedia.org> wrote:
There's actually several ways:
- pause -> will preserve the current running status, with whatever
is on ram. It will store the VM ram info on the hypervisor RAM, so it will stay on the current hypervisor but will be fast to start.
- suspend -> similar as above, but storing the VM ram on disk.
- shut off -> will turn the OS on the VM off, same as turning off a
bare metal, the VM OS will stop any processes and such, and will have to boot when turning it on (slower, but allows moving the VM easily).
Cloud mailing list -- cloud@lists.wikimedia.org mailto:cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/ https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
-- David Caro SRE - Cloud Services Wikimedia Foundation <https://wikimediafoundation.org/ https://wikimediafoundation.org/> PGP Signature: 7180 83A2 AC8B 314F B4CE 1171 4071 C7E1 D262 69C3
"Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment." _______________________________________________ Cloud mailing list --cloud@lists.wikimedia.org mailto:cloud@lists.wikimedia.org List information:https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/ https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/