Date   

CAB Calls — Cancelled

Ram Iyengar
 

Dear Cloud Foundry community,

Starting Jan 2023, we have decided to cancel CAB calls. We are exploring other formats to be able to showcase upcoming technology to the larger CF community. We will write back to you once we have concrete plans. 

In case you would like to be part of a discussion about this, please feel free to write back to me at ram@... or ping me on the CF Slack instance (@ramiyengar). 

Regards,
Ram

P.S. the event has been removed from the Community Calendar. In case it is still on your calendars, please remove the CAB Call event manually. 


Re: CAB Call: 2022 Special Edition - 23rd Dec 2022

Ram Iyengar
 

Hey all,

We will be using the following Zoom link for the CAB call: https://zoom.us/j/99017750021?pwd=L3E0QnpyT3hHYTgxemMrMXJnZnFyZz09

On Thu, Dec 22, 2022 at 7:25 PM Ram Iyengar <riyengar@...> wrote:
Hey CF Community,

Please join us for a special CAB call tomorrow. We will be going over a bunch of updates to summarize the end of a rather eventful year. We will also be sharing some details about what to look forward to in the upcoming year.

Date: 23rd Dec 2022
Time: 11AM Eastern/8AM Pacific/4PM London/5PM CET

We definitely invite comments and suggestions about the various activities undertaken by the community. The more folks can join and engage us, the better!

Regards,
Ram Iyengar
Chief Evangelist, CFF


CAB Call: 2022 Special Edition - 23rd Dec 2022

Ram Iyengar
 

Hey CF Community,

Please join us for a special CAB call tomorrow. We will be going over a bunch of updates to summarize the end of a rather eventful year. We will also be sharing some details about what to look forward to in the upcoming year.

Date: 23rd Dec 2022
Time: 11AM Eastern/8AM Pacific/4PM London/5PM CET

We definitely invite comments and suggestions about the various activities undertaken by the community. The more folks can join and engage us, the better!

Regards,
Ram Iyengar
Chief Evangelist, CFF


Heads Up: The ginkgo CLI will be removed from the cloudfoundry/cf-deployment-concourse-tasks image moving forward

Carson Long
 

Dear CF Devs,

 

The ARD working group will soon release a cloudfoundry/cf-deployment-concourse-tasks image that no longer includes an installed ginkgo CLI. [1]

 

We have successfully migrated most of our projects to v2 of the Ginkgo module [2], which has been out for long enough that we hope most other projects have been done the same. Therefore, we started using v2 of the ginkgo CLI as well. However, we couldn't just install the latest version of the ginkgo CLI in our docker image, as, ever since Ginkgo v2.3.0, the CLI and the local library versions are required to be in sync. This has led us to manage our ginkgo CLI version as a typical Golang tool dependency and install/use it on-demand in our projects. [3]

 

If your project uses the latest tag of the cloudfoundry/cf-deployment-concourse-tasks image and hasn't yet migrated to Ginkgo v2, then you may want to consider locking to an older tag of the image until you complete your Ginkgo v2 upgrade or adjust your workflows accordingly.

 

Best regards,

Carson Long

 

[1] https://github.com/cloudfoundry/cf-deployment-concourse-tasks/pull/127

[2] https://onsi.github.io/ginkgo/MIGRATING_TO_V2

[3] https://onsi.github.io/ginkgo/#recommended-continuous-integration-configuration


Welcome to Cloud Foundry Day! (tune in at 9am ET)

Chris Clark
 

Hi all, 

Today's the day! Welcome to Cloud Foundry Day 2022! 

For those of you who aren't here in person, you can register here for free. If you can't make the full day, check out the schedule here and drop in for sessions when you can. 
See you soon!
 


--
Chris Clark
Program Manager
Cloud Foundry Foundation


CAB call in 1 hour

Ram Iyengar
 

Just a reminder to folks that the CAB call for October starts in an hour. 

Our main topic for discussion is the Interoperator, which helps bridge the gap between Kubernetes operators and Cloud Foundry installations.
Change in date and time: THU Oct 20th 11 AM Eastern

