When the user tried to use an ovirt.config with a ca_file the ca_file path is written to the secret but this will not be the path of the file in the created machines which will cause connection errors in the machine object that tries to find the file that doesn't exist.
Instead we should read the file content and write it as the ovirt_ca_bundle in case the ovirt_ca_bundle is not set on the ovirt.config file.
This change removes support for the insecure mode from the oVirt installer. Previously, when no certificate could be obtained from the oVirt engine the installer would proceed without certificate verification. Due to recent improvements this is no longer a valid use case and is being deprecated. The user is instead presented with a message explaining the situation and linking to the to-be-written documentation. If the user wants to use insecure mode they have to create a file named ~/.ovirt/ovirt-config.yaml with the following contents before running the installer:
```yaml
ovirt_url: https://ovirt.example.com/ovirt-engine/api
ovirt_fqdn: ovirt.example.com
ovirt_pem_url: ""
ovirt_username: admin@internal
ovirt_password: super-secret-password
ovirt_insecure: true
```
- Add Table of Contents to oVirt documentation.
- Add oVirt Logo
- Fix the order for bootstrap vm and ovirt-config.yaml
Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>
- Replace the need of provide Engine API URL
- Remove the need of copy/past certificate
- Auto-dectect if Engine CA cert is installed
- Check if engine domain provided is responsive
- User cannot fix wrong oVirt user once provided
- Replace static strings in the code from oVirt to Engine
- Do not allow users to select uninitialized DC
- Credentials - set max login attempts
- ovirt: DNS VIP removal
- Update explain for installer
Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>
