Date   
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

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.

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

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

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

Re: CFCR public backlog

Mike Lloyd
 

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

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
 

CF Application Runtime PMC: Diego Project Lead Call for Nominations

Eric Malm
 

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

Re: CF Application Runtime PMC: Diego Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

Pivotal is nominating Josh Collins for the Diego project lead in the Application Runtime PMC.

Josh joined Pivotal R&D in March 2018 as the product manager for the Release Integration team and as of April 2019 has been carrying out most of the PM responsibilities on the Diego team.

Josh was previously the director of product management for a personalized products company and subsequently managed the A/B testing and optimization efforts for a B2C career development company. Early in his career, Josh worked with a team of three to design and launch the flagship product of what is now a successful company in the backup and disaster recovery space (Aptare).

In a previous life, Josh worked for the Berkeley Unified School District as a middle-school teacher and supplemented his income selling foraged wild mushrooms to local restaurants in Berkeley and Oakland. While working as a teacher he ran the school's computer lab and began his journey into networking, graphic design, web development and beyond. His early successes moonlighting on tech gigs changed his trajectory and ultimately led to his current employment at Pivotal.

Josh holds a BA in Art from the University of California, Santa Cruz, and an MA in Education from University Washington Seattle.

Please send any other nominations directly to me or in reply to this message no later than 11:59 PM PDT on Monday, June 24, 2019.

Thanks,
Eric Malm

On Thu, Jun 13, 2019 at 3:51 PM Eric Malm <emalm@...> wrote:
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

IMPORTANT NOTICE: End of support for cflinuxfs2 buildpacks after 2019-08-31

Elliott Shanks
 

This notice is regarding the end of support for cflinuxfs2 buildpacks after 2019-08-31. As previously mentioned, Ubuntu has ended support for 14.04, and with that, support for cflinuxfs2 has also ended. Due to the need to migrate all applications from cflinuxfs2 to cflinuxfs3, we have continued to release cflinuxfs2 buildpacks while those migrations came to a conclusion. After August 31, 2019, all buildpack releases will be for cflinuxfs3 only.


If you are still in need of migrating your applications over to cflinuxfs3, the Stack Auditor tool can be of use.


Thanks,

Elliott Shanks

PM, Buildpacks


Re: CF Application Runtime PMC: Diego Project Lead Call for Nominations

Benjamin Gandon
 

Congratulations Eric for the great work done as Diego project lead!

Benjamin


Le 14 juin 2019 à 00:50, Eric Malm <emalm@...> a écrit :

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

Re: CF Application Runtime PMC: Diego Project Lead Call for Nominations

Nima
 

Thank you Eric for all the great work on Diego. It definitely was a great pleasure working with you.
 

----- Original message -----
From: "Eric Malm" <emalm@...>
Sent by: cf-dev@...
To: cf-dev <cf-dev@...>
Cc:
Subject: [EXTERNAL] [cf-dev] CF Application Runtime PMC: Diego Project Lead Call for Nominations
Date: Thu, Jun 13, 2019 3:51 PM
 
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
 

cf-networking-release & silk-release v2.23.0 published

Aidan Obley
 

The Networking Program has released silk-release 2.23.0 and cf-networking-release 2.23.0.

cf-networking-release

Release Highlights

  • golang version bumped to 1.12.6 story
  • golang version is now discoverable in docs [story]
  • Default values for database connections have been updated to reduce pressure on the database story
  • Dynamic Egress ping tests can be disabled when running Networking Acceptance Tests to support environments that prevent ping requests story
  • Increase timeout for fixture apps to start in Networking Acceptance Tests to better support small footprint environments story
  • Policy Server API now returns X-XSS-Protection header story

Manifest Property Changes

Job Property 2.22.0 Default 2.23.0 Default
policy-server max_idle_connections 200 10
policy-server-internal max_idle_connections 200 10

silk-release

Release Highlights

  • golang version bumped to 1.12.6 story
  • golang version is now discoverable in docs story
  • Default values for database connections and silk daemon polling have been updated to reduce pressure on the database story
  • Silk accurately calculates cidr pools for some cidr ranges story
  • vxlan-policy-agent fails fast when unable to mount container-metadata dir story
  • silk-daemon drain points to the correct pid file story
  • Bumped containernetworking/plugins dependency for latest fixes story

Manifest Property Changes

