1. cf-dev@lists.cloudfoundry.org
  2. Messages
   Date   
CF Extensions PMC changes and Community Advisory Board (CAB) lead nominations

Troy Topnik
 

I am both happy and sad to announce that as of next week I'll be at a new job outside of the Cloud Foundry sphere. I'll need to hand off my Community Advisory Board and CF Extensions responsibilities.

The Extensions PMC lead role will probably not require a direct replacement because of how the CF governance structure is changing, but the CF CAB meetings should have someone nominated from the community to run them. If you're interested in taking this on, please contact Chris Clark or myself in the CF Slack. If you'd like to nominate someone to lead these monthly calls, feel free to do that in this thread.

Cloud Foundry is the most supportive and inclusive software community I've encountered, and I thank all of you that have made this so. I promise I won't be a stranger. 

Cheers,

TT

--
Troy Topnik
Re: UAA error: InResponseToField of the Response doesn't correspond to sent message

Daniel Jones
 

Nice one for finding the reason, and also for taking the time to share it for the next person that stumbles across this post in search results :)

Regards,
Daniel 'Deejay' Jones - Managing Director
+44 (0)79 8000 9153
EngineerBetter Ltd - More than cloud platform specialists


On Tue, 23 Feb 2021 at 11:42, Enrique Cano <enrique.canocarballar@...> wrote:
I've found the issue. The parameter servlet.idle-timeout was set to 60 seconds. That meant the session was removed after that timeout if there was no communication from the IdP. When eventually a SAML response was sent back to UAA, UAA would try to find the corresponding SAML request in the cache associated to the session, but because the session was no longer there, it was raising that error.

Re: UAA error: InResponseToField of the Response doesn't correspond to sent message

Enrique Cano
 

I've found the issue. The parameter servlet.idle-timeout was set to 60 seconds. That meant the session was removed after that timeout if there was no communication from the IdP. When eventually a SAML response was sent back to UAA, UAA would try to find the corresponding SAML request in the cache associated to the session, but because the session was no longer there, it was raising that error.
Community interest in osb-cmdb ?

Guillaume Berche
 

Hi,

Orange has contributed a component to ease sharing of an open-service-broker marketplace among multiple client platforms. See cab recording at [1], and a longer full slide deck at [2] and actual repo at [3].

Before proposing this project to the cf-extension pmc (or new working group in new CF technical governance), I'd like to hear if there is community interest in using or contributing to this project ?

Thanks in advance for your feedback,
UAA error: InResponseToField of the Response doesn't correspond to sent message

Enrique Cano
 

Hi

I've got UAA connected to an Identity Provider using SAML. I've noticed that if the Identity Provider takes some time (in my case, 1 minute 40 seconds) in responding to the SAML request with a SAML response, then I get this error in UAA: "InResponseToField of the Response doesn't correspond to sent message..."
In the logs, I can see:
DEBUG --- HttpSessionStorage: Storing message a4g4f9f5259jb7ji12eah767h6e0i20 to session 82190965-9a09-4618-9c21-90a01cab7be5
But then it seems that that session no longer exists... Is there some sort of timeout that is deleting that HttpSession?

Many thanks in advance

Enrique
Re: CF Application Runtime PMC: Release Integration Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

VMware is nominating Andrew "Birdrock" Wittrock for the Release Integration project lead in the Application Runtime PMC.

Andrew has worked on Cloud Foundry since 2019, most recently as an engineer leading work on the Release Integration team, and before that on the UAA team. Prior to joining Pivotal/VMware, Andrew worked as a full-stack engineer with an emphasis on developer tooling and automation.

Please send any other nominations directly to me or in reply to this message no later than 11:59 PM PST on Wednesday, March 3, 2021.

Thanks,
Eric Malm

From: cf-dev@... <cf-dev@...> on behalf of Eric Malm via lists.cloudfoundry.org <emalm=vmware.com@...>
Sent: Wednesday, February 17, 2021 5:29 PM
To: cf-dev@... <cf-dev@...>
Subject: [cf-dev] CF Application Runtime PMC: Release Integration Project Lead Call for Nominations
 
Hi, everyone,