The presentation is by Anoop Joseph Babu and Jintu Sebastian from the SAP Labs office in Bengaluru, India. They're both active contributors to several Cloud Foundry Services projects. 


One week until Cloud Foundry Day at KubeCon!

Chris Clark
 

Hello all, 

There's just one week left until Cloud Foundry Day 2022, our first in-person event in 3 years! I can't wait to see many of you in Detroit next week; it's been far too long. 

Reminder: for those of you who will be tuning in virtually, registration is FREE. Register here.

We've got a terrific lineup of talks this year on all things Cloud Foundry: Korifi, Paketo Buildpacks, App Runtime, BOSH, and community updates. There'll be general talks anyone can get something out of, as well as some technical deep-dives. Check out the schedule here.

Please reach out if you have any questions.  And, thank you to anynines and VMware for generously sponsoring the event!


--
Chris Clark
Program Manager
Cloud Foundry Foundation


Heads up: Jammy stemcell in cf-deployment is coming

Jochen Ehret
 

Dear CF Developers,

 

we will soon release a new major version of cf-deployment [1] which switches the default stemcell from Bionic [2] to Jammy [3]. From then on, we will run the cf-deployment release and evaluation process only with Jammy. If you have a custom CF deployment, you should check if an upgrade to Jammy is possible.

 

For Bionic, we will set up a basic validation which deploys a default CF installation and runs the CF Acceptance and Smoke tests. We will also provide an ops file to switch back the default stemcell to Bionic.

 

If you have questions, you can contact us in the cf-deployment Slack channel [4].

 

Best Regards,

 

  Application Runtime Deployments Working Group.

 

 

[1] https://github.com/cloudfoundry/cf-deployment

[2] https://bosh.cloudfoundry.org/stemcells/#ubuntu-bionic

[3] https://bosh.cloudfoundry.org/stemcells/#ubuntu-jammy

[4] https://cloudfoundry.slack.com/archives/C2U7KA7M4

 


Cloud Foundry Day schedule is live!

Chris Clark
 

Hello all,

I'm very happy to announce that the Cloud Foundry Day schedule is now live, and am looking forward to seeing you in Detroit (or virtually) on October 25th! 

Big thanks to anynines, SAP, and VMware for sponsoring this event and making this all happen.

Some reminders: 
  • If you haven't registered yet, especially folks who are coming in-person, please do! 
  • Hotels in Detroit are starting to book up, so make those reservations now
  • Please reach out with any questions.

--
Chris Clark
Program Manager
Cloud Foundry Foundation


Cloud Foundry Day CFP Extended

Chris Clark
 

Hi all, 

We've had a couple requests to extend the Cloud Foundry Day CFP a bit, so we're doing just that. You now have until next Tuesday, August 30th at midnight Pacific Time to submit. 





--
Chris Clark
Program Manager
Cloud Foundry Foundation
--
Chris Clark
Program Manager
Cloud Foundry Foundation


Cloud Foundry Day CFP closing Friday! And more...

Chris Clark
 

Hello all, 

A few reminders for Cloud Foundry Day: 

The CFP closes this Friday! Get those talks submitted! And, if there is a problem with getting your proposal in this week, please reach out and let me know and we'll do our best to accommodate. 

Also, if you have already registered for KubeCon, but haven't yet registered for CF Day, please add that to your registration. Or, if you haven't yet registered for KubeCon, please register for both at your earliest convenience. 

Lastly, a reminder that sponsorships close this September 2nd - please reach out if interested. 

Thank you! Looking forward to seeing you in Detroit. 

--
Chris Clark
Program Manager
Cloud Foundry Foundation


Final Call: Join the Cloud Foundry Day Program Committee

Ram Iyengar
 

Hello everyone - A reminder that today is the last day that we are seeking nominations to the Program Committee for Cloud Foundry Day. Please use this form to indicate your interest.

Being a part of the Program Committee is an opportunity to shape the messaging and ideas that will be presented on stage at Cloud Foundry Day this year. You can help shape the outward facing content put forth by the Cloud Foundry community.

Regards,
Ram Iyengar


Reminder: CAB call later today!

