... | @@ -27,6 +27,9 @@ Many of the core services require configuration data to be loaded up-front, this |
... | @@ -27,6 +27,9 @@ Many of the core services require configuration data to be loaded up-front, this |
|
The data definition team has completed the schemas for the R3 scope on January 29th. We now have a stable version of data schemas that can be loaded at deployment time that forms the basis of the R3 data validation, and is used by the initial ingestion validation tests. The schemas are located [here](https://community.opengroup.org/osdu/platform/system/schema-service/-/tree/master/deployments/shared-schemas)
|
|
The data definition team has completed the schemas for the R3 scope on January 29th. We now have a stable version of data schemas that can be loaded at deployment time that forms the basis of the R3 data validation, and is used by the initial ingestion validation tests. The schemas are located [here](https://community.opengroup.org/osdu/platform/system/schema-service/-/tree/master/deployments/shared-schemas)
|
|
Schemas are loaded into the Azure OSDU instance at deployment time through the deployment scripts. It is important that schemas are loaded in order as defined in [load script](https://community.opengroup.org/osdu/platform/system/schema-service/-/blob/master/deployments/shared-schemas/osdu/load_sequence.1.0.0.json).
|
|
Schemas are loaded into the Azure OSDU instance at deployment time through the deployment scripts. It is important that schemas are loaded in order as defined in [load script](https://community.opengroup.org/osdu/platform/system/schema-service/-/blob/master/deployments/shared-schemas/osdu/load_sequence.1.0.0.json).
|
|
|
|
|
|
|
|
### Bring-Your-Own Schemas
|
|
|
|
To load your own schemas, both Microsoft and GCP/EPAM are currently working on scripts to load schemas into OSDU
|
|
|
|
|
|
### Managing multiple data partitions
|
|
### Managing multiple data partitions
|
|
The Microsoft version of OSDU enables support for multiple data partition separated by physical boundaries. While the MVP instance provided in Gitlab enables one data partition by default, [this section](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/infra/templates/osdu-r3-mvp/data_partition) walks you through the process of adding a new partition to your terraform deployment.
|
|
The Microsoft version of OSDU enables support for multiple data partition separated by physical boundaries. While the MVP instance provided in Gitlab enables one data partition by default, [this section](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/infra/templates/osdu-r3-mvp/data_partition) walks you through the process of adding a new partition to your terraform deployment.
|
|
|
|
|
... | @@ -35,9 +38,9 @@ Multiple OSDU environments can be supported in Azure as multiple OSDU deployment |
... | @@ -35,9 +38,9 @@ Multiple OSDU environments can be supported in Azure as multiple OSDU deployment |
|
1. Automatically, by using Gitlab mirroring into your person ADO environment, and using ADO deployment pipelines
|
|
1. Automatically, by using Gitlab mirroring into your person ADO environment, and using ADO deployment pipelines
|
|
2. Manually, by using a modified version of the following [helm charts](https://community.opengroup.org/osdu/platform/deployment-and-operations/helm-charts-azure)
|
|
2. Manually, by using a modified version of the following [helm charts](https://community.opengroup.org/osdu/platform/deployment-and-operations/helm-charts-azure)
|
|
|
|
|
|
|
|
### Environment Specific Configuration Files
|
|
### Bring-Your-Own Schemas
|
|
<link to override tfvars>
|
|
To load your own schemas, both Microsoft and GCP/EPAM are currently working on scripts to load schemas into OSDU.
|
|
Central <https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/infra/templates/osdu-r3-mvp/central_resources#azure-osdu-mvc-central-resources-configuration>
|
|
|
|
|
|
## Deployment and Release Management
|
|
## Deployment and Release Management
|
|
|
|
|
... | | ... | |