Paul Warren, the lead for the Release Integration project within the Application Runtime PMC, is stepping down from the role, as he has taken on other responsibilities inside of VMware. We thank him for his service.

The Release Integration team, based in San Francisco, now has an opening for its project lead. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PST on Wednesday, March 3, 2021.

Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

Thanks,
Eric Malm, CF Application Runtime PMC Lead
CF Application Runtime PMC: Release Integration Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

Paul Warren, the lead for the Release Integration project within the Application Runtime PMC, is stepping down from the role, as he has taken on other responsibilities inside of VMware. We thank him for his service.

The Release Integration team, based in San Francisco, now has an opening for its project lead. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PST on Wednesday, March 3, 2021.

Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

Thanks,
Eric Malm, CF Application Runtime PMC Lead
Bi-weekly Round-Up: Technical + Ecosystem Updates from Cloud Foundry

Chris Clark
 

Hi folks! Here are a few CF events I’d like to highlight coming up this month:  

From the Last Few Weeks

Notable Releases

  • cf-deployment v16.0.0

    • Breaking change: removed ubuntu-trusty stemcell from references in the cf-deployment manifest

    • Enables TLS between route_registrar and NATS

  • cflinuxfs3 v0.222.0

  • uaa v75.0.0

    • Allows multiple oauth client secrets to be configured

    • Updated logging timestamp format

  • BOSH v271.3.0

    • Allows changing of the root domain for DNS

    • Improves director pre-start time

  • cf-java-client v5.1.0

    • Added support for v3 Roles and renaming spaces

  • cloud-service-broker v0.2.2

    • Moved brokerpaks into their own repositories: AWS, Azure, GCP


Dates To Remember (All times U.S. Pacific)

  • Livestream: JavaScript Apps on Kubernetes & Cloud Foundry - February 4 at 9 am

  • CF Technical Governance meeting - February 4 at 8 am (Moved from Feb 5!)

  • CF Technical Governance meeting - February 12 at 8 am

  • CF for Kubernetes SIG meeting - February 16 at 8:30 am

  • How to Monitor Cloud Foundry webinar with DataDog - February 16 at 10 am

  • Bi-Weekly CF App Runtime PMC meeting - February 16 at 10:30 am

  • CAB call - February 17 at 8 am

  • CF Technical Governance meeting - February 19 at 8 am

  • Office Hours: Logging and Metrics - February 19 at 10:30 am 

  • SHIELDing Data in Your Cloud Foundry Apps Hands-on Lab with Stark & Wayne - February 23 at 10 am

Check the community calendar for updates and meeting details here. 

Ecosystem and General News

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? Check out the #jobs channel in our community slack; folks are sharing the job openings in our community. (And if you are hiring, please do share the info in that channel.)


--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
CAB call: Wednesday January 20 @8am Pacific

Troy Topnik
 

No talks scheduled (yet) for tomorrow's meeting, so it might be a short one again.

https://zoom.us/j/886369973

If anyone has anything they'd like to present, let me know in Slack in the #cab channel.

TT


CF month CAB calls used to discuss Cloud Foundry community related news and QAs
 
----------
Chat room: go to slack.cloudfoundry.org and then join the #cab channel
 
 
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/757994996
 
Or iPhone one-tap :
    US: +16468769923,,757994996#  or +16699006833,,757994996#
Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        US: +1 646 876 9923  or +1 669 900 6833  or +1 408 638 0968
    Meeting ID: 757 994 996
    International numbers available: https://zoom.us/zoomconference?m=BbM_MZowkH08pdKycQk10at13V5cLneM
 
Agenda doc: https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI
──────────
Join Zoom Meeting
https://zoom.us/j/886369973
 
Meeting ID: 886 369 973
 
One tap mobile
+16699006833,,886369973# US (San Jose)
+16465588656,,886369973# US (New York)
 


Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        877 369 0926 US Toll-free
        855 880 1246 US Toll-free
        +1 647 558 0588 Canada
        855 703 8985 Canada Toll-free
Meeting ID: 886 369 973
Find your local number: https://zoom.us/u/abSAPsJbM


--
Troy Topnik
Senior Product Manager, 
SUSE Cloud Application Platform 
troy.topnik@...
 
