|
Re: Announcing Cloud Foundry CLI v7 Release Plan
For now, application manifests will remain the same.
We did recently introduce versioning to manifests, which will allow us to iterate on manifest structure and features more aggressively in the future (and independently from API/CLI version).
|
|
|
Re: Seeking Nominations: Cloud Foundry Extensions PMC
Swarna Podila
Hi Everyone, Just a quick reminder to send us your nominations by the end of Friday (May 8).
Cheers!
-- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more.
On Thu, Apr 30, 2020 at 4:30 PM Swarna Podila < spodila@...> wrote: Hi All, You may have seen Dr. Max's note earlier. After leading Extensions PMC for almost four years, he would like to step down and make space for new folks to take on the role.
Please send in your nominations for a new lead for Cloud Foundry Extensions PMC by the end of day next Friday, May 8, 2020.
-- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more.
|
|
|
Re: cf-for-k8s 0.2.0 alpha release
Chip Childers <cchilders@...>
More progress! I particularly appreciate two parts of this: The clear indication of what's next up in the release notes, and the appropriate use of a flame emoji for the logging feature. 👍
Chip Childers Executive Director Cloud Foundry Foundation
On Mon, May 4, 2020 at 7:08 PM Saikiran Yerram < syerram@...> wrote: Hello CF community,
We just shipped cf-for-k8s 0.2.0 alpha release, so please check out the release notes here. Some notable highlights of this release,
- Users can now see streaming logs during cf push command. woot! - Users can now see app metrics. - Removed install.sh so users have the freedom to use ytt and kapp however they like (e.g. pass additional config of their choice)
There are many other updates worth looking into. Please take it for a spin and give us your feedback via issues or in slack channel #cf-for-k8s.
Thank you to all the contributors!!
Resources:
--
|
|
|
Hands on Labs at CF Summit
Hello folks,
As you've likely heard, Cloud Foundry Summit will be a virtual event for the first time. While I'm disappointed we won't all be gathering together in Austin, there is some upside to a virtual summit. With fewer time/space restraints, Summit will run for two days, not one, and we'll be having technical Hands on Labs sessions each day.
As far as the labs go, we're still in the planning stages, and we wanted to reach out to the community and ask a few questions:
What kind of technical lab/demo content would you want to see included? Any particular topics you think we'd be remiss to exclude?
If you've recently attended any virtual events, any wisdom you'd like to impart on how hands on labs were organized, and how successful they were (or weren't)?
Are you or your project team interested in running a lab?
Feel free to respond publicly, or to me directly. Hope you're all safe and healthy out there.
-- Chris Clark Technical Operations Manager Cloud Foundry Foundation
|
|
|
Re: Bi-weekly Round-Up: Technical + Ecosystem Updates
Hello, everyone. We’ve launched a new Tutorials website to serve as a hub for learning in our community! The hub includes an interactive hands-on lab for first-time Cloud Foundry users to experience how easy the platform makes deploying applications to Kubernetes and is open for the community to contribute. Read the release.
Special thanks to Steve Greenberg at Resilient Scale for the heavy lifting to make this happen! Expect more news on this soon, and if you’re interested in contributing/feedback, please let us know.
Also, CF Summit is going virtual. Here’s the full story. From the Last Few Weeks:Community Updates:Have a question for the staff at Cloud Foundry Foundation? Want to stay current with updates for the Foundation? Join the #cff-forum channel on the community Slack. Looking for a job? Don’t hesitate to check out the #jobs channel in our community slack; folks are stepping up and sharing the job openings in our community.
(And if you are hiring, please do share the info in that channel.) All things Cloud Foundry Summit:Dates To Remember (All times US Pacific):CF for Kubernetes SIG call - 8:30 AM on May 12 Bi-Weekly CF App Runtime PMC meeting - 10:30 AM on May 12 AMA Monthly call - 8:00 AM on May 19 CF CAB call - 8:00 AM on May 20
Interesting Finds from Around the Web:
Who’s hiring?
On Tue, Apr 7, 2020 at 10:30 AM Swarna Podila < spodila@...> wrote: Hi all, Chris is on PTO this week; so here's this edition of bi-weekly roundup from me.
Hope you’re safe, sane, and comfortable out there. Some exciting new changes at the Cloud Foundry Foundation, just announced: https://www.cloudfoundry.org/blog/cloud-foundry-foundations-cto-steps-into-executive-director-role: Abby Kearns is moving on from the Foundation. Chip Childers has been appointed the new Executive Director. While we’re going to miss Abby tremendously, we are very grateful to have had such tremendous leadership here at the CFF for the past few years, and also that we are fortunate enough to be left in Chip’s capable hands going forward. Read Chip’s post here and Abby’s post here. Join a community AMA tomorrow, Thursday, April 9th, from 8-10 AM PST on Cloud Foundry Slack in the #cff-forum channel to discuss this transition.
From the Last Few Weeks:Chip Childers is now the Executive Director of Cloud Foundry Foundation. Paul Fazzone has been named new chairman of the CFF Board. We’re launching a new tutorials website! Content creation is happening now, and we’d love your input, contributions, and feedback!. Please reach out in the #cloudfoundry-tutorials slack channel if you’d like to get involved. Official launch is scheduled for a few weeks from now. The Release Integration team is requesting review for cf-deployment V13 scope. Google steps up to Platinum membership in the CFF! Read more here. Nice blog post here on Project Quarks and KubeCF. The BOSH PMC is making a few changes outlined here, most notably moving the BOSH project to a distributed committer model. Cloud Foundry Volume Services team has shipped the first alpha version of their SMB volume service. CF for Kubernetes SIG call video from March 31 is up. Video here.
Community Updates:Have a question for the staff at Cloud Foundry Foundation? Want to stay current with updates for the Foundation? Join the new #cff-forum channel on the community Slack. Do you miss the water cooler conversations? Hop on to the Cloud Foundry Break Room if you would like to hang out with your peers from the community. Please note that the Cloud Foundry Code of Conduct applies here as well.
All things Cloud Foundry Summit:Dates To Remember (All times US Pacific):CF for Kubernetes SIG call - 8:30 AM on April 14 Bi-Weekly CF App Runtime PMC meeting - 10:30 AM on April 14 CAB call - 8:00 AM on April 15
Interesting Finds from Around the Web:
-- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more.
On Tue, Mar 24, 2020 at 12:27 PM Chris Clark < cclark@...> wrote: It is an understatement when we say “these are unprecedented times.” During these times of uncertainty, the Cloud Foundry Foundation wants to offer an open zoom “break room” for our community. Please feel free to “walk” into this break room and hang out with others. (Please do remember: Code of conduct applies here as well.)
From the Last Few Weeks:
- KubeCF released v1.0 AND v1.0.1! Message here. Blog post here. Press release here.
- Stratos released v3.0! Message here.
- CF routing v0.199.0 was released. Message here.
- Miguel Luna has taken over as project lead of the Services API project.
- CF for Kubernetes SIG call video from March 17 is up. Focus on container to container networking. Video here.
- CF CAB call video from March 18 is up here. Nice update and demo of CF-for-k8s!
Community Updates:
- Have a question for the staff at Cloud Foundry Foundation? Want to stay current with updates for the Foundation? Join the new #cff-forum channel on the community Slack.
All things Cloud Foundry Summit:
Dates To Remember (All times US Pacific):
- CF Operators Sig Meeting – 8:00 AM on March 25
- CF for Kubernetes SIG call – 8:30 AM on March 31
- Bi-Weekly CF App Runtime PMC meeting – 10:30 AM on March 31
Interesting Finds from Around the Web:
Who’s hiring?
Looking for an industry event to attend or to submit a speaking proposal? We put together a helpful calendar of events for 2020: https://calendar.google.com/calendar?cid=Y2xvdWRmb3VuZHJ5Lm9yZ181Yjg2a2dobzkwdmNqOWtncDE3cjljYjh1c0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
-- Chris Clark Technical Operations Manager Cloud Foundry Foundation
|
|
|
Hi folks,
Thanks Zach for starting this thread. There's been some good conversation in the document about different reasons and benefits of using CRDs.
Connor (cc'ed) and I have been exploring what introducing CRDs to Cloud Foundry might look like centered around the different outcomes described in the doc. We've generated this document (titled "CF App Runtime CRD Approaches") and would love to have feedback and a discussion via comments.
Cheers, Angela and Connor
On Tue, Apr 28, 2020 at 10:16 AM Zach Robinson < zrobinson@...> wrote: Hey all,
As we move towards a kubernetes-based Cloud Foundry, the inclusion of CRDs into CF has been a recurring topic. At this point we already see CRDs being incorporated into CF in a number of ways, as well as questions about them such as a thread on this list titled "Is anyone working on a CF CRD & Controller?".
We would like to use this space to start gathering an understanding of how folks are using CRDs, the reasons folks are using CRDs, and what CRDs folks would like to see in the future.
This will help us build a better understanding as a community towards the outcomes of
- Include CRDs in CF with well-defined architectural patterns
- Understand how CRDs should be exposed as a user interface
This document has been created to help house the discussion asynchronously. It has been built with the understanding of cf contributors from a couple of teams, but we need everybody's help to flesh out the full picture.
Looking forward to discussion
|
|
|
Re: Is anyone working on a CF CRD & Controller?
Hi folks,
Connor (cc'ed) and I have been exploring what introducing CRDs to Cloud Foundry might look like centered around the different outcomes that were generated. We've generated this document (titled "CF App Runtime CRD Approaches") and would love to have feedback and a discussion via comments.
Cheers, Angela and Connor
On Sat, May 2, 2020 at 9:48 AM pierre Oblin < oblinp@...> wrote: Just as inspiration, and maybe spike implémentation, a déclarative approach based on terraform HCL is probably a good way to start
Le mar. 28 avr. 2020 à 19:18, Zach Robinson < zrobinson@...> a écrit : Hey Daniel,
Shared with the mailing list under topic "Exploring CRDs in CF". Would love to get your thoughts and feedback.
-Zach
On Thu, Apr 16, 2020 at 4:09 PM Zach Robinson < zrobinson@...> wrote: Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
Yes, this is the current approach for the CRDs that Cloud Controller interacts with now. There are also reconciliation loops that we run for these resources analogous to how we've always reconciled CCDB state with Diego.
I think this method has developed organically from our goal of preserving in-place workflows via having the same API surface, allowing cli to function without changes, while trying to consume existing functionality in k8s. I think the longer term goal here is to review that usage and be more intentional about how we expect CRDs to fit into the system as a whole.
-Zach
Thanks for that folks - especially for such a long and detailed response, Zach. Much appreciated.
It's great that folks are already thinking about this.
Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
I'd kinda imagined things going the other way around, introducing the CRDs as a new user interface, and have the controllers do the diff and then post/put to CloudController. The intention here would be saving Kubes-native folks (and CI servers!) from having to deal with the imperative interface. I was working on the assumption that all CF concepts would be exposed as CRDs.
From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well.
I'd always dodged this area in cf-converger as it was the most complicated, and the biggest break from the current CF experience :)
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I can imagine that the logical concept of orgs may one day map onto distinct Kubernetes namespaces, but I hadn't imagined that orgs would in any way disappear, or not be configurable via the Kubernetes approach.
It'd be great to hear what others think on all of this.
Thanks again for sharing, Keshav and Zach. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
On Wed, 15 Apr 2020 at 23:45, Zach Robinson < zrobinson@...> wrote: Hey Daniel,
Thanks for starting a convo. The timing couldn't be better. I can share some of the thinking going on in both CAPI and VMware land.
But first and foremost I want to address the question: "Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort?" - yes, yes, a thousand times yes to community collaboration!
The topic of CRDs is kind of huge. It's really great to hear your focus is on things like orgs/spaces. From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well. There's a lot of ground to cover clearly.
In terms of things that are in flight now. - Keshav kindly shared that networking is looking to provide Route CRDs.
- Networking is also exploring providing Security Groups as CRDs.
- CAPI is integrating kpack into CF to provide buildpack staging. This is done by generating kpack CRDs.
Currently these CRDs are being created and owned by the Cloud Controller, which enables us to present backward compatible APIs to our CLI and UI like stratos, while moving the implementation down into controllers fronted by CRDs. There's an obvious potential to interact with k8s directly in the future, but the current use case is to be used by CC. Except for kpack which is an excellent stand alone tool already :).
These efforts are great and are allowing us to begin a path towards using existing k8s tooling and projects to provide Cloud Foundry outcomes, but obviously there's a lot further to go.
From VMware's side, over the last couple weeks, there has been an effort to explore what it might look like to use CRDs entirely as a source of truth for *all* CF data, in place of a SQL database, as a learning exercise, not necessarily a desired outcome. The primary goal of that effort was to start the convo that we're having now, and to be able to contribute in a meaningful way. Note there are no VMware-based plans to dump a fully fledged proposal. We need to start from a premise as a community of understanding how/why/and which resources are valuable as CRDs.
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I think we'll need to start some dedicated working document to collaborate in. I had planned on facilitating that after some of the investigation that VMware has wraps up, but I don't think that's a reason to hold off if you or somebody else in the community has thoughts they want to start getting down. CAPI and other teams can contribute to an existing doc if that makes sense. Any other thoughts you'd prefer for next steps?
Looking forward to a continued conversation.
-Zach
On Wed, Apr 15, 2020 at 9:56 AM Keshav Sharma < ksharma@...> wrote: Hi Daniel,
The CF-K8s Networking team is currently working on a solution using Route CRD- to introduce a “Route” custom resource and have Cloud Controller make/update these directly as part of the `cf map-route` and `cf unmap-route` workflows.
Happy to discuss this further in our Cloud-Foundry Slack- #networking group.
Regards,
Keshav Sharma
Product Manager | CF-K8s-Networking
VMware
Hi all,
In the spirit of community, I'm going to ask this question outright and in the open - is anyone (*looks at VMware MAPBU*) working on a CRD and accompanying controller for CF on Kubernetes?
Anyone with a non-trivial amount of Cloud Foundry experience knows that whilst the imperative interface of the CF CLI is great for exploratory work, it's far from ideal for production environments. I make a point of telling folks in CF training courses that no human should be using the CLI in production, other than for debugging.
A declarative interface for CF has always been desirable, and its omission is going to become even more stark once running CF on Kubernetes is the norm. We've had cf-mgmt which is close, but involves more steps than is ideal.
It'd be great to have one or more CRDs that represent the state of a Cloud Foundry, and accompanying controllers that converge upon that state. When I talk about state, I mean things like orgs, spaces, service broker registrations, service instances, roles and so on.
Four years ago I started work on a project called cf-converger to diff and converge a Cloud Foundry instance on a state declared in YAML. I got distracted with running a business and doing billable work, so whilst the concept was proven, it never really got to a state of usefulness. Plus, I seemed to spend half my coding time just writing excessively-verbose chained method calls on the official Java CF client :D
I see such a solution as an inevitability in the Kubernetes-based future. Whilst I'm personally tempted to resurrect the project, it makes very little sense for a company like EngineerBetter to divert resources from billable work to a project that is needed, but can't be monetised.
Are any of the big players working on something similar? Is it something we should all be thinking and talking about? Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort? Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
|
|
|
cf-for-k8s 0.2.0 alpha release
Hello CF community,
We just shipped cf-for-k8s 0.2.0 alpha release, so please check out the release notes here. Some notable highlights of this release,
- Users can now see streaming logs during cf push command. woot! - Users can now see app metrics. - Removed install.sh so users have the freedom to use ytt and kapp however they like (e.g. pass additional config of their choice)
There are many other updates worth looking into. Please take it for a spin and give us your feedback via issues or in slack channel #cf-for-k8s.
Thank you to all the contributors!!
Resources:
--
|
|
|
IMPORTANT NOTICE: [nodejs-buildpack] End of Support for Node.js versions 13.x after 2020-06-04
The first release of the Node.js buildpack after 2020-06-04 will no longer include Node.js versions 13.x. These Node.js versions will no longer be supported upstream.[1] Please migrate your Node.js apps to supported versions of Node.js before that time.
As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[2].
[1] - https://github.com/nodejs/Release [2] - https://cloudfoundry.slack.com/archives/C02HWMDUQ
Thanks, Kashyap Vedurmudi, Buildpacks PM
|
|
|
Re: Deployment of HDI in US10 fails
Jonathan Matthews <contact+cfdev@...>
Hi Vidhya,
I’m afraid I’ve never heard of most of these terms in Cloud Foundry context!
After a bit of googling, assuming they’re terms as they’re being used here (
J
Hi,
We are trying to deploy HDI mta to US10 and we encounter the below issue.
The service created for hdi has parameters defined for schema and databaseid.
The same mta was deployed on EU10 successfully.
Caused by: org.cloudfoundry.client.v2.ClientV2Exception: CF-ServiceFetchInstanceParametersNotSupported(120004): This service does not support fetching service
instance parameters.
at org.cloudfoundry.reactor.util.ErrorPayloadMappers.lambda$null$0(ErrorPayloadMappers.java:47)
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Assembly trace from producer [reactor.core.publisher.MonoFlatMap] :
reactor.core.publisher.Mono.checkpoint(Mono.java:1863)
org.cloudfoundry.reactor.client.v2.serviceinstances.ReactorServiceInstances.getParameters(ReactorServiceInstances.java:94)
Error has been observed at the following site(s):
|_ Mono.checkpoint ? at org.cloudfoundry.reactor.client.v2.serviceinstances.ReactorServiceInstances.getParameters(ReactorServiceInstances.java:94)
Stack trace:
at org.cloudfoundry.reactor.util.ErrorPayloadMappers.lambda$null$0(ErrorPayloadMappers.java:47)
Could you please help us troubleshoot the issue.
Thank You
Regards
Vidhya
|
|
|
Deployment of HDI in US10 fails
A N, Sri Vidhya <sri.vidhya.a.n@...>
Hi,
We are trying to deploy HDI mta to US10 and we encounter the below issue.
The service created for hdi has parameters defined for schema and databaseid.
The same mta was deployed on EU10 successfully.
Caused by: org.cloudfoundry.client.v2.ClientV2Exception: CF-ServiceFetchInstanceParametersNotSupported(120004): This service does not support fetching service
instance parameters.
at org.cloudfoundry.reactor.util.ErrorPayloadMappers.lambda$null$0(ErrorPayloadMappers.java:47)
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Assembly trace from producer [reactor.core.publisher.MonoFlatMap] :
reactor.core.publisher.Mono.checkpoint(Mono.java:1863)
org.cloudfoundry.reactor.client.v2.serviceinstances.ReactorServiceInstances.getParameters(ReactorServiceInstances.java:94)
Error has been observed at the following site(s):
|_ Mono.checkpoint ? at org.cloudfoundry.reactor.client.v2.serviceinstances.ReactorServiceInstances.getParameters(ReactorServiceInstances.java:94)
Stack trace:
at org.cloudfoundry.reactor.util.ErrorPayloadMappers.lambda$null$0(ErrorPayloadMappers.java:47)
Could you please help us troubleshoot the issue.
Thank You
Regards
Vidhya
|
|
|
Re: Removing bits-service from cf-deployment
Hi,
I don’t think that using bits-service with the mentioned ops files will work. In fact support for bits-service is broken since cf-deployment v12.39 (incl. CAPI v1.92, more precisely commit
https://github.com/cloudfoundry/cloud_controller_ng/commit/66fb2bd434656e8caa060ff55e6c87a296ab1455 that adds a new method which is not implemented in the Ruby BitsService::Client class). Is our observation correct or are we doing something wrong when setting
up a current version of cf-d with bits-service?
Thanks,
Philipp
|
|
|
Re: Is anyone working on a CF CRD & Controller?
Just as inspiration, and maybe spike implémentation, a déclarative approach based on terraform HCL is probably a good way to start
Le mar. 28 avr. 2020 à 19:18, Zach Robinson < zrobinson@...> a écrit : Hey Daniel,
Shared with the mailing list under topic "Exploring CRDs in CF". Would love to get your thoughts and feedback.
-Zach
On Thu, Apr 16, 2020 at 4:09 PM Zach Robinson < zrobinson@...> wrote: Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
Yes, this is the current approach for the CRDs that Cloud Controller interacts with now. There are also reconciliation loops that we run for these resources analogous to how we've always reconciled CCDB state with Diego.
I think this method has developed organically from our goal of preserving in-place workflows via having the same API surface, allowing cli to function without changes, while trying to consume existing functionality in k8s. I think the longer term goal here is to review that usage and be more intentional about how we expect CRDs to fit into the system as a whole.
-Zach
Thanks for that folks - especially for such a long and detailed response, Zach. Much appreciated.
It's great that folks are already thinking about this.
Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
I'd kinda imagined things going the other way around, introducing the CRDs as a new user interface, and have the controllers do the diff and then post/put to CloudController. The intention here would be saving Kubes-native folks (and CI servers!) from having to deal with the imperative interface. I was working on the assumption that all CF concepts would be exposed as CRDs.
From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well.
I'd always dodged this area in cf-converger as it was the most complicated, and the biggest break from the current CF experience :)
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I can imagine that the logical concept of orgs may one day map onto distinct Kubernetes namespaces, but I hadn't imagined that orgs would in any way disappear, or not be configurable via the Kubernetes approach.
It'd be great to hear what others think on all of this.
Thanks again for sharing, Keshav and Zach. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
On Wed, 15 Apr 2020 at 23:45, Zach Robinson < zrobinson@...> wrote: Hey Daniel,
Thanks for starting a convo. The timing couldn't be better. I can share some of the thinking going on in both CAPI and VMware land.
But first and foremost I want to address the question: "Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort?" - yes, yes, a thousand times yes to community collaboration!
The topic of CRDs is kind of huge. It's really great to hear your focus is on things like orgs/spaces. From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well. There's a lot of ground to cover clearly.
In terms of things that are in flight now. - Keshav kindly shared that networking is looking to provide Route CRDs.
- Networking is also exploring providing Security Groups as CRDs.
- CAPI is integrating kpack into CF to provide buildpack staging. This is done by generating kpack CRDs.
Currently these CRDs are being created and owned by the Cloud Controller, which enables us to present backward compatible APIs to our CLI and UI like stratos, while moving the implementation down into controllers fronted by CRDs. There's an obvious potential to interact with k8s directly in the future, but the current use case is to be used by CC. Except for kpack which is an excellent stand alone tool already :).
These efforts are great and are allowing us to begin a path towards using existing k8s tooling and projects to provide Cloud Foundry outcomes, but obviously there's a lot further to go.
From VMware's side, over the last couple weeks, there has been an effort to explore what it might look like to use CRDs entirely as a source of truth for *all* CF data, in place of a SQL database, as a learning exercise, not necessarily a desired outcome. The primary goal of that effort was to start the convo that we're having now, and to be able to contribute in a meaningful way. Note there are no VMware-based plans to dump a fully fledged proposal. We need to start from a premise as a community of understanding how/why/and which resources are valuable as CRDs.
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I think we'll need to start some dedicated working document to collaborate in. I had planned on facilitating that after some of the investigation that VMware has wraps up, but I don't think that's a reason to hold off if you or somebody else in the community has thoughts they want to start getting down. CAPI and other teams can contribute to an existing doc if that makes sense. Any other thoughts you'd prefer for next steps?
Looking forward to a continued conversation.
-Zach
On Wed, Apr 15, 2020 at 9:56 AM Keshav Sharma < ksharma@...> wrote: Hi Daniel,
The CF-K8s Networking team is currently working on a solution using Route CRD- to introduce a “Route” custom resource and have Cloud Controller make/update these directly as part of the `cf map-route` and `cf unmap-route` workflows.
Happy to discuss this further in our Cloud-Foundry Slack- #networking group.
Regards,
Keshav Sharma
Product Manager | CF-K8s-Networking
VMware
Hi all,
In the spirit of community, I'm going to ask this question outright and in the open - is anyone (*looks at VMware MAPBU*) working on a CRD and accompanying controller for CF on Kubernetes?
Anyone with a non-trivial amount of Cloud Foundry experience knows that whilst the imperative interface of the CF CLI is great for exploratory work, it's far from ideal for production environments. I make a point of telling folks in CF training courses that no human should be using the CLI in production, other than for debugging.
A declarative interface for CF has always been desirable, and its omission is going to become even more stark once running CF on Kubernetes is the norm. We've had cf-mgmt which is close, but involves more steps than is ideal.
It'd be great to have one or more CRDs that represent the state of a Cloud Foundry, and accompanying controllers that converge upon that state. When I talk about state, I mean things like orgs, spaces, service broker registrations, service instances, roles and so on.
Four years ago I started work on a project called cf-converger to diff and converge a Cloud Foundry instance on a state declared in YAML. I got distracted with running a business and doing billable work, so whilst the concept was proven, it never really got to a state of usefulness. Plus, I seemed to spend half my coding time just writing excessively-verbose chained method calls on the official Java CF client :D
I see such a solution as an inevitability in the Kubernetes-based future. Whilst I'm personally tempted to resurrect the project, it makes very little sense for a company like EngineerBetter to divert resources from billable work to a project that is needed, but can't be monetised.
Are any of the big players working on something similar? Is it something we should all be thinking and talking about? Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort? Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
|
|
|
Release Integration No Longer Testing CATs on BOSH Lite
Dave Walter <dwalter@...>
Hi All,
The CF Release Integration team wanted to give y'all a heads up that we have decided to stop running CATs on our BOSH lite CI environment due to its flakey nature and the time wasted debugging.
Going forward, we are only validating new changes on BOSH lite by running smoke-tests. Please feel free to reach out if you have any questions.
|
|
|
Re: Is anyone working on a CF CRD & Controller?
On the Quarks team we’ve been working with CRDs for some time and we’d like to socialize with other teams doing similar work.
Maybe we could setup a slack channel specific to this?
Cheers,
Vlad
toggle quoted message
Show quoted text
From: Daniel Jones
Sent: Friday, May 1, 2020 1:31 PM
To: Discussions about Cloud Foundry projects and the system overall.
Subject: Re: [cf-dev] Is anyone working on a CF CRD & Controller?
Ta! I've been on full-time billable work with customers all week, but I'll take a look now.
Regards,
Daniel 'Deejay' Jones - CEO
On Tue, 28 Apr 2020 at 18:17, Zach Robinson <zrobinson@...> wrote:
Hey Daniel,
Shared with the mailing list under topic "Exploring CRDs in CF". Would love to get your thoughts and feedback.
On Thu, Apr 16, 2020 at 4:09 PM Zach Robinson <zrobinson@...> wrote:
Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
Yes, this is the current approach for the CRDs that Cloud Controller interacts with now. There are also reconciliation loops that we run for these resources analogous to how we've always reconciled CCDB state with Diego.
I think this method has developed organically from our goal of preserving in-place workflows via having the same API surface, allowing cli to function without changes, while trying to consume existing functionality in k8s. I think the longer
term goal here is to review that usage and be more intentional about how we expect CRDs to fit into the system as a whole.
Thanks for that folks - especially for such a long and detailed response, Zach. Much appreciated.
It's great that folks are already thinking about this.
Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
I'd kinda imagined things going the other way around, introducing the CRDs as a new user interface, and have the controllers do the diff and then post/put to CloudController. The intention here would be saving Kubes-native folks (and CI
servers!) from having to deal with the imperative interface. I was working on the assumption that
all CF concepts would be exposed as CRDs.
From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well.
I'd always dodged this area in cf-converger as it was the most complicated, and the biggest break from the current CF experience :)
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I can imagine that the logical concept of orgs may one day map onto distinct Kubernetes namespaces, but I hadn't imagined that orgs would in any way disappear, or not be configurable via the Kubernetes approach.
It'd be great to hear what others think on all of this.
Thanks again for sharing, Keshav and Zach.
Regards,
Daniel 'Deejay' Jones - CEO
On Wed, 15 Apr 2020 at 23:45, Zach Robinson <zrobinson@...> wrote:
Hey Daniel,
Thanks for starting a convo. The timing couldn't be better. I can share some of the thinking going on in both CAPI and VMware land.
But first and foremost I want to address the question: "Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any
community effort?" - yes, yes, a thousand times yes to community collaboration!
The topic of CRDs is kind of huge. It's really great to hear your focus is on things like orgs/spaces. From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts
in this area as well. There's a lot of ground to cover clearly.
In terms of things that are in flight now.
-
Keshav kindly shared that networking is looking to provide Route CRDs.
-
Networking is also exploring providing Security Groups as CRDs.
-
CAPI is integrating kpack into CF to provide buildpack staging. This is done by generating kpack CRDs.
Currently these CRDs are being created and owned by the Cloud Controller, which enables us to present backward compatible APIs to our CLI and UI like stratos, while moving the implementation down into controllers fronted by CRDs. There's
an obvious potential to interact with k8s directly in the future, but the current use case is to be used by CC. Except for kpack which is an excellent stand alone tool already :).
These efforts are great and are allowing us to begin a path towards using existing k8s tooling and projects to provide Cloud Foundry outcomes, but obviously there's a lot further to go.
From VMware's side, over the last couple weeks, there has been an effort to explore what it might look like to use CRDs entirely as a source of truth for *all* CF data, in place of a SQL database, as a learning exercise, not necessarily
a desired outcome. The primary goal of that effort was to start the convo that we're having now, and to be able to contribute in a meaningful way. Note there are no VMware-based plans to dump a fully fledged proposal. We need to start from a premise as a
community of understanding how/why/and which resources are valuable as CRDs.
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I think we'll need to start some dedicated working document to collaborate in. I had planned on facilitating that after some of the investigation that VMware has wraps up, but I don't think that's a reason to hold off if you or somebody
else in the community has thoughts they want to start getting down. CAPI and other teams can contribute to an existing doc if that makes sense. Any other thoughts you'd prefer for next steps?
Looking forward to a continued conversation.
On Wed, Apr 15, 2020 at 9:56 AM Keshav Sharma <ksharma@...> wrote:
Hi Daniel,
The CF-K8s Networking team is currently working on
a solution using Route CRD- to introduce a “Route” custom resource and have Cloud Controller make/update these directly as part of the `cf map-route` and `cf unmap-route` workflows. Happy to
discuss this further in our Cloud-Foundry Slack-
#networking group. Regards, Keshav Sharma Product Manager | CF-K8s-Networking VMware
Hi all,
In the spirit of community, I'm going to ask this question outright and in the open - is anyone (*looks at VMware MAPBU*) working on a CRD and accompanying controller for CF on Kubernetes?
Anyone with a non-trivial amount of Cloud Foundry experience knows that whilst the imperative interface of the CF CLI is great for exploratory work, it's far from ideal for production environments. I make a point of telling folks in CF
training courses that no human should be using the CLI in production, other than for debugging.
A declarative interface for CF has always been desirable, and its omission is going to become even more stark once running CF on Kubernetes is the norm. We've had
cf-mgmt which is close, but involves more steps than is ideal.
It'd be great to have one or more CRDs that represent the state of a Cloud Foundry, and accompanying controllers that converge upon that state. When I talk about state, I mean things like orgs, spaces, service broker registrations,
service instances, roles and so on.
Four years ago I started work on
a project called cf-converger to diff and converge a Cloud Foundry instance on a state declared in YAML. I got distracted with running a business and doing billable work, so whilst the concept was proven, it never really got to a state of usefulness. Plus,
I seemed to spend half my coding time just writing excessively-verbose chained method calls on the official Java CF client :D
I see such a solution as an inevitability in the Kubernetes-based future. Whilst I'm personally tempted to resurrect the project, it makes very little sense for a company like EngineerBetter to divert resources from billable work
to a project that is needed, but can't be monetised.
Are any of the big players working on something similar? Is it something we should all be
thinking and talking about? Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort?
Regards,
Daniel 'Deejay' Jones - CEO
|
|
|
Re: Stepping down as CF Extension PMC lead and a small TBT present
Thanks Max - it brought a smile to my face to go over those photos and see all the friends I've had the opportunity to make in the ecosystem, and remember the fun times at conferences. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
Hi Dr. Max,
Sad to see you stepping down as Extensions PMC lead. Thank you very much for all you have done for the CF community!
I’m hopeful that one day in the (hopefully not too distant) future we’ll again bump into each other at one of the great open source conferences somewhere in the world so that we can hang out together.
All the best,
Bernd
Bernd Krannich
SAP Cloud Platform
SAP SE
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
E bernd.krannich@...
Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten
haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby
notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
Your presence is invaluable to our community. I can only name a few hats you wore over the years, but all the roles you've taken on helped us immensely in shaping our community!
-
hosting Community Call
-
leading the Extensions-PMC
-
supporting us immensely for Hackathons at Summit
-
advocating Cloud Foundry technology in our community and within the broader open source community
-
representing our community everywhere
-
being a true Cloud Foundry Ambassador!
-
capturing all the amazing memories and sharing the pictures with us
-
...and so many more.
Thank you so much for all your contributions and efforts. We genuinely and sincerely thank you.
-- Swarna Podila
(she/her)
Director
| Cloud Foundry Foundation
You can read more about pronouns here, or please ask if you'd like to find
out more.
Thanks Dr Max for everything you’ve done — and all the photos!
On Fri, 1 May 2020 at 8:33 am, Michael Maximilien <maxim@...> wrote:
Hi, all,
After four years (almost) at the helm of CF Extensions, I am announcing that I am stepping down as the lead. I believe the time is ripe as CF is transitioning to new waters and since I am less involved with the projects these days, it's time for someone else
to take over and steer us to greener pastures.
I took on the CF Extensions lead role when none existed at the end of 2016. I remember, like yesterday, when Sam asked me to start an Extensions PMC for Cloud Foundry during our summit in Frankfurt. Since then, we have added close to 20 extensions projects
with many having graduated and a few fading away. Exactly what we envisioned, so for that I am happy and thankful to your participation and contributions.
Overall, I feel positive and hopeful that better days are ahead for CF and this community. You have a vibrant group of contributors and excellent committed leadership in the Cloud Foundry Foundation. I will miss the kindness, brersity, and excellence that this
community has always strived to achieve and uphold.
That said, I will not be far away. I am still involved in OSS for IBM and will be happy to help in any way I can, when you need me. Swarna will be sending a separate email to look for volunteers and elect a leader.
-----
With that, my little TBT present to you are the following curated photographs I have taken of you during our time together at the many CF Summits, CF days, and events all across the world.
From some of the first CF Summit NA: Santa Clara in
2015-16-17; to CF Summit Asia in Shanghai 2016; to CF Days: Pune, India 2016, Misk, Belarus 2016, London 2018, NY 2018, and Copenhagen 2018; to CF Summit Europe: Frankfurt 2016, Basel 2017-2018, Den Haag 2019; and most recently CF Summit NA: Boston 2018 and
Philadelphia 2019.
You've often seen me with a camera in hand shooting away. So here's the main reason, to allow us to remember, to look back, and to reminisce a bit on the great memories, fun times, and lasting friendships we have forged in this community. With that, here are
two curated sets of what I believe are my most memorable and best 150 photographs of Cloud Foundry community events and members. Hope you like:
50 B&W:
https://photos.app.goo.gl/JUHVSRCKc9SrvuZD8
100 Color:
https://photos.app.goo.gl/mAarRq8QvAWm8Mki6
PS: While I took care to select the best photos, I can fully understand if there is a photo of you, or that you are in a photo, that you do not like or rather I not share. Please let me know and I will remove ASAP.
Also, to respect the privacy of all, I ask you to get permissions before re-sharing, of course, if the photograph includes someone other than yourself. In my experience most people agree, so just ask.
--
--
You received this message because you are subscribed to the Google Groups "cf-extensions-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cf-extensions-pmc+unsubscribe@....
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/cf-extensions-pmc/CAM-_pPbYBdugvoaq4achwtKb_Pbb2_X0wFjy6Hsm8rtVfb9Gjg%40mail.gmail.com.
|
|
|
Re: Is anyone working on a CF CRD & Controller?
Ta! I've been on full-time billable work with customers all week, but I'll take a look now. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
On Tue, 28 Apr 2020 at 18:17, Zach Robinson < zrobinson@...> wrote: Hey Daniel,
Shared with the mailing list under topic "Exploring CRDs in CF". Would love to get your thoughts and feedback.
-Zach
On Thu, Apr 16, 2020 at 4:09 PM Zach Robinson < zrobinson@...> wrote: Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
Yes, this is the current approach for the CRDs that Cloud Controller interacts with now. There are also reconciliation loops that we run for these resources analogous to how we've always reconciled CCDB state with Diego.
I think this method has developed organically from our goal of preserving in-place workflows via having the same API surface, allowing cli to function without changes, while trying to consume existing functionality in k8s. I think the longer term goal here is to review that usage and be more intentional about how we expect CRDs to fit into the system as a whole.
-Zach
Thanks for that folks - especially for such a long and detailed response, Zach. Much appreciated.
It's great that folks are already thinking about this.
Zach, am I correct in thinking that the current approach is the have clients interact with CloudController, have CloudController persist to CCDB as per usual, and then CloudController post stuff to CRDs in the Kube API?
I'd kinda imagined things going the other way around, introducing the CRDs as a new user interface, and have the controllers do the diff and then post/put to CloudController. The intention here would be saving Kubes-native folks (and CI servers!) from having to deal with the imperative interface. I was working on the assumption that all CF concepts would be exposed as CRDs.
From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well.
I'd always dodged this area in cf-converger as it was the most complicated, and the biggest break from the current CF experience :)
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I can imagine that the logical concept of orgs may one day map onto distinct Kubernetes namespaces, but I hadn't imagined that orgs would in any way disappear, or not be configurable via the Kubernetes approach.
It'd be great to hear what others think on all of this.
Thanks again for sharing, Keshav and Zach. Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
On Wed, 15 Apr 2020 at 23:45, Zach Robinson < zrobinson@...> wrote: Hey Daniel,
Thanks for starting a convo. The timing couldn't be better. I can share some of the thinking going on in both CAPI and VMware land.
But first and foremost I want to address the question: "Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort?" - yes, yes, a thousand times yes to community collaboration!
The topic of CRDs is kind of huge. It's really great to hear your focus is on things like orgs/spaces. From a CAPI perspective, I've been thinking more about representing apps and push as CRDs, and I believe the Eirini team has some thoughts in this area as well. There's a lot of ground to cover clearly.
In terms of things that are in flight now. - Keshav kindly shared that networking is looking to provide Route CRDs.
- Networking is also exploring providing Security Groups as CRDs.
- CAPI is integrating kpack into CF to provide buildpack staging. This is done by generating kpack CRDs.
Currently these CRDs are being created and owned by the Cloud Controller, which enables us to present backward compatible APIs to our CLI and UI like stratos, while moving the implementation down into controllers fronted by CRDs. There's an obvious potential to interact with k8s directly in the future, but the current use case is to be used by CC. Except for kpack which is an excellent stand alone tool already :).
These efforts are great and are allowing us to begin a path towards using existing k8s tooling and projects to provide Cloud Foundry outcomes, but obviously there's a lot further to go.
From VMware's side, over the last couple weeks, there has been an effort to explore what it might look like to use CRDs entirely as a source of truth for *all* CF data, in place of a SQL database, as a learning exercise, not necessarily a desired outcome. The primary goal of that effort was to start the convo that we're having now, and to be able to contribute in a meaningful way. Note there are no VMware-based plans to dump a fully fledged proposal. We need to start from a premise as a community of understanding how/why/and which resources are valuable as CRDs.
For example when we look at orgs/spaces - we have to wonder if those are even resources we want to represent as CRDs, when k8s already has a namespace construct.
I think we'll need to start some dedicated working document to collaborate in. I had planned on facilitating that after some of the investigation that VMware has wraps up, but I don't think that's a reason to hold off if you or somebody else in the community has thoughts they want to start getting down. CAPI and other teams can contribute to an existing doc if that makes sense. Any other thoughts you'd prefer for next steps?
Looking forward to a continued conversation.
-Zach
On Wed, Apr 15, 2020 at 9:56 AM Keshav Sharma < ksharma@...> wrote: Hi Daniel,
The CF-K8s Networking team is currently working on a solution using Route CRD- to introduce a “Route” custom resource and have Cloud Controller make/update these directly as part of the `cf map-route` and `cf unmap-route` workflows.
Happy to discuss this further in our Cloud-Foundry Slack- #networking group.
Regards,
Keshav Sharma
Product Manager | CF-K8s-Networking
VMware
Hi all,
In the spirit of community, I'm going to ask this question outright and in the open - is anyone (*looks at VMware MAPBU*) working on a CRD and accompanying controller for CF on Kubernetes?
Anyone with a non-trivial amount of Cloud Foundry experience knows that whilst the imperative interface of the CF CLI is great for exploratory work, it's far from ideal for production environments. I make a point of telling folks in CF training courses that no human should be using the CLI in production, other than for debugging.
A declarative interface for CF has always been desirable, and its omission is going to become even more stark once running CF on Kubernetes is the norm. We've had cf-mgmt which is close, but involves more steps than is ideal.
It'd be great to have one or more CRDs that represent the state of a Cloud Foundry, and accompanying controllers that converge upon that state. When I talk about state, I mean things like orgs, spaces, service broker registrations, service instances, roles and so on.
Four years ago I started work on a project called cf-converger to diff and converge a Cloud Foundry instance on a state declared in YAML. I got distracted with running a business and doing billable work, so whilst the concept was proven, it never really got to a state of usefulness. Plus, I seemed to spend half my coding time just writing excessively-verbose chained method calls on the official Java CF client :D
I see such a solution as an inevitability in the Kubernetes-based future. Whilst I'm personally tempted to resurrect the project, it makes very little sense for a company like EngineerBetter to divert resources from billable work to a project that is needed, but can't be monetised.
Are any of the big players working on something similar? Is it something we should all be thinking and talking about? Is there any point in the community working on such a solution, or are one of the bigger companies secretly working on something that would supersede any community effort? Regards, Daniel 'Deejay' Jones - CEO +44 (0)79 8000 9153
|
|
|
Re: Stepping down as CF Extension PMC lead and a small TBT present
Hi Dr. Max,
Sad to see you stepping down as Extensions PMC lead. Thank you very much for all you have done for the CF community!
I’m hopeful that one day in the (hopefully not too distant) future we’ll again bump into each other at one of the great open source conferences somewhere in the world so that we can hang out together.
All the best,
Bernd
Bernd Krannich
SAP Cloud Platform
SAP SE
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
E bernd.krannich@...
Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten
haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby
notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
From: <cf-dev@...> on behalf of Swarna Podila <spodila@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, 1. May 2020 at 01:16
To: Dr Nic Williams <drnicwilliams@...>
Cc: CF Developers Mailing List <cf-dev@...>, cf-extensions-pmc <cf-extensions-pmc@...>
Subject: Re: [cf-dev] Stepping down as CF Extension PMC lead and a small TBT present
Your presence is invaluable to our community. I can only name a few hats you wore over the years, but all the roles you've taken on helped us immensely in shaping our community!
-
hosting Community Call
-
leading the Extensions-PMC
-
supporting us immensely for Hackathons at Summit
-
advocating Cloud Foundry technology in our community and within the broader open source community
-
representing our community everywhere
-
being a true Cloud Foundry Ambassador!
-
capturing all the amazing memories and sharing the pictures with us
-
...and so many more.
Thank you so much for all your contributions and efforts. We genuinely and sincerely thank you.
-- Swarna Podila
(she/her)
Director
| Cloud Foundry Foundation
You can read more about pronouns here, or please ask if you'd like to find
out more.
toggle quoted message
Show quoted text
On Thu, Apr 30, 2020 at 3:47 PM Dr Nic Williams < drnicwilliams@...> wrote:
Thanks Dr Max for everything you’ve done — and all the photos!
On Fri, 1 May 2020 at 8:33 am, Michael Maximilien <maxim@...> wrote:
Hi, all,
After four years (almost) at the helm of CF Extensions, I am announcing that I am stepping down as the lead. I believe the time is ripe as CF is transitioning to new waters and since I am less involved with the projects these days, it's time for someone else
to take over and steer us to greener pastures.
I took on the CF Extensions lead role when none existed at the end of 2016. I remember, like yesterday, when Sam asked me to start an Extensions PMC for Cloud Foundry during our summit in Frankfurt. Since then, we have added close to 20 extensions projects
with many having graduated and a few fading away. Exactly what we envisioned, so for that I am happy and thankful to your participation and contributions.
Overall, I feel positive and hopeful that better days are ahead for CF and this community. You have a vibrant group of contributors and excellent committed leadership in the Cloud Foundry Foundation. I will miss the kindness, brersity, and excellence that this
community has always strived to achieve and uphold.
That said, I will not be far away. I am still involved in OSS for IBM and will be happy to help in any way I can, when you need me. Swarna will be sending a separate email to look for volunteers and elect a leader.
-----
With that, my little TBT present to you are the following curated photographs I have taken of you during our time together at the many CF Summits, CF days, and events all across the world.
From some of the first CF Summit NA: Santa Clara in
2015-16-17; to CF Summit Asia in Shanghai 2016; to CF Days: Pune, India 2016, Misk, Belarus 2016, London 2018, NY 2018, and Copenhagen 2018; to CF Summit Europe: Frankfurt 2016, Basel 2017-2018, Den Haag 2019; and most recently CF Summit NA: Boston 2018 and
Philadelphia 2019.
You've often seen me with a camera in hand shooting away. So here's the main reason, to allow us to remember, to look back, and to reminisce a bit on the great memories, fun times, and lasting friendships we have forged in this community. With that, here are
two curated sets of what I believe are my most memorable and best 150 photographs of Cloud Foundry community events and members. Hope you like:
50 B&W:
https://photos.app.goo.gl/JUHVSRCKc9SrvuZD8
100 Color:
https://photos.app.goo.gl/mAarRq8QvAWm8Mki6
PS: While I took care to select the best photos, I can fully understand if there is a photo of you, or that you are in a photo, that you do not like or rather I not share. Please let me know and I will remove ASAP.
Also, to respect the privacy of all, I ask you to get permissions before re-sharing, of course, if the photograph includes someone other than yourself. In my experience most people agree, so just ask.
--
--
You received this message because you are subscribed to the Google Groups "cf-extensions-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cf-extensions-pmc+unsubscribe@....
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/cf-extensions-pmc/CAM-_pPbYBdugvoaq4achwtKb_Pbb2_X0wFjy6Hsm8rtVfb9Gjg%40mail.gmail.com.
|
|
|
Seeking Nominations: Cloud Foundry Extensions PMC
Swarna Podila
Hi All, You may have seen Dr. Max's note earlier. After leading Extensions PMC for almost four years, he would like to step down and make space for new folks to take on the role.
Please send in your nominations for a new lead for Cloud Foundry Extensions PMC by the end of day next Friday, May 8, 2020.
-- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more.
|
|
|
Re: Stepping down as CF Extension PMC lead and a small TBT present
Swarna Podila
Hi Dr. Max,
Your presence is invaluable to our community. I can only name a few hats you wore over the years, but all the roles you've taken on helped us immensely in shaping our community! - hosting Community Call
- leading the Extensions-PMC
- supporting us immensely for Hackathons at Summit
- advocating Cloud Foundry technology in our community and within the broader open source community
- representing our community everywhere
- being a true Cloud Foundry Ambassador!
- capturing all the amazing memories and sharing the pictures with us
- ...and so many more.
Thank you so much for all your contributions and efforts. We genuinely and sincerely thank you.
-- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more.
Thanks Dr Max for everything you’ve done — and all the photos!
Dr Nic On Fri, 1 May 2020 at 8:33 am, Michael Maximilien < maxim@...> wrote:
Hi, all,
After four years (almost) at the helm of CF Extensions, I am announcing that I am stepping down as the lead. I believe the time is ripe as CF is transitioning to new waters and since I am less involved with the projects these days, it's time for someone else to take over and steer us to greener pastures.
I took on the CF Extensions lead role when none existed at the end of 2016. I remember, like yesterday, when Sam asked me to start an Extensions PMC for Cloud Foundry during our summit in Frankfurt. Since then, we have added close to 20 extensions projects with many having graduated and a few fading away. Exactly what we envisioned, so for that I am happy and thankful to your participation and contributions.
Overall, I feel positive and hopeful that better days are ahead for CF and this community. You have a vibrant group of contributors and excellent committed leadership in the Cloud Foundry Foundation. I will miss the kindness, brersity, and excellence that this community has always strived to achieve and uphold.
That said, I will not be far away. I am still involved in OSS for IBM and will be happy to help in any way I can, when you need me. Swarna will be sending a separate email to look for volunteers and elect a leader.
-----
With that, my little TBT present to you are the following curated photographs I have taken of you during our time together at the many CF Summits, CF days, and events all across the world.
From some of the first CF Summit NA: Santa Clara in
2015-16-17; to CF Summit Asia in Shanghai 2016; to CF Days: Pune, India 2016, Misk, Belarus 2016, London 2018, NY 2018, and Copenhagen 2018; to CF Summit Europe: Frankfurt 2016, Basel 2017-2018, Den Haag 2019; and most recently CF Summit NA: Boston 2018 and Philadelphia 2019.
You've often seen me with a camera in hand shooting away. So here's the main reason, to allow us to remember, to look back, and to reminisce a bit on the great memories, fun times, and lasting friendships we have forged in this community. With that, here are two curated sets of what I believe are my most memorable and best 150 photographs of Cloud Foundry community events and members. Hope you like:
50 B&W:
https://photos.app.goo.gl/JUHVSRCKc9SrvuZD8
100 Color:
https://photos.app.goo.gl/mAarRq8QvAWm8Mki6
PS: While I took care to select the best photos, I can fully understand if there is a photo of you, or that you are in a photo, that you do not like or rather I not share. Please let me know and I will remove ASAP.
Also, to respect the privacy of all, I ask you to get permissions before re-sharing, of course, if the photograph includes someone other than yourself. In my experience most people agree, so just ask.
Dr Nic Williams Stark & Wayne LLC +61 437 276 076 twitter @drnic
You received this message because you are subscribed to the Google Groups "cf-extensions-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cf-extensions-pmc+unsubscribe@....
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/cf-extensions-pmc/CAM-_pPbYBdugvoaq4achwtKb_Pbb2_X0wFjy6Hsm8rtVfb9Gjg%40mail.gmail.com.
|
|
|
