Planned UI features for CloudConductor 3.0

Results of CloudConductor Coding Day - 2015-09-14

Planned Changes

We will perform a complete GUI overhaul for the server. By using AngularJS we try to utilise a clean MVC architecture for the web frontend.

• Install page
  • Currently the install page is implemented as a bean. An alternative would be nice, but is probably not feasible.
  • Help entries explaining every input field.
  • We will move most of the property file in the database.
• Implement multi user support
• Implement login page
• Use of a new design
• Home page: overhaul, possibly as a dashboard
• Templates page
  • Overhaul
  • Implement function service restart on all servers
  • Services should be controlled via the Templates page or should it be an own page
  • Hosts list needs to be collapsable
  • Site list must go
  • Template list should give a better overview.
  • Should users be able to group templates (or packages)
  • All functions concerning templates should be accessible via the template page
  • Make a subpage with temporary Packages
  • Package management for templates as a table with package version
  • Auto Refresh may be implemented later
• Hosts page
  • Same problems the template page has.
  • Grouping by hosts, for each host a subgroup
  • Statusview for each template is necessary
  • Overview and detail information is placed at the hosts page
  • Live information up to the top of the page
• Config page
  • Look will be kept the same
  • Search function is planed
  • Different configuration layers should be made clearer
  • Resolve for each key
  • "Add" requires a dropdown menu for services and templates
  • Import / Export for config files
  • Files subpage
    • Overview Hub with supage for each file
    • Keep tags
  • Packages subpage
    • Include search
    • Optimise (possibly a 2-click solution)
    • Forbid edits, only auto generated entries. Configs through cloud conductor
    • Repository tag or selection
  • SSH-Keys subpage
    • 2-click solution
    • Template as a default
    • User management as own page
  • Services subpage
    • 2-click solution
    • Automate
    • Rename "Initscript Name"
    • Service Name + description
    • Repository Tag or selection
    • Mirrorlist for the repositories must be taggable
• Navigation
  • Rework of navigation
• Audit
  • Throw away, complete overhaul
• Package Server rework to repos, see tags
• Options: settings page with initial settings, implemented after setup wizard
• Links, keep inside settings
• Report fix URL, improve
• Footer, change Cinovo to Cloud Conductor