DfR Management Operations
This thread includes any part of managing DfR services. It has a strong cross-thread with the Security Thread.
Topics
How should management be handled in DfR?
What are the requirements for the management console?
Management Console
- Current functions
- User enters username, credentials, basic info
- Create accounts (by DuraSpace staff)
- Define storage provider(s)
- Manage instances: start, stop, restart, launch instance
- Where we see users associated with accounts
- For multi-tenant accounts, lets us set up a cluster of accounts/users
- Two different kinds of accounts - full account (classic), community account (multi-tenant)
- (We have monitors that check on the instances, but that's not part of the MC)
- For DfR - Thinking about an "admin console" - tweak the MC to meet the DfR needs
- We need services surrounding OCS , i.e., we need MC to spin up instances that are *not* DuraCloud, e.g., Sidora, CloudSync, etc - a UI for an admin to use
- Currently OCS knows about *one* Fedora; could also have many OCS's talking to many Fedoras; right now we are associating OCS with DuraCloud and one Fedora
- We may not need to make OCS visible to the user initially; e.g., for this sprint we are putting in a configuration for Sidora,( should it do other stuff here? Probably not--probably will have an OCS console)
- Need a branded feel for DfR MC - reconfigure current MC to create as little duplicative code as possible
- Need shib stuff
- Users need to create profiles
- Users make a request to have DfR account to be created on their behalf (for now, communication will happen outside of the software)
- Once we provision an account, admins can set up their own users
- Admins should be able to download up-sync utility from here
- We need services surrounding OCS , i.e., we need MC to spin up instances that are *not* DuraCloud, e.g., Sidora, CloudSync, etc - a UI for an admin to use
- For now the MC needs to start and configure the DfR deployments. It will permanently include DuraCloud, OCS, related functions, security, and Fedora
- For demonstration purposes we will also startup SIdora but whether it becomes a Cloud-provided services is TBD
- We won't build any assumptions in the interfaces to SIdora that make it depend on running it within the DuraCloud platform
- In the future, there may be a DfR provided UI for content but DfR will always equally support generic interfaces that can be used by content-related products running in the customer's infrastructure
- However, for the grant demonstration we likely be able to run everything including SIdora on on DfR instance (including DuraCloud).
Conclusions
- The required functional changes to the existing MC are minimal mostly in starting up the OCS (and for demonstration) the SIdora subsystems
- There will be the need for branding changes, and that may require refactor to make the MC easier to rebrand for other purposes
