Hello everyone,

 

The Services API Team has been working on a model for the Cloud Controller V3 API for service bindings, service keys and service route bindings.
You can view the proposal here:

https://docs.google.com/document/d/115XMaCGvtkuXpmSA-UwnEowYdZ75mLB_OdXsuSiwRf4

We are seeking feedback from the community to help us finalize this proposal and move forward with implementation.

We are looking forward to your comments! You can contact us by replying to this email, or in our cloud foundry slack channel #svat 

Best regards
Felisia
On Behalf of the Services API Team

Hi Josh

Am 27.04.2020 um 18:13 schrieb Josh Collins:
> Dear Cloud Foundry Community,
>
>
> We are nearing the completion of the v7 CF CLI and we’re excited to
> announce that we’ll be cutting our GA release soon!

This is fantastic news. Our developers are waiting for some of the
experimental v3-commands to be replaced with stable CLI v7 commands.

> The exact target date for the launch hasn’t been finalized but because
> transitioning from v6 to v7 will require coordination and planning we’re
> sending an initial heads up. We'll send follow ups to this communication
> once the launch date and associated details become concrete.
>
>  
>
> In case you haven’t been following the development of the v7 CLI
> closely, here’s three of many new capabilities that will become
> available when v7 GAs:
>
>   *
>
>     Rolling Deploys
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.cloudfoundry.org_devguide_deploy-2Dapps_rolling-2Ddeploy.html&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=zV_urrEjeWCta68K3cScoA&m=YeWLNHeSMdg9ByYElGUn1Z6tYysmnfqN-WG7A9-Db50&s=d1K8PTiAZKqEa-ufU1Sba8TGGzX7Pae4jRJvPUFnfd8&e= >using
>     the "--strategy" flag for "cf push" and other commands
>
>   *
>
>     Metadata
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.cloudfoundry.org_adminguide_metadata.html&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=zV_urrEjeWCta68K3cScoA&m=YeWLNHeSMdg9ByYElGUn1Z6tYysmnfqN-WG7A9-Db50&s=bQHubdd5Qkr-cstS5XJkoF5b44i_kMuV3zRhS74OCB0&e= >apply labels
>     and annotations to apps, spaces, organizations, and other resources
>
>   *
>
>     Sidecar Processes
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.cloudfoundry.org_devguide_sidecars.html&d=DwIFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=zV_urrEjeWCta68K3cScoA&m=YeWLNHeSMdg9ByYElGUn1Z6tYysmnfqN-WG7A9-Db50&s=IpVJPQf06TQ78_X8hsiNmDipQAadSAK01KOI9lvxU9g&e= >for
>     applications using application manifests
>
> ...

How about manifest files? Do we have to expect any manifest syntax or
naming changes? Will some of the new CLI features also be available in
the manifest?

Thanks,

   Stefan

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 Foundation

spodila

@cloudfoundry.org

@

skpodila

You can read more about pronouns here, or please ask if you'd like to find out more.

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:

[1] Release notes for 0.2.0

[2] Slack channel # cf-for-k8s

--

Saikiran Yerram

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:

• Please read this update. TL;DR: Call for Papers has been extended until Friday, April 17th and Program Chairs have been announced.

• In the likely event that CF Summit does become a virtual event, CFP submissions will still be selected from those submitted by you by 4/17.

• Thank you for electing the program committee and special thanks to Amelia, Dr. Nic, Molly and Matthias for helping us curate the content.

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

Check the community calendar for updates and meeting details here: https://www.cloudfoundry.org/community-calendar/

Interesting Finds from Around the Web:

• https://developer.ibm.com/callforcode/

• https://www.cnbc.com/2020/04/01/new-microsoft-google-amazon-cloud-battle-over-world-without-code.html

• https://www.theregister.co.uk/2020/03/30/it_events_after_coronavirus/

• https://hbr.org/2020/03/that-discomfort-youre-feeling-is-grief

• https://www.nytimes.com/2020/03/23/technology/coronavirus-facebook-amazon-youtube.html

• https://www.theguardian.com/australia-news/2020/mar/30/astrophysicist-gets-magnets-stuck-up-nose-while-inventing-coronavirus-device

• https://twitter.com/stephenking/status/1243638441834930186?s=21

• https://www.cnet.com/roadshow/news/real-id-license-deadline-coronavirus/#ftag=CAD590a51e

• https://www.msn.com/en-us/money/companies/thousands-of-zoom-video-calls-left-exposed-on-open-web/ar-BB128jQI?li=BBnb7Kz

• https://www.nytimes.com/2020/04/01/arts/music/ellis-marsalis-dead-virus.html

• RIP Bill Withers.

• https://twitter.com/svrc/status/1246664953244704768

-- Swarna Podila (she/her)

Senior

 Director

, Community

 | Cloud Foundry Foundation

spodila

@cloudfoundry.org

@

skpodila

You 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:

• Call for proposals for Cloud Foundry NA Summit is (still) open (extended to April 3).

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

Check the community calendar for updates and meeting details here: https://www.cloudfoundry.org/community-calendar/

Interesting Finds from Around the Web:

• https://medium.com/@eeenotes/containerizing-cf-be4ebb81cf0f
• https://github.blog/2020-03-16-npm-is-joining-github/?utm_campaign=1584377606&utm_medium=social&utm_source=twitter&utm_content=1584377606
• https://techcrunch.com/2020/03/11/aws-launches-bottlerocket-a-linux-based-os-for-container-hosting/
• https://headtopics.com/us/vmware-created-a-new-business-unit-that-includes-pivotal-and-heptio-business-insider-11779107
• https://www.zdnet.com/article/pet-the-cat-own-the-bathrobe-linus-torvalds-on-working-from-home/
• https://www.zdnet.com/article/with-kubecf-cloud-foundry-comes-to-kubernetes/
• https://www.sdxcentral.com/articles/news/cloud-foundry-foundation-adopts-kubecf-runtime/2020/03/

Who’s hiring?  

Check out the jobs board https://www.cloudfoundry.org/cf-jobs/

• SAP Cloud Platform is hiring https://twitter.com/voelzmo/status/1240626439898136578 
• Resilient Scale is looking for folks with experience in Cloud Foundry and Concourse: https://www.linkedin.com/pulse/join-our-team-resilient-scale-steve-greenberg/?published=t
• Royal Bank of Scotland is looking for a Cloud Application Architect: https://jobs.rbs.com/jobs/4784789-cloud-application-architect 
• Anynines is looking for a Sys Admins, System Engineers, and Software Developers: https://www.anynines.com/career 

 

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 

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

Just as inspiration, and maybe spike implémentation, a déclarative approach based on terraform HCL is probably a good way to start

https://github.com/cloudfoundry-community/terraform-provider-cf/blob/master/README.md

Le mar. 28 avr. 2020 à 19:18, Zach Robinson <zrobinson@...> a écrit :

Hey Daniel,

Wanted to follow up. There's now a doc to start building out our understanding of CRDs here https://docs.google.com/document/d/1mIMH4uEtIJkZjVa5mKWJoIAIeVyM4gVqO-Cx5JtYgtE/edit?usp=sharing

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

On Thu, Apr 16, 2020 at 4:10 AM Daniel Jones <daniel.jones@...> wrote:

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

@DanielJonesEB

EngineerBetter Ltd - More than cloud platform specialists

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

On Wed, Apr 15, 2020 at 3:01 AM Daniel Jones <daniel.jones@...> wrote:

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

@DanielJonesEB

EngineerBetter Ltd - More than cloud platform specialists

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