Proposal for Custom Domains in cf-for-k8s

Lay, Stefan
 

Hello CF community,

 

We created a proposal to add support for user owned domains to cf-for-k8s. The proposal is available here: https://docs.google.com/document/d/17zIHB-L6tLEJPdbB4JYUEb4ii8w2YIUL5TQU7fV9jlM/edit?usp=sharing

 

This document should serve as starting point for discussion. We would be very happy for feedback in the document about the use case and the technical implementation.

 

Regards,

Tamara, Soha and Stefan

on behalf of the SAP Cloud Platform team

 

 
Bi-weekly Round-Up: Technical + Ecosystem Updates from Cloud Foundry

Chris Clark
 

Happy New Year! Pretty slow news week out there in the wider world, so here are some Cloud Foundry happenings to occupy your stimulation-deprived brains.

From the Last Few Weeks:

Notable Releases:

  • Stratos v4.4.0, with many new features, including:

    • updates to visible Kubernetes resource types

    • application deployment from private repositories

    • an improved homepage 

    • Read more here.

  • Routing-release v0.211.0

    • adds support for sticky sessions when CF-deployed reverse proxy is used

(see: https://github.com/cloudfoundry/routing-release/issues/170)


Dates To Remember (All times U.S. Pacific):

  • CF Technical Governance meeting - January 15 at 10 am 

  • CF for Kubernetes SIG meeting - January 19 at 8:30 am

  • Bi-Weekly CF App Runtime PMC meeting - January 19 at 10:30 am

  • Office Hours: Logging and Metrics - January 19 at 11 am

  • CAB call - January 20 at 8 am

  • CF Technical Governance meeting - January 22 at 10 am

  • CF Extensions PMC meeting - January 25 at 11 am

  • “cf push for Modern Observability” Webinar with DataDog - January 26 at 10 am

Check the community calendar for updates and meeting details here. 

Ecosystem and General News:

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? Check out the jobs board and the #jobs channel in our community slack; folks are sharing job openings in our community there. (And if you are hiring, please do share that in that channel.)


--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
Migration of cf-deployment concourse images

pollardja@...
 

Hi everyone,


Release Integration team here.

We’ve moved the homes of several of our images (such as cf-deployment-concourse-tasks) from relintdockerhubpushbot to the cloudfoundry dockerhub to avoid potential rate-limiting.

We’ll no longer be updating the images in the old location so please switch your pipelines over if they're using any images from relintdockerhubpushbot/<image>.

 

Best,
relint
Re: New CFF Contributor License Agreement will need to be signed

Chris Clark
 

We'll be making the switch on Monday Jan 11, at 12 noon pacific time, in order to give a bit more time for contributing companies to get set up with the new CLA (and avoid breaking things on a Friday).  

Apologies in advance for any chaos that may ensue, hopefully minimal. Please reach out as needed!  

On Wed, Jan 6, 2021 at 2:19 PM Chris Clark via lists.cloudfoundry.org <cclark=cloudfoundry.org@...> wrote:
:)

One thing to clarify... for anyone looking to sign the new CCLA on behalf of their company, here are explicit instructions. We'd emailed all previous "CLA managers" who'd signed the old CLA, but I realize some of those folks might no longer be an active contact:  

· Please log in with, or create your Linux Foundation Account, and go to the corporate CLA dashboard here: https://corporate.v1.easycla.lfx.linuxfoundation.org/

· Click "Get Started" and select your company from the list or create a new company

· On the next screen, click "Sign New CLA" at the top.

· Select "Cloud Foundry - Series LLCs" from the list.

· You may click "Yes" to sign the CCLA, or "No" to send it to someone in your company with corporate authority.

· Once signed, please re-add your GitHub organization or individual contributors to the approved list for the new "Cloud Foundry - Series LLCs" CLA. 


On Tue, Jan 5, 2021 at 11:36 AM Chris Clark via lists.cloudfoundry.org <cclark=cloudfoundry.org@...> wrote:

Hello all,


On January 1, 2021, the Cloud Foundry Foundation changed the corporate structure used to support the organization, and is now a directed fund within the Linux Foundation. This means we’ve had to make some small revisions to our Contributor License Agreement (CLA).


