Closed lukegonis closed 3 years ago
One hour workshop as first iteration to gather the metadata, with three possible sources:
Question for the team: cost accounting is just one aspect, so can we take that out of the title? We'll likely capture most of what we need, including for cost accounting, in the workshop.
BC Gov Azure base tags (cf. Sec 2.5.1 in BC Gov's Azure Foundation v0.9):
Note that tag naming convention needs to be take into account multiple providers (GCP mandates lower-case only for example).
Three things to consider:
Whiteboard from meeting on Tue Mar 3. Next step is to break down the pieces -- metadata store, provisioning, etc.
https://github.com/BCDevOps/openshift-tools/tree/master/provisioning/environment/playbook
Here is the Ansible script for provisioning in OpenShift withe the proper tags.
Here is the meta data we add to an openshift namespace: In the background we use the GAL codes for the org structure, notably missing is the standard GL coding from iStore orders because we wanted to force the conversation of rolling up quota to the IMB level as a single "digital investment" instead of a chargeback. Labels:
bus_org_code=CITZ bus_org_unit_code=BCDEV category=venture environment=prod mcio=CITZ-IM miso=CITZ-IMBSPC mpo=CITZ-IMBSPC name=devhub product=devhub project_type=user team=DevOps Annotations:
openshift.io/description=The home and supporting services for the BC Government Developer program (developer.gov.bc.ca) (prod) openshift.io/display-name=BC Developer Hub (prod) product-lead=Patrick.Simonian@gov.bc.ca product-owner=todd.wilson@gov.bc.ca