Commit 19de5d4c authored by Abhishek Kumar (SLB)'s avatar Abhishek Kumar (SLB)
Browse files
parents fee0bb86 36b05fad
......@@ -55,17 +55,20 @@ osdu-gcp-test:
osdu-gcp-dev2-test:
needs: ["osdu-gcp-bootstrap-dev2"]
osdu-gcp-containerize-bootstrap-gitlab:
osdu-gcp-containerize-bootstrap-schema:
stage: containerize
image: docker:19.03.15
tags: ["osdu-medium"]
needs: ["compile-and-unit-test"]
services:
- docker:20.10.7-dind
variables:
IMAGE_NAME: osdu-gcp-bootstrap-schema
script:
- export EXTRA_DOCKER_TAG=""; if [ "$CI_COMMIT_TAG" != "" ] ; then EXTRA_DOCKER_TAG="-t $CI_REGISTRY_IMAGE/osdu-gcp-bootstrap:$CI_COMMIT_TAG" ; elif [ "$CI_COMMIT_REF_NAME" = "master" ] ; then EXTRA_DOCKER_TAG="-t $CI_REGISTRY_IMAGE/osdu-gcp-bootstrap:latest" ; fi
- docker build -t $CI_REGISTRY_IMAGE/osdu-gcp-bootstrap:$CI_COMMIT_SHORT_SHA $EXTRA_DOCKER_TAG --file devops/$OSDU_GCP_VENDOR/bootstrap-osdu-module/Dockerfile .
- export EXTRA_DOCKER_TAG=""; if [ "$CI_COMMIT_TAG" != "" ] ; then EXTRA_DOCKER_TAG="-t $CI_REGISTRY_IMAGE/$IMAGE_NAME:$CI_COMMIT_TAG" ; elif [ "$CI_COMMIT_REF_NAME" = "master" ] ; then EXTRA_DOCKER_TAG="-t $CI_REGISTRY_IMAGE/$IMAGE_NAME:latest" ; fi
- docker build -t $CI_REGISTRY_IMAGE/$IMAGE_NAME:$CI_COMMIT_SHORT_SHA $EXTRA_DOCKER_TAG --file devops/$OSDU_GCP_VENDOR/bootstrap-osdu-module/Dockerfile .
- docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
- docker push $CI_REGISTRY_IMAGE/osdu-gcp-bootstrap
- docker push $CI_REGISTRY_IMAGE/$IMAGE_NAME
rules:
- if: '$OSDU_GCP == "true" && $CI_COMMIT_BRANCH =~ /^master$/'
when: on_success
......
......@@ -323,10 +323,25 @@ curl -L -X PATCH 'https://dev.osdu.club/api/partition/v1/partitions/opendes' -H
</details>
### Bucket configuration:
At Minio should be created bucket:
**name:** `<project name from tenant info>-schema`
This bucket used to store full schemas in `.json` files.
\ No newline at end of file
### Object store configuration <a name="ObjectStoreConfig"></a>
#### Used Technology
MinIO (or any other supported by OBM)
#### Per-tenant buckets configuration
These buckets must be defined in tenants’ dedicated object store servers. OBM connection properties of these servers (url, etc.) are defined as specific properties in tenants’ PartitionInfo registration objects at the Partition service as described in accordant sections of this document.
<table>
<tr>
<td>Bucket Naming template
</td>
<td>Permissions required
</td>
</tr>
<tr>
<td>&lt;PartitionInfo.projectId>-<strong>schema</strong>
</td>
<td>ListObjects, CRUDObject
</td>
</tr>
</table>
\ No newline at end of file
......@@ -57,13 +57,25 @@ It can be overridden by:
- through the Spring Boot property `gcp.schema-changed.topic-name`
- environment variable `GCP_SCHEMA_CHANGED_TOPIC_NAME`
## GCS configuration:
At Google cloud storage should be created bucket:
**name:** `<project name from tenant info>-schema`
This bucket used to store full schemas in `.json` files.
## GCS configuration <a name="ObjectStoreConfig"></a>
### Per-tenant buckets configuration
These buckets must be defined in tenants’ “data” GCP projects that names are pointed in tenants’ PartitionInfo registration objects’ “projectId” property at the Partition service.
<table>
<tr>
<td>Bucket Naming template
</td>
<td>Permissions required
</td>
</tr>
<tr>
<td>&lt;PartitionInfo.projectId><strong>-schema</strong>
</td>
<td>ListObjects, CRUDObject
</td>
</tr>
</table>
## Google cloud service account configuration :
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment