Date   

IMPORTANT NOTICE: [python-buildpack] End of support for Python versions 2.7.x after 2020-01-01

Kashyap Vedurmudi <kvedurmudi@...>
 

The first release of the Python buildpack after January 1, 2020 will no longer include Python versions 2.7.x. These Python versions will no longer be supported upstream.[1] Please migrate your Python apps to supported versions of Python before that time.


As 2.7.x is the current default for the Python version in the buildpack, the default Python version will be updated to 3.8.x as a part of this removal. If you’d like to use a different Python version, please configure your application to select that version[2]. As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel.


Please note that as miniconda2 depends on Python 2.X, miniconda2 will also be removed as a part of this release. Miniconda3 is currently available in the buildpack.


[1] https://www.python.org/dev/peps/pep-0373/

[2] https://docs.cloudfoundry.org/buildpacks/python/index.html#runtime



Thanks,

Kashyap Vedurmudi, CF Buildpacks PM



IMPORTANT NOTICE: [nodejs-buildpack] End of support for Node.js versions 8.x after 2020-01-05

Elliott Shanks
 

The first release of the Node.js buildpack after January 5, 2020 will no longer include Node.js versions 8.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.


Note: While the default version of Node.js in the Node.js buildpack is 10.x, it is recommended that you ensure your Node.js applications are not specifying a Node.js version of 8.x in either a buildpack.yml, .nvmrc, or package.json files. As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel.


[1] https://nodejs.org/en/about/releases/


Thanks,

Elliott Shanks, CF Buildpacks PM



Routing Release 0.196.0

Keshav Sharma <ksharma@...>
 

Hello CF community, 

Release Highlights

  • Platform Operators can now know the maximum impact from a single component on their database details

Application Developers can see metrics that help them more easily determine if latency is coming from the gorouter or their application details

  • Platform Operators can now leverage jq on the router vm to debug more easily details

  • Application Developers can leverage w3c trace context to experience better:

    • Visibility into the behavior of distributed applications
    • Management of micro-service applications details

      Manifest Property Changes

Job Property 0.195.0 Default 0.196.0 Default
gorouter tracing.enable_w3c Did Not Exist False
gorouter tracing.w3c_tenant_id Did Not Exist “”

CF-Bosh Networking



CF CLI 6.48.0 released today

Mukesh Gadiya
 

Hi everyone,

The CF CLI team released v6.48.0 today which includes improved behavior of random-route flag, few bug fixes and and windows installer update. 

Please reach out to us in cloudfoundry #cli slack channel if you have any questions. Thanks.

Best,
CF CLI team


IMPORTANT NOTICE: [.NET Core buildpack] End of support for .NET Core versions 2.2.x after 2020-01-04

Elliott Shanks
 

The first release of the .NET Core buildpack after January 4, 2020 will no longer include .NET Core versions 2.2.x. These .NET Core versions will no longer be supported upstream.[1] Please migrate your .NET Core apps to supported versions of .NET Core before that time.


Additionally, the default version of .NET Core will change from 2.2.x to 3.1.x at this time.


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


[1] https://dotnet.microsoft.com/platform/support/policy/dotnet-core


Thanks,

Elliott Shanks, CF Buildpacks PM



Re: Eirini is 1.0!

Julian Fischer
 

I am delighted. Congratulations!

Am 12.11.2019 um 12:45 schrieb Julz Friedman <julz.friedman@...>:

Hi cloud foundries, 

We’re happy to announce the Eirini team has hit our internal “1.0” milestone and shipped a release marked as 1.0 [0]!.

This means we believe the core Eirini component is stable and ready to use (although there are some optional features - such as the new v3 API, tasks and container-to-container networking support - that are only available in the Diego backend, for now). 

This work would not have been possible without contributions from across the Cloud Foundry community, but especially from IBM, Pivotal, SAP, SUSE and Google.

# What is Eirini?

Eirini brings the simplicity of `cf push` to Kubernetes. Kubernetes has quickly become the de-facto standard container scheduler across the cloud community, and now - via Eirini - Cloud Foundry users can take advantage of this powerful technology to put their containers on servers. Even better (in my opinion anyway), Kubernetes users can now try out the Cloud Foundry developer experience in a native, easy and interoperable way -- which means: less YML, more code.