Ram Iyengar
 

Just a reminder for folks ... the CAB calf or August starts in roughly 30 minutes. In this edition, we're going to be hosting Matt Royal, who is going to talk to us about some of the internals of Korifi.

Please use this Zoom link to join the call: Join Zoom Meeting https://qarik.zoom.us/j/88435355853?pwd=WUpYb1V2UnhXRjFJMWdMN3plc01idz09

Remember - the most value out of these CAB calls is to have as many folks from the community join us and chime in with questions/comments/feedback. Please do take some time ot join us today if your schedule permits it.

Thanks!

- ram

p.s. The #cab channel on the Cloud Foundry Slack is always open for comments about CAB calls.


Re: i/o timemout on deployment on vCenter 7.1

Al West
 

I tried using the same VLAN and the directory and it completes now.
 


i/o timemout on deployment on vCenter 7.1

Al West
 

I am following 

VMware vSphere - Cloud Foundry BOSH

I get the following error.  I can ping the host but none of the end points seem to be up, for example port 22 or 6868

Deploying:

  Creating instance 'bosh/0':

    Waiting until instance is ready:

      Post "https://mbus:<redacted>@10.0.10.222:6868/agent": dial tcp 10.0.10.222:6868: i/o timeout

Exit code 1

 


Re: Buildpack deployment in cflinuxfs3 stack for AWS

Peter Burkholder
 

What we would need is a way for buildpack consumers like us, to build automation (in Concourse or anything similar) that warns the correct people in the enterprise for taking action when some Buildpack is discontinuing some language version
At cloud.gov, we email our customers when there's a newer buildpack available for their applications: https://github.com/cloud-gov/cg-buildpack-notify

