As Sahara grows and we add more capability, how do we balance the needs of users ranging from expert to novice?
Experts may know about and want control over fine details of cluster configuration and deployment. A novice knows not much more than the amount of resources available to them.
Can we find ways to do both well?
===========================
2) Get rid of / improve Image Registry
* Get rid of Image Registry - differentiate images by name pattern or etc. * Remove hard dependency on user in image registry in case of Heat provisioning engine
TL;DR
Due to the moving on using Heat instead of direct provisioning, we could now rely on user created by Heat, so, the only profit of Image Registry is handling tags for different plugins. Probably, we should take a look on overall UX of Image Registry mechanism in this case. Currently, the main role of Image Registry is just to not display all images in dropdowns in UI.
===========================
3) Sahara dashboard in Horizon
Short discussion of status / plans for merging sahara-dashboard into the horizon.
