Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- demoable
- groomed

Story Points:
5
Blocked:
False
Blocked Reason:
None
Ready:
False
Epic Link:
Run OSUS on APP-SRE integration enviornment with EC builds
Feature Link:
OCPSTRAT-440 - OpenShift Eng should be the first to know if OCP code doesn't work in managed services
Intelligence Requested:
Market:

Sprint:
OTA 234, OTA 235

SFDC Cases Links:
SFDC Cases Counter:

We need to add the OTA stage cluster as a integration environment to the existing app-interface repository i.e. add it to https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/cincinnati/cicd/ci-int/saas.yaml

For example we have below configuration for stage and production.

targets:
  - namespace:
      $ref: /services/cincinnati/namespaces/cincinnati-stage.yml
    ref: master
    upstream:
      instance:
        $ref: /dependencies/ci-int/ci-int.yml
      name: openshift-cincinnati-gh-build-master
    parameters:
      GB_MEMORY_LIMIT: "1.5Gi"
      PE_MEMORY_LIMIT: "2Gi"
      GB_CPU_LIMIT: "2"
      PE_CPU_LIMIT: "2"
      GB_LOG_VERBOSITY: "v"
      PE_LOG_VERBOSITY: "v"
      REPLICAS: 3
  - namespace:
      $ref: /services/cincinnati/namespaces/cincinnati-production.yml
    ref: b8efb69b17188886a04cd5d33221ff11fb49870b
    parameters:
      GB_MEMORY_LIMIT: "1.5Gi"
      PE_MEMORY_LIMIT: "4Gi"
      PE_MEMORY_REQUEST: "1Gi"
      GB_CPU_LIMIT: "2"
      PE_CPU_LIMIT: "3"
      PE_CPU_REQUEST: "1"
      GB_LOG_VERBOSITY: "v"
      PE_LOG_VERBOSITY: "v"
      REPLICAS: 4
      PDB_MIN: 3

Definition of done:

Add required files for the Cincinnati integration environment.
- Add required modification in https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/cincinnati/cicd/ci-int/saas.yaml
- Add yaml file about the ota-stage cluster in https://gitlab.cee.redhat.com/service/app-interface/-/tree/master/data/services/cincinnati/namespaces

- - Create a service account which will be used by SRE-platform (SRE-platform is responsible for integration environment and not app-sre). It would be added to vault-secret which is owned by service delivery.