1. cf-dev@lists.cloudfoundry.org
  2. Messages
   Date   
CF Application Runtime PMC: Diego Project Lead Call for Nominations

Eric Malm <emalm@...>
 

Hi, everyone,

I am stepping down as the lead for the Diego project within the Application Runtime PMC, although I will remain in my role as the lead for the PMC itself.

The Diego team, located primarily in San Francisco with remote members in New York and Virginia, 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 PDT on Monday, June 24, 2019.

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
REMINDER: CAB call for June is next week Wednesday 19th @ 8a Pacific

Michael Maximilien
 

 
Hi, all,
 
Reminder that the CAB call for June is next Wednesday 19th @ 8a Pacific.
 
We will have regular highlights, QAs, as well as one planned talk with another TBD:
 
1. External DNS connector for Cloud Foundry [1] by Sergey Matochkin and Comcast engineering team
2. TBD (contact me if you have a talk to share)
 
All other info in agenda [0]. Zoom soon. Best,

------
dr.max
ibm ☁ 
silicon valley, ca
maximilien.org
 
Re: CFCR public backlog

Mike Lloyd <mike@...>
 

Elisabeth,

 

I would like to second Guillaume’s statement; if it’s too difficult to use the native Github constructs for greater discoverability, then Pivotal Tracker is fine.

 

Thanks,

 

Mike.

 

From: cf-dev@... <cf-dev@...> On Behalf Of Guillaume Berche via Lists.Cloudfoundry.Org
Sent: Friday, June 7, 2019 7:55 AM
To: cf-dev <cf-dev@...>
Subject: Re: [cf-dev] CFCR public backlog

 

Hi Elisabeth,

 

Thanks for your prompt reply and action to improve things!

 

Regarding github vs pivotal tracker preference:

 

I believe that what matters most is that the content that the CRCF team produces be shared with the rest of the community as to enable best collaboration. With other CFF teams, this typically includes epics, stories with their associated design discussions/docs, milestones, weekly planned and completed work (usually with associated story points), story life cycle through its status (delivered, accepted, rejected, ...)

 

If there is a way the CFCR team can share this content on github that would be easier for the community: github content is more discoverable through web search, can be crossed referenced from other github projects, and accepts community inputs. See related email thread [1] regarding an experiment my team conducted a few years back to automatically mirror pivotal tracker content onto github.

If instead CRCR team only manages to share a smaller fraction of its content onto github and the rest remains unavailable to the community, then I believe a single public pivotal tracker would be more beneficial to the community.

 

Thanks again,


Guillaume.

 

 

 

On Fri, Jun 7, 2019 at 3:54 AM Elisabeth Hendrickson <ehendrickson@...> wrote:

Hi Guillaume,

Thank you so much for raising this issue. You're right - the public backlog is not being kept up to date right now and we need to fix that. We are working to bring the details of the work to a more public place so it is more easily visible. We are hoping to have that finished by the end of next week.

We're currently debating whether to use github issues or Pivotal Tracker. I'm curious if you have a preference?

Many thanks for raising this concern,

Elisabeth

Re: CFCR public backlog

Guillaume Berche
 

Hi Elisabeth,

Thanks for your prompt reply and action to improve things!

Regarding github vs pivotal tracker preference:

I believe that what matters most is that the content that the CRCF team produces be shared with the rest of the community as to enable best collaboration. With other CFF teams, this typically includes epics, stories with their associated design discussions/docs, milestones, weekly planned and completed work (usually with associated story points), story life cycle through its status (delivered, accepted, rejected, ...)

If there is a way the CFCR team can share this content on github that would be easier for the community: github content is more discoverable through web search, can be crossed referenced from other github projects, and accepts community inputs. See related email thread [1] regarding an experiment my team conducted a few years back to automatically mirror pivotal tracker content onto github.

If instead CRCR team only manages to share a smaller fraction of its content onto github and the rest remains unavailable to the community, then I believe a single public pivotal tracker would be more beneficial to the community.

Thanks again,

Guillaume.



On Fri, Jun 7, 2019 at 3:54 AM Elisabeth Hendrickson <ehendrickson@...> wrote:
Hi Guillaume,

Thank you so much for raising this issue. You're right - the public backlog is not being kept up to date right now and we need to fix that. We are working to bring the details of the work to a more public place so it is more easily visible. We are hoping to have that finished by the end of next week.

We're currently debating whether to use github issues or Pivotal Tracker. I'm curious if you have a preference?

Many thanks for raising this concern,

Elisabeth

Asynchronous Service Broker Bindings is now GA

Aarti Kriplani
 

Hello CF Devs,

We are happy to announce that Asynchronous Service Broker Bindings feature is now Generally Available starting from CC API Version: 2.137.0 (CAPI Release 1.82.0).

It allows service brokers to support long running binding operations, such as provisioning user accounts, setting up firewalls and etc. without the need to change the default CF timeout as requested in this issue.

Corresponding changes to leverage this feature have also been part from CF CLI v6.40.1.


We would like to thank for your feedback during the experimental phase.

