Must, Should, May, Should Not, Must Not used as in RFCs.
Should support Redfish for server management (fallback: IPMI)
5.4+
5.x+
octopus+
Must support federation of users
Must support SP role allowing Identities from Open ID Connect (OIDC) IdP
Must support flexible mapping of identity attributes to roles/rights
Should also support SP role with SAML Federation, also allowing mapping rules
Should support IdP role, allowing exposure of locally managed identities to 3rd party SPs via OIDC
Victoria or later
Follow SCS: SCS release ~5mo after OpenStack release, 1mo to upgrade to SCS-latest
Must comply (at least) to OpenStack Powered Compute 2020.11
Will move forward with newer SCS releases
domains must be cross-region
user management is per domain, thus also cross-region
projects may be cross-region
TL;DR: regions must share identity management (keystone)
Regions may share object storage namespace
Regions should provide a simple method to create network connections between them
Each customer is assigned a domain
Sub structure (projects) can be managed by customer
User management (local users AND federated users) at domain level
Customer can create projects (limited by quota)
Customers should have more than one project quota by default
Project deletion: Cloud must revoke tokens.
Cloud may require customer to have cleaned out all resources for project deletion to succeed.
Cloud may do resource cleanup for customer when asked for deletion of project. Resource cleanup may be asynchronous. Resource cleanup must not take longer than 24hrs.
Cloud must remove orphaned resources within 24hrs after project deletion. Billing for orphaned resources must stop within 24hrs after project deletion.
Compute availability zones must be fire protection zones, must have independent power supply and must be reported by openstack availability zone list --compute.
Block storage (openstack availability zone list --volumes) must be EITHER one AZ for the whole region OR the same set as compute AZs. In the latter case, compute instances must have access to the volumes in the same AZ and may have access to volumes in other AZs.
Networks should not use availability zones. All networks in one region (for one project and connected by a router) should have connectivity. (TODO: Should we allow per-AZ networking? Then mandate same zoning&naming as compute. Or can we make this a must)
TBW
must provide keystone v3
must have option to connect users via OIDC
must provide catalog with all services for auto-discovery
must allow user management
should support cells?
must support groups and affinity/anti-affinity
should support shelving/unshelving (?)
must support pause/unpause
must support suspend/resume
must support resize
must support rebuild
must support metadata service (shoud be using config drive)
may support lock/unlock
may support rescue/unrescue
must support dynamic block storage attachment / detachment
must support dynamic network interface attachment / detachment
should support (the more robust) config-drive metadata injection; may use network datasource instead
should use placement service for scheduling
must follow flavor specification
must support console log
must (should?) support (no)vnc attachment
must support cinderv3
may additionally support cinderv2
must support volume backup function
may support different volume types
may support volume QoS settings
should support volume transfer
should support multiattach
must encrypt data written to disk/SSD
must support routers
must support SNAT; SNAT should be enabled by default
must support DHCP and static IP assignment
must offer public network
must offer IPv4 floating IPs
should offer IPv6 support internally (East-West)
may offer IPv6 floating IPs
must allow multiple subnets in a network (mainly for IPv4 plus IPv6 dual-stack)
must support LBaaSv2 as a proxy to Octavia (recommended) or independently
should support FWaaS
should support VPNaaS (IPsec)
may support BGP-VPN
must support security groups
must support port security (allowed address pair settings); port security must be enabled by default
should support DNS integration
must allow users to register own images
must support image sharing (member setting)
must support qcow2 and raw image input
must support bare container format
must not require properties outside of SCS image standard
must support health checks, stickiness, SSL/TLS termination ...
Trademark spec (OpenStack Powered DNS 2020.11 add-on)
must allow users to serve their own registered zone
should offer a default domain allowing users to register subdomains as zones
should have a code of conduct on using subdomains (or encode unique identifiers in there)
must be protected against DoS
TODO: Anything needed for secure DNS?
Support at least HOT version 2018-08-31 (Rocky)
Trademark spec (OpenStack Powered Orchestration 2020.11 add-on)
Should have same namespace as S3
OpenStack Powered (Object) Storage 2020.11 Interop Tests (exceptions needed for Ceph?)
TODO: Predefined templates?
OpenStack Powered Shared Filesystem 2020.11 add-on
Horizon may be used
Other OpenStack services may be offered
Non-OpenStack services may be added to the catalog, but then must have a provider prefix
TODO: Should we require that providers offer a per-project setting where only SCS-base, SCS-extended or full will be listed in service catalog? Making it easier for dev teams to ensure they don't introduce a dependency by mistake?
must have https support
must provide static web hosting
must not enforce 100 bucket limit
should have policy for bucket naming resolution
must encrypt data stored
should support S3 access controls ... (TBW)
Must provide K8s Cluster API version XX (beta1?)
Must output kubectl config files
Should provide multi-SCS-cloud cluster management
May provide multi-partially-non-SCS-cloud cluster management
Must provice CSI
Must provide CNI (with proper network separation, not just flat networks)
Must provide registry for customer images
Should provide registry with provider vetted images
Should offer artifact security scanning
Should provide mesh discovery
Should offer sidecars for containers
Should offer proxy
OSB, kyma, ...
OPA ...
Must have event log
Must have control plane tests (e.g. os-health-monitor)
Must have data plane tests
Must have capacity monitoring in place (storage, CPU, RAM, network)
Should have multi-tenant Prometheus service
Should offer scraping of user-defined data exporters
Should have configurable retention/aggregation policies
Should expose relevant metrics from underlaying infra (CaaS/IaaS)
Should deploy SCS fixes daily
Must have CI pipeline to validate fixes in reference environment
Must include compliance/certification tests in CI (refstack - OpenStack InterOp, TBD k8s test workload)
Must deploy latest SCS release within 1 month
Must update operator-managed images at least monthly (until declared EOL)
Must not use HT on L1TF affected (Intel) CPUs except special flavors
Must have current mitigation against CPUs vulnerabilities (latest kernel defaults fine, except HT, see above)
Should use VxLAN for network isolation between tenants (?)
Must encrypt all volume data before it hits permanent storage (disk/SSD/nvme)
Encryption keys must be under user control; operator managed keys must not be global and must be rotated
Should have ISO27k1, 27k17, 27k18
...
Consumption reports
Consumption alerts
Complete Software Bill of Materials (BOM)?