So a major issue that we keep kicking around has been the web ui for adding a provider has not been successful in communicating that other steps are required before you can build/push a image (to this provider that was just defined in the wui).
pre-tim... that was the requirement that provider names needed to match a definition in imagefactory json config files (for rhevm and vsphere). In addition, there is also the rhevm nfs export domain mount.
Now that tim is somewhat in place, the provider values are being passed directly to imagefactory on the build/push action and the json files are no longer needed. However, there is still the rhev export domain mount.
I lean towards wanting the provider wui to be aware of it as well as logic in place to manage it as its required for the rhev provider.
So a major issue that we keep kicking around has been the web ui for adding a provider has not been successful in communicating that other steps are required before you can build/push a image (to this provider that was just defined in the wui).
pre-tim... that was the requirement that provider names needed to match a definition in imagefactory json config files (for rhevm and vsphere). In addition, there is also the rhevm nfs export domain mount.
Now that tim is somewhat in place, the provider values are being passed directly to imagefactory on the build/push action and the json files are no longer needed. However, there is still the rhev export domain mount.
I lean towards wanting the provider wui to be aware of it as well as logic in place to manage it as its required for the rhev provider.