Uploaded image for project: 'Container / Cluster Management (XCM) Strategy'
  1. Container / Cluster Management (XCM) Strategy
  2. XCMSTRAT-59

Remove Default Machine Pool or Add Taints to Default Machine Pool

    XMLWordPrintable

Details

    • False
    • False
    • Green
    • 100
    • 100% 100%
    • Undefined
    • Hide

      OSD on non CCS issue OCM-3567 is still in discussion. UI released on Sept 7th and docs will release on Sept 10th. Demo recording of the UI https://drive.google.com/file/d/1aov93vaDto-QWfyKCnO-uzhQ8mPsVgiO/view?usp=sharing

      OCM Team Weekly Status for Oct 11th:

      QE:

      • All bugs normal or higher than normal had been verified and closed.
      • Due to many fixes and new logic introduced, regression ongoing

      OCM Team Weekly Status for Oct 4

       

      • OCM : 
        • Team is working on fixing bugs in ocm-114 
        • Asked BU (Bala) to move the support for non ccs to a new xcmstrat since it involves a spike and a prioritization. 

       

      OCM Team Weekly Status for Sep 19

      • QE :
        • UI card HAC-3801 is closed
        • TF provider OCM-2648 is not ready for testing
        • OCM-112 have some cards not ready for testing
        • OCM-22 under epic OCM-112 is waiting for tc-approved to close, no blocker
      • Docs: OSDOCS-2470 and OSDOCS-6244 are completed

      OCM Team Weekly Status for Aug 24

      • QE :
        • Got blocking issue  OCM-3395
        • Testing finished for staging. But we need to run migration checker for all clusters existing on production to make sure all clusters are migrated correctly after OCM-22 deployed

      OCM Team Weekly Status for Aug 17  

      • Day-1 machine pool data migration complete!\
      • Backend changes enabling edit/deletion of day-1 pool has been pushed into stage, under review by QE

      OCM Team Weekly Status For Aug 9th

      • Migration delayed last week due to bug. Has been resolved and qualified by QE.
      • A document describing the steps of the migration has been made. BU has approved the process.
      • We will initiate the migration process in production on 08/10/2023.

      OCM Team Weekly Status for Aug 2nd 

      • Enabled the toggle for migration to QE Organization test 
      • Plan is to enable for internal Organization after QE finishes testing this weel 
      • After the migration is tested we will enable Day 1 operation to create a new entries  
      •  

      ET Team Weekly Status for July 19th

      • OCM-19 - In Progress
        • This is in a review cycle now, comments are addressed and further review continues
        • WIP just waiting for final review and merge

      UI team status for 11-Oct

      Docs team status for 6-Sept

      • OSDOCS-7645 - On track for publication on Monday, clarifying doc details with PM 
      Show
      OSD on non CCS issue OCM-3567 is still in discussion. UI released on Sept 7th and docs will release on Sept 10th. Demo recording of the UI https://drive.google.com/file/d/1aov93vaDto-QWfyKCnO-uzhQ8mPsVgiO/view?usp=sharing OCM Team Weekly Status for Oct 11th: QE: All bugs normal or higher than normal had been verified and closed. Due to many fixes and new logic introduced, regression ongoing OCM Team Weekly Status for Oct 4   OCM :  Team is working on fixing bugs in ocm-114  Asked BU (Bala) to move the support for non ccs to a new xcmstrat since it involves a spike and a prioritization.    OCM Team Weekly Status for Sep 19 QE : UI card HAC-3801 is closed TF provider OCM-2648 is not ready for testing OCM-112 have some cards not ready for testing OCM-22 under epic OCM-112 is waiting for tc-approved to close, no blocker Case updated to OCM-22 to remove recreation part, needs dev's review. Heads up of https://issues.redhat.com/browse/OCM-3689 , when can we deprecate cluster.nodes? Docs: OSDOCS-2470 and OSDOCS-6244 are completed OCM Team Weekly Status for Aug 24 QE : Got blocking issue  OCM-3395 Testing finished for staging. But we need to run migration checker for all clusters existing on production to make sure all clusters are migrated correctly after OCM-22 deployed OCM Team Weekly Status for Aug 17    Day-1 machine pool data migration complete!\ Backend changes enabling edit/deletion of day-1 pool has been pushed into stage, under review by QE OCM Team Weekly Status For Aug 9th Migration delayed last week due to bug. Has been resolved and qualified by QE. A document describing the steps of the migration has been made. BU has approved the process. We will initiate the migration process in production on 08/10/2023. OCM Team Weekly Status for Aug 2nd   Enabled the toggle for migration to QE Organization test  Plan is to enable for internal Organization after QE finishes testing this weel  After the migration is tested we will enable Day 1 operation to create a new entries     ET Team Weekly Status for July 19th OCM-19 - In Progress This is in a review cycle now, comments are addressed and further review continues WIP just waiting for final review and merge OCM-23 (not started yet) - dependent on OCM-19 Picked up OCM-2455 - Clean up machine pool reserve quota logic Created MR https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/merge_requests/6130 OCM-20 Not started yet OCM-22 Draft MR for delete pool api OCM-2170 Worker is part of integration, fixing found race OCM-2590: picking this up as well UI team status for 11-Oct https://issues.redhat.com/browse/HAC-3801: The feature implementing functionality in prod https://issues.redhat.com/browse/HAC-4858: A followup to redesign the screens is on code review ( MR ) - its a huge MR though and it will take time to review and verify it. Got the first ACK on the MR and a good review from the second reviewer. The remarks were implemented yesterday, now waiting for the next round of review Docs team status for 6-Sept OSDOCS-7645 - On track for publication on Monday, clarifying doc details with PM 
    • 0

    Description

      User Story

      1. As an OSD or ROSA admin, I want to be able to remove the default machine pool for worker nodes, so that I can solely use the additional machine pool that I have created.

      2. [Added as per the design and concurrence with the OCM contributors]As an OSD or ROSA admin, I want to be able to add Taints to the default machine pool worker nodes so that I can place pods that tolerate the taints on the default machine pool worker nodes. 

      More details included in the linked document 

      Acceptance Criteria

      • Deletion of machine pool supports where ID is Default. i..e, day-1 machine pool created along with cluster can be deleted.
      • Modification of machine pool to add Taints supports where ID is Default. i.e., Taints can be added to the Default Machine pool. 
      • Requirements: Minimum either 2 (in case of 1 AZ clusters) or 3 (in case of 3 AZ clusters) untainted compute node of m5.xlarge or higher 
      • This can be configured by customers via any of our current clients (UI, CLI, Terraform)

      Default Done Criteria

      • All existing/affected SOPs have been updated.
      • New SOPs have been written.
      • Internal training has been developed and delivered.
      • The feature has both unit and end to end tests passing in all test
        pipelines and through upgrades.
      • If the feature requires QE involvement, QE has signed off.
      • The feature exposes metrics necessary to manage it (VALET/RED).
      • The feature has had a security review.* Contract impact assessment.
      • Service Definition is updated if needed.* Documentation is complete.
      • Product Manager signed off on staging/beta implementation.

      Dates

      Integration Testing:
      Beta:
      GA:

      Current Status

      GREEN | YELLOW | RED
      GREEN = On track, minimal risk to target date.
      YELLOW = Moderate risk to target date.
      RED = High risk to target date, or blocked and need to highlight potential
      risk to stakeholders.

      References

      Links to Gdocs, github, and any other relevant information about this epic.

      Attachments

        Issue Links

          is cloned by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. XCMSTRAT-112 Remove Default Machine Pool or Add Taints to Default Machine Pool

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          Web Link Default Machine Pool Requirements v3.0

          Web Link KCS 6384881: Creating and configuring MachineSets/MachinePools in OSD and ROSA

          Activity

            People

              rh-ee-bchandra Balachandran Chandrasekaran
              wgordon.openshift Will Gordon
              Manuel Dewald, Marek Libra, Renan Campos, Sebastien Han
              Oleg Silkin Oleg Silkin
              Xue Li Xue Li
              Mark Letalien Mark Letalien
              Renan Campos Renan Campos
              Thi Le Thi Le (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: