Hello!
There is some effort right now to make Bodhi gate updates based on Greenwave. We would like to test Bodhi and Greenwave together in staging and ultimately use it in production soon.
However, there is some question about how to deploy Greenwave and WaiverDB in our infrastructure. The Greenwave/WaiverDB authors had been planning to deploy them onto OpenShift, and have already done the work to make them work that way. However it seems that we don't have a production-ready OpenShift just yet. The question is: should the Greenwave authors wait for an OpenShift to be deployed on our infrastructure, or should they go ahead and plan for a "traditional" deployment?
They would prefer to use OpenShift since they have already put the effort into being compatible with it, but they would also like to know as soon as possible if that isn't going to be a reality in time so they can start the effort to write playbooks and set up VMs for a traditional deployment. Thus, it would help them to know soon if they will not be able to use OpenShift.
Thoughts?
On Wed, Jul 19, 2017 at 02:32:26PM -0400, Randy Barlow wrote:
Hello!
There is some effort right now to make Bodhi gate updates based on Greenwave. We would like to test Bodhi and Greenwave together in staging and ultimately use it in production soon.
However, there is some question about how to deploy Greenwave and WaiverDB in our infrastructure. The Greenwave/WaiverDB authors had been planning to deploy them onto OpenShift, and have already done the work to make them work that way. However it seems that we don't have a production-ready OpenShift just yet. The question is: should the Greenwave authors wait for an OpenShift to be deployed on our infrastructure, or should they go ahead and plan for a "traditional" deployment?
They would prefer to use OpenShift since they have already put the effort into being compatible with it, but they would also like to know as soon as possible if that isn't going to be a reality in time so they can start the effort to write playbooks and set up VMs for a traditional deployment. Thus, it would help them to know soon if they will not be able to use OpenShift.
Thoughts?
I had a chat with Ralph about this a little bit ago and we agreed that if on the 24th openshift wasn't in prod we would roll back to traditional deployment.
Ny hopes are that openshift in prod isn't too far and thus we can roll with it.
Pierre
On Wed, 2017-07-19 at 21:36 +0200, Pierre-Yves Chibon wrote:
I had a chat with Ralph about this a little bit ago and we agreed that if on the 24th openshift wasn't in prod we would roll back to traditional deployment.
Thanks for the replies everyone!
The 24th was yesterday. I haven't seen an announcement about OpenShift. Do we have one in place? Should we plan on a traditional deployment?
On 07/25/2017 12:35 PM, Randy Barlow wrote:
On Wed, 2017-07-19 at 21:36 +0200, Pierre-Yves Chibon wrote:
I had a chat with Ralph about this a little bit ago and we agreed that if on the 24th openshift wasn't in prod we would roll back to traditional deployment.
Thanks for the replies everyone!
The 24th was yesterday. I haven't seen an announcement about OpenShift. Do we have one in place? Should we plan on a traditional deployment?
Ricky is going to see about deploying waverdb to the stg openshift today. So, we are a bit behind, but making progress.
Was the 24th a hard deadline? or can we wait a bit more?
Once we have stg working, prod should be pretty easy.
kevin
On Wed, Jul 26, 2017 at 12:25:49PM -0700, Kevin Fenzi wrote:
On 07/25/2017 12:35 PM, Randy Barlow wrote:
On Wed, 2017-07-19 at 21:36 +0200, Pierre-Yves Chibon wrote:
I had a chat with Ralph about this a little bit ago and we agreed that if on the 24th openshift wasn't in prod we would roll back to traditional deployment.
Thanks for the replies everyone!
The 24th was yesterday. I haven't seen an announcement about OpenShift. Do we have one in place? Should we plan on a traditional deployment?
Ricky is going to see about deploying waverdb to the stg openshift today. So, we are a bit behind, but making progress.
Was the 24th a hard deadline? or can we wait a bit more?
As long as it's moving it's fine, would be awesome if we could get both waiverdb and greenwave running in stg by the end of the week, but if it's a little later it's not the end of the world :)
Pierre
On Wed, Jul 19, 2017 at 02:32:26PM -0400, Randy Barlow wrote:
Hello!
There is some effort right now to make Bodhi gate updates based on Greenwave. We would like to test Bodhi and Greenwave together in staging and ultimately use it in production soon.
We do have the staging instance of openshift, could it be leveraged for your tests ?
Pierre
On Wed, Jul 19, 2017 at 09:36:52PM +0200, Pierre-Yves Chibon wrote:
On Wed, Jul 19, 2017 at 02:32:26PM -0400, Randy Barlow wrote:
Hello!
There is some effort right now to make Bodhi gate updates based on Greenwave. We would like to test Bodhi and Greenwave together in staging and ultimately use it in production soon.
We do have the staging instance of openshift, could it be leveraged for your tests ?
From last night's discussion in IRC, it sounded like the agreement was that:
(1) Ralph & co. will get a deployment template ready for our OpenShift in staging; (2) Ricky Elrod is working on similar for our Modernpaste (currently in staging) to make that a first target for production; (3) We were up until just recently waiting for a production wildcard cert, but that is now in place AIUI from other list mail from Smooge
From (2) and (3) it sounds like we can have something in production Very Soon(tm), but this doesn't change the need to test things out in staging before they go to production. (And everyone gets that, and can roll with it.) Is there another wrinkle here I missed?
On Wed, 2017-07-19 at 21:36 +0200, Pierre-Yves Chibon wrote:
We do have the staging instance of openshift, could it be leveraged for your tests ?
Certainly; we can and should use that for testing. I think we'd also like to know how at-risk the production deployment of it will be (a separate concern).
infrastructure@lists.fedoraproject.org