On 10/05/2016 02:11 PM, mj wrote:
> Hi,
>
> Just noticed something we find counterintuitive in proxmox:
>
> We are using HA for some of our machines.
>
> As we needed to work on an HA-managed machine, we disabled HA, so that
> we could manually halt/reboot/start it.
>
> But to our surprise, the
On 10/06/2016 11:51 AM, Kevin Lemonnier wrote:
That's not a bid idea. I assume we all make the mistake for the same reason :
trying to disable HA without losing the comment and having to figure out the id
again.
Exactly the same here! :-)
I personnaly use the comment to put the machine name
On 10/06/2016 11:51 AM, Kevin Lemonnier wrote:
Yes, I would find that logical. And perhaps also a third option: to
disable-HA management, so we can work on a machine, without having to
completely remove it from the HA system.
That's not a bid idea. I assume we all make the mistake for the same
>
> Yes, I would find that logical. And perhaps also a third option: to
> disable-HA management, so we can work on a machine, without having to
> completely remove it from the HA system.
>
That's not a bid idea. I assume we all make the mistake for the same reason :
trying to disable HA withou
On 10/06/2016 11:38 AM, Emmanuel Kasper wrote:
if we can propose name I would propose 'ensure-always-off' and
'ensure-always-on' but this would only work in the context of a service
being a guest system
Yes, I would find that logical. And perhaps also a third option: to
disable-HA management
On 10/06/2016 11:27 AM, Thomas Lamprecht wrote:
> Hi,
>
>
> On 10/06/2016 11:01 AM, Eneko Lacunza wrote:
>> Hi,
>>
>> About the "disable" thing, wouldn't it be much clearer and less prone
>> to confusion to rename it to "disable-ha-and-stop"? And I guess,
>> "enable-ha-and-start"?
>
> for me n
>
> I'd propose adding a tooltip to the HA resource edit window which pops
> up if a
> user changes the "enabled" status of a service.
>
Yes, good idea ! That way someone who knows won't be bothered by the change,
and new users shouldn't make the mistake, I like it.
--
Kevin Lemonnier
PGP Fin
Hi,
On 10/06/2016 11:01 AM, Eneko Lacunza wrote:
Hi,
About the "disable" thing, wouldn't it be much clearer and less prone
to confusion to rename it to "disable-ha-and-stop"? And I guess,
"enable-ha-and-start"?
for me not, as its not disabling ha but disabling the service (ok, I'm
really
Hi,
About the "disable" thing, wouldn't it be much clearer and less prone to
confusion to rename it to "disable-ha-and-stop"? And I guess,
"enable-ha-and-start"?
El 06/10/16 a las 09:39, Thomas Lamprecht escribió:
On 10/06/2016 09:08 AM, Kevin Lemonnier wrote:
He wanted to remove it from HA
On 10/06/2016 09:08 AM, Kevin Lemonnier wrote:
He wanted to remove it from HA managed but said to HA it should be
stopped, nothing to do with the stop/shutdown button confusion :)
Yeah sorry about that, I hijacked this thread with my somewhat un-related
complaint, that's my bad :).
No worries,
> He wanted to remove it from HA managed but said to HA it should be
> stopped, nothing to do with the stop/shutdown button confusion :)
Yeah sorry about that, I hijacked this thread with my somewhat un-related
complaint, that's my bad :).
The HA enable / disable is a bit confusing, it just does
Thanks Thomas, sorry for the snottiness on my part. Pre coffee :(
On 6 October 2016 at 15:54, Thomas Lamprecht wrote:
> Hi,
>
> On 10/05/2016 09:52 PM, Lindsay Mathieson wrote:
>>
>> On 6/10/2016 1:09 AM, Thomas Lamprecht wrote:
>>>
>>> Please *always* read the documentation if you want HA and if
Hi,
On 10/05/2016 09:52 PM, Lindsay Mathieson wrote:
On 6/10/2016 1:09 AM, Thomas Lamprecht wrote:
Please *always* read the documentation if you want HA and if you want
to use it
in production you surely shouldn't assume anything and read the docs
first.
Ignores the point people are making -
On 6/10/2016 1:09 AM, Thomas Lamprecht wrote:
Please *always* read the documentation if you want HA and if you want
to use it
in production you surely shouldn't assume anything and read the docs
first.
Ignores the point people are making - if you use stop its because you
*need* to. Now they c
On Wed, 5 Oct 2016 17:35:28 +0200
Michael Rasmussen wrote:
> My biggest issue with the current functionality is that I sometimes
> forgets a VM is HA enabled so pressing 'Shutdown' to be able to do
> maintenance has the unwanted side effect of a reboot. Maybe the
> shutdown and stop button could
On Wed, 5 Oct 2016 17:17:22 +0200
Thomas Lamprecht wrote:
>
> We can pick it up again, if someone is willing to open a bug report at
> https://bugzilla.proxmox.com/ to help me track this issue would be great.
> I can do it too myself tomorrow..
> As changing the behaviour between releases seems
> jokes aside, we evaluated the option of the clean shutdown for HA
> and changing it for the stop command. But it was seen is minor (annoying)
> problem and other more important stuff let me forgot about that.
I can understand that, it's clearly not a priority, but it would be nice !
>
> We can
On 05.10.2016 17:06, Michael Rasmussen wrote:
On Wed, 5 Oct 2016 17:01:23 +0200
Thomas Lamprecht wrote:
Our reason for this is that a HA enabled service should be *cleanly* shutdown.
Stopping a VM is like pulling the power cord out, which can be bad :)
We can re evaluate that. For us HA man
>
>
> Our reason for this is that a HA enabled service should be *cleanly* shutdown.
> Stopping a VM is like pulling the power cord out, which can be bad :)
> We can re evaluate that. For us HA managed service are thought for service
> which have to run and do that always.
> "Killing" them often
Hi,
On 05.10.2016 14:11, mj wrote:
Hi,
Just noticed something we find counterintuitive in proxmox:
We are using HA for some of our machines.
As we needed to work on an HA-managed machine, we disabled HA, so that we could
manually halt/reboot/start it.
But to our surprise, the "disable" butt
On Wed, 5 Oct 2016 17:01:23 +0200
Thomas Lamprecht wrote:
>
> Our reason for this is that a HA enabled service should be *cleanly* shutdown.
> Stopping a VM is like pulling the power cord out, which can be bad :)
> We can re evaluate that. For us HA managed service are thought for service
> whic
Hi,
On 05.10.2016 14:43, mj wrote:
Hi Kevin,
On 10/05/2016 02:25 PM, Kevin Lemonnier wrote:
Just as it's weird and very very annoying that you can't "Stop" a VM
when HA is enabled. If you click on "Stop", it actually tries to do a
shutdown on it, and only does an actual stop after that times o
Not that this pertains to your situation, just a share/fyi
pre v4 I had an occasion where I enabled HA a few VMs (while running)
and ended up with what I will call ghost VMs running. Hope its better
now, but if and when I return to this feature I'm sure I will use extra
caution. The way I fin
Hi Kevin,
On 10/05/2016 02:25 PM, Kevin Lemonnier wrote:
Just as it's weird and very very annoying that you can't "Stop" a VM
when HA is enabled. If you click on "Stop", it actually tries to do a
shutdown on it, and only does an actual stop after that times out.
So much time lost waiting for thi
>
> Are we the only ones feeling this?
>
No, I killed a few production VMs because of this too. Took me longer
than I'd like to admit to understand why the VMs where powering down ..
Just as it's weird and very very annoying that you can't "Stop" a VM
when HA is enabled. If you click on "Stop",
Hi,
Just noticed something we find counterintuitive in proxmox:
We are using HA for some of our machines.
As we needed to work on an HA-managed machine, we disabled HA, so that
we could manually halt/reboot/start it.
But to our surprise, the "disable" button in HA actually seems to mean:
sh
26 matches
Mail list logo