# How can I try Eirini / Cloud Foundry on Kubernetes?

Eirini-based Cloud Foundry is already available commercially as a technology preview from IBM Cloud, SUSE and Pivotal. You can also deploy your own Eirini from the open-source bits by following the instructions in the eirini-release repository [1] (these are still a little harder than we'd like them to be, but there's lots of work going on in the wider eiriniverse to make them better!) - and let us know how you get on (see next paragraph!).

# Talking to us:

We’re available in Cloud Foundry slack in the #eirini-dev and #cf-for-k8s channels, and there’s a cross-community meeting [2] discussing CF on Kubernetes and the broader “Eiriniverse” every second Tuesday which you can find in the CF Community Calendar [3] - everyone is very very welcome to join and help steer the direction of the projects.

Thanks y’all-
The Eirini Team,

[3]: https://www.cloudfoundry.org/community-calendar/




Upcoming changes to bosh-linux-stemcell-builder

Aakash Shah
 

Hey all,
In an effort to have the bosh-linux-stemcell-builder be more maintainable for the bosh team, we are hoping to remove build targets not explicitly maintained by the bosh team. These include the following:

* OpenSuse
* PhotonOS
* Red Hat Enterprise Linux (RHEL)
* CentOS
* Ubuntu Trusty
* PowerPC

The work of removing support for these targets is currently happening on "wip/reduce-build-targets", with the goal of bringing it into the "master" branch. This only impacts forward development, and should not impact past branches. For any consumers of the above build targets, we'd love to hear from you in the #bosh-core-dev channel in Cloud Foundry slack.

We will continue cutting releases for ubuntu-xenial lines and centos 3763.x, per our standard support policy.

Context:
Feature work has been difficult on the bosh-linux-stemcell-builder repository as it's housed so much logic. Maintaining compatibility across all of the build targets has made stages (written in bash) very complicated. As we explore making bigger improvements to the builder, we're looking to lessen the builder's responsibility

- Aakash, bosh team


Re: Announcing cf-abacus end of life

Michael Maximilien
 

Thanks for the summary email and blog post Hristo and for all of your work and dedication to this project.

Like any projects, it had its heyday and moments of excitement. And now retirement.

I know at least one person indicated interest during the last CAB call, perhaps they will reach out.

In any case, many thanks again and happy holiday season. Best,

Max

On Tue, Nov 26, 2019 at 12:59 PM Hristo Iliev <hsiliev@...> wrote:
Hi cf-dev,

Abacus was started in 2015 by IBM with SAP joining shortly after. Since several years SAP is the only contributor, as it used Abacus in production.

Most users do not find the project robust and cost effective solution. Several reasons for this are outlined in this blog. We started solving some of the problems as part of version 2, but in the meantime our focus as a company has shifted.

As a result of all this, there is no activity around the project for more than a year, so we moved Abacus to the attic to reach its end of life.

If this still is a topic you are interested in, please reach out to us by replying to this mail or contacting me directly.

Best regards,
Hristo Iliev




Announcing cf-abacus end of life

Hristo Iliev
 

Hi cf-dev,

Abacus was started in 2015 by IBM with SAP joining shortly after. Since several years SAP is the only contributor, as it used Abacus in production.

Most users do not find the project robust and cost effective solution. Several reasons for this are outlined in this blog. We started solving some of the problems as part of version 2, but in the meantime our focus as a company has shifted.

As a result of all this, there is no activity around the project for more than a year, so we moved Abacus to the attic to reach its end of life.

If this still is a topic you are interested in, please reach out to us by replying to this mail or contacting me directly.

Best regards,
Hristo Iliev


Routing Release 0.195.0

Keshav Sharma <ksharma@...>
 

Hello CF community,

Release Highlights

  • Platform Operators can continue routing to applications and system components even during a control plane outage details

  • Application Developers can ensure that their Java apps communicate to the gorouter successfully and do not experience any error caused due to TLS1.3 details

Manifest Property Changes

JobProperty0.193.0 Default0.195.0 Default
gorouterrouter.prune_all_stale_routesdid not existfalse
goroutertls1.3did not existfalse

CF-Bosh Networking