The template (https://github.com/cloud-gov/cg-buildpack-notify/blob/main/templates/mail/notify.txt) includes a link to the release notes, so it's still an exercise for the developers on the receiving end to check on language version support.

Does that help or are you looking for something else?

-Peter

On Fri, Aug 12, 2022 at 5:42 AM Benjamin Gandon <benjamin@...> wrote:
Hi Carlos,

The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases
These need to be read regularly by a human for taking action when necessary, like when some language versions are discontinued.

For newer Paketo buildpacks, I’ve raised some similar concern in the Paketo Slack last year:

What we would need is a way for buildpack consumers like us, to build automation (in Concourse or anything similar) that warns the correct people in the enterprise for taking action when some Buildpack is discontinuing some language version. I don’t know if there has been any progress on this since last year.

Benjamin


Le 4 août 2022 à 10:54, Delgado, Carlos via lists.cloudfoundry.org <carlos.delgado02=sap.com@...> a écrit :

Hello team,
 
I am interested to know about communications whenever a new buildpack is deployed and available in AWS cflinuxfs3 stack, in order to adapt our projects timely fashion, I am interested in Nodejs buildpack in particular, since a new version has been released recently that removed Node 12 and affected our deployments.
 
Do you know by any chance if such communication exists?
 
Many thanks,
BR.
 
 
Carlos Delgado

DevOps Lead, Customer Success Automation ES

SAP ESPAÑA, S.A.
 Torre Diagonal Mar - B1 C/, 08019 Barcelona, Spain

T +34 93 483-3238, M +34 678 684650, E carlos.delgado02@...

 
Pflichtangaben/Mandatory Disclosure Statement:
 
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.  Sollten Sie
diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der
E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.
Vielen Dank.
 
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.  If you have received
this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform
us immediately and destroy the original transmittal.
Thank you for your cooperation
 
<image001.png>
<image002.jpg>
 



--
Peter Burkholder |  cloud.gov ISSO, compliance & security lead
please use cloud-gov-compliance@... for cloud.gov matters


Re: Buildpack deployment in cflinuxfs3 stack for AWS

Benjamin Gandon
 

That’s great, thanks for sharing Jim!

Benjamin


Le 12 août 2022 à 12:12, Conner UK, Jim via lists.cloudfoundry.org <jim.conner=fil.com@...> a écrit :

At my place of work, we have concourse jobs which sends us messages on our MS Teams channel whenever a new release appears. Maybe this will be useful for someone else too.
 
Here’s some sanitised snippets from our release-notification-pipeline.
 
***
resources:
- name: java-buildpack-release
  type: github-release
  source:
    user: cloudfoundry
    repository: java-buildpack
    release: true
    access_token: ((github_token))
 
- name: notify-new-java-buildpack-releases
  plan:
  - do:
    - in_parallel:
      - get: release-notifications-pipeline
      - get: release-repo
        resource: java-buildpack-release
        params:
          globs: [notthisthing] # because we only want to watch for tag changes & data, not the release tgz itself (proxy won't allow download of it)
        trigger: true
    - task: check-versions
      config:
        platform: linux
        inputs:
        - name: release-notifications-pipeline
        - name: release-repo
        image_resource:
          type: docker-image
          source:
            repository: ((any_docker_image_which_has_curl_and_jq))
            tag: latest
        run:
          path: cf-deployment-notifications/check_versions.sh
      params:
        RELEASE_NAME: java-buildpack
        TEAMS_WEBHOOK_URL: ((ms_teams_webhook_url))
    timeout: 15m
***
 
.. and the source for the check_versions.sh script.
 
***
#!/bin/bash
 
set -e
 
if [[ -f "release-repo/body" ]]; then
  split --line-bytes=7500 release-repo/body release-repo/release-body-
 
  for file in $(find release-repo -name "release-body-*" | sort )
  do
    request_body=$(jq -n --arg body "$(cat "${file}")" --arg title "New $RELEASE_NAME $(cat release-repo/version) release" '{title: $title, text: $body}')
    curl -if -X POST --data "${request_body}" -k "${TEAMS_WEBHOOK_URL}"
    rm "${file}"
  done
else
  request_body=$(jq -n --arg body "The author was too lazy to add a release note" --arg title "New $RELEASE_NAME $(cat release-repo/version) release" '{title: $title, text: $body}')
  curl -if -X POST --data "${request_body}" -k "${TEAMS_WEBHOOK_URL}"
fi
***
 
Jim
 
 
From: <cf-dev@...> on behalf of Benjamin Gandon <benjamin@...>
Reply to: "cf-dev@..." <cf-dev@...>
Date: Friday, 12 August 2022 at 10:42
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Buildpack deployment in cflinuxfs3 stack for AWS
 
Hi Carlos, The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases These need to be read regularly by a human for taking action when necessary, like when 
Hi Carlos,
 
The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases
These need to be read regularly by a human for taking action when necessary, like when some language versions are discontinued.
 
For newer Paketo buildpacks, I’ve raised some similar concern in the Paketo Slack last year:
 
What we would need is a way for buildpack consumers like us, to build automation (in Concourse or anything similar) that warns the correct people in the enterprise for taking action when some Buildpack is discontinuing some language version. I don’t know if there has been any progress on this since last year.
 
Benjamin
 


Le 4 août 2022 à 10:54, Delgado, Carlos via lists.cloudfoundry.org<carlos.delgado02=sap.com@...> a écrit :
 
Hello team,
 
I am interested to know about communications whenever a new buildpack is deployed and available in AWS cflinuxfs3 stack, in order to adapt our projects timely fashion, I am interested in Nodejs buildpack in particular, since a new version has been released recently that removed Node 12 and affected our deployments.
 
Do you know by any chance if such communication exists?
 
Many thanks,
BR.
 
 
Carlos Delgado

DevOps Lead, Customer Success Automation ES

SAP ESPAÑA, S.A.
 Torre Diagonal Mar - B1 C/, 08019 Barcelona, Spain

T +34 93 483-3238, M +34 678 684650, E carlos.delgado02@...


 
Pflichtangaben/Mandatory Disclosure Statement:
 
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.  Sollten Sie
diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der
E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.
Vielen Dank.
 
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.  If you have received
this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform
us immediately and destroy the original transmittal.
Thank you for your cooperation
 
<image001.png>
<image002.jpg>
 
 


The information transmitted is intended for the person or entity to which it is addressed and may contain confidential, privileged or copyrighted material. If you receive this in error, please contact the sender and delete the material from any computer. Any views or opinions expressed are those of the author and do not necessarily represent those of Fidelity International. All e-mails may be monitored. FIL Investments International (Reg. No.1448245), FIL Investment Services (UK) Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142), Financial Administration Services Limited (Reg. No. 1629709) and FIL Wealth Management Limited (Registered. No. 06121251) are authorised and regulated in the UK by the Financial Conduct Authority. FIL Life Insurance Limited (Reg No. 3406905) is authorised in the UK by the Prudential Regulation Authority and regulated in the UK by the Financial Conduct Authority and the Prudential Regulation Authority. Registered offices at Beech Gate, Millfield Lane, Lower Kingswood, Tadworth, Surrey KT20 6RP.


