Red Hat Bugzilla – Bug 978862
[Admin] [Docs] Migrate ovirt-engine-setup and AIO plugin to otopi
Last modified: 2015-09-22 09:09 EDT
Any impact should be limited to changes to the Upgrades/Updates content that result from a new way of updating.
+++ This bug was initially created as a clone of Bug #975668 +++
* Quick Start?
+++ This bug was initially created as a clone of Bug #967508 +++
cloned for RHEV-M 3.3 tracking
+++ This bug was initially created as a clone of Bug #911191 +++
engine-setup, engine-cleanup, engine-upgrade and the AIO plugin should be migrated to otopi.
--- Additional comment from Alon Bar-Lev on 2013-05-09 07:52:32 EDT ---
packaging: setup: re-write using otopi
We introduce a complete rewrite of ovirt-engine setup, which includes
engine-setup, engine-upgrade, engine-cleanup.
The new implementation is installed side-by-side, user may have a choice
which implementation to use.
Implementation are incompatible, once setup using legacy, upgrade and
cleanup will not work using the new implementation and vise versa.
Answer file is not compatible between implementations.
Implementation is not feature complete, setup is is almost complete,
cleanup needs more work to clean files that where partially modified,
currently, setup is not able to upgrade non-new implementation setup.
Fully support development environment installation.
Up until now, developers had maintained parallel environment, manually
customized, partial featured.
Now, developers may setup product much like production using unprivileged
user, custom location and custom database. For more information refer to
Platform independent implementation
The new implementation can/should be able to run in multiple
distributions, setting up valid engine environment. So far tested
fedora, rhel, centos, gentoo, ubuntu.
Split between host provisioning and database setup.
Host provisioning is the part setup can configure the database package on
host to be able to serve the application. The provisioning phase is now
completely optional and is supported only at legacy distributions.
Database setup is the part that a schema is created in existing
database. This enables the dba to provide ovirt administration
unprivileged database user and database for his use.
Pluggable, mission centric, consistent, modern, customizable implementation.
Reuse the otopi infrastructure that is also used for host-deploy, and
future reuse of setup for dwh and reports components.
Signed-off-by: Alon Bar-Lev <email@example.com>
Signed-off-by: Sandro Bonazzola <firstname.lastname@example.org>
Signed-off-by: Alex Lourie <email@example.com>
--- Additional comment from Alon Bar-Lev on 2013-05-10 05:19:35 EDT ---
During implementation, the pki configuration were moved from vdc_options to /etc/ovirt-engine/engine.conf[.d/*].
These are determine by setup and should not be changed, so there is no reason to store them in database, and handle setup/upgrade that are database related.
Another reason was that the root application (/) should serve some of these resources, and having root access database is undesired.
Red Hat Enterprise Virtualization hosts are now deployed using oVirt Task
Oriented Pluggable Installer/Implementation, or otopi.
The otopi package provides deployment infrastructure required by Red Hat
Enterprise Virtualization Manager to deploy new hosts.
The package contains python library and Java library used by the Red Hat
Enterprise Virtualization Manager and ovirt-host-deploy packages. These
libraries are the core deployment logic.
The Red Hat Enterprise Virtualization Manager and optionally other projects that
require host deployment such as OpenStack use this package.
* The host deployment application previously used by Red Hat Enterprise
Virtualization has been replaced by oVirt Task Oriented Pluggable
Installer/Implementation, otopi, a standalone plugin based installation
framework used to set up system components.
The plugin-nature of otopi makes it simple to add new installation
functionality without the complexity of the state and transaction
This package is required to deploy hosts.
I'll take this one.
This bug was clearly cloned from an engineering bug, and was probably cloned out of a desire for throughness with a mind toward better-to-have-it-and-not-need-it-than-need-it-and-not-have-it. Our Installation Guide 3.4 procedures explain OTOPI (indeed, they assume the existence and use of OTOPI), so I am closing this NOTABUG.