Skip to content

Latest commit

 

History

History
24 lines (18 loc) · 2.8 KB

References.md

File metadata and controls

24 lines (18 loc) · 2.8 KB
Raw

References

This file collects links to the most important/influential sources related to Open Cloud. "Open Cloud" is a semantically overloaded term. Google search brings up all kind of sites with this title.

Open Specifications

  1. Google Open Cloud - Google's interpretation of Open Cloud. All Kubernetes, of course.
  2. Open Cloud Services - One Commons declaration of intent similar to OCIX's.
  3. Cloud Native Computing Foundation - a lot of Kubernetes-oriented projects
  4. POSIX - Wikipedia article with a high-level overview of the Portable Operating System Interface specification. The Open Cloud Interface Specification (OCIX) obviously portrayed the general idea of treating the cloud as hardware from here. The most recent specification (Issue 8) was released on June 18th. Download or access requires a registration (unclear if it is available for individuals or only for organizations). The previous Issue 7 is available here. We could portray some ideas about the structure and conventions from here.
  5. Cloud Events - a CNCF project aiming at defining a standard schema of cloud events. Could be related eventually to putting the specs in sync, but also for the near term as a source of ideas of how such a spec could be structured.
  6. Open Telemetry - an open standard for metrics, logs, and traces. Also, the CNCF project. As with POSIX and Cloud Events, we may consider using some ideas of the spec structure, terminology, etc.
  7. Open Container Initiative - a Linux Foundation project; all major cloud vendors are here.

Cloud Resources Specifications

Could be a useful source for preflight specifications.

  1. AWS CDK - Wing preflight is a cloud-neutral version of CDK.
  2. Terraform CDK - the Terraform's interpretation of CDK ideas. Resource specifications are still cloud-vendor specific (e.g. S3Bucket).
  3. Pulumi - like with Terraform, cloud resource specification is vendor-dependent.
  4. Ampt.dev - cloud resources are specified in a cloud vendor-neutral form (e.g. storage)
  5. Go Cloud - an interesting implementation of the Google Open Cloud in Golang. Resource specifications seem to be cloud-neutral. The project seems to be abandoned, as it very often happens with Google. Some ideas for structuring the documentation might be useful.

There are probably more. TBD.