Re: Buildpack deployment in cflinuxfs3 stack for AWS

Conner UK, Jim
 

At my place of work, we have concourse jobs which sends us messages on our MS Teams channel whenever a new release appears. Maybe this will be useful for someone else too.

 

Here’s some sanitised snippets from our release-notification-pipeline.

 

***

resources:

- name: java-buildpack-release

  type: github-release

  source:

    user: cloudfoundry

    repository: java-buildpack

    release: true

    access_token: ((github_token))

 

- name: notify-new-java-buildpack-releases

  plan:

  - do:

    - in_parallel:

      - get: release-notifications-pipeline

      - get: release-repo

        resource: java-buildpack-release

        params:

          globs: [notthisthing] # because we only want to watch for tag changes & data, not the release tgz itself (proxy won't allow download of it)

        trigger: true

    - task: check-versions

      config:

        platform: linux

        inputs:

        - name: release-notifications-pipeline

        - name: release-repo

        image_resource:

          type: docker-image

          source:

            repository: ((any_docker_image_which_has_curl_and_jq))

            tag: latest

        run:

          path: cf-deployment-notifications/check_versions.sh

      params:

        RELEASE_NAME: java-buildpack

        TEAMS_WEBHOOK_URL: ((ms_teams_webhook_url))

    timeout: 15m

***

 

.. and the source for the check_versions.sh script.

 

***

#!/bin/bash

 

set -e

 

if [[ -f "release-repo/body" ]]; then

  split --line-bytes=7500 release-repo/body release-repo/release-body-

 

  for file in $(find release-repo -name "release-body-*" | sort )

  do

    request_body=$(jq -n --arg body "$(cat "${file}")" --arg title "New $RELEASE_NAME $(cat release-repo/version) release" '{title: $title, text: $body}')

    curl -if -X POST --data "${request_body}" -k "${TEAMS_WEBHOOK_URL}"

    rm "${file}"

  done

else

  request_body=$(jq -n --arg body "The author was too lazy to add a release note" --arg title "New $RELEASE_NAME $(cat release-repo/version) release" '{title: $title, text: $body}')

  curl -if -X POST --data "${request_body}" -k "${TEAMS_WEBHOOK_URL}"

fi

***

 

Jim

 

 

From: <cf-dev@...> on behalf of Benjamin Gandon <benjamin@...>
Reply to: "cf-dev@..." <cf-dev@...>
Date: Friday, 12 August 2022 at 10:42
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Buildpack deployment in cflinuxfs3 stack for AWS

 

Hi Carlos, The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases These need to be read regularly by a human for taking action when necessary, like when

Hi Carlos,

 

The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases

These need to be read regularly by a human for taking action when necessary, like when some language versions are discontinued.

 

For newer Paketo buildpacks, I’ve raised some similar concern in the Paketo Slack last year:

 

What we would need is a way for buildpack consumers like us, to build automation (in Concourse or anything similar) that warns the correct people in the enterprise for taking action when some Buildpack is discontinuing some language version. I don’t know if there has been any progress on this since last year.

 

Benjamin

 



Le 4 août 2022 à 10:54, Delgado, Carlos via lists.cloudfoundry.org <carlos.delgado02=sap.com@...> a écrit :

 

Hello team,

 

