Bug 1090796 - OVIRT35 - [RFE] Re-work engine ovirt-node host-deploy sequence
Summary: OVIRT35 - [RFE] Re-work engine ovirt-node host-deploy sequence
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Ravi Nori
QA Contact: Jiri Belka
URL:
Whiteboard: infra
Depends On:
Blocks: 989546
TreeView+ depends on / blocked
 
Reported: 2014-04-24 07:57 UTC by Oved Ourfali
Modified: 2016-02-10 19:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-17 12:41:48 UTC
oVirt Team: Infra
Embargoed:

Attachments (Terms of Use)

Description Oved Ourfali 2014-04-24 07:57:41 UTC 
CURRENT IMPLEMENTATION

ovirt-node can be either added like regular host or registered/approved.

Once added, it can only be upgraded.

NEW IMPLEMENTATION

Support two options:

1. ovirt-node upgrade - as in current implementation.

2. ovirt-node reinstall - behaves as host re-install, just perform the host-deploy again.

REASONING

If ovirt-node was reinstalled, or there was other issues like require to re-enroll certificate, there is no need to upgrade node to different version, just to deploy again.

APPENDIXES

While doing this work, please also separate the VdsInstallCommand into two commands, once for installation/reinstallation (both node and host), and one for ovirt-node upgrade. These two logics resides within the same command which is invalid.
Comment 1 Jiri Belka 2014-08-01 09:41:00 UTC 
ok as BZ989546.
Comment 2 Sandro Bonazzola 2014-10-17 12:41:48 UTC 
oVirt 3.5 has been released and should include the fix for this issue.
Note You need to log in before you can comment on or make changes to this bug.