Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create mandatory-and-supported-os-services.md #173

Closed
wants to merge 8 commits into from
Closed

Create mandatory-and-supported-os-services.md #173

Changes from 5 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
146f6aa
Create mandatory-and-supported-os-services.md
josephineSei Mar 26, 2024
ee625f7
Merge branch 'main' into supported-os-services
josephineSei Apr 8, 2024
580ebe6
Merge branch 'main' into supported-os-services
josephineSei Apr 8, 2024
27221f8
Update mandatory-and-supported-os-services.md
josephineSei Apr 22, 2024
1766753
Update mandatory-and-supported-os-services.md
josephineSei Apr 25, 2024
94706dc
Apply suggestions from code review
josephineSei May 3, 2024
e27188d
Update mandatory-and-supported-os-services.md
josephineSei May 3, 2024
023dea2
Merge branch 'main' into supported-os-services
josephineSei May 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 55 additions & 0 deletions docs/02-iaas/mandatory-and-supported-os-services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# SCS mandatory and supported OpenStack services

There are many OpenStack APIs and their services that can be applied on IaaS-Level.
These services have differences in the quality of their implementation and liveness and some of them may be easily omitted when creating an IaaS-Deployment.
To fulfill all SCS-provided standards there are only some of these APIs required.
More but not all OpenStack services are tested or integrated in the reference implementation.
This document will give readers insight about how the SCS looks at all the OpenStack services.
If a cloud provides all mandatory and maybe some supported OpenStack APIs and implementation of their services it can be tested for SCS-compliance.
Any unsupported services will not be tested.

## Mandatory OpenStack services

The following OpenStack services MUST be present in SCS-compliant IaaS-Deployments:

| OpenStack Service | description |
|-----|-----|
| **Cinder** | Block Storage service |
| **Glance** | Image service |
| **Keystone** | Identity service |
| **Neutron** | Networking service |
| **Nova** | Compute service |
| **Octavia** | Load-balancer service |
| **Placement** | Hardware Describing Service for Nova |
| **S3 API object storage** | No formal standard exists, many implementations: Swift, RadosGW, minio... |
artificial-intelligence marked this conversation as resolved.
Show resolved Hide resolved

## Supported OpenStack services

The following services MAY be present in SCS-compliant IaaS-Deployment and their integration had been tested by the SCS:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does "their integration had(sic!) been tested" mean here exactly?
e.g. I'm not aware of any automated tests we run for masakari (maybe I just don't know them, it's hard to track every single test across different repositories).


| OpenStack Service | description | comment |
josephineSei marked this conversation as resolved.
Show resolved Hide resolved
|-----|-----|-------|
| **Barbican** | Key Manager service | maybe a future mandatory service |
| **Cloudkitty** | Rating/Billing service | maybe move to unsupported |
| **Ceilometer** | Telemetry service | |
| **Designate** | DNS service | |
| **Gnocchi** | Time Series Database service | needed for Ceilometer |
| **Heat** | Orchestration service | **maybe unsupported?** |
| **Horizon** | Dashboard | |
| **Ironic** | Bare Metal libraries | |
josephineSei marked this conversation as resolved.
Show resolved Hide resolved
| **Manila** | Shared File Systems service | |
| **Masakari** | Instances High Availability service | |
| **Skyline** | Dashboard | if not used, move to unsupported |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the skyline note should be clarified. I don't think it belongs into the final form of this document?


## Unsupported OpenStack services

All other OpenStack services that are not mentioned in the mandatory or supported lists are not tested for their integration and behavior by the SCS.
josephineSei marked this conversation as resolved.
Show resolved Hide resolved
Those services MAY be used in IaaS-Deployments but the SCS will not assume they are present and potential issues that occur during the deploying or usage have to be handled by the CSP alone.

There are still some notable services, that might come into the supported list, when there will be enough CSPs wanting this.
This list is not exhaustive:
josephineSei marked this conversation as resolved.
Show resolved Hide resolved

| OpenStack Service | description | comment |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As commented above for the other table, I suggest removing the comment column and moving any statements into the Design Considerations section of the corresponding standard document.

|-----|-----|-------|
| **Magnum** | Container Infrastructure Management service | |
| **Freezer** | Backup, Restore, and Disaster Recovery service | interesting service, that some people on upstream want to revive |
Loading