I am interested to know about communications whenever a new buildpack is deployed and available in AWS cflinuxfs3 stack, in order to adapt our projects timely fashion, I am interested in Nodejs buildpack in particular, since a new version has been released recently that removed Node 12 and affected our deployments.

 

Do you know by any chance if such communication exists?

 

Many thanks,

BR.

 

 

Carlos Delgado


DevOps Lead, Customer Success Automation ES


SAP ESPAÑA, S.A.
 Torre Diagonal Mar - B1 C/, 08019 Barcelona, Spain


T +34 93 483-3238, M +34 678 684650, E carlos.delgado02@...


 

Pflichtangaben/Mandatory Disclosure Statement:

 

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.  Sollten Sie

diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der

E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.

Vielen Dank.

 

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.  If you have received

this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform

us immediately and destroy the original transmittal.

Thank you for your cooperation

 

<image001.png>

<image002.jpg>

 

 


The information transmitted is intended for the person or entity to which it is addressed and may contain confidential, privileged or copyrighted material. If you receive this in error, please contact the sender and delete the material from any computer. Any views or opinions expressed are those of the author and do not necessarily represent those of Fidelity International. All e-mails may be monitored. FIL Investments International (Reg. No.1448245), FIL Investment Services (UK) Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142), Financial Administration Services Limited (Reg. No. 1629709) and FIL Wealth Management Limited (Registered. No. 06121251) are authorised and regulated in the UK by the Financial Conduct Authority. FIL Life Insurance Limited (Reg No. 3406905) is authorised in the UK by the Prudential Regulation Authority and regulated in the UK by the Financial Conduct Authority and the Prudential Regulation Authority. Registered offices at Beech Gate, Millfield Lane, Lower Kingswood, Tadworth, Surrey KT20 6RP.


Re: Buildpack deployment in cflinuxfs3 stack for AWS

Benjamin Gandon
 

Hi Carlos,

The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases
These need to be read regularly by a human for taking action when necessary, like when some language versions are discontinued.

For newer Paketo buildpacks, I’ve raised some similar concern in the Paketo Slack last year:

What we would need is a way for buildpack consumers like us, to build automation (in Concourse or anything similar) that warns the correct people in the enterprise for taking action when some Buildpack is discontinuing some language version. I don’t know if there has been any progress on this since last year.

Benjamin


Le 4 août 2022 à 10:54, Delgado, Carlos via lists.cloudfoundry.org <carlos.delgado02=sap.com@...> a écrit :

Hello team,
 
I am interested to know about communications whenever a new buildpack is deployed and available in AWS cflinuxfs3 stack, in order to adapt our projects timely fashion, I am interested in Nodejs buildpack in particular, since a new version has been released recently that removed Node 12 and affected our deployments.
 
Do you know by any chance if such communication exists?
 
Many thanks,
BR.
 
 
Carlos Delgado

DevOps Lead, Customer Success Automation ES

SAP ESPAÑA, S.A.
 Torre Diagonal Mar - B1 C/, 08019 Barcelona, Spain

T +34 93 483-3238, M +34 678 684650, E carlos.delgado02@...

 
Pflichtangaben/Mandatory Disclosure Statement:
 
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.  Sollten Sie
diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der
E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.
Vielen Dank.
 
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.  If you have received
this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform
us immediately and destroy the original transmittal.
Thank you for your cooperation
 
<image001.png>
<image002.jpg>
 


CAB Call 17th Aug

Ram Iyengar
 

Hey folks! 
Wanted to give everyone a heads up about the CAB call next week. Matt Royal from VMware will be joining us for a talk on RunWorkload and BuildWorkload which are both a part of Korifi. 
Korifi, as you have all heard, is a Cloud Foundry interface for Kubernetes clusters. Matt is a regular contributor to the project and has agreed to share some valuable insights about the internals that power the tool. 
Date: 17th August '22
Day: Wednesday
Time: 8 AM Pacific/11 AM Eastern/4 PM London

Please try and make yourself available. The more interactive the session is, the more valuable it can be good the whole community. Look forward to learning together. 

Cheers,
Ram Iyengar
Chief Evangelist
CFF

1 - 20 of 9429