Re: [Users] Remove host from hosted-engine setup

2014-02-12 Thread Doron Fediuck


- Original Message -
 From: Frank Wall f...@moov.de
 To: Doron Fediuck dfedi...@redhat.com
 Cc: users@ovirt.org, Greg Padgett gpadg...@redhat.com, Jiri Moskovcak 
 jmosk...@redhat.com, Martin Sivak
 msi...@redhat.com
 Sent: Tuesday, February 11, 2014 7:05:49 PM
 Subject: Re: [Users] Remove host from hosted-engine setup
 
 Hi Doron,
 
 On Tue, Feb 11, 2014 at 11:49:30AM -0500, Doron Fediuck wrote:
  This is still in the works, but the right way to retire a host
  is first to put it into local maintenance (there's CLI for it
  and hopefully by 3.4 GA we will do it when you use the UI to put
  a host into maintenance).
  Once the host is in local HA maintenance, stale data is no longer
  reported, which should give you a valid status report.
  
  Just FYI, we prefer to keep the original data for forensics, as
  HA behavior is sensitive and we'd like to be able to trace back
  in case of a failure.
 
 thanks for this clarification. Would it be possible to overwrite
 a retired host by choosing the same Host ID for a new host?
 
 
 Thanks
 - Frank
 

Hi Frank,
yes. I'm assuming you're going to assign a new host with the
retired's host ID. In this case the data will be overwritten.
If you have any issues, please report.

Thanks!
Doron
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] Remove host from hosted-engine setup

2014-02-11 Thread Frank Wall
Hi,

I've retired a host that was part of a hosted-engine setup. How do I
remove this host from my hosted-engine HA setup?

I have retired host01 and would like to remove it completely:

[root@host03 ~]# hosted-engine --vm-status

--== Host 1 status ==--

Status up-to-date  : False
Hostname   : host01.example.com
Host ID: 1
Engine status  : unknown stale-data
Score  : 2400
Local maintenance  : False
Host timestamp : 1390840600
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1390840600 (Mon Jan 27 17:36:40 2014)
host-id=1
score=2400
maintenance=False
bridge=True
cpu-load=0.0034
engine-health={reason: vm not running on this host, health: 
bad, vm: down, detail: unknown}
gateway=True
mem-free=127844


--== Host 2 status ==--

Status up-to-date  : True
Hostname   : host02.example.com
Host ID: 2
Engine status  : {health: good, vm: up, detail: 
up}
Score  : 2400
Local maintenance  : False
Host timestamp : 1392129793
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1392129793 (Tue Feb 11 15:43:13 2014)
host-id=2
score=2400
maintenance=False
bridge=True
cpu-load=0.0057
engine-health={health: good, vm: up, detail: up}
gateway=True
mem-free=107251


--== Host 3 status ==--

Status up-to-date  : True
Hostname   : host03.example.com
Host ID: 3
Engine status  : {reason: vm not running on this host, 
health: bad, vm: down, detail: unknown}
Score  : 2400
Local maintenance  : False
Host timestamp : 1392129796
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1392129796 (Tue Feb 11 15:43:16 2014)
host-id=3
score=2400
maintenance=False
bridge=True
cpu-load=0.0134
engine-health={reason: vm not running on this host, health: 
bad, vm: down, detail: unknown}
gateway=True
mem-free=127838


Thanks
- Frank
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Remove host from hosted-engine setup

2014-02-11 Thread Doron Fediuck


- Original Message -
 From: Frank Wall f...@moov.de
 To: users@ovirt.org
 Sent: Tuesday, February 11, 2014 4:51:14 PM
 Subject: [Users] Remove host from hosted-engine setup
 
 Hi,
 
 I've retired a host that was part of a hosted-engine setup. How do I
 remove this host from my hosted-engine HA setup?
 
 I have retired host01 and would like to remove it completely:
 
 [root@host03 ~]# hosted-engine --vm-status
 
 --== Host 1 status ==--
 
 Status up-to-date  : False
 Hostname   : host01.example.com
 Host ID: 1
 Engine status  : unknown stale-data
 Score  : 2400
 Local maintenance  : False
 Host timestamp : 1390840600
 Extra metadata (valid at timestamp):
   metadata_parse_version=1
   metadata_feature_version=1
   timestamp=1390840600 (Mon Jan 27 17:36:40 2014)
   host-id=1
   score=2400
   maintenance=False
   bridge=True
   cpu-load=0.0034
   engine-health={reason: vm not running on this host, health: bad,
   vm: down, detail: unknown}
   gateway=True
   mem-free=127844
 
 
 --== Host 2 status ==--
 
 Status up-to-date  : True
 Hostname   : host02.example.com
 Host ID: 2
 Engine status  : {health: good, vm: up, detail:
 up}
 Score  : 2400
 Local maintenance  : False
 Host timestamp : 1392129793
 Extra metadata (valid at timestamp):
   metadata_parse_version=1
   metadata_feature_version=1
   timestamp=1392129793 (Tue Feb 11 15:43:13 2014)
   host-id=2
   score=2400
   maintenance=False
   bridge=True
   cpu-load=0.0057
   engine-health={health: good, vm: up, detail: up}
   gateway=True
   mem-free=107251
 
 
 --== Host 3 status ==--
 
 Status up-to-date  : True
 Hostname   : host03.example.com
 Host ID: 3
 Engine status  : {reason: vm not running on this
 host, health: bad, vm: down, detail: unknown}
 Score  : 2400
 Local maintenance  : False
 Host timestamp : 1392129796
 Extra metadata (valid at timestamp):
   metadata_parse_version=1
   metadata_feature_version=1
   timestamp=1392129796 (Tue Feb 11 15:43:16 2014)
   host-id=3
   score=2400
   maintenance=False
   bridge=True
   cpu-load=0.0134
   engine-health={reason: vm not running on this host, health: bad,
   vm: down, detail: unknown}
   gateway=True
   mem-free=127838
 
 
 Thanks
 - Frank

Hi Frank.

This is still in the works, but the right way to retire a host
is first to put it into local maintenance (there's CLI for it
and hopefully by 3.4 GA we will do it when you use the UI to put
a host into maintenance).
Once the host is in local HA maintenance, stale data is no longer
reported, which should give you a valid status report.

Just FYI, we prefer to keep the original data for forensics, as
HA behavior is sensitive and we'd like to be able to trace back
in case of a failure.

Doron
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Remove host from hosted-engine setup

2014-02-11 Thread Frank Wall
Hi Doron,

On Tue, Feb 11, 2014 at 11:49:30AM -0500, Doron Fediuck wrote:
 This is still in the works, but the right way to retire a host
 is first to put it into local maintenance (there's CLI for it
 and hopefully by 3.4 GA we will do it when you use the UI to put
 a host into maintenance).
 Once the host is in local HA maintenance, stale data is no longer
 reported, which should give you a valid status report.
 
 Just FYI, we prefer to keep the original data for forensics, as
 HA behavior is sensitive and we'd like to be able to trace back
 in case of a failure.

thanks for this clarification. Would it be possible to overwrite
a retired host by choosing the same Host ID for a new host?


Thanks
- Frank
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users