This new agreement is substantively very similar to the last one, except for these minor changes: 

  • updates to references to the legal entities receiving the contributions

  • removal of extraneous schedules at the end of the CCLA

  • clearer references to the use of EasyCLA and process for each company to maintain the list of their authorized contributors

You will likely want to consult with your legal department if you have any questions about the CCLA text itself.


If you are a CLA manager for your respective company, we’ve already reached out to you directly, with instructions asking you to sign the new Corporate Contributor License Agreement (CCLA), and add the same people and groups you had previously added to the approved list for your company. This should just take a few minutes, and, given the minor change to the previous agreement should hopefully be quickly approved by your legal department as needed :)


If you are covered under an existing Corporate Contributor License Agreement (CCLA), your company will need to take the steps outlined above before your pull requests go through.  


If you have signed an Individual Contributor License Agreement (ICLA), you’ll be prompted to resign the next time a pull request goes into a Cloud Foundry repository. This only takes a minute or two. 


We’ll be crossing over to the new CLA later this week; please reach out if you have any questions or concerns.



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
Re: New CFF Contributor License Agreement will need to be signed

Chris Clark
 

:)

One thing to clarify... for anyone looking to sign the new CCLA on behalf of their company, here are explicit instructions. We'd emailed all previous "CLA managers" who'd signed the old CLA, but I realize some of those folks might no longer be an active contact:  

· Please log in with, or create your Linux Foundation Account, and go to the corporate CLA dashboard here: https://corporate.v1.easycla.lfx.linuxfoundation.org/

· Click "Get Started" and select your company from the list or create a new company

· On the next screen, click "Sign New CLA" at the top.

· Select "Cloud Foundry - Series LLCs" from the list.

· You may click "Yes" to sign the CCLA, or "No" to send it to someone in your company with corporate authority.

· Once signed, please re-add your GitHub organization or individual contributors to the approved list for the new "Cloud Foundry - Series LLCs" CLA. 


On Tue, Jan 5, 2021 at 11:36 AM Chris Clark via lists.cloudfoundry.org <cclark=cloudfoundry.org@...> wrote:

Hello all,


On January 1, 2021, the Cloud Foundry Foundation changed the corporate structure used to support the organization, and is now a directed fund within the Linux Foundation. This means we’ve had to make some small revisions to our Contributor License Agreement (CLA).


This new agreement is substantively very similar to the last one, except for these minor changes: 

  • updates to references to the legal entities receiving the contributions

  • removal of extraneous schedules at the end of the CCLA

  • clearer references to the use of EasyCLA and process for each company to maintain the list of their authorized contributors

You will likely want to consult with your legal department if you have any questions about the CCLA text itself.


If you are a CLA manager for your respective company, we’ve already reached out to you directly, with instructions asking you to sign the new Corporate Contributor License Agreement (CCLA), and add the same people and groups you had previously added to the approved list for your company. This should just take a few minutes, and, given the minor change to the previous agreement should hopefully be quickly approved by your legal department as needed :)


If you are covered under an existing Corporate Contributor License Agreement (CCLA), your company will need to take the steps outlined above before your pull requests go through.  


If you have signed an Individual Contributor License Agreement (ICLA), you’ll be prompted to resign the next time a pull request goes into a Cloud Foundry repository. This only takes a minute or two. 


We’ll be crossing over to the new CLA later this week; please reach out if you have any questions or concerns.



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
Stratos 4.4.0

Richard Cox
 

Hi All,

It gives me great pleasure to announce Stratos 4.4.0. Here's the highlights...

- Show more meaningful data on the Home page
- Show more resource types in Kubernetes Cluster and Workload views
- Deploy CF Applications from Private Repos in Github and Gitlab
- Deploy CF Applications from Public and Private Repos in Enterprise GitHub and GitLab
- Persist list settings over browser refresh
- Upgrade to Angular 10

Full release notes are available from https://github.com/cloudfoundry/stratos/blob/master/CHANGELOG.md#440

