Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1079

Address limitation of installation of CRW in only one 'workspaces' namespace

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • 2.5.0.GA
    • 2.4.0.GA, 2.5.0.GA
    • testing
    • Address limitation of installation of CRW in only one 'workspaces' namespace

      There should be the only one "workspaces" namespace used to install CRW starting from Eclipse Che 7.19 / CRW 2.5.

      Notes: https://hackmd.io/nWfj_ZlZTrK7xrqoQutxTA

      We can't have more that 5 OCP instances at a time on our CRW PSI having 750 RAM, because of single OCP 4.x instance requires https://github.com/openshift/installer/tree/master/docs/user/openstack#openstack-requirements :

      • Floating IPs: 2 (plus one that will be created and destroyed by the Installer during the installation process)
      • Security Groups: 3
      • Security Group Rules: 60
      • Routers: 1
      • Subnets: 1
      • Server Groups: 1
      • RAM: 112 GB
      • vCPUs: 28
      • Volume Storage: 175 GB
      • Instances: 7

      To address this limitation we should:
      1) make pipeline for installing OCP on PSI Openstack be able to be triggered from another pipeline (https://issues.redhat.com/browse/CRW-838)

      2) fix existed CRW testing pipelines to use "workspaces" namespace to install CRW starting from 2.5 version (https://issues.redhat.com/browse/CRW-1132)

      3) fix CRW testing pipelines to run the E2E tests against dedicated QE OCP instance created instantly (https://issues.redhat.com/browse/CRW-1133)

      4) provide tests of migration from CRW 2.3 installed in non-default namespace to CRW 2.5 (https://issues.redhat.com/browse/CRW-1134)

       
       

              rhopp@redhat.com Radim Hopp
              dnochevn Dmytro Nochevnov
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: