Add Angular defaults panel in admin
Summary
=======
Adding another defaults panel in admin implemented in angular
Motivation
========
The community has agreed to migrate existing panels to angular.js.
Description
=========
The existing defaults page (written using django templates) will be converted to angular js.
UX
===
Uses the exiting table design from other panels.
Wireframes, Mocks, Videos and UI Markup
-------
No specific mockups were provided.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Rajat Vig
- Direction:
- Needs approval
- Assignee:
- Rajat Vig
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Rob Cresswell
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add angular defaults panel for admin
Gerrit topic: https:/
Addressed by: https:/
WIP : API for getting default quotas in admin
Gerrit topic: https:/
Addressed by: https:/
WIP: API for updating default quotas in admin
Addressed by: https:/
Create a Angular Modules for Admin Dashboard
Gerrit topic: https:/
Addressed by: https:/
WIP : API for Metadata Definitions
Addressed by: https:/
WIP : Angular panel for Metadata Definitions
Gerrit topic: https:/
Addressed by: https:/
Dashboard Panels should not include SCSS
Addressed by: https:/
WIP: Add API services for system information
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add angular defaults panel subflows for admin
UX Review: Closed out with the following notes:
We identified that there were lots of requests/factors that needed to be acknowledged (not necessarily implemented):
1. Use of the Wizard-style modal rather than the old modal style
a. It was agreed that we should use the wizard-style in all cases so that additional steps/areas may be added
2. Inline editing on the main page
a. It was agreed that we should only do this as a secondary approach
b. Not all values are editable
3. Selection of units (GB, MB, etc. and/or default increments)
a. This can’t be done logically since the exact data points displayed and their ranges and nature are not known
b. In other words, these are just numbers that go into a black box that either accepts or rejects them.
4. Better handling of -1 as “unlimited”
a. Same problem as 3; cannot be addressed because we cannot be assured of which fields allow for “unlimited” in which contexts.
5. Grouping of defaults
a. We agreed that this should be doable; both to display the source (name and general type, e.g. ‘Nova’ and ‘Compute’)
Thus the only remaining execution items for Defaults are:
1. Use the Wizard-style modal [kbrown: this has been implemented. The update defaults modal is now using the wizard-style modal]
2. Display the Source as a column in the table [kbrown: also implemented]
3. Group the fields by Source in the wizard [kbrown: done]
a. Do not separate them into steps
b. Use standard bootstrap header to separate
Gerrit topic: https:/