We welcome your feedback, comments and bug reports. Please feel free to raise them in github (https://github.com/cloudfoundry/stratos) or reach out directly to us in slack (#stratos)

Regards,

Richard Cox
on behalf of the Stratos team
Re: New CFF Contributor License Agreement will need to be signed

Steve Taylor <sttaylor@...>
 

Two points to Gryffindor! Well played.

________________________________________
From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams <drnicwilliams@...>
Sent: Tuesday, January 5, 2021 12:47 PM
To: cf-dev@...
Subject: Re: [cf-dev] New CFF Contributor License Agreement will need to be signed

LOL

On Wed, 6 Jan 2021 at 6:36 am, Jonathan Matthews <contact+cfdev@...<mailto:contact%2Bcfdev@...>> wrote:
On Tue, 5 Jan 2021 at 21:36, Chris Clark <cclark@...<mailto:cclark@...>> wrote:
you’ll be prompted to resign the next time a pull request goes into a Cloud Foundry repository.
But what if I *like* my job? Plus, my code’s not /that/ bad :-(
--
Jonathan Matthews
https://jpluscplusm.com<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjpluscplusm.com%2F&data=04%7C01%7Csttaylor%40vmware.com%7C8356505ba5c94cd1f4bd08d8b1bb2dde%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637454764779235940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Kr4QKfn0sWq%2BpQ6Tdi2dtPI7zMVURWCGf%2FVbIdJ5bBM%3D&reserved=0>

--
Dr Nic Williams
+61 437 276 076
twitter @drnic
Re: New CFF Contributor License Agreement will need to be signed

Dr Nic Williams <drnicwilliams@...>
 

LOL

On Wed, 6 Jan 2021 at 6:36 am, Jonathan Matthews <contact+cfdev@...> wrote:
On Tue, 5 Jan 2021 at 21:36, Chris Clark <cclark@...> wrote:
> you’ll be prompted to resign the next time a pull request goes into a Cloud Foundry repository.

But what if I *like* my job? Plus, my code’s not /that/ bad :-(
--
Jonathan Matthews
https://jpluscplusm.com

--
Dr Nic Williams
+61 437 276 076
twitter @drnic
Re: New CFF Contributor License Agreement will need to be signed

Jonathan Matthews <contact+cfdev@...>
 

On Tue, 5 Jan 2021 at 21:36, Chris Clark <cclark@...> wrote:
> you’ll be prompted to resign the next time a pull request goes into a Cloud Foundry repository.

But what if I *like* my job? Plus, my code’s not /that/ bad :-(
--
Jonathan Matthews
https://jpluscplusm.com
New CFF Contributor License Agreement will need to be signed

Chris Clark
 

Hello all,


On January 1, 2021, the Cloud Foundry Foundation changed the corporate structure used to support the organization, and is now a directed fund within the Linux Foundation. This means we’ve had to make some small revisions to our Contributor License Agreement (CLA).


This new agreement is substantively very similar to the last one, except for these minor changes: 

  • updates to references to the legal entities receiving the contributions

  • removal of extraneous schedules at the end of the CCLA

  • clearer references to the use of EasyCLA and process for each company to maintain the list of their authorized contributors

You will likely want to consult with your legal department if you have any questions about the CCLA text itself.


If you are a CLA manager for your respective company, we’ve already reached out to you directly, with instructions asking you to sign the new Corporate Contributor License Agreement (CCLA), and add the same people and groups you had previously added to the approved list for your company. This should just take a few minutes, and, given the minor change to the previous agreement should hopefully be quickly approved by your legal department as needed :)


If you are covered under an existing Corporate Contributor License Agreement (CCLA), your company will need to take the steps outlined above before your pull requests go through.  


If you have signed an Individual Contributor License Agreement (ICLA), you’ll be prompted to resign the next time a pull request goes into a Cloud Foundry repository. This only takes a minute or two. 


We’ll be crossing over to the new CLA later this week; please reach out if you have any questions or concerns.



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation

PDF
CF CCLA.pdf
PDF
CF ICLA.pdf

Routing Release 0.211.0 now available

Amin Jamali <ajamali@...>
 

Hey cf-eng!

 Routing release 0.211.0 is now available.

 Release Highlights
181 - 200 of 9431