Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spike: Deliver OS/Kernel Patches for an existing site #604

Closed
eak13 opened this issue Jul 12, 2021 · 1 comment
Closed

Spike: Deliver OS/Kernel Patches for an existing site #604

eak13 opened this issue Jul 12, 2021 · 1 comment
Assignees
@sreejithpunnapuzha
Labels
Day2 Relates to day 2 operations (brownfield upgrades, etc.) enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release priority/medium Default priority for items size m
Milestone
v2.1

Comments

@eak13
Copy link

eak13 commented Jul 12, 2021

Problem description
As part of ongoing operations, we need the ability to perform various component upgrades & understand the behavior of the site/clusters when these upgrades occur. When it comes to OS/Kernel patches for an existing site, the plan is to use Cluster API & Metal 3 to deliver a new image with the upgrades.

Proposed change

  • Generate a new image via image-builder with a kernel and/or OS patches
  • Test the ability to deliver the image to an existing cluster via Cluster API/Metal3.
  • Document & provide findings of the upgrade (e.g. What was the process? What issues were encountered, if any?, etc.)
  • Are there any other components that need to be upgraded at the same time?
@eak13 eak13 added enhancement New feature or request triage Needs evaluation by project members Day2 Relates to day 2 operations (brownfield upgrades, etc.) labels Jul 12, 2021
@eak13 eak13 changed the title Deliver OS/Kernel Patches for an existing site Spike: Deliver OS/Kernel Patches for an existing site Jul 12, 2021
@eak13 eak13 added this to the v2.2 milestone Jul 13, 2021
@jezogwza jezogwza added priority/critical Items critical to be implemented, usually by the next release and removed triage Needs evaluation by project members labels Jul 14, 2021
@sreejithpunnapuzha sreejithpunnapuzha self-assigned this Jul 22, 2021
@sreejithpunnapuzha sreejithpunnapuzha added the priority/medium Default priority for items label Jul 26, 2021
@eak13 eak13 added the size m label Jul 26, 2021
@sreejithpunnapuzha
Copy link
Member

As per the discussion in design call, we have identified all the issues. This is mentioned in the hackmd https://hackmd.io/@Pallav/BkU2FuWZY. Closing this spike story. Follow up for this will be done once baremetal-operator/ironic is uplifted.

This was referenced Aug 27, 2021
Open
Closed
@eak13 eak13 modified the milestones: v2.2, v2.1 Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sreejithpunnapuzha sreejithpunnapuzha

Labels
Day2 Relates to day 2 operations (brownfield upgrades, etc.) enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release priority/medium Default priority for items size m
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
3 participants
@eak13 @jezogwza @sreejithpunnapuzha