Thanks,

Services API Team
Re: CFCR public backlog

Elisabeth Hendrickson
 

Hi Guillaume,

Thank you so much for raising this issue. You're right - the public backlog is not being kept up to date right now and we need to fix that. We are working to bring the details of the work to a more public place so it is more easily visible. We are hoping to have that finished by the end of next week.

We're currently debating whether to use github issues or Pivotal Tracker. I'm curious if you have a preference?

Many thanks for raising this concern,

Elisabeth
CFCR public backlog

Guillaume Berche
 

Hi,

It seems that the CFCR project has switched from using the oss backlog [1] to a backlog which is not yet accessible to the community. Can the permissions please be fixed to allow the community to understand commits rationales, planned future work, and efficiently contribute to the project ? More details below.

Thanks in advance,

Guillaume.

ps: I don't have direct email to CFCR lead and PM Colin Humphreys and  Brendan Nolan. I hope that someone can forward them this email if they're not subscribed to this list.
Important Notice: [nodejs-buildpack] End of support for nodejs versions 11.x after 2019-06-05

Elliott Shanks
 

The first release of the Node.js buildpack after June 05, 2019 will no longer include any versions of Node.js 11.x. These Node.js versions are no longer supported upstream [1]. Please migrate your Node.js apps to supported versions of Node.js before that time.


Note: Unless you are manually specifying a version of Node.js for the buildpack to use, or you have customized your Node.js buildpack, no action is required.


[1] https://github.com/nodejs/Release


Thanks,

Elliott Shanks, CF Buildpacks PM
CF CLI v6.45.0 is released

Will Murphy
 

Hello everyone,

The CF CLI team has just released version v6.45.0. Please see https://github.com/cloudfoundry/cli/releases/tag/v6.45.0 for release notes.

Thanks!
The CF CLI Team
Important Notice: [Stack-Auditor] Issue with Stack Auditor change-stack command in version 0.0.3

Elliott Shanks
 

We have identified an issue with Stack Auditor version 0.0.3 and the change-stack command. In some cases, the wrong application will attempt to change stacks if another application with the same name exists in a different space. A fix has been included in the latest release of Stack Auditor (0.0.4). It is recommended that all users of Stack Auditor no longer use version 0.0.3 and migrate to a later version of Stack Auditor.

For more information, see https://github.com/cloudfoundry/stack-auditor/releases


--
Respectfully, 

Elliott Shanks
Product Manager, Buildpacks
Contribute to the Cloud Foundry YouTube Channel

Brie Rogers
 

Hello All,


Several of you have expressed interest in creating instructional “how-to” videos for the broader Cloud Foundry community. If you are interested in making video content to be published on the Cloud Foundry Foundation YouTube channel for end users, contributors, developers, operators, and others, please read the publishing guide.


Guidelines for production include:

  • The content should be vendor neutral, provide objective viewpoints and cannot make subjective competitive comparisons to other technologies.

  • This content is a teaching mechanism. This video should be functionally educational and provide viewers with applicable knowledge.

  • Videos should be under 10 minutes in length.


Please reach out to me if you’re interested in contributing video content to the Cloud Foundry Foundation YouTube channel. We’re looking forward to growing this program.


Thank you!


Brie Rogers


CFCD v2 Tester Signup

Chip Childers <cchilders@...>
 

Google Forms
Hi everyone! We are looking for testers for the new CFCD version 2 exam, which is set to launch in the fall of this year. There's no cost, and if you pass you will be awarded the certification when final cut scores are determined and the exam is launched. Depending on response rate, we may or may not be able to use everyone that signs up. If you sign up and we don't use you during the testing process, we will provide you with a discount code to take the final version post launch.
CFCD v2 Tester Signup
We are working to launch a version 2 of the Cloud Foundry Certified Developer certification exam in the fall of this year (2019). As part of the process, we are looking for willing individuals to take an early version of the exam. Candidates that take the exam as part of the testing process, and score an acceptable score, will be awarded the v2 certification when launched.

If you are willing to take the exam, as well as provide feedback to the exam development team, please let us know!

We will only use your contact information for the purpose of coordinating the testing process, getting feedback and awarding certifications to those that pass.
Fill out form
Create your own Google Form
user creation and activation in uaa #cf #uaa #java

charanavengers@...
 

Hi all,

I want to create users in the cloudfoundary uaa for my web application.I am using the authorization code grant for that instead of redirecting to the client redirected url it is redirecting to the uaa login url.Is there any help


Thank You,
Announcement: Planned Deprecation of the v6 cf CLI

Abby Chau
 

Hello everyone,

Hope this finds you well. 

Following on the CC V2 API Deprecation Plan notification recently, the cf CLI team are writing to also announce the planned deprecation of the v6 cf CLI. Please provide feedback and review the v6 CF CLI Deprecation Plan for details on strategy and timeframes. 

We hope to make the upgrade process as seamless as possible for our users, and that the v7 cf CLI will provide greater opportunities to grow and enhance the product for our users.

