This page provides some considerations and recommendation on the tenancy management. There are no one correct answer but rather things to consider for each specific situation.
Tenant admins
VM updates
- keep your VMs up to date!
- turning on/off automatic updates
- providing only private IP for VMs where public one is not needed, opening only necessary ports in security groups
- follow advices in security guidelines (yet to be published)
Deployment
- Do everything using code to reproduce
- Patch/update application and VMs periodically
- Keep logs
Backups
- perform data backup
- refund the critical data and applications when possible
- VMs backup (but not rely only on it, perform data backup and automated deployment)
Remove VMs
- Remove unused VMs
Resource management
- Keeping eye on budget vs. consumption → shutting down unnecessary VMs
- Possibility for burst capacity
- Estimate and plan
- Request quota/budget modification when required
Communications
- Tenant admin → Tenant users
- Tenant admin → comp reps
- Tenant admin → EWC support
- Keep contacts updated (e.g. if anyone leave organization)
- Share info about relevant news, important updates and events
Users management
- Review periodically contacts and list of users that have access
- Delete/disable tenant user accounts that do not require it anymore
Computing Representatives
Tenancy division models
- one tenancy for the whole Member State
- specific tenancies for each use case
Resource management
- Keeping eye on budget vs. consumption → shutting down unnecessary VMs
- Possibility for burst capacity
- Periodic tenancies reviews
User management
- Identity provider integration
- Local users in VMs vs. LDAP
Communications
- Comp Rep → Tenant admins
- Comp Rep → EWC support
- Keep contacts updated
- Share info about relevant news, important updates and events