Video summary
The South Cloud team convened for their August 11th meeting to review recent releases, budget status, and upcoming priorities. Both the weekly release and a previous security update proceeded smoothly, though a minor issue regarding a failing curl command for Fastly cache purging required further investigation via a mail desk ticket. The team confirmed that Azure spending remains within thresholds, while AWS costs have slightly increased compared to last week, prompting a review of Artifactory usage. Digital Ocean expenses were reported as stable, and the group noted that no major security releases are scheduled for September. Additionally, the team addressed an expiring MTM token which has been renewed, with plans for Damien to handle the CF Factory admin token upon his return from leave.
A significant portion of the discussion focused on the roadmap to transition away from Puppet towards Antebodies and reduce AWS sponsorship costs. Key technical milestones include upgrading Ubuntu containers and moving public gates to sponsored subscriptions, specifically targeting the Sweden region which will require private endpoints. The team also discussed dropping support for Windows Server 2019 in Jenkins container images before the next LTS baseline; this decision has been approved by the Platform SIG, and the necessary pull requests are ready for merging. To facilitate this transition, a blog post is planned to be written once Damien returns, ensuring clear communication about the end of support for the older Windows version.
In terms of ongoing development work, several infrastructure upgrades were completed or advanced during the week. The team successfully upgraded JDK versions in packer image templates and agent images used by their CI systems, with plans to move on to Docker packaging updates. A Go port was prepared for the incremental publisher to replace a Node.js dependency, aiming to reduce JavaScript usage across services. Furthermore, improvements were made to test splitting efficiency, allowing builds to run on fewer agents without increasing total build time, which significantly reduces load on the Jenkins data infrastructure. The team also addressed the migration of controllers to the Sweden region and completed the installation of PostgreSQL on a census machine to support report generation jobs.
The meeting concluded with updates on various support requests and project statuses, including enabling preview features for contributor spotlights and plugin modernizer stats. While some tasks related to GSoC projects are still pending finalization, the team expressed confidence in their progress toward maintaining up-to-date infrastructure. With most immediate issues resolved or planned for the following week, the team adjourned with a brief wrap-up, looking forward to the next meeting on Tuesday and continuing their efforts to modernize their cloud environment and tooling stack.
Read the full video transcript
Hello and welcome to the South Cloud
team meeting.
Uh
we are the
on the wrong page.
Um we are the 11th of August. We have
>> [snorts]
>> We have Mark, Jim, and myself.
Uh Dennis is off. He won't be here
today.
On the announcements
last week, we had a security release. Um
today we had
weekly release.
Both releases went well. Minor issue
about Fastly cache purge.
Uh curl command that failed again for a
third time. I need to open a mail desk
to check what's wrong with that.
On the announcements,
uh it's in capacity. I'm off until
next Monday.
And I will be off
for the rest of the month next week.
Uh for our roadmap
Uh
currently peak, we have
We are all
the puppets.
Puppet transition to antibodies are one
of our priorities.
Decreasing AWS group sponsoring sponsor
that couldn't cost. Ubuntu container
upgrade.
That's working on my milestone. Um
main priority.
Anything to add on the announcements?
No.
Upcoming calendar, next infra meeting
will be next
next Tuesday,
next weekly will be on
as
next Tuesday too. Next LTS will be on
September. No security release
announced.
Upcoming credential expiration, we have
a MTM token that will expire I have new
maths.
>> I've already done should be
>> Yeah, cool.
And Damien will take care of CF factory
admin token when he'll be back.
No major event
planned.
Any questions or remarks? No.
On the cloud budget on Azure, we are
good. We are below our threshold.
We still need to move public gate as to
the sponsored subscription. We want to
make
the
transition of set CI first because we
will use the Sweden region that will
require us some private endpoint uh
and adjustment like that.
On the Azure sponsored subscription,
we are at the same forecast as last
week. Uh
all good.
On Digital Ocean, nothing too special to
say.
Ooh, we're good.
AWS
the forecasted
amount is
uh
bigger than last week.
I don't know yet why. Maybe related to
I'm via I don't know. I have a I don't
know.
We
will look at next week if still high.
If Artifactory usage still big,
nothing to say about utilization for
good.
Anything else to
say on the cards?
Okay, going to the
uh L desk
>> [clears throat]
>> um
so Jay,
uh I'll let you take the first one.
About 10 p.m. token expiration.
>> Uh yeah, that's been closed. The token
has been renewed and updated in socks
and
also been applied with Kubernetes
management.
>> Okay.
Anything special?
>> No.
>> Um okay, perfect. Uh this one that may
close added some tags on
uh
previous weeks.
It won't really help us.
So, it's there, but yeah. Uh not really
helping.
On the keep
infrastructure up to date,
we've made some backports for last
week's LTS release and I look at the
control
uh I've been updated.
On the working progress,
uh Jay, I'll let you speak about search
the capacity upgrade.
>> Yeah, so the JDK
uh versions for our packer image
templates have been upgraded.
Uh those pull requests have been merged.
It's also been upgraded in the agent
images used by
infra CI CI.CI
CI [clears throat]
CI.jenkins.io and also the EC2
templates.
So, the packer images stuff is done and
we'll be moving on to the Docker
packaging part.
>> Perfect.
>> [clears throat]
>> I've been doing
on the
pipeline already updates.
The request to which minor just
the instructions things that the new
version.
>> Okay.
>> But I didn't would say certification.
Daniel is waiting for to come back to
his PTO to share
the encrypted files. Nothing
else to be done on that part because
he's only one to have access to it right
now.
Bump Node.js to from 22 to 24.
Your turn again, Jay.
>> Yes, so there is some unfinished
work in this issue. So,
the incremental publisher's Docker file
needs It It is at
Node.js 24 but needs to be updated to
the current latest version that we're
using across infra.
>> On the incremental
publisher,
small teaser, I prepare a Go port.
>> Okay.
>> I need to open an issue to
plan how to test and to deploy this Go
port to replace this Node.js version.
So,
one service less with JavaScript and
dependency.
On
the drop Windows
2019 support, we
We Daniel opened a request on the
all agent to drop uh
drop them.
I don't know. Uh do you have more
information about this, Mark, or is it
just a matter of
having a consensus?
>> I think it's a matter of getting a con-
getting the consensus. We just need to
announce it. We really want to do it
before the next LTS baseline, for sure.
>> Okay.
Uh have you planned to make some blog
post, or is Tim now taking care of it?
>> Uh I thought I thought we had the plan
that there would be a blog post, but I
don't recall who
>> Well, maybe
>> I know actually
I know I'm not sure that Yeah, I'll have
to look in the notes of the platform
SIG, but that the next meeting of the
platform SIG is 2 weeks from now.
>> Okay.
>> So So we'll we'll it will I suspect
we'll discuss it there.
>> But 2 weeks from now, we'll we will be
very close to the next LTS release.
>> Yeah. Well, yeah, the next baseline.
Let's Let me look. Let's see. When do we
choose the next baseline? We choose the
next baseline next week, right? So we'll
need
>> Because in the platform SIG,
as I
see,
you, me, Damien, Chris.
So um
Yeah.
Maybe can we increase to ask uh what she
think about it and if we can go
>> Yeah, I think
>> without waiting for the next
>> So the last the last platform SIG
already decided yes, we are we are go we
are good to go. The last The notes from
the last platform SIG um
show that we the first item is Windows
2019 end of support in Jenkins container
images, and we want to drop support in
August.
Uh Damien would will propose two pull
requests to propose the change and he's
happy to have help on the blog post.
Willing to do it himself if needed.
>> So two pull requests are
open since a week ago. We are missing
>> we just we just So we just need to merge
these and then then the blog post can be
done.
>> Okay.
Perfect.
Let's discuss that on
next Monday when or Tuesday when Damien
will be back soon.
On
the support parts, request for pair
preview to be enabled on contributor
contributor spotlights
stories and plugin modernizers stats.
On the contributor spotlights
there is a small change to add but I
think this is one
should be good. The one for stories is
good. Contributors needs small
adjustments like the one from stories.
And for for plugin modernizer stats,
since [snorts] there is no
Jenkins pipeline and
preview deployment yet and since it's a
GSoC project that has not been finalized
we
encourage mentors and students to put in
place share share for preview.
It's waiting for Chris to
to work on this
elements that Damien gave.
On the keeper first and maintainable
define a common node with finite and
retry function for website build. That's
about two preview. It's I think it will
be back in the backlog.
I mean I did not have time to work on
it.
Decrease bomb car space splitting test
more efficiently. I now have
better understanding of the split test
plugin and its limitation.
But I found out
proper workaround for now to
do my split task I want.
And I
I opened a pull request to get
>> [snorts]
>> out first
basic fixed splits.
You can see on Mac but in the pull
request that we have
fixed amount [snorts] of splits.
And the build time, not this one because
it has a restart at the penultimate
splitting so it restarted each of them
but
we are about the same ballpark of
total build time but with only 20 or 40
agent if aligned tested instead of 300
or 600 and
overloading CI to Jenkins data.
So that's a big win.
So after this one will be merged, I will
open another new one with please split
tests and then I will probably open or
complete existing parallel test executor
issues.
Maybe contribute to some feature I want.
On the
migrate controller
that's [snorts] yeah, that's the about
earlier that we didn't set them up and
start yet. We have to ensure that
everything is working on when on the
Sweden region on the Sweden region.
And then the last one is move that out
to the research that that stick
generation out of from under machine.
I've got
what I needed to do with Daniel
to install post GRE SQL on census
machine.
Ensure this installation is done and
it's set up is done from the bits.
Then I will launch the end system job
myself from that machine and export and
we'll start by manually exporting
all the wrong running so export job. So
generation so report job so
before doing
it later. [snorts]
On the new issue to triage, I think
there are only two.
We have this one which is the credential
we spoke earlier on Italian country. So
I don't know.
Yes, then we'll do it.
And
someone proposed a new mirror in
Switzerland.
The other one we'll wait.
Any questions? Remark?
Anything else? Okay, perfect.
Then
I'll stop sharing and I'll stop the
recording. See you next week.
>> See you next week.
That was quick.