Hello,
In change[1] we move the reference to PKI artifacts from database to
configuration files.
For all of you who are hacking the product to work in development mode, there
is an environment variable called ENGINE_DEFAULTS which causes the engine to
load its default configuration from a file.
A template is available at ./packaging/conf/engine.conf.defaults.in
If you do not set this environment variable
/usr/share/ovirt-engine/conf/engine.conf.defaults will be used, so if you have
rpm based installation of ovirt-engine an incompatible/incomplete configuration
will be loaded.
We now need additional variables:
ENGINE_PKI_CA=${ENGINE_PKI}/ca.pem
ENGINE_PKI_ENGINE_CERT=${ENGINE_PKI}/certs/engine.cer
ENGINE_PKI_TRUST_STORE=${ENGINE_PKI}/.truststore
ENGINE_PKI_TRUST_STORE_PASSWORD=
ENGINE_PKI_ENGINE_STORE=${ENGINE_PKI}/keys/engine.p12
ENGINE_PKI_ENGINE_STORE_PASSWORD=
ENGINE_PKI_ENGINE_STORE_ALIAS=1
Set ENGINE_PKI to point to where PKI resources resides, or just
/etc/pki/ovirt-engine and if you actually use PKI, set the password to the
correct password of your installations.
Regards,
Alon Bar-Lev
[1] http://gerrit.ovirt.org/#/c/14333/
_______________________________________________
Engine-devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-devel
