Hello Tzach,
Agree for a graceful shutdown there should be some steps ahead. Im
actually asking the question because the hardware we use has a high
failure rate on RAID controllers. The physical machine reacts with a
reboot, so its not controlable from our side. We dont want to delete the
ins
Hello Remo,
Exactly what I was looking for! If I could give you a rating it would be
the highest :)
Cheers,
Chris
On 2017-11-03 1:27, Remo Mattei wrote:
sorry forgot to paste the file location
/etc/sysconfig/libvirt-guests
On 11/2/17 11:21 AM, Remo Mattei wrote:
If you are using CentOS
>There is this nova option:
>resume_guests_state_on_host_boot=true
>
>But it doesn't delete or shutdown instances but rather turns them on
>automatically once compute host resumes.
>which might also work for you, probably not just mentioning it any way.
Note that you might want to check some thin
you could upgrade to Tripleo :)
Ciao,
On 11/2/17 11:18 AM, Ken Houle wrote:
>
> Evgeniy L.
>
>
>
> Thank you for the information. I have rebuilt the Fuel Community 11
> server and left everything default with the exception of setting the
> PXE support to eth1. I am seeing the same issue.
>
> T
sorry forgot to paste the file location
/etc/sysconfig/libvirt-guests
On 11/2/17 11:21 AM, Remo Mattei wrote:
> If you are using CentOS / Red Hat you can modify this file:
>
> libvirt-guests:#ON_SHUTDOWN=suspend
>
>
>
> # action taken on host shutdown
> # - suspend all running guests are sus
If you are using CentOS / Red Hat you can modify this file:
libvirt-guests:#ON_SHUTDOWN=suspend
# action taken on host shutdown
# - suspend all running guests are suspended using virsh managedsave
# - shutdown all running guests are asked to shutdown. Please be
careful with
# th
Evgeniy L.
Thank you for the information. I have rebuilt the Fuel Community 11 server and
left everything default with the exception of setting the PXE support to eth1.
I am seeing the same issue.
The Silicon Mechanics server with a Supermicro system board as been configured
in every possib
On 11/02/2017 01:03 AM, Chris wrote:
Hello,
When we shut down a compute node the instances running on it get suspended. This
generates some difficulties with some applications like RabbitMQ dont like to be
suspended. Is there a way to change this behavior so that the running instances
gets kille
On 11/02/2017 04:32 AM, Ramu, MohanX wrote:
Hi All,
Whenever I run devstack set up scripts it always download the latest
minor version of OpenStack.
I want to control that by connecting my local OpenStack repo is it
possible?
Please let me know.
Thanks & regards,
Mohan Ramu
It is, we d
On Thu, Nov 2, 2017 at 6:32 AM, Ramu, MohanX wrote:
> I want to control that by connecting my local OpenStack repo is it possible?
In stackrc you will find a number of environment variable pairs of the
form XXX_REPO and XXX_BRANCH. Those can be used to get very specific
about the repo and branch
Hi All,
Whenever I run devstack set up scripts it always download the latest minor
version of OpenStack.
I want to control that by connecting my local OpenStack repo is it possible?
Please let me know.
Thanks & regards,
Mohan Ramu
___
Mailing list:
Hi Evgeniy,
apt-cache policy fuel-ha-utils says that the package is not to be found.
Now I re-installed fuel on another node(as there was a lot of issues faced
on the old one), and created local repo using these commands:
fuel-mirror create -P ubuntu -G ubuntu
fuel-mirror apply -G ubuntu -I /usr
Hi!
When I need to reboot a compute node (because of some driver lock-up or such
problems), I first stop nova-compute so that it does not report the shutoff
state of VMs to the database and resume_guests_state_on_host_boot=true does
actually start them. Then I press the power switch on the VMs
Hi,
A better Q would be why do you shutdown a compute node to begin with?
I mean if you need you should do so in an orderly fashion basically
excavate instances
or shut instances down manually, put the compute node in maintenance mode.
On rebooting compute node remove it from maintenance mode, tur
Hello,
When we shut down a compute node the instances running on it get
suspended. This generates some difficulties with some applications like
RabbitMQ dont like to be suspended. Is there a way to change this
behavior so that the running instances gets killed or shutdown instead?
Thanks in
15 matches
Mail list logo