Re: Networking - http ingress routing

Dr Nic Williams <drnicwilliams@...>
 

This is fabulous seeing some cf-on-k8s native functionality.

Nic
--
Dr Nic Williams
Stark & Wayne LLC
+61 437 276 076
twitter @drnic


Networking - http ingress routing

Wa Gao
 

Hello cf-dev!


The cf-k8s-networking team ship a new feature leveraging Istio and Envoy technology that App Developer can rely on the platform to provide http ingress routing to the workload on Cloud Foundry running on Kubernetes details

 

Please reach out if you have any questions. Thanks.

 

Regards,


--

Wa Gao (Claire) | Senior Product Manager, Networking | Pivotal

Phone: 508-615-8644 | Email: wgao@...

 


Re: CAB call for November 2019 is next week Wednesday 20th @ 8a Pacific - LAST CAB call for 2019!

Michael Maximilien
 

Hello from rainy San Diego, CA.

This is a final REMINDER... call in a few hours, see below. No planned talks, just updates, and chit chat, so might be done early.

Questions for you: what shall we do do with these calls in 2020? What should we change (if any)? Format? Frequency? Lead?

Zoom soon. Best,

Max

On Wed, Nov 13, 2019 at 4:03 PM Michael Maximilien <maxim@...> wrote:
FYI...
 
CAB call for November 2019 is next week Wednesday 20th @ 8a Pacific.
 
If you have a talk, a project, or would like to present something, please contact me ASAP.
 
Reply here (to me) or ping me on Slack. Best,

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

--
dr.max Sent from my iPhone http://maximilien.org


Re: Anyone want to take over cf-zsh autocomplete?

Danny Rosen
 

Thanks Chip. This plugin has had a history of maintainers, thanks to Ferran Rodenas (@ferdy) who originally authored it. As an added bonus, once the plugin is up to date and running feel free to put a pull into https://github.com/zsh-users/zsh-completions/blob/master/src/_cf as well. 


On Mon, Nov 18, 2019 at 1:10 PM Chip Childers <cchilders@...> wrote:
Hey folks,

Danny Rosen had built a zsh autocomplete for CF tool, and is looking to see if anyone in the community wants to take over maintaining it... https://github.com/Dannyzen/cf-zsh-autocomplete-plugin

If you want to take it on, or if a couple of people want to share the responsibility, shout out. I can help move it into the cloudfoundry-community GH org if the volunteer(s) want, or you can do with it as you want. :)

Chip Childers, CTO
Cloud Foundry Foundation



Anyone want to take over cf-zsh autocomplete?

Chip Childers <cchilders@...>
 

Hey folks,

Danny Rosen had built a zsh autocomplete for CF tool, and is looking to see if anyone in the community wants to take over maintaining it... https://github.com/Dannyzen/cf-zsh-autocomplete-plugin

If you want to take it on, or if a couple of people want to share the responsibility, shout out. I can help move it into the cloudfoundry-community GH org if the volunteer(s) want, or you can do with it as you want. :)

Chip Childers, CTO
Cloud Foundry Foundation


Announcing new Cloud Foundry Buildpacks

Elliott Shanks
 

TL;DR:


In the coming weeks, the CF Buildpacks team will be releasing a new Node.js buildpack, composed of modular buildpacks, that implements the Cloud Native Buildpacks (CNB) API. This buildpack can be used with any platform that supports CNB.


A buildpack release that contains a compatibility layer for use on the Cloud Foundry Application Runtime can be found in the nodejs-cnb repo. Add the buildpack to your list of buildpacks and `cf push` to begin building Node.js applications with the new Node.js buildpack.


Introduction to new buildpacks

Over the past year, the buildpacks team has worked to build the next set of Cloud Foundry buildpacks using the Cloud Native Buildpacks (CNB) API. In the coming weeks, we will be releasing the Node.js CNB. This new buildpack is compatible with any CNB platform (such as the pack CLI or kpack) and additionally contains a limited compatibility layer for the Cloud Foundry Application Runtime. (Note that the compatibility layer produces a droplet, while CNB platforms output special, rebasable OCI images.)


What are Cloud Native Buildpacks?

