-
Notifications
You must be signed in to change notification settings - Fork 0
Cloud Label Standard
This document outlines the label standard that will be used to set meta data information associated with cloud projects in the Public Health Data Center of Excellence (PDCP). The tagging standard consists of tags that must be filled out when creating a new project. The standard is designed to provide important information about the project, including the client organization, technical contacts, environment, data sensitivity, cloud usage profile, and project name.
The tagging standard consists of mandatory and optional tags that must be filled out when creating a new subscription. The following table lists the mandatory tags that must be filled out, along with their descriptions and example values:
| Tag Key | Description | Examples |
|---|---|---|
| clientorg | The department who is responsible for the subscription | PHAC |
| projectlead | The individual who is paying for the subscription | john__dot__bain__at__phac-aspc__dot__gc__dot__ca |
| techlead | The main technical contact(s) for the subscription | john__dot__bain__at__phac-aspc__dot__gc__dot__ca |
| env | The type of environment | experiment, sandbox, dev, test, qa, prod |
| datasensitivity | The highest data classification of the workloads in the subscription | unclass, proa, prob |
| cloudprofile | The cloud usage profile for the workload | 1, 2, 3 |
| projectname | The name for the main workload or project in the subscription | zero_sugar_zero_caffeine |
Only hyphens (-), underscores (_), lowercase characters, and numbers are allowed. International characters are allowed.
The label standard outlined in this document is designed to ensure that all projects managed by the PDCP contain important information about the client organization, technical contacts, environment, data sensitivity, cloud usage profile, and project name.
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧
Under Development
- This wiki and the documents being developed under it are living documents.
- They are all pre-decisional.
- Some of these documents were generated using chatGPT or were developed by other organizations for reuse and adaptation.
- Some of the documents in this wiki are in early early drafts, they make reference to things that do no exist or to process not yet being used.
- The Center of practice(COP) is best effort and will be developed iteratively. This includes the technology supporting the COP
- At the early stages of the COP expect change; short life cycles and rapid changes. Plan accordingly.
- Stability in the COP will materialize over time.
- For immediate reference engage your COP support channel, use the documentation as a secondary source.
- There is reference to the COP and PDCP in the documentation, these are the same entity. We haven't picked a name yet :)
All of the pages in this wiki should be considered draft, underdevelopment and needing review. None of these pages are official documentation. All of the pages are a work in progress and discussion is encouraged via the GitHub issues mechanism.
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