As always, we value your feedback and would appreciate comments in the document. We also hang out on Cloud Foundry Slack at #cli. We hope to hear from you. 

Many thanks,

Abby Chau and the CF CLI team
Cloud Foundry Summit CFP Deadline is Friday

Swarna Podila
 

Just wanted to remind you all about the CFP deadline that is creeping up.  Please go ahead and get your submissions in before this Friday.

-- Swarna Podila (she/her)
Senior
 Director
, Community
 | Cloud Foundry Foundation

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


---------- Forwarded message ---------
From: Deborah Giles <dgiles@...>
Date: Wed, May 29, 2019 at 8:34 AM
Subject: Cloud Foundry Summit CFP Deadline is Friday
To: <spodila@...>


 
 
The deadline to submit your CFP for Cloud Foundry Summit in The Hague, The Netherlands is quickly approaching. Join us September 11-12, 2019 to discuss how you’re building the cloud native future using Cloud Foundry Technologies. The CFP deadline is Friday, May 31, 2019. 

Whether you’re a contributor to the open source project, a platform end user, an operator or a business decision maker, we want to hear from you.

Summit topics include Cloud Foundry 101: Getting Started; Cloud Foundry for Business; Cloud Foundry for Developers; Cloud Foundry for Operators; Experiments & Extensions; Project Updates and User Stories. 

We also invite you to submit a talk for the Cloud Foundry Summit Diversity Luncheon. You can find the Diversity Luncheon application embedded in the standard CFP for the event. The Foundation is committed to five value-driven actions: Be open, be inclusive, be kind, be transparent and be curious. We aim to bring these sensibilities into the Diversity Luncheon.

The Cloud Foundry community has elected the co-chairs that will review speaking submissions. Learn more about the co-chairs. 

If you want your abstract reviewed by your peers or just want a second set of eyes before you submit it, you can always tag @cfp-help in #summit on Cloud Foundry slack.
Submit Your CFP »

1 Letterman Drive Building D, Suite D4700 San Francisco, CA 94129
You are receiving this email because you signed up to receive email communications from Cloud Foundry. Update your email preferences.
 

Re: Integration of UAA with Kerberos #uaa #kerberos

Camilo Aguilar
 

If you don’t have a SAML provider already in place, I would rather use Keycloak.

The SAML provider we used was our customer’s Active Directory Federated Services. We used UAA to not have to integrate our apps with SAML and Kerberos, which was our customer’s authentication and authorization solution. 

On Wed, May 29, 2019 at 10:55 AM Enrique Cano <enrique.canocarballar@...> wrote:
Thanks, Camilo, that's very interesting and helpful. So, it's possible to do it, we just need to have a SAML provider integrated with Kerberos, and then we can integrate UAA with that SAML provider, is that correct? What SAML provider did you use?

Many thanks

Enrique

--
Camilo Aguilar
Software Engineer
Re: Integration of UAA with Kerberos #uaa #kerberos

Enrique Cano
 

Thanks, Camilo, that's very interesting and helpful. So, it's possible to do it, we just need to have a SAML provider integrated with Kerberos, and then we can integrate UAA with that SAML provider, is that correct? What SAML provider did you use?

Many thanks

Enrique
Eirini office hours

Oleksandr Slynko
 

Hi cf-dev,

Project Eirini got lots of attention during the last Cloud Foundry Summit. We decided to run open office hours, so people can ask any questions about Eirini and current progress.
It will happen every first Monday of the month at 3-30 PM Irish time (also known as GMT) starting next week. Check this link to convert it to your time http://www.timebie.com/std/irish.php?q=15.5
We will use the following Zoom room https://zoom.us/j/8743349130
Feel free to join!

Thank you,
Oleksandr & Eirini team
[Proposal] CF-RFC 020: BOSH: setting global kernel parameters by jobs

Stanislav German-Evtushenko
 

Hi, everyone,


Somebody who has already tried to ensure kernel parameters to be in a certain state for a particular bosh job must have noticed that there is no simple and reliable way to do this (see https://github.com/cloudfoundry/routing-release/issues/138 as an example). I would like to share a proposal with the aim to solve it.


Link to the proposal: https://docs.google.com/document/d/1BEi2A5T47K8f26B-QSotuYr-16tUCNRbX6BumNKXb7c

Pull request: https://github.com/cloudfoundry/os-conf-release/pull/47

Slack channel: https://cloudfoundry.slack.com/messages/CJZLX6NDT


Please let us know your opinions here, on the document or on the slack channel.


Thanks,

Stanislav
Re: Config Server Roadmap

Guillaume Berche
 

Hi Mike,

You might be interested in zipcar's hashicorp vault bosh config server api impl:


Le mer. 22 mai 2019 18:09, Mike Lloyd <mike@...> a écrit :

Team,

 

I’ve been researching non-Credhub integrations for secrets management with BOSH, and I wanted to see if there was a Config Server roadmap? I wasn’t able to find one but I also wasn’t entirely sure where to look.

 

Respectfully,

 

Mike Lloyd

t: @mxplusc

g: @mxplusb

 
801 - 820 of 9429