Hi all,
I welcome your comments on this feature.
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/All_provider_c...
This contents of the wiki page is included below.
# Summary
Users should be asked to enter provider credentials and information
once. Currently users are asked to enter credentials in two places, once
in config files used by Configure and then again in Conductor when
creating a provider account. This can be confusing. We wil move all
provider creditials and information into a single place and that will be
Conductor.
Historically, Configure needed to know the provider credentials in order
to create private cloud definition files that are later used by
imagefactory (rhevm.json and vsphere.json). Credentials are no longer
needed in these private cloud definition files because of oauth. But the
private cloud definition files are still needed and the additional
provider parameters entered into Configure will need to be moved to
Conductor.
For RHEV, Configure also does additional validation to check the export
mount point is correctly specified, and if it is correct, mounts it.
This will need to be moved into Conductor as part of validation checks
Conductor performs when creating provider accounts.
Since all provider information will be moved out of Configure, Configure
will also stop creating providers in Configure for RHEV and vSphere.
Users will now create the providers and provider accounts. EC2 is
unaffected.
# Owner
Richard Su (rwsu)
and others who are interested
# Status
Planning phase.
# Screencast Demo
* Show Configure does not ask for credentials.
* Show Conductor asks for additional provider information used to create
private cloud definition files (rhevm.json and vsphere.json)
* Show provider validation logic performed by Configure has been moved
to Conductor.
# Tasks
This is being tracked as #2094.
* Remove credentials and provider information from Configure.
* Remove rhevm and vsphere profiles from Configure.
* In Conductor, add additional provider information needed by RHEV: nfs
server, nfs export, nfs mount point, and push timeout.
* In Conductor, add additional provider information needed by vSphere:
datastore and network name.
* Conductor creates rhevm.json and vsphere.json.
* RHEV export validation is moved to Conductor as part of provider
account validation before the account is created.
* Verify default configure profile works with RHEV and vSphere.
# Additional Details
The implementation needs to work with a head-less Conductor, that is a
Conductor environment where the user choses to only use the API and not
the UI. In this case, the API should ask for all information that is
needed to create the provider, provider account, json files and that is
need to perform provider specific validation.
It may also be worth investigating if we can eliminate the json files.
Imagefactory and/or Image Warehouse may be able to now just read the
information that used to reside in those files directly from Conductor.
# Open Questions
Configure mounts the RHEV nfs export. Should Conductor now be
responsible for mounting it? Or should it simply check the mount exist
and ask the user to mount it if it doesn't? And perhaps provide a
command to perform the mount in a warning message.