Job Property 2.22.0 Default 2.23.0 Default
silk-controller max_idle_connections 200 10
silk-daemon lease_poll_interval_seconds 5 30

Regards,
The Networking Program

Unconference at Den Haag - Talks and Sponsors Please!

Daniel Jones
 

Hi all,

The Unconference will return at CF Summit Europe 2019, the night before the first day of the summit (Tuesday 10th September, 6pm). If you want to attend, please register so we know how much food and drink to procure.

We'll have talks (submit proposals please!), and more importantly open space discussions (suggest topics too, please) where you can chat with peers about the hottest issues in the ecosystem.

By now, y'all will know if your talks were accepted for the summit proper. At the Unconference we want to give talks that weren't accepted a second chance, along with talks that are off-the-wall. The Unconference is also a great friendly crowd for new speakers - in Philadelphia we had some first-timers give a staggeringly good talk.

We're looking for sponsors too. At the last EU Unconference 20% of the entire summit audience attended, so it's a really cost-effective way of reaching the community. Contact Ivana Scott (ivana.scott@...) and Sara Lenz (slenz@...) for more details on sponsor packages.


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

FINAL REMINDER: CAB call for June is next week Wednesday 19th @ 8a Pacific

Michael Maximilien
 

FYI...

Change in agenda: Talk by Dr Nic Williams of Stark & Wayne entitled "Distributing sidecars with buildpacks" [2]

Zoom soon. Best,

dr.max
ibm ☁️
silicon valley, ca
maximilien.org

using IBM Verse

[2] https://gist.github.com/drnic/28ba8d0dc8e91bfdc47e53916d6cdb56

---------- Forwarded message ---------
From: Michael Maximilien <maxim@...>
Date: Thu, Jun 13, 2019 at 1:18 PM
Subject: [cf-dev] REMINDER: CAB call for June is next week Wednesday 19th @ 8a Pacific
To: < cf-dev@...>

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
 

#java #springboot #java #springboot

rajkinra@...
 

Please advise on the best approach to specify an external directory folder for use by springboot application to store business data (such as images).  The following attempt to do so far did not work:  By adding it to the User Provided JAVA_OPTS Environment Variable (using the syntax:  -cp /myfoo ).  This did not work because PCF start command adds an additional -cp entry with the $PWD present working directory that appears to override (and mask) the user provided value of /myfoo.  

Re: #java #springboot #java #springboot

Warren, Paul <Paul.Warren@...>
 

You should take a look at CloudFoundry's Volume Service feature.  This feature allows you to bind NFS, or SMB volumes into your application containers.  

You may also want to take a look at Spring Content.  A project that allows you to quickly and easily create headless Content Services (with Spring Boot if you would like) for managing unstructured data such as; images, documents and movies, in any of a number of different types of storage including the filesystem (that you would use with the Volume Service feature).

You can reach out to the Volume Service team on slack #cf-persistence

HTH
_Paul 

CAPI V3 Deployment states

Scott Sisil
 

Hi All,

The CAPI team has been gathering feedback on how we communicate state of a rolling deployment through the V3 deployments resource.  After getting feedback from integrating client teams, we have generated a new proposal that defines a new approach to communicating a more robust status for deployment state.


We are seeking feedback over the next week from the community to help us finalize this proposal and move forward with implementation in the coming weeks.

Looking forward to your comments!

Thanks,
Scott Sisil

CAPI PM

Removing Consul support from capi-release

Tim Downey
 

Hello everyone!

As you're likely aware, in 2017 Cloud Foundry began moving away from using Consul for distributed locks and service discovery. Additionally, last year's release of cf-deployment 5.0.0 removed it as a default component of CF completely.

We have begun the process of removing Consul support from some of the jobs in capi-release, starting with the cc-uploader. This means that as of the next capi-release (1.83.0), staging will no longer work in deployments that are relying on Consul for discovery. If you're using cf-deployment (BOSH DNS) or some other mechanism for service discovery this should not cause any issues.

Best,
Tim Downey, Connor Braa, and the CAPI Team

Re: Announcement: Planned Deprecation of the v6 cf CLI

Guillaume Berche
 

Hi Abby,

It seems that the notification URL [1] mentionned into your email isn't accessible to the OSS community. Can you please share its content if its different from the cf-dev@ announcement?

Thanks in advance,

Guillaume.

On Fri, May 31, 2019 at 2:20 AM Abby Chau <achau@...> wrote:
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