Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
On Thu, Jun 25, 2020 at 9:20 AM Vipul Siddharth vipul@redhat.com wrote:
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
Great work in getting this ready and available :)
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It would be great to see the workloads and some stats so we know who has moved and so on. Perhaps include that in your weekly shout out to remind people to migrate that we have migrated XX% of workloads?
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Great work in getting this ready and available :)
Shout out to @Brian Stinson, @David Kirwan and @Fabian Arrotin for most of the work :)
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It would be great to see the workloads and some stats so we know who has moved and so on. Perhaps include that in your weekly shout out to remind people to migrate that we have migrated XX% of workloads?
Interesting idea! We will have to think on how to do these matrices since there are tons of projects that are just not active anymore.. Will think about it Thank you :)
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
--
Leigh Griffin
Engineering Manager
Red Hat Waterford
Communications House
Cork Road, Waterford City
lgriffin@redhat.com M: +353877545162 IM: lgriffin
@redhatjobs redhatjobs @redhatjobs _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to start working on updating your workload ". Our project is in maintenance mode but is still built and images keep being pushed for regular updates, so it's essential that that should keep working. But we don't have a dedicated person anymore dealing with the CI/CD side of things. So is there any documentation you can point to that explains what " updating your workload " would entail and how to go about migrating things?
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com wrote:
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com wrote:
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to start working on updating your workload ". Our project is in maintenance mode but is still built and images keep being pushed for regular updates, so it's essential that that should keep working. But we don't have a dedicated person anymore dealing with the CI/CD side of things. So is there any documentation you can point to that explains what " updating your workload " would entail and how to go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know and I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com wrote:
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Ok, so if I understand correctly if we don't do anything any Jenkins jobs should be transferred automatically?
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near future. We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com wrote:
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com wrote:
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to start working on updating your workload ". Our project is in maintenance mode but is still built and images keep being pushed for regular updates, so it's essential that that should keep working. But we don't have a dedicated person anymore dealing with the CI/CD side of things. So is there any documentation you can point to that explains what " updating your workload " would entail and how to go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know and I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com wrote:
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team http://vipul.dev _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, so if I understand correctly if we don't do anything any Jenkins jobs should be transferred automatically?
oh no! apologies! seems the doc is not as clear as I had hoped it to be :) I will modify it again (tomorrow or on Monday) We will create you a namespace (say Launcher) with Jenkins provisioned and you can configure these jobs there. You will have admin access to the namespace and the Jenkins so you would be able to do anything there. If I am still confusing you, please let me know and we can talk on IRC or a call and then I will also try to refine the doc as per suggestions.
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near future. We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com wrote:
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com wrote:
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to start working on updating your workload ". Our project is in maintenance mode but is still built and images keep being pushed for regular updates, so it's essential that that should keep working. But we don't have a dedicated person anymore dealing with the CI/CD side of things. So is there any documentation you can point to that explains what " updating your workload " would entail and how to go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know and I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com wrote:
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start working on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team
Wait wait, I'd have to redo the jobs? I didn't even create them in the first place, I have no idea what and how to do that, I'm just here to make sure they keep running and give a shout if anything goes wrong. :-)
Being a project in maintenance mode there's no one available to do that work, So if I understood it correctly this time I'll have to kick this up the chain to see how to best handle this.
On Sat, Jul 18, 2020 at 8:54 PM Vipul Siddharth vipul@redhat.com wrote:
On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, so if I understand correctly if we don't do anything any Jenkins
jobs should be transferred automatically?
oh no! apologies! seems the doc is not as clear as I had hoped it to be :) I will modify it again (tomorrow or on Monday) We will create you a namespace (say Launcher) with Jenkins provisioned and you can configure these jobs there. You will have admin access to the namespace and the Jenkins so you would be able to do anything there. If I am still confusing you, please let me know and we can talk on IRC or a call and then I will also try to refine the doc as per suggestions.
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near
future.
We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com
wrote:
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com
wrote:
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to
start working
on updating your workload ". Our project is in maintenance mode but is
still
built and images keep being pushed for regular updates, so it's
essential that
that should keep working. But we don't have a dedicated person anymore dealing with the CI/CD side of things. So is there any documentation
you can
point to that explains what " updating your workload " would entail
and how to
go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know and
I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com
wrote:
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we want to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start
working
on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Hi Tako
From what I understand, right now you have 4 jobs in Jenkins instance on
ci.centos.org. We will create you a namespace in OpenShift and you will have to migrate your jobs to the new Jenkins (that we will provision in the namespace created for you).
On Sun, Jul 19, 2020 at 8:29 PM Tako Schotanus tschotan@redhat.com wrote:
Wait wait, I'd have to redo the jobs? I didn't even create them in the first place, I have no idea what and how to do that, I'm just here to make sure they keep running and give a shout if anything goes wrong. :-)
Being a project in maintenance mode there's no one available to do that work, So if I understood it correctly this time I'll have to kick this up the chain to see how to best handle this.
On Sat, Jul 18, 2020 at 8:54 PM Vipul Siddharth vipul@redhat.com wrote:
On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, so if I understand correctly if we don't do anything any Jenkins
jobs should be transferred automatically?
oh no! apologies! seems the doc is not as clear as I had hoped it to be :) I will modify it again (tomorrow or on Monday) We will create you a namespace (say Launcher) with Jenkins provisioned and you can configure these jobs there. You will have admin access to the namespace and the Jenkins so you would be able to do anything there. If I am still confusing you, please let me know and we can talk on IRC or a call and then I will also try to refine the doc as per suggestions.
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near
future.
We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com
wrote:
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com
wrote:
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to
start working
on updating your workload ". Our project is in maintenance mode but
is still
built and images keep being pushed for regular updates, so it's
essential that
that should keep working. But we don't have a dedicated person anymore dealing with the CI/CD side of things. So is there any documentation
you can
point to that explains what " updating your workload " would entail
and how to
go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know and
I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com
wrote:
Reminder to tenants :)
---------- Forwarded message --------- From: Vipul Siddharth vipul@redhat.com Date: Thu, Jun 25, 2020 at 1:48 PM Subject: Call for migration to new openshift cluster To: ci-users ci-users@centos.org Cc: David Kirwan dkirwan@redhat.com
Hi all,
We are done and ready with the new Openshift 4 CI cluster. Now we
want
to start the second phase of it i.e migrating projects to the new cluster.
If you are currently using apps.ci.centos.org (OCP 3.6), please contact us off-list so that we can create a namespace for you in the new OCP 4.4 cluster, so you can start migrating your workloads.
It's not a hard deadline but we are hoping to retire the older Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy (ci.centos.org) environment in a couple of months after that.
If you are using ci.centos.org, it's a very good time to start
working
on updating your workload
If you have any questions, please reach out to us Thank You and stay safe
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
-- Vipul Siddharth Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Ok, but "migrate" is, "export from the old server and import into the new server and everything should work fine" or "you have to know what you're doing and possibly redo the jobs"? :-)
On Sun, Jul 19, 2020 at 5:06 PM Vipul Siddharth vipul@redhat.com wrote:
Hi Tako From what I understand, right now you have 4 jobs in Jenkins instance on ci.centos.org. We will create you a namespace in OpenShift and you will have to migrate your jobs to the new Jenkins (that we will provision in the namespace created for you).
On Sun, Jul 19, 2020 at 8:29 PM Tako Schotanus tschotan@redhat.com wrote:
Wait wait, I'd have to redo the jobs? I didn't even create them in the first place, I have no idea what and how to do that, I'm just here to make sure they keep running and give a shout if anything goes wrong. :-)
Being a project in maintenance mode there's no one available to do that work, So if I understood it correctly this time I'll have to kick this up the chain to see how to best handle this.
On Sat, Jul 18, 2020 at 8:54 PM Vipul Siddharth vipul@redhat.com wrote:
On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, so if I understand correctly if we don't do anything any Jenkins
jobs should be transferred automatically?
oh no! apologies! seems the doc is not as clear as I had hoped it to be :) I will modify it again (tomorrow or on Monday) We will create you a namespace (say Launcher) with Jenkins provisioned and you can configure these jobs there. You will have admin access to the namespace and the Jenkins so you would be able to do anything there. If I am still confusing you, please let me know and we can talk on IRC or a call and then I will also try to refine the doc as per suggestions.
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near
future.
We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com
wrote:
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com
wrote:
Hi Vipul,
you said "If you are using ci.centos.org, it's a very good time to
start working
on updating your workload ". Our project is in maintenance mode but
is still
built and images keep being pushed for regular updates, so it's
essential that
that should keep working. But we don't have a dedicated person
anymore
dealing with the CI/CD side of things. So is there any documentation
you can
point to that explains what " updating your workload " would entail
and how to
go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know
and I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
Thanks! -Tako
On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com
wrote:
> > Reminder to tenants :) > > ---------- Forwarded message --------- > From: Vipul Siddharth vipul@redhat.com > Date: Thu, Jun 25, 2020 at 1:48 PM > Subject: Call for migration to new openshift cluster > To: ci-users ci-users@centos.org > Cc: David Kirwan dkirwan@redhat.com > > > Hi all, > > We are done and ready with the new Openshift 4 CI cluster. Now we
want
> to start the second phase of it i.e migrating projects to the new > cluster. > > If you are currently using apps.ci.centos.org (OCP 3.6), please > contact us off-list so that we can create a namespace for you in the > new OCP 4.4 cluster, so you can start migrating your workloads. > > It's not a hard deadline but we are hoping to retire the older > Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy > (ci.centos.org) environment in a couple of months after that. > > If you are using ci.centos.org, it's a very good time to start
working
> on updating your workload > > If you have any questions, please reach out to us > Thank You and stay safe > > -- > Vipul Siddharth > Fedora | CentOS CI Infrastructure Team > > > -- > Vipul Siddharth > Fedora | CentOS CI Infrastructure Team > > _______________________________________________ > CI-users mailing list > CI-users@centos.org > https://lists.centos.org/mailman/listinfo/ci-users >
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team http://vipul.dev _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Sun, Jul 19, 2020 at 8:40 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, but "migrate" is, "export from the old server and import into the new server and everything should work fine" or "you have to know what you're doing and possibly redo the jobs"? :-)
Unfortunately, it would be the latter case here Of course, we will be around to help if needed
On Sun, Jul 19, 2020 at 5:06 PM Vipul Siddharth vipul@redhat.com wrote:
Hi Tako From what I understand, right now you have 4 jobs in Jenkins instance on ci.centos.org. We will create you a namespace in OpenShift and you will have to migrate your jobs to the new Jenkins (that we will provision in the namespace created for you).
On Sun, Jul 19, 2020 at 8:29 PM Tako Schotanus tschotan@redhat.com wrote:
Wait wait, I'd have to redo the jobs? I didn't even create them in the first place, I have no idea what and how to do that, I'm just here to make sure they keep running and give a shout if anything goes wrong. :-)
Being a project in maintenance mode there's no one available to do that work, So if I understood it correctly this time I'll have to kick this up the chain to see how to best handle this.
On Sat, Jul 18, 2020 at 8:54 PM Vipul Siddharth vipul@redhat.com wrote:
On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, so if I understand correctly if we don't do anything any Jenkins
jobs should be transferred automatically?
oh no! apologies! seems the doc is not as clear as I had hoped it to be :) I will modify it again (tomorrow or on Monday) We will create you a namespace (say Launcher) with Jenkins provisioned and you can configure these jobs there. You will have admin access to the namespace and the Jenkins so you would be able to do anything there. If I am still confusing you, please let me know and we can talk on IRC or a call and then I will also try to refine the doc as per suggestions.
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near
future.
We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com
wrote:
On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com
wrote:
> > Hi Vipul, > > you said "If you are using ci.centos.org, it's a very good time to
start working
> on updating your workload ". Our project is in maintenance mode but
is still
> built and images keep being pushed for regular updates, so it's
essential that
> that should keep working. But we don't have a dedicated person
anymore
> dealing with the CI/CD side of things. So is there any
documentation you can
> point to that explains what " updating your workload " would entail
and how to
> go about migrating things?
Hi Tako, Apologies for the delay I wrote a page [1] trying to explain some things. I hope it helps. If you think I should add something more there, please let me know
and I will do it with priority.
[1] https://centosci.github.io/ocp4-docs/sops/migration/
> > Thanks! > -Tako > > On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com
wrote:
>> >> Reminder to tenants :) >> >> ---------- Forwarded message --------- >> From: Vipul Siddharth vipul@redhat.com >> Date: Thu, Jun 25, 2020 at 1:48 PM >> Subject: Call for migration to new openshift cluster >> To: ci-users ci-users@centos.org >> Cc: David Kirwan dkirwan@redhat.com >> >> >> Hi all, >> >> We are done and ready with the new Openshift 4 CI cluster. Now we
want
>> to start the second phase of it i.e migrating projects to the new >> cluster. >> >> If you are currently using apps.ci.centos.org (OCP 3.6), please >> contact us off-list so that we can create a namespace for you in
the
>> new OCP 4.4 cluster, so you can start migrating your workloads. >> >> It's not a hard deadline but we are hoping to retire the older >> Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy >> (ci.centos.org) environment in a couple of months after that. >> >> If you are using ci.centos.org, it's a very good time to start
working
>> on updating your workload >> >> If you have any questions, please reach out to us >> Thank You and stay safe >> >> -- >> Vipul Siddharth >> Fedora | CentOS CI Infrastructure Team >> >> >> -- >> Vipul Siddharth >> Fedora | CentOS CI Infrastructure Team >> >> _______________________________________________ >> CI-users mailing list >> CI-users@centos.org >> https://lists.centos.org/mailman/listinfo/ci-users >> > > > -- > TAKO SCHOTANUS > SENIOR SOFTWARE ENGINEER > Red Hat > > > > > _______________________________________________ > CI-users mailing list > CI-users@centos.org > https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team http://vipul.dev _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Ok , it's clear to me now, thanks!
On Sun, Jul 19, 2020 at 5:18 PM Vipul Siddharth vipul@redhat.com wrote:
On Sun, Jul 19, 2020 at 8:40 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, but "migrate" is, "export from the old server and import into the new server and everything should work fine" or "you have to know what you're doing and possibly redo the jobs"? :-)
Unfortunately, it would be the latter case here Of course, we will be around to help if needed
On Sun, Jul 19, 2020 at 5:06 PM Vipul Siddharth vipul@redhat.com wrote:
Hi Tako From what I understand, right now you have 4 jobs in Jenkins instance on ci.centos.org. We will create you a namespace in OpenShift and you will have to migrate your jobs to the new Jenkins (that we will provision in the namespace created for you).
On Sun, Jul 19, 2020 at 8:29 PM Tako Schotanus tschotan@redhat.com wrote:
Wait wait, I'd have to redo the jobs? I didn't even create them in the first place, I have no idea what and how to do that, I'm just here to make sure they keep running and give a shout if anything goes wrong. :-)
Being a project in maintenance mode there's no one available to do that work, So if I understood it correctly this time I'll have to kick this up the chain to see how to best handle this.
On Sat, Jul 18, 2020 at 8:54 PM Vipul Siddharth vipul@redhat.com wrote:
On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus tschotan@redhat.com wrote:
Ok, so if I understand correctly if we don't do anything any Jenkins
jobs should be transferred automatically?
oh no! apologies! seems the doc is not as clear as I had hoped it to be :) I will modify it again (tomorrow or on Monday) We will create you a namespace (say Launcher) with Jenkins provisioned and you can configure these jobs there. You will have admin access to the namespace and the Jenkins so you would be able to do anything there. If I am still confusing you, please let me know and we can talk on IRC or a call and then I will also try to refine the doc as per suggestions.
We have 4 configurations in the current CI:
https://ci.centos.org/search/?q=launcher
The only thing I care about is that they keep running for the near
future.
We'll probably not touch them anymore.
Thanks!
On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth vipul@redhat.com
wrote:
> > > > On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus tschotan@redhat.com
wrote:
>> >> Hi Vipul, >> >> you said "If you are using ci.centos.org, it's a very good time
to start working
>> on updating your workload ". Our project is in maintenance mode
but is still
>> built and images keep being pushed for regular updates, so it's
essential that
>> that should keep working. But we don't have a dedicated person
anymore
>> dealing with the CI/CD side of things. So is there any
documentation you can
>> point to that explains what " updating your workload " would
entail and how to
>> go about migrating things? > > > Hi Tako, > Apologies for the delay > I wrote a page [1] trying to explain some things. I hope it helps. > If you think I should add something more there, please let me know
and I will do it with priority.
> > [1] https://centosci.github.io/ocp4-docs/sops/migration/ > >> >> Thanks! >> -Tako >> >> On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth vipul@redhat.com
wrote:
>>> >>> Reminder to tenants :) >>> >>> ---------- Forwarded message --------- >>> From: Vipul Siddharth vipul@redhat.com >>> Date: Thu, Jun 25, 2020 at 1:48 PM >>> Subject: Call for migration to new openshift cluster >>> To: ci-users ci-users@centos.org >>> Cc: David Kirwan dkirwan@redhat.com >>> >>> >>> Hi all, >>> >>> We are done and ready with the new Openshift 4 CI cluster. Now we
want
>>> to start the second phase of it i.e migrating projects to the new >>> cluster. >>> >>> If you are currently using apps.ci.centos.org (OCP 3.6), please >>> contact us off-list so that we can create a namespace for you in
the
>>> new OCP 4.4 cluster, so you can start migrating your workloads. >>> >>> It's not a hard deadline but we are hoping to retire the older >>> Openshift 3.6 cluster in the upcoming quarter (3 months) and
legacy
>>> (ci.centos.org) environment in a couple of months after that. >>> >>> If you are using ci.centos.org, it's a very good time to start
working
>>> on updating your workload >>> >>> If you have any questions, please reach out to us >>> Thank You and stay safe >>> >>> -- >>> Vipul Siddharth >>> Fedora | CentOS CI Infrastructure Team >>> >>> >>> -- >>> Vipul Siddharth >>> Fedora | CentOS CI Infrastructure Team >>> >>> _______________________________________________ >>> CI-users mailing list >>> CI-users@centos.org >>> https://lists.centos.org/mailman/listinfo/ci-users >>> >> >> >> -- >> TAKO SCHOTANUS >> SENIOR SOFTWARE ENGINEER >> Red Hat >> >> >> >> >> _______________________________________________ >> CI-users mailing list >> CI-users@centos.org >> https://lists.centos.org/mailman/listinfo/ci-users > > > > -- > Vipul Siddharth > He/His/Him > Fedora | CentOS CI Infrastructure Team > _______________________________________________ > CI-users mailing list > CI-users@centos.org > https://lists.centos.org/mailman/listinfo/ci-users
-- TAKO SCHOTANUS SENIOR SOFTWARE ENGINEER Red Hat
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team http://vipul.dev _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat http://redhat.com
https://www.redhat.com/ https://red.ht/sig
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team http://vipul.dev _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Leigh Griffin -
Tako Schotanus -
Vipul Siddharth