Re: Rethinking fedora websites deployment

2022-12-03 Thread T.C. Hollingsworth
On Sun, Nov 27, 2022 at 5:32 PM Kevin Fenzi wrote: > > C) Same as B, but with an external builder > > We already build the new websites on Gitlab CI, and since the S3 > > gateway is accessible from the outside, we could just push the build > > artifacts to s3 directly from GitLab CI. Then

Re: Rethinking fedora websites deployment

2022-11-28 Thread Kevin Fenzi
On Mon, Nov 28, 2022 at 02:24:14PM +0100, darknao wrote: > > > On 2022-11-28 01:32, Kevin Fenzi wrote: > > Some more I have thought on: > > > > E) a twist on A. We build and serve in openshift, but we stick > > cloudfront in front of it. This would solve the speed problems, but > > still would

Re: Rethinking fedora websites deployment

2022-11-28 Thread darknao
On 2022-11-28 01:32, Kevin Fenzi wrote: Some more I have thought on: E) a twist on A. We build and serve in openshift, but we stick cloudfront in front of it. This would solve the speed problems, but still would have the openshift down issue. I'm not familiar with Cloudfront, so I can't

Re: Rethinking fedora websites deployment

2022-11-27 Thread Kevin Fenzi
On Fri, Nov 25, 2022 at 01:07:50PM +0100, darknao wrote: > I like C too. > Currently, when something breaks on the websites (the most common issue is > outdated content), the websites team needs to reach out to infra to > understand what's happening and ask them to check the build logs. > Using

Re: Rethinking fedora websites deployment

2022-11-27 Thread Kevin Fenzi
On Thu, Nov 24, 2022 at 05:28:22PM -, Francois Andrieu wrote: > Hi everyone! Hello. > The Websites & Apps team is currently working on rewriting all major Fedora > websites (such as getfedora, spins & alt) and I believe this is a good > opportunity to revisit the current deployment

Re: Rethinking fedora websites deployment

2022-11-25 Thread darknao
I like C too. Currently, when something breaks on the websites (the most common issue is outdated content), the websites team needs to reach out to infra to understand what's happening and ask them to check the build logs. Using Openshift is not a widespread skill, and it can be a bit difficult

Re: Rethinking fedora websites deployment

2022-11-25 Thread Pierre-Yves Chibon
On Thu, Nov 24, 2022 at 07:25:03PM +0100, darknao wrote: > > > On 2022-11-24 18:58, Jan K wrote: > > What is likelyhood of Openshift going down? A would be best > > solution if stable enough. > > > > copperi > > > > Openshift is quite stable. But everything around it may not. Having a >

Re: Rethinking fedora websites deployment

2022-11-24 Thread darknao
On 2022-11-24 18:58, Jan K wrote: What is likelyhood of Openshift going down? A would be best solution if stable enough. copperi Openshift is quite stable. But everything around it may not. Having a network outage, internal VPN issue, datacenter incident, or just an openshift

Re: Rethinking fedora websites deployment

2022-11-24 Thread Ahmed Almeleh
My vote is for C. If we can reduce the amount of steps required to implement service redundancy. Deployment to S3 provides out of the box access to the public domain and is straightforward. Regards, Ahmed Al-meleh Fedora QA Contributor On Thu, 24 Nov 2022, 17:28 Francois Andrieu, wrote: > Hi

Re: Rethinking fedora websites deployment

2022-11-24 Thread Jan K
What is likelyhood of Openshift going down? A would be best solution if stable enough. copperi From: Francois Andrieu Sent: Thursday, November 24, 2022 7:28 PM To: infrastructure@lists.fedoraproject.org Subject: Rethinking fedora websites deployment Hi

Rethinking fedora websites deployment

2022-11-24 Thread Francois Andrieu
Hi everyone! The Websites & Apps team is currently working on rewriting all major Fedora websites (such as getfedora, spins & alt) and I believe this is a good opportunity to revisit the current deployment workflow and try to make it simpler. Currently, websites are being built in Openshift,