Cloud Native Buildpacks, a CNCF sandbox project, uses a modular approach to building applications by splitting major dependencies and operations on applications into their own dedicated CNBs. What was once the Node.js buildpack is now a combination of the node-engine, yarn, and npm CNBs. This allows for a transparent build process that is easier to debug when a build fails. CNB also employs better caching and data deduplication, and as a result, faster builds and faster deploys on platforms that support OCI images. 


Note: Due to the modular nature of CNB, the new Node.js buildpack does not currently include certain external integration helpers, such as those for APM agents. It has been difficult to manage and test these integrations, and we plan to shift towards modular integration CNBs that are maintained outside the project by integration authors and platform vendors.

Using CNBs on Cloud Foundry Application Runtime

To use the new Node.js CNB, it is as simple as grabbing the shimmed release artifact from the nodejs-cnb repo and adding the buildpack to your list of buildpacks on your foundation. 


Note: Because the CNB API results in an OCI image, a compatibility (shim) is required in order to translate the new Cloud Native Buildpacks API to the existing CF Buildpack API. This compatibility layer is less performant than CNB, but fully supports CF multi-buildpack mode when multiple CNBs are specified, by translating it to CNB’s native modular buildpack mode. Additionally, it provides compatibility with older supply-only CF buildpacks, as long as those buildpacks precede the CNBs.



To add the new buildpack to CFAR:

cf create-buildpack <buildpack-name> <path/to/downloaded_shimmed_nodejs_buildpack> <detection order>


If you want to cf push without -b <buildpack-name> use a <detection order> number smaller than the current Node.js buildpack detection order number during `create-buildpack`. To see the detection order of buildpacks run `cf buildpacks`.


Ways to Provide Feedback

The buildpacks team would love to gather feedback from the CF community about your experience using the Node.js CNB when it is released. As always, you can drop into the Cloud Foundry slack in the #buildpacks channel to reach out. 


We hope that you are as excited as we are about the new future of buildpacks.


Respectfully,

CF Buildpacks Team



Re: Eirini is 1.0!

Troy Topnik
 

Whenrini? Nowrini? Forrealrini?

Congratulations!

TT

--
Troy Topnik
Senior Product Manager, 
SUSE Cloud Application Platform 
troy.topnik@...
 


IMPORTANT NOTICE: [php-buildpack] End of support for PHP versions 7.1.x after 2019-12-14

Elliott Shanks
 


The first release of the PHP buildpack after December 14, 2019 will no longer include PHP versions 7.1.x. These PHP versions will no longer be supported upstream.[1] Please migrate your PHP apps to supported versions of PHP before that time.


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


[1] https://www.php.net/supported-versions.php


Thanks,

Elliott Shanks, CF Buildpacks PM



Re: CF Application Runtime PMC: Garden-Windows Project Lead Call for Nominations

Eric Malm <emalm@...>
 

Hi, everyone,

Pivotal is nominating Kartik Lunkad for the Garden-Windows Project Lead in the Application Runtime PMC.

Kartik is a Staff Product Manager at Pivotal working closely with the Garden-Windows team as part of driving the product vision and strategy for .NET and Windows investments in Pivotal products.

Previously, Kartik was a Platform Architect at Pivotal focused on helping Fortune-100 enterprise customers transform their technology teams to build and deliver software faster with Cloud Foundry. Prior to Pivotal, Kartik worked as a software engineer at Citrix, a technology consultant at PwC, and an operational fellow at Make A Difference.

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

Thanks,
Eric Malm

On Wed, Nov 13, 2019 at 4:50 PM Eric Malm <emalm@...> wrote:
Hi, everyone,

William Martin, the lead for the Garden-Windows project within the Application Runtime PMC, is stepping down from the project, as he is now focused on responsibilities internal to Pivotal. We thank him for his service.

The Garden-Windows team, located in New York, 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 Monday, November 25, 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 Application Runtime PMC: Garden-Windows Project Lead Call for Nominations

Eric Malm <emalm@...>
 

Hi, everyone,

William Martin, the lead for the Garden-Windows project within the Application Runtime PMC, is stepping down from the project, as he is now focused on responsibilities internal to Pivotal. We thank him for his service.

The Garden-Windows team, located in New York, 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 Monday, November 25, 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

581 - 600 of 9369