Date   
Important Notice: [go-buildpack] End of support for Go versions 1.10.x after May 18, 2019

Elliott Shanks
 

The first release of the Go buildpack after May 18, 2019 will no longer include any versions of Go 1.10.x. These Go versions are no longer supported upstream [1]. Please migrate your Go apps to supported versions of Go before that time.


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


[1] https://golang.org/doc/devel/release.html


Thanks,

Elliott Shanks, CF Buildpacks PM

Cloud Foundry Operators SIG

Swarna Podila
 

Hello Everyone,
It has been recently brought up that it would be useful to have a forum for Cloud Foundry operators to come together and discuss regularly.  The folks at SAP took the lead and have scheduled a call for April 24th, 11AM CET, and repeats every fourth Wednesday of the month.  The appointment is now on the Community calendar; it has the conference bridge info so you can all add it to your own calendars.

Thank you, Gowrisankar and team, for taking lead on this.

-- 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.

How to run strace within cf droplet

gschoep@...
 

So, I have a strange problem going on in my CF container. I can "cf ssh appname" into it and reproduce it with command line. I was hoping to run strace on it, but when I run it I get

"PTRACE_TRACEME doesn't work: Operation not permitted"

This is a dev instance, I don't mind if I break things. Is there a way to enable PTRACE_TRACEME so I can run strace?


My setup...

(sorry I don't know what version of CF our servers are running)

buildpack: https://github.com/cloudfoundry/ruby-buildpack#v1.7.23

Re: How to run strace within cf droplet

Giuseppe Capizzi
 

Hi!

So, I have a strange problem going on in my CF container. I can "cf ssh appname" into it and reproduce it with command line. I was hoping to run strace on it, but when I run it I get

"PTRACE_TRACEME doesn't work: Operation not permitted"
This is expected, as we drop the `CAP_SYS_PTRACE` capability for our
unprivileged containers, and every container created through `cf push`
is unprivileged by default.

This is a dev instance, I don't mind if I break things. Is there a way to enable PTRACE_TRACEME so I can run strace?
You *could* enable privileged containers, see the dedicated
cf-deployment opsfile [1] for details.

[1] https://github.com/cloudfoundry/cf-deployment/blob/master/operations/enable-privileged-container-support.yml

Hope it helps!
--
Giuseppe Capizzi

Re: Cloud Foundry Operators SIG

Swarna Podila
 

Kicking off in a few hours is the first cf-operators sig meeting.  Don’t forget to join: at 5AM US Eastern | 11AM CET. 

Topic: Cloud Foundry Operators SIG Meeting
Time: Apr 24, 2019 2:00 AM Pacific Time (US and Canada)

Join Zoom Meeting

One tap mobile
+16699006833,,4084184280# US (San Jose)
+19292056099,,4084184280# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 929 205 6099 US (New York)
Meeting ID: 408 418 4280
Find your local number: https://zoom.us/u/ali1NKUd8


On Thu, Apr 18, 2019 at 19:08 Swarna Podila <spodila@...> wrote:
Hello Everyone,
It has been recently brought up that it would be useful to have a forum for Cloud Foundry operators to come together and discuss regularly.  The folks at SAP took the lead and have scheduled a call for April 24th, 11AM CET, and repeats every fourth Wednesday of the month.  The appointment is now on the Community calendar; it has the conference bridge info so you can all add it to your own calendars.

Thank you, Gowrisankar and team, for taking lead on this.

-- 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.
--
-- Swarna Podila
Senior Director, Community | Cloud Foundry Foundation
spodila@...
@skpodila

Re: How to run strace within cf droplet

gschoep@...
 

Thanks, I'll keep that as a note, I got one of our CF  admins to help out and we ended up figuring out the issue with tcpdump(not inside the droplet). It looked to be that our Firewall was dropping a DNS request packet, due to a possible bug in the cflinuxfs2 stack. We are upgrading to cflinuxfs3 shortly, as well as moving to a DNS that isn't outside our firewall. So we think both will fix the problem.

windows installed cf-cli failed

Kou, Guanghai <guanghai.kou@...>
 

Hi cf-dev team

I need your help.

I installed the cf-cli  with the steps of https://docs.cloudfoundry.org/cf-cli/install-go-cli.html -> Windows Installation.

But the result is failed. Please check the result-picture.

 

 

What should I do?

 

Best Regards

Kou Guanghai

+86 15242607550

 




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com

Re: windows installed cf-cli failed

Jonathan Matthews
 

On Sun, 28 Apr 2019 at 17:24, Kou, Guanghai <guanghai.kou@...> wrote:

Hi cf-dev team

I need your help.

I installed the cf-cli  with the steps of https://docs.cloudfoundry.org/cf-cli/install-go-cli.html -> Windows Installation.

But the result is failed. Please check the result-picture.


Hey there. 

Your installation has succeeded. Your problem is happening when running the now-installed tool. 

I’ve observed this previously when a windows profile has its home directory set to a network drive which is inaccessible from its current location or network. 

If you cannot access the Z: drive, set the CF_HOME environment variable to a drive and directory which you *can* access.

For more in-depth help, your local IT team will be your best place to ask. 

J
--
Jonathan Matthews
London, UK
http://www.jpluscplusm.com/contact.html

NOTICE: [nginx-buildpack] End of support for Nginx versions 1.14.x after 2019-05-30

Elliott Shanks
 

The first release of the Nginx buildpack after May 30, 2019 will no longer include any versions of Nginx 1.14.x. Please migrate your Nginx apps to supported versions of Nginx before that time.


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


Thanks,

Elliott Shanks, CF Buildpacks PM


NOTICE: [php-buildpack] End of support for Nginx versions 1.14.x after 2019-05-30

Elliott Shanks
 

The first release of the Php buildpack after May 30, 2019 will no longer include any versions of Nginx 1.14.x. Please migrate your Php apps to supported versions of Nginx before that time.


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


Thanks,

Elliott Shanks, CF Buildpacks PM

IMPORTANT NOTICE: [all buildpacks] End of support for cflinuxfs2 on all new dependency version lines within buildpacks

Elliott Shanks
 

This notice is regarding the end of support for cflinuxfs2 and how it affects all buildpacks and dependencies contained within them.


cflinuxfs2 (based on Ubuntu 14.04) is no longer receiving security updates due to the end of upstream support. As we desire to ensure that buildpacks are always shipped with the latest security patch updates, all new dependency version lines within buildpacks will only be shipped with cflinuxfs3.


We understand that migrating applications over to cflinuxfs3 can take some time. Because of that, existing dependency version lines that support cflinuxfs2 will continue to receive patch updates for both cflinuxfs2 and cflinuxfs3.


Warning: It is not safe to run applications on cflinuxfs2. While buildpacks will still contain dependencies supported on cflinuxfs2, we do not recommend that they be used due to the absence of security updates for cflinuxfs2.


Additionally, a secondary notice will be coming in the near future explaining the timeline for ending cflinuxfs2 supported buildpacks.


Thanks,

CF Buildpacks Team

CF CLI v6.44.0

Brendan Smith <brsmith@...>
 

We released! 🎉

Highlights of our current release notes

  • Client credentials update to address security concerns
  • Deprecation Notice for some subcommands
  • Using client credential for setting org and space roles
  • Minimum Version Warning
  • Built with Golang 1.12.1 
  • New Translations

Contributors:
Thomas Viehman, Will Murphy, Brendan Smith, Abby Chau, Andrew Crump, Alexander Berezovsky, SAPI team (Aarti Kriplani, Alex Blease, George Blue, Georgi Lozev, Henry Stanley, Nikolay Maslarski, Will Martin) for all the services-related work, Simon Seif (thanks for the pull request!), V3 Acceleration Team

Thanks all!

Brendan and the CF CLI team

Re: CF CLI v6.44.0

Brendan Smith
 

Hello,

Unfortunately this release shipped with a regression when authenticated with `--client-credentials`. When authenticating with client credentials, the CLI does not show logs for commands such as `cf logs` and `cf push`. 

Thanks to the CF Release Integration team for reporting this issue. We are working on a patch to fix this regression. 

If your workflow involves `cf auth --client-credentials` you may want to hold off upgrading until a patched version is released.

Best,
Brendan and the CF CLI team


On Thu, May 2, 2019 at 9:25 AM Brendan Smith <brsmith@...> wrote:
We released! 🎉

Highlights of our current release notes

  • Client credentials update to address security concerns
  • Deprecation Notice for some subcommands
  • Using client credential for setting org and space roles
  • Minimum Version Warning
  • Built with Golang 1.12.1 
  • New Translations

Contributors:
Thomas Viehman, Will Murphy, Brendan Smith, Abby Chau, Andrew Crump, Alexander Berezovsky, SAPI team (Aarti Kriplani, Alex Blease, George Blue, Georgi Lozev, Henry Stanley, Nikolay Maslarski, Will Martin) for all the services-related work, Simon Seif (thanks for the pull request!), V3 Acceleration Team

Thanks all!

Brendan and the CF CLI team

[REQUEST for REVIEW] Upcoming CF-Deployment v9.0 release with an important security update

Saikiran Yerram
 

Hello CF folks,

We plan to release cf-deployment v9.0 with an important security update. Please review the following doc and provide your feedback. Anyone with the link above can review and comment.



Lastly, if you have any questions please reach out to Release Integration team on CF slack channel:
  • #cf-deployment
  • #release-integration
--
Saikiran Yerram
PM - CF R&D Release Integration

REMINDER: CAB call for May is next week Wednesday 15th @ 8a Pacific

Michael Maximilien
 

 
Hi, all,
 
Reminder that the CAB call for May is next Wednesday 15th @ 8a Pacific.
 
We will have regular highlights, QAs, as well as three exciting talks:
 
1. Deploying application sidecars in Cloud Foundry by Tim Downy (Pivotal) and Scott Sisil (Pivotal) [1]
 
2. Comcast presentations by Sergey Matochkin and engineering team
  a. Vault plugin for authentication for CF & Spring [2]
  b. External DNS connector for Cloud Foundry [3]
 
All other info in agenda [0]. Zoom soon. Best,

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

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

CF Application Runtime PMC: Loggregator Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

Johannes Tuchscherer, the lead for the Loggregator project within the Application Runtime PMC, is stepping down from the project, as he has recently left Pivotal. We thank him for his many years of service and contribution within the Cloud Foundry community, both as a product manager and as an engineer.

The Loggregator team, located in Denver, 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, May 20, 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: Loggregator Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

Pivotal is nominating Fred Krone for the Loggregator Project Lead in the Application Runtime PMC.

Fred is currently working at Pivotal as a product manager on the Loggregator team. Prior to that, he has worked for the past year as a product manager on the Pivotal application usage service project and before that as a product manager on Gemfire and Apache Geode since January 2017. Before joining Pivotal, Fred worked as product manager at both Riot Games and Twilio on their enterprise data teams.

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

Thanks,
Eric Malm


On Wed, May 8, 2019 at 3:41 PM Eric Malm <emalm@...> wrote:
Hi, everyone,

Johannes Tuchscherer, the lead for the Loggregator project within the Application Runtime PMC, is stepping down from the project, as he has recently left Pivotal. We thank him for his many years of service and contribution within the Cloud Foundry community, both as a product manager and as an engineer.

The Loggregator team, located in Denver, 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, May 20, 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

token retrieve url throwing 401 error

Arun Gupta <guptaarun11@...>
 

Hi Team,
We are in the process of evaluating resource based dynamic authorization platform using cloudfoundry uaa and eclipse keti. 

While accessing below token  tokenKeyUrl  , I am getting 401 error code. Can someone help me.  I am using gradlew -Dspring.profiles.active=default,postgresql run command to run cloudfoundry uaa. I am not able to find out server log.



Attache is uaa.yml file for your reference.
Regards,
Arun

Vote Today! CF Summit Track Co-Chairs

Swarna Podila
 

Please vote for the track co-chairs who will help shape the content at the next Cloud Foundry Summit Europe.
Deadline: May 13, 11:59PM US Pacific

-- 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.

CF Application Runtime PMC: Release Integration Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

Josh Collins, the lead for the Release Integration project within the Application Runtime PMC, is stepping down from the project to join the Diego project team.

The Release Integration team, located in San Francisco, 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 Friday, May 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