Re: Openshift 4 SOP PR review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 29, 2021 at 10:35:07AM +0900, David Kirwan wrote:
> On Wed, 29 Sept 2021 at 02:28, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> 
> >
> > So, as far as migrating over to the new cluster...how do we want to
> > handle that? Obviously we want to do staging first and sort out any
> > issues. Should that be a task that infra and releng takes on this next
> > quater? Or something you all are going to keep working on?
> >
> 
> I hope this is something we can continue to work on as we shift back into
> the infra & releng. Might be good to catch you for a few minutes for a chat
> this week to bounce a few ideas about how we could do it, we were

Sure. :) 

> considering adding new roles for each individual app, it could allow us to
> deploy them with any new ocp4 required changes without affecting the
> existing 3.11 cluster versions.

Well, in some cases thats fine, but in other cases we really need to
actually migrate them (ie, stop old one, start new one, repoint
proxies). This would be the case for anything that had persistent data
volumes and possibly others. 

I would hope for most it would just be changing the playbook to run on
os-control hosts instead of os-masters of the old cluster and possibly a
few apis changing versions. Then, changing the proxies to point to the
new cluster instead of old for that app.

> > Also, I will have 2 more compute nodes we can add (one to stg and one to
> > prod) in a bit (need to get vlans sorted, etc). Perhaps it's worth
> > adding a sop to add new nodes I can just do it? Or hand off the machines
> > when they are ready for you all.
> >
> 
> Nice! Yep we have a SOP from the CentOS CI infra we can use, it would be
> great if you wanted to follow it to add these new nodes!

Sounds good. It will be a bit as I need to get them prepped and make
sure they are ready, and also we head into final freeze next tuesday, so
not much time there. ;( 

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux