Cloud Foundry Advisory Board Meeting, July 2020: Adopting Neutral Naming
This month’s Cloud Foundry Community Advisory Board (CAB) meeting discussed the adoption of neutral naming and featured regular development updates around the ecosystem projects.
The meeting was moderated by Troy Topnik from SUSE.
Considering neutral naming
On July 4, 2020, Dan Williams, a Linux kernel maintainer, proposed to shift from non-inclusive to a neutral terminology. Dan proposed a bunch of alternatives to the master and slave terms, which include primary/secondary, main/replica or subordinate, and initiator/target among others. He also suggested denylist/allowlist or blocklist/passlist as opposed to blacklist and whitelist. Linus Torvalds, in his turn, approved this commit.
In the wake of this news, Dieu Cao from VMware brought up the idea of adopting neutral-naming conventions for Cloud Foundry projects. Specifically, it touches upon modifying master branches to main branches.
“I’m hoping we can get to the point where all the PMCs have bought in and agreed to make this particular change. I’ve noticed a number of foundations are also adopting policies around language and preferring terms like allow and deny over whitelist and blacklist. It’s worth considering some of those terms.”
—Dieu Cao, VMware
Eric Malm of VMware provided the following updates:
- The CLI team released the first general availability of CLI v7.
- The Release Integration team delivered Cloud Foundry for Kubernetes v0.4.0 with Paketo buildpacks and Route CRD. They are now working on secret management.
- The KubeCF team is refining multi-cluster Diego configurations and is working on alternative stacks for Eirini.
- The CAPI teams is working on automatic rollout of kpack stack updates for Cloud Foundry for Kubernetes.
- The Networking team is working on route logs and system component network policies in Cloud Foundry for Kubernetes.
- The Eirini team is progressing on application tasks and internal CRDs.
- The UAA team is exposing metrics for Prometheus and Kubernetes deployment artifacts.
- The Logging and Metrics team is resolving local Syslog Agent issues. They are also exploring the usage of CAPI metadata for log annotations.
Chris Clark noted the Cloud Foundry Foundation is already planning for the European Summit, and the details will be shared in a few weeks. He added that all the talks from the recent North American summit are now available on YouTube.
Through a blog on the foundation’s website, Chris also shared his bi-weekly technical round-up. In this article, he highlighted the prominent releases, some updates and news, as well as community events for July.
The foundation recently welcomed two new developer advocates, Ram Iyengar and Shedrack Akintayo. Ram noted that Cloud Foundry is useful not only to large enterprises, but also small businesses, and he is happy for the opportunity to teach.
“There’s an opportunity to spread the cheer to people who are not enterprise developers and not part of companies with over 1,000 employees. The idea is to focus on Cloud Foundry for smaller teams and startups.” —Ram Iyengar
Shedrack, who just recently started using Cloud Foundry, also shared his experience with the technology.
“Coming from a background of a front-end engineer, it’s quite easy for me to break into a cloud-native sector. So far, my learning has been fruitful. I’ve managed to do a couple of things, and I’m looking forward to learning more and also sharing my knowledge.” —Shedrack Akintayo
The next community call is tentatively scheduled for August 19, 2020, at 8 a.m. PDT. Anyone interested can join Cloud Foundry’s CAB Slack channel.
Want details? Watch the videos!
Below, you will find the video recording of the call.
Another video features updates from the Cloud Foundry for Kubernetes special interest group for July.