-
Define openstack tenants
Openstack Tenants, also described as “Projects” in Openstack, isolate cloud resources and users. Tenant administrators can configure individual quotas per tenant.
- Collecting tenant details (EMS_Refresh)
- allow api authentication per tenant (reconnect for each tenant where necessary)
- hopefully this only applies to collecting quota information (see next point), otherwise this may require tweaking the ems_refresh flow - tenant discovery
- when a new tenant is found, ManageIQ may not have credentials to that tenant if the EMS Admin is not also the tenant admin
- store the tenant details (name, description)
- attempt to authenticate
- Collecting quota information (EMS_Refresh)
- openstack quota cli info
- has to be collected for individual services
- nova (compute)
- cinder (block storage)
- neutron (network) - modeling quota details
- probably three fields
service(or,service_type)quota_type(e.g., cpu [nova], gigabytes [cinder], ports [neutron])value
- Tenant crud (actually, probably view only for now except for credential details)
- show tenant details
- name
- description
- id? (openstack uuid) - admin credentials (optional – fallback to EMS credentials – UI Note required) - display quota details for different services
- compute quota available
- block storage quota available (do we do anything with this yet?)
- network quota available
- RBAC
- control access to tenants via RBAC
- Provisioning
- present tenant selection
- show quota details for selected tenant
- C&U
- dual pass rollup
- VM rolls up to Tenant
- VM rolls up to AZ
- Reporting and Tenants
