cf-dev@lists.cloudfoundry.org | Discontinuing Distribution of the Offline Buildpacks

Home Messages Hashtags Subgroups

Date Date 1 - 3 of 3

Discontinuing Distribution of the Offline Buildpacks

Stephen Levine #6857 Hi All, As a reminder, new buildpack BOSH releases created after June 1, 2017 will have this change. Preparing for this change might include: 1. Making sure that your pipelines and/or CF deployments allow internet access during staging, if you plan to switch to the online buildpacks 2. Making sure that you can build and install the offline buildpacks, if you plan to continue using the offline buildpacks Thanks, Stephen toggle quoted message Show quoted text On Wed, Apr 26, 2017 at 2:38 PM, Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, After June 1, 2017, new releases created in the following buildpack BOSH release repositories will not supply “offline” or “cached” buildpacks that are packaged with their dependencies (ex. language interpreters, compilers). These BOSH releases will instead supply “online” or “uncached” buildpacks that require an internet connection when staging Cloud Foundry apps. https://github.com/cloudfoundry/dotnet-core-buildpack-release https://github.com/cloudfoundry/go-buildpack-release https://github.com/cloudfoundry/nodejs-buildpack-release https://github.com/cloudfoundry/php-buildpack-release https://github.com/cloudfoundry/python-buildpack-release https://github.com/cloudfoundry/ruby-buildpack-release https://github.com/cloudfoundry/staticfile-buildpack-release https://github.com/cloudfoundry-incubator/hwc-buildpack-release The following releases are already “online” or “uncached,” and will not change. https://github.com/cloudfoundry/binary-buildpack-release https://github.com/cloudfoundry/java-buildpack-release The following releases will no longer be maintained, and will eventually move to the attic. https://github.com/cloudfoundry/java-offline-buildpack-release These changes will also apply to the corresponding release in bosh.io for each of these repositories. In addition, we will cease to publish “offline” or “cached” versions of the buildpacks attached to Github release notes. Online versions will be made available in their place. Instructions for building the offline buildpacks are available in the README.md file in each buildpack repository. Once built, offline buildpacks may contain proprietary dependencies that may require distribution licensing and/or export control measures to redistribute. Thanks, Stephen On Tue, Apr 11, 2017 at 11:35 AM, Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, Ben and I will provide more details about this transition in the near future. The current plan is to provide online buildpack BOSH releases to replace the offline buildpack BOSH releases, and to ship only online buildpacks in cf-release. Thanks, Stephen On Tue, Apr 11, 2017 at 11:20 AM, Chip Childers < cchilders(a)cloudfoundry.org> wrote: The Cloud Foundry Foundation strives to keep Cloud Foundry both open source and tailored to enterprise needs. Occasionally this is not straightforward, and requires us to change the way we make Cloud Foundry available to downstream distributions and open source users. Currently, the buildpack project teams distribute the official Cloud Foundry buildpacks on Github and bosh.io as pre-packaged bundles that include all of their dependencies, such as language interpreters and compilers. These offline buildpacks do not require an internet connection when they are used to push Cloud Foundry apps. The project teams package these offline buildpacks and make them available to encourage downstream distributions to include the unmodified, official buildpacks wherever possible. This promotes a consistent experience for developers across different Cloud Foundry distributions. Recently, the CFF has clarified its guidance to project teams with regard to the distribution of proprietary software [1]. Since the buildpacks include integrations with proprietary agent software, we need to change our approach to buildpack distribution. We will soon cease to package and distribute the offline buildpacks. Instead, we will publish instructions for downstream consumers to package the offline buildpacks themselves. Organizations who wish to distribute the offline buildpacks will be responsible for any required licensing or export compliance obligations. The buildpack project teams will publish and maintain a public list of these integrations to make this process easier. We still encourage downstream distributions to include the official buildpacks with minimal changes where possible, and to work with the Cloud Foundry Buildpacks team to integrate any changes they require upstream into the official buildpacks. I've CC'ed Ben Hale (Java Buildpack Lead) and Stephen Levine (Core Buildpacks Lead), who can help answer any questions about this change. [1] https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cl oudfoundry.org/thread/PLV44TLOBQVS7UEHRPQFCXPJMVQIA3T3/ -- Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815 <(267)%20250-0815> attachment.html attachment.html
More All Messages By This Member
Peter Dotchev <dotchev@...> #6861 Hi, Should we expect some performance change with the switch from offline to online buildpacks? BR, Peter toggle quoted message Show quoted text On Wed, May 31, 2017 at 6:42 PM Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, As a reminder, new buildpack BOSH releases created after June 1, 2017 will have this change. Preparing for this change might include: 1. Making sure that your pipelines and/or CF deployments allow internet access during staging, if you plan to switch to the online buildpacks 2. Making sure that you can build and install the offline buildpacks, if you plan to continue using the offline buildpacks Thanks, Stephen On Wed, Apr 26, 2017 at 2:38 PM, Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, After June 1, 2017, new releases created in the following buildpack BOSH release repositories will not supply “offline” or “cached” buildpacks that are packaged with their dependencies (ex. language interpreters, compilers). These BOSH releases will instead supply “online” or “uncached” buildpacks that require an internet connection when staging Cloud Foundry apps. https://github.com/cloudfoundry/dotnet-core-buildpack-release https://github.com/cloudfoundry/go-buildpack-release https://github.com/cloudfoundry/nodejs-buildpack-release https://github.com/cloudfoundry/php-buildpack-release https://github.com/cloudfoundry/python-buildpack-release https://github.com/cloudfoundry/ruby-buildpack-release https://github.com/cloudfoundry/staticfile-buildpack-release https://github.com/cloudfoundry-incubator/hwc-buildpack-release The following releases are already “online” or “uncached,” and will not change. https://github.com/cloudfoundry/binary-buildpack-release https://github.com/cloudfoundry/java-buildpack-release The following releases will no longer be maintained, and will eventually move to the attic. https://github.com/cloudfoundry/java-offline-buildpack-release These changes will also apply to the corresponding release in bosh.io for each of these repositories. In addition, we will cease to publish “offline” or “cached” versions of the buildpacks attached to Github release notes. Online versions will be made available in their place. Instructions for building the offline buildpacks are available in the README.md file in each buildpack repository. Once built, offline buildpacks may contain proprietary dependencies that may require distribution licensing and/or export control measures to redistribute. Thanks, Stephen On Tue, Apr 11, 2017 at 11:35 AM, Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, Ben and I will provide more details about this transition in the near future. The current plan is to provide online buildpack BOSH releases to replace the offline buildpack BOSH releases, and to ship only online buildpacks in cf-release. Thanks, Stephen On Tue, Apr 11, 2017 at 11:20 AM, Chip Childers < cchilders(a)cloudfoundry.org> wrote: The Cloud Foundry Foundation strives to keep Cloud Foundry both open source and tailored to enterprise needs. Occasionally this is not straightforward, and requires us to change the way we make Cloud Foundry available to downstream distributions and open source users. Currently, the buildpack project teams distribute the official Cloud Foundry buildpacks on Github and bosh.io as pre-packaged bundles that include all of their dependencies, such as language interpreters and compilers. These offline buildpacks do not require an internet connection when they are used to push Cloud Foundry apps. The project teams package these offline buildpacks and make them available to encourage downstream distributions to include the unmodified, official buildpacks wherever possible. This promotes a consistent experience for developers across different Cloud Foundry distributions. Recently, the CFF has clarified its guidance to project teams with regard to the distribution of proprietary software [1]. Since the buildpacks include integrations with proprietary agent software, we need to change our approach to buildpack distribution. We will soon cease to package and distribute the offline buildpacks. Instead, we will publish instructions for downstream consumers to package the offline buildpacks themselves. Organizations who wish to distribute the offline buildpacks will be responsible for any required licensing or export compliance obligations. The buildpack project teams will publish and maintain a public list of these integrations to make this process easier. We still encourage downstream distributions to include the official buildpacks with minimal changes where possible, and to work with the Cloud Foundry Buildpacks team to integrate any changes they require upstream into the official buildpacks. I've CC'ed Ben Hale (Java Buildpack Lead) and Stephen Levine (Core Buildpacks Lead), who can help answer any questions about this change. [1] https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/PLV44TLOBQVS7UEHRPQFCXPJMVQIA3T3/ -- Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815 <(267)%20250-0815> attachment.html attachment.html
More All Messages By This Member
Stephen Levine #6862 Hi Peter, The only change is that buildpacks will now reach out to the internet to download language dependencies. For example, staging a Python app will require the Python buildpack to download Python from the CloudFront-distributed S3 bucket at buildpacks.cloudfoundry.org. Our testing indicates that the performance impact of this change is minimal, as long a reasonably fast internet connection is available in the application staging container. Thanks, Stephen toggle quoted message Show quoted text On Thu, Jun 1, 2017 at 12:25 AM, Peter Dotchev <dotchev(a)gmail.com> wrote: Hi, Should we expect some performance change with the switch from offline to online buildpacks? BR, Peter On Wed, May 31, 2017 at 6:42 PM Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, As a reminder, new buildpack BOSH releases created after June 1, 2017 will have this change. Preparing for this change might include: 1. Making sure that your pipelines and/or CF deployments allow internet access during staging, if you plan to switch to the online buildpacks 2. Making sure that you can build and install the offline buildpacks, if you plan to continue using the offline buildpacks Thanks, Stephen On Wed, Apr 26, 2017 at 2:38 PM, Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, After June 1, 2017, new releases created in the following buildpack BOSH release repositories will not supply “offline” or “cached” buildpacks that are packaged with their dependencies (ex. language interpreters, compilers). These BOSH releases will instead supply “online” or “uncached” buildpacks that require an internet connection when staging Cloud Foundry apps. https://github.com/cloudfoundry/dotnet-core-buildpack-release https://github.com/cloudfoundry/go-buildpack-release https://github.com/cloudfoundry/nodejs-buildpack-release https://github.com/cloudfoundry/php-buildpack-release https://github.com/cloudfoundry/python-buildpack-release https://github.com/cloudfoundry/ruby-buildpack-release https://github.com/cloudfoundry/staticfile-buildpack-release https://github.com/cloudfoundry-incubator/hwc-buildpack-release The following releases are already “online” or “uncached,” and will not change. https://github.com/cloudfoundry/binary-buildpack-release https://github.com/cloudfoundry/java-buildpack-release The following releases will no longer be maintained, and will eventually move to the attic. https://github.com/cloudfoundry/java-offline-buildpack-release These changes will also apply to the corresponding release in bosh.io for each of these repositories. In addition, we will cease to publish “offline” or “cached” versions of the buildpacks attached to Github release notes. Online versions will be made available in their place. Instructions for building the offline buildpacks are available in the README.md file in each buildpack repository. Once built, offline buildpacks may contain proprietary dependencies that may require distribution licensing and/or export control measures to redistribute. Thanks, Stephen On Tue, Apr 11, 2017 at 11:35 AM, Stephen Levine <slevine(a)pivotal.io> wrote: Hi All, Ben and I will provide more details about this transition in the near future. The current plan is to provide online buildpack BOSH releases to replace the offline buildpack BOSH releases, and to ship only online buildpacks in cf-release. Thanks, Stephen On Tue, Apr 11, 2017 at 11:20 AM, Chip Childers < cchilders(a)cloudfoundry.org> wrote: The Cloud Foundry Foundation strives to keep Cloud Foundry both open source and tailored to enterprise needs. Occasionally this is not straightforward, and requires us to change the way we make Cloud Foundry available to downstream distributions and open source users. Currently, the buildpack project teams distribute the official Cloud Foundry buildpacks on Github and bosh.io as pre-packaged bundles that include all of their dependencies, such as language interpreters and compilers. These offline buildpacks do not require an internet connection when they are used to push Cloud Foundry apps. The project teams package these offline buildpacks and make them available to encourage downstream distributions to include the unmodified, official buildpacks wherever possible. This promotes a consistent experience for developers across different Cloud Foundry distributions. Recently, the CFF has clarified its guidance to project teams with regard to the distribution of proprietary software [1]. Since the buildpacks include integrations with proprietary agent software, we need to change our approach to buildpack distribution. We will soon cease to package and distribute the offline buildpacks. Instead, we will publish instructions for downstream consumers to package the offline buildpacks themselves. Organizations who wish to distribute the offline buildpacks will be responsible for any required licensing or export compliance obligations. The buildpack project teams will publish and maintain a public list of these integrations to make this process easier. We still encourage downstream distributions to include the official buildpacks with minimal changes where possible, and to work with the Cloud Foundry Buildpacks team to integrate any changes they require upstream into the official buildpacks. I've CC'ed Ben Hale (Java Buildpack Lead) and Stephen Levine (Core Buildpacks Lead), who can help answer any questions about this change. [1] https://lists.cloudfoundry.org/archives/list/cf-dev@ lists.cloudfoundry.org/thread/PLV44TLOBQVS7UEHRPQFCXPJMVQIA3T3/ -- Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815 <(267)%20250-0815> attachment.html attachment.html
More All Messages By This Member

1 - 3 of 3

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms