Dashboard Page v1

[timalces]

Add a new project dashboard page, containing 3 sections:

Overview

• Balance (as of start of the billing cycle)
• Cost this cycle (as of the start of today)
• Spend Profile (this comes from the current BudgetPolicy)
• Current cycle budget
• Billing Date
• Project end date (if there isn't one, this should read 'none')
• A link button to the costs breakdown page

All of this data is currently shown on the Billing Management page, so the same data (see @policy, @billing_date and @latest_cycle_details, in the billing_management ProjectsController method) can be used here.

Groups

Core

• The current status of the Core infrastructure. For now we will assume this is always "UP" (not something we currently check or record)
• The core costs for this cycle (up until start of today). This is core costs + core storage costs
• These costs can be determined using chart_cumulative_costs from CostsPlotter. Note: this will be the forecast costs for yesterday
• Alternatively/better you can add method(s) to CostsPlotter specifically for this groups section. The raw costs are returned by the cost_breakdown method
• A 'More Info' link that takes you to the costs breakdown page, filtered to just core costs. This can be achieved by adding the param datasets[]=core to the costs breakdown link

Compute Groups

• Similarly show the current status of each compute group
• How many instances are currently on, out of the total available for that group. E.g. 3 of 5 UP
• This can be determined by manipulating data returned by project.latest_instances, or a new method added to InstanceTracker that queries the InstanceLogs directly (e.g. determine_counts calculates how many are on, but does not record the total of on + off)
• Two existing examples of dealing with instance counts are in the 'Current States' table on the Costs Breakdown page, and the 'Requested Total' column on the Create Event page
• The costs for this cycle (up until start of today). This is the group compute costs + the group storage costs. They can be retrieved in the same way as for core costs (see above)
• A link button to Events for that compute group. This should go to the manage events page, filtered for that group. This can be achieved by adding the param groups[]=compute_group_name to the page link
• A 'More Info' link button to the costs breakdown page, filtered to that compute group. This can be achieved by adding the param datasets[]=compute_group_name to the costs breakdown link

Upcoming Events

• A table showing the next 5 events for the project
• A project's events can be retrieved using project.events. I'm not sure these are sorted by date. There is also the method events_by_date(events) that may or may not help
• Show the date, time and description
• These events can be either be instances of OneOffChangeRequest or BudgetSwitchOffDecorator so any view logic will need to accommodate both of these
• If an event is editable?, and the user has correct permissions, include a cog icon link that goes to that event's edit page
• If there are no upcoming events, a suitable message should be shown (i.e. don't display an empty table)
• Include a link button to the Create Event page
• Include a link button to the Audit page
• This is somewhat similar (but not identical) to the "Upcoming" and "Future Events" tables on the Manage Events page
• This is probably the most complex section of the page

General Things to Consider/add

• This will require a new route, projects controller method, and view. Some parts of the view can be separated into partials
• You can use styling from other pages in control or flight hub for inspiration, and we also use Bootstrap styling heavily
• The Bootstrap grid will greatly help in positioning the different sections of the page
• A new policy check will need to be added, in app/policlies/project_policy.rb. This will be the same as for show?
• The top navbar will need to be updated to have a Dashboard option. This can be found in views/partials/_nav.erb
• This initial version will be static, so new data only shown on a page refresh
• Mock up can be found here

[megan-godfrey]

Hi @ColonelPanicks, I've got a couple of questions about this issue - Firstly, re. the descriptions for upcoming events - if no description is set for the event, I'm currently just displaying a dash '-' for that event. To generate a description of the event automatically, it would require knowing the state of previous events to know what is being turned on/off. I'm happy to look into doing that but wanted to run it by you first before I spent time working it out. Also, re. the 'settings' buttons for each of the compute groups - there's not currently an obvious place for them to link to. In your mock up, you did mention that this may be a future addition. I've currently got them linking to the Policies tab as a placeholder, but I wanted to check whether you had something else in mind for now?

[timalces]

To generate a description of the event automatically, it would require knowing the state of previous events to know what is being turned on/off.

Just to add to this, if I recall correctly @ColonelPanicks we had a meeting a while back where Steve mentioned (in the context of the manage events page) that we should not be explicitly committing to actions - e.g. don't say turn off 3 nodes on this date. As the actual state of nodes when the request is carried out is uncertain, with users potentially making changes before then/ monitor might have switched things off, etc.

Perhaps instead we could generate simplified descriptions here of 'Match exact counts' or 'Match minimum counts'?

[timalces]

Resolved by #50