I think it's more sensible, the initial status should be the real status for
this host (trusted / untrusted) only the untrusted host will be set to
non-operational.
we just need poll this host instead of all of the hosts in the cluster if this
can be done in InitVdsOnUpCommand, and we suppose
Hi Dave,
Can't a host become untrusted without being rebooted?
If that is really the case, there is no need for a periodic check - the trigger
for the check would be the host rebooting (which is visible to the engine).
Thanks,
Ofri
- Original Message -
From: Wei D Chen
- Original Message -
From: Ofri Masad oma...@redhat.com
To: Wei D Chen wei.d.c...@intel.com
Cc: Oved Ourfalli ov...@redhat.com, engine-devel@ovirt.org
Sent: Thursday, April 18, 2013 9:38:26 AM
Subject: Re: [Engine-devel] minutes for sync up on Open Attestation
integration with
Yes, the host must be rebooted to take effect. Doron, what do you think?
Best Regards,
Dave Chen
-Original Message-
From: Omer Frenkel [mailto:ofren...@redhat.com]
Sent: Thursday, April 18, 2013 3:20 PM
To: Ofri Masad
Cc: Chen, Wei D; Oved Ourfalli; engine-devel@ovirt.org
Subject: Re:
Generally speaking I agree, we can drop the periodic check is
this is the way we expect it to work (ie- change trust level only during
reboot).
The only thing I'd like to verify is what happens is we miss something.
ie- let's assume the engine crashed. During the engine down time a host
reboots
We run the query each time the host is moving to UP state.
Which means, we query all the hosts on engine restart. if the host was
unreachable or down for any reason - we will query it again before moving to UP
state.
Ofri
- Original Message -
From: Doron Fediuck dfedi...@redhat.com
True, I just want folks to be aware of it.
So this should resolve it all.
Now just make sure to optimize the attestation call.
- Original Message -
From: Ofri Masad oma...@redhat.com
To: Doron Fediuck dfedi...@redhat.com
Cc: Oved Ourfalli ov...@redhat.com, engine-devel@ovirt.org
Sent:
Hi Dave,
The VdsUpdateRunTimeInfo runs every 3 seconds or so. so it not a good place to
call the attestation host.
Instead, like we suggested earlier, create a new Quartz job (like the one I've
sent you in the QuotaManager class) which run every couple of minutes and
update the hosts state.
Thanks Ofri, whether Quartz job is configurable? If we can config interval
time, it will do us a favor.
Best Regards,
Dave Chen
-Original Message-
From: Ofri Masad [mailto:oma...@redhat.com]
Sent: Wednesday, April 17, 2013 3:23 PM
To: Chen, Wei D
Cc: Omer Frenkel; Doron Fediuck; Oved
Of course,
If you create a new Quartz job is fully configurable.
look at my answers in the beginning of this thread
Ofri
- Original Message -
From: Wei D Chen wei.d.c...@intel.com
To: Ofri Masad oma...@redhat.com
Cc: Omer Frenkel ofren...@redhat.com, Doron Fediuck
On 04/17/2013 10:23 AM, Ofri Masad wrote:
Hi Dave,
The VdsUpdateRunTimeInfo runs every 3 seconds or so. so it not a good place to
call the attestation host.
Instead, like we suggested earlier, create a new Quartz job (like the one I've
sent you in the QuotaManager class) which run every couple
- Original Message -
From: Wei D Chen wei.d.c...@intel.com
To: Doron Fediuck dfedi...@redhat.com, Ofri Masad oma...@redhat.com
Cc: engine-devel@ovirt.org
Sent: Monday, April 15, 2013 8:54:18 AM
Subject: Re: [Engine-devel] minutes for sync up on Open Attestation
integration with
- Original Message -
From: Itamar Heim ih...@redhat.com
To: Oved Ourfalli ov...@redhat.com
Cc: engine-devel@ovirt.org
Sent: Monday, April 15, 2013 9:49:12 AM
Subject: Re: [Engine-devel] minutes for sync up on Open Attestation
integration with oVirt in 4/9
On 04/15/2013 09:20
- Original Message -
From: Doron Fediuck dfedi...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: Oved Ourfalli ov...@redhat.com, engine-devel@ovirt.org
Sent: Monday, April 15, 2013 10:05:57 AM
Subject: Re: [Engine-devel] minutes for sync up on Open Attestation
integration with
Good approach, thanks all. How long it needs to invoke periodic check in the
class of VdsUpdateRunTimeInfo? Whether this time configurable? My concern is if
the initial status of each host added into trusted cluster is non-operational,
we need wait a long time for the invoking of this periodic
Hi Doron and Ofri,
Thanks for your reply, here is some other question.
ii. When adding a host into the trusted cluster, the host will be attested via
OAT service, only trusted hosted can be added.
Would you also kindly tell me if there is any mandatory logic check when adding
a host into a
16 matches
Mail list logo
