Date   

CFNASummit 2020: CFP Extended!

Swarna Podila
 

Dear Cloud Foundry Community,
Please note that the deadline to submit your speaking proposals for Cloud Foundry Summit North America 2020 has been extended. 

Here is the new timeline:
CFP Deadline: 11:59pm (US Pacific) April 3, 2020
Schedule Announcement: April 22, 2020

You can find a more detailed timeline here [1].  Please also stay tuned to this page [2] as we post updates around the event plan, given the times we are in now.  If you have any questions, please drop me a note or post it on #summit on CF Slack.

During these times, if anyone wants informal community calls where we just hangout on zoom to socialize, please drop me a note here or on slack.

Please stay healthy.
Bleiben Sie gesund. 

-- 

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


Re: Statement from the Cloud Foundry Foundation regarding COVID-19

Marco Voelz
 

Thanks Chip!

 

I recently read https://deniseyu.io/2020/03/07/remote-collaboration.html written by Denise Yu and found it to be a very good collection of hardware, software, and process – in case someone is looking for some general advice on how to foster collaboration/pairing when working remote.

 

Everybody stay safe and healthy!

 

Warm regards

Marco

 

From: <cf-bosh@...> on behalf of Chip Childers <cchilders@...>
Reply to: "cf-bosh@..." <cf-bosh@...>
Date: Monday, 16. March 2020 at 17:55
Subject: [cf-bosh] Statement from the Cloud Foundry Foundation regarding COVID-19

 

To our community and members,

 

We recognize the global emergency caused by COVID-19 is impacting all of us. Our thoughts are with our community, members, friends, and colleagues as we approach this new challenge together. 

 

As many parts of the world are implementing social distancing and, in many cases, urging or even requiring citizens to stay at home, many of us are privileged to be able to work from home. Some of our project teams have significant experience working and pairing remotely. For those of you that are new to working from home, please reach out to the larger community for support and or best practices. If you have experience working remotely, we encourage you to share your best practices with others -- both in the community and more broadly (in the form of blog posts, podcasts, tweets). Now is the time for our community to show its support for each other in any way possible.

 

As we near our June 25th Cloud Foundry Summit North America, please know that we are actively monitoring the situation as it evolves and will be adjusting plans as necessary to ensure the safety and health of our community. As of today, we remain hopeful we will have the opportunity to come together in person. On Friday, we updated the event’s novel coronavirus update page. We will keep you updated on any future changes to the event plans, and remind everyone to continue to check for updates on that page. 

 

It is important to remember that each of us will experience the impact of this outbreak in different ways. Our community is a global network of individuals who genuinely care about each other. In this time of uncertainty, let us demonstrate that kindness to each other by remaining flexible and supportive - in the Cloud Foundry community and in your local community. Help where you can. Be patient, be safe, and remember to take care of yourself. We will all get through this together.

 

In the meantime, please don’t hesitate to reach out to us, at the Foundation, if there is anything we can do to better support you during this time.

 

 

Chip Childers, CTO

Cloud Foundry Foundation


Statement from the Cloud Foundry Foundation regarding COVID-19

Chip Childers
 

To our community and members,


We recognize the global emergency caused by COVID-19 is impacting all of us. Our thoughts are with our community, members, friends, and colleagues as we approach this new challenge together. 


As many parts of the world are implementing social distancing and, in many cases, urging or even requiring citizens to stay at home, many of us are privileged to be able to work from home. Some of our project teams have significant experience working and pairing remotely. For those of you that are new to working from home, please reach out to the larger community for support and or best practices. If you have experience working remotely, we encourage you to share your best practices with others -- both in the community and more broadly (in the form of blog posts, podcasts, tweets). Now is the time for our community to show its support for each other in any way possible.


As we near our June 25th Cloud Foundry Summit North America, please know that we are actively monitoring the situation as it evolves and will be adjusting plans as necessary to ensure the safety and health of our community. As of today, we remain hopeful we will have the opportunity to come together in person. On Friday, we updated the event’s novel coronavirus update page. We will keep you updated on any future changes to the event plans, and remind everyone to continue to check for updates on that page. 


It is important to remember that each of us will experience the impact of this outbreak in different ways. Our community is a global network of individuals who genuinely care about each other. In this time of uncertainty, let us demonstrate that kindness to each other by remaining flexible and supportive - in the Cloud Foundry community and in your local community. Help where you can. Be patient, be safe, and remember to take care of yourself. We will all get through this together.


In the meantime, please don’t hesitate to reach out to us, at the Foundation, if there is anything we can do to better support you during this time.



Chip Childers, CTO
Cloud Foundry Foundation


Re: Not able to list the teams in concourse, using API /api/v1/teams

arutsudar.a95@...
 

Hi Daniel,

Thank you for your suggestions.

Regards,
Arutsudar


BOSH OpenStack CPI maintenance

Riegger, Felix
 

Dear Friends of OpenStack,

 

SAP announced in August 2019 [1] to stop the maintenance of the BOSH OpenStack CPI and related projects by the end of 2019. Pivotal/VMware jumped in to take over the maintenance of the CPI. The handover has been completed and Pivotal/VMware now officially maintains the BOSH OpenStack CPI [2]. To get support please reach out to #bosh [6] or #bosh-core-dev [7] Slack channels.

 

The CF OpenStack validator [3] and bosh-openstack-environment-templates [4] are now unmaintained and will be moved to the cloudfoundy-attic [5] organization after a short grace period.

 

Kind regards,

Morgan and Felix

 

 

[1] https://lists.cloudfoundry.org/g/cf-bosh/message/2651

[2] https://github.com/cloudfoundry/bosh-openstack-cpi-release

[3] https://github.com/cloudfoundry-incubator/cf-openstack-validator

[4] https://github.com/cloudfoundry-incubator/bosh-openstack-environment-templates

[5] https://github.com/cloudfoundry-attic/

[6] https://cloudfoundry.slack.com/archives/C02HPPYQ2

[7] https://cloudfoundry.slack.com/archives/C094QRLEQ


Cloud Foundry Community Workroom at Kubecon/CloudnativeCon EU 2020

Swarna Podila
 

Dear Cloud Foundry Community,
For those of you attending Kubecon/CloudnativeCon EU 2020, please note that F002/F003 room is available for the cloud foundry community.  This is to foster the cross-community collaboration onsite.

This room is an "open-for-cf-community" workroom with no prior reservation required.  This room will be equipped with tables and chairs along with a whiteboard and some markers.  

Please do not hesitate to reach out to me (prior to the event) or the events team onsite, if you have any questions.

-- 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-dev] Call for Help with Vulnerability Management for CFF projects

Swarna Podila
 

For those of you who are not on cf-dev mailing list.

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


---------- Forwarded message ---------
From: Dieu Cao <dcao@...>
Date: Wed, Feb 26, 2020 at 11:42 AM
Subject: [cf-dev] Call for Help with Vulnerability Management for CFF projects
To: cf-dev <cf-dev@...>


All,

The CF community is looking for a handful of volunteers to help reconstitute a multi-member vulnerability management team for CFF projects. Recently, the task has fallen to the Pivotal/VMware security team alone. However, the whole community has a stake in this process.

We're looking for individuals that either: (1) have past experience managing security reports responsibly within either a commercial or open source setting, or (2) are willing and capable of learning by doing. One of the keys to success here will be for the volunteers to have a true sense of being responsible for this process.

Don't worry if you're not a security expert. You do have to be willing to spend a few hours a week helping manage the process.

If interested, reply here or contact me directly. Once we get a reasonable group of volunteers, we'll setup the appropriate meetings to get started.

Thanks,
Dieu Cao
CFF PMC Council Chair


Re: Not able to list the teams in concourse, using API /api/v1/teams

Daniel Jones
 

Hi Aratsudar,

A better place to look for help would be the Concourse forums: https://discuss.concourse-ci.org/

You may also like to consider Control Tower if you want a simpler way to deploy Concourse via BOSH: https://github.com/EngineerBetter/control-tower

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


On Wed, 19 Feb 2020 at 08:49, <arutsudar.a95@...> wrote:

I am using concourse v4.2.1 deployed using bosh on AWS.

When I hit the API endpoint /api/v1/info (in Postman, with Basic auth), I am able to get the response as below

{
    "version": "4.2.1",
    "worker_version": "2.1"
}

When I try to hit the API endpoint /api/v1/teams (in Postman, with Basic auth), I am getting Status 200 OK with an empty response like below.

[]

I am able to see the teams using fly command or also in the web UI, but not through API.

  • Should I enable basic authentication for hitting API endpoints of concourse?
  • Why am I not able to list the teams in concourse using the API /api/v1/teams? What am I missing?


Additional Info:

Referred to this concourse-bosh-deployment github repo for deploying concourse.

The sample command used to deploy concourse is given below:

bosh -e boshconcoursedir deploy -d boshconcourse concourse.yml \
  -l ../versions.yml \
  --vars-store cluster-creds.yml  \
  -o operations/static-web.yml  \
  --var web_ip=<<REDACTED>>   \
  --var network_name=default  \
  --var web_vm_type=<<REDACTED>>  \
  --var db_vm_type=<<REDACTED>>   \
  --var db_persistent_disk_type=<<REDACTED>> \
   --var worker_vm_type=<<REDACTED>> \
    --var deployment_name=boshconcourse \
    --var external_url=https://<<REDACTED>> \
    -o operations/add-local-users.yml \
    --var main_team_local_users=[admin] \
    --var add_local_users=[admin:<<REDACTED>>,myid@...:<<REDACTED>>]

Today I added the below line to the deployment command and deployed again, and still failed to get the teams from the API

  -o operations/basic-auth.yml \

After logging in as admin in fly, I am able to list the teams as below.

fly -t admin login -c https://something.com -u admin -p <<REDACTED>>
logging in to team 'main'


target saved

fly -t admin teams
name
team-1 
team-2
main 

I am not sure if this is the right place to ask this issue. Sorry if it is not. (Also posted a similar question in StackOverflow). Kindly assist me in resolving this issue.

Regards,
Arut


Re: BOSH PMC meeting series cancelled

Marco Voelz
 

Re sending this


From: Voelz, Marco <marco.voelz@...>
Sent: Wednesday, February 19, 2020 9:49:09 AM
To: cf-bosh@... <cf-bosh@...>
Subject: BOSH PMC meeting series cancelled
 

Dear friends of BOSH,

 

I just cancelled the series of BOSH PMC meetings due to inactivity. I have updated the CFF calendar accordingly and deleted the event.

If there's a topic you'd like to discuss around BOSH, please drop in #bosh on slack, write a mail to this list or to me personally.

 

Warm regards

Marco

 


BOSH PMC meeting series cancelled

Marco Voelz
 

Dear friends of BOSH,

 

I just cancelled the series of BOSH PMC meetings due to inactivity. I have updated the CFF calendar accordingly and deleted the event.

If there's a topic you'd like to discuss around BOSH, please drop in #bosh on slack, write a mail to this list or to me personally.

 

Warm regards

Marco

 


Re: Deprecating global compiled package cache

Marco Voelz
 

Dear Maya,

 

From my point of view the removal certainly makes sense. The global compiled package cache has severe issues, which to my knowledge have never been fixed [1,2,3]. I'd be interested in existing use-cases that people have for this, but my assumption is this feature doesn't live up to the expectations we had back in 2013 when it was added ;)

 

+1 for removing this, thanks for bringing this up!

 

Warm regards

Marco

 

[1] https://github.com/cloudfoundry/bosh/issues/1478

[2] https://github.com/cloudfoundry/bosh/issues/1300

[3] https://github.com/cloudfoundry/bosh/issues/1353

 

 

From: <cf-bosh@...> on behalf of Maya Rosecrance <mrosecrance@...>
Reply to: "cf-bosh@..." <cf-bosh@...>
Date: Tuesday, 18. February 2020 at 23:30
To: "cf-bosh@..." <cf-bosh@...>
Subject: [cf-bosh] Deprecating global compiled package cache

 

Hi Everyone,

I'm considering removing the global compiled package cache. It was a feature that made a lot of sense in a world before compiled releases where users with multiple directors wanted to only compile on one director then share that artifact with the others. Currently, when the BOSH director searches for a compiled package, it first searches the blobstore for any exact or fuzzy (for floating stemcell lines) compiled package matches before checking the global package cache. My hope is that as more and more BOSH release authors have adopted compiled releases, the need for the global package cache has become minimal to none as most compiled packages have been 'pre-seeded' to the blobstore. 

 

For users still ingesting source releases, we've since made manual workarounds to avoid the compilation time hit. Namely anyone can export a release and upload that artifact to any number of directors.

 

Please reach out if you have any use cases that might be broken by this change.


Not able to list the teams in concourse, using API /api/v1/teams

arutsudar.a95@...
 

I am using concourse v4.2.1 deployed using bosh on AWS.

When I hit the API endpoint /api/v1/info (in Postman, with Basic auth), I am able to get the response as below

{
    "version": "4.2.1",
    "worker_version": "2.1"
}

When I try to hit the API endpoint /api/v1/teams (in Postman, with Basic auth), I am getting Status 200 OK with an empty response like below.

[]

I am able to see the teams using fly command or also in the web UI, but not through API.

  • Should I enable basic authentication for hitting API endpoints of concourse?
  • Why am I not able to list the teams in concourse using the API /api/v1/teams? What am I missing?


Additional Info:

Referred to this concourse-bosh-deployment github repo for deploying concourse.

The sample command used to deploy concourse is given below:

bosh -e boshconcoursedir deploy -d boshconcourse concourse.yml \
  -l ../versions.yml \
  --vars-store cluster-creds.yml  \
  -o operations/static-web.yml  \
  --var web_ip=<<REDACTED>>   \
  --var network_name=default  \
  --var web_vm_type=<<REDACTED>>  \
  --var db_vm_type=<<REDACTED>>   \
  --var db_persistent_disk_type=<<REDACTED>> \
   --var worker_vm_type=<<REDACTED>> \
    --var deployment_name=boshconcourse \
    --var external_url=https://<<REDACTED>> \
    -o operations/add-local-users.yml \
    --var main_team_local_users=[admin] \
    --var add_local_users=[admin:<<REDACTED>>,myid@...:<<REDACTED>>]

Today I added the below line to the deployment command and deployed again, and still failed to get the teams from the API

  -o operations/basic-auth.yml \

After logging in as admin in fly, I am able to list the teams as below.

fly -t admin login -c https://something.com -u admin -p <<REDACTED>>
logging in to team 'main'


target saved

fly -t admin teams
name
team-1 
team-2
main 

I am not sure if this is the right place to ask this issue. Sorry if it is not. (Also posted a similar question in StackOverflow). Kindly assist me in resolving this issue.

Regards,
Arut


Deprecating global compiled package cache

Maya Rosecrance
 

Hi Everyone,
I'm considering removing the global compiled package cache. It was a feature that made a lot of sense in a world before compiled releases where users with multiple directors wanted to only compile on one director then share that artifact with the others. Currently, when the BOSH director searches for a compiled package, it first searches the blobstore for any exact or fuzzy (for floating stemcell lines) compiled package matches before checking the global package cache. My hope is that as more and more BOSH release authors have adopted compiled releases, the need for the global package cache has become minimal to none as most compiled packages have been 'pre-seeded' to the blobstore. 

For users still ingesting source releases, we've since made manual workarounds to avoid the compilation time hit. Namely anyone can export a release and upload that artifact to any number of directors.

Please reach out if you have any use cases that might be broken by this change.


Re: CF Summit North America 2020: Seeking Program Chair Nominations

Swarna Podila
 

Hi Dan,
Yes, blind review of CFP submissions is possible and we do intend to do blind review this year.  I will update the blog post accordingly; thank you for asking the question.

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


On Mon, Feb 10, 2020 at 1:48 AM Daniel Jones <daniel.jones@...> wrote:
Hi Swarna,

Will a blind selection process be possible this year?

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


On Fri, 7 Feb 2020 at 17:04, Swarna Podila <spodila@...> wrote:
Dear Friends,
It is that time of Cloud Foundry Summit again where we need your help in establishing the program committee to review CFP submissions.  Given the new format of Summits this year, we will also look to our program chairs to help structure the content in the best way suited for our community.

I've written up a quick post [1] that explains it and hopefully answers all your questions (if there are more questions, please don't hesitate to ask here or on in #summit or #cff-forum channels on slack).

Get nominating today [2]!  The nominations close on Feb 18, 11:59PM US PST.


--

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


Re: New lead for Community (CAB) meetings

Michael Maximilien <maxim@...>
 

This is wonderful news!
 
Thanks Swarna for organizing the search and finding a leader.
 
And super thanks to Troy for stepping up. I am sure you will do fantastically well.
 
I am at your service. Best,

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

----- Original message -----
From: Swarna Podila <spodila@...>
To: CF Developers Mailing List <cf-dev@...>, cf-bosh <cf-bosh@...>, Troy Topnik <troy.topnik@...>, Michael Maximilien <maxim@...>
Cc: Neil MacDougall <nmacdougall@...>
Subject: [EXTERNAL] Re: New lead for Community (CAB) meetings
Date: Thu, Feb 6, 2020 2:48 PM
 
Hi Friends,
Please join me in welcoming @Troy Topnik as the Cloud Foundry Community Advisory Board (CAB) Meeting host.  Please also join me in thanking Dr. Max for his gracious, thoughtful, and inspiring leadership through these years in not establishing (the call and more importantly, the momentum) and leading CAB meetings to such great success.  We will sorely miss him as the host but we will continue to see him as a participant.
 
A huge thank you to @Neil MacDougall as well, for offering to support Troy as and when needed.
 
I would also like to take this opportunity to thank the awesome folks at Stark & Wayne (especially Ashley!) for diligently hosting this meeting on their zoom bridge and recording every meeting.  The recordings[1] are so much more helpful for those who cannot join these meetings live.  Thank you, Ashley and the S&W crew, for continuing to do this.
 
I would also like to thank the awesome folks at Altoros for diligently writing a summary of each call on their website[2].  These are extremely useful for those who are unable to either attend live or watch the recording.  Thank you, Team Altoros.
 
Looking forward to seeing you all in the next CAB meeting on Wednesday, February 19th at 11AM US Eastern. 
(You can add this and other regular community meetings to your own calendar from the community calendar posted here[3])
 
Cheers,
Swarna.
 
 
 
-- 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.
 
On Thu, Jan 23, 2020 at 7:54 AM Swarna Podila <spodila@...> wrote:
Dear CF Community,
Max (popularly known as "Dr. Max", cc'd here) has been running Cloud Foundry Community Advisory Board (CAB) meetings for the past 4-ish years now.  As he mentioned during the recent calls, 2020 is a great opportunity for any of you in the community to nominate yourself (or someone you know is interested) to take the baton from Max.  Max will continue being an active member of our community; we just think that other members may want to take an opportunity to step up and make their mark in our community.  
 
The responsibilities will be to host 
  • the monthly CAB calls by sourcing interesting topics/demos for the meetings
  • in-person CAB meetings at Cloud Foundry Summits (we, from the Foundation, can help you with that)
If you are unsure of the responsibilities or if you would like to talk to Max directly, please feel free to reach out to him.
 
Please send us your nominations no later than February 5th. 
 
-- 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.
 


Re: CF Summit North America 2020: Seeking Program Chair Nominations

Daniel Jones
 

Hi Swarna,

Will a blind selection process be possible this year?

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


On Fri, 7 Feb 2020 at 17:04, Swarna Podila <spodila@...> wrote:
Dear Friends,
It is that time of Cloud Foundry Summit again where we need your help in establishing the program committee to review CFP submissions.  Given the new format of Summits this year, we will also look to our program chairs to help structure the content in the best way suited for our community.

I've written up a quick post [1] that explains it and hopefully answers all your questions (if there are more questions, please don't hesitate to ask here or on in #summit or #cff-forum channels on slack).

Get nominating today [2]!  The nominations close on Feb 18, 11:59PM US PST.


--

-- 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 Summit North America 2020: Seeking Program Chair Nominations

Swarna Podila
 

Dear Friends,
It is that time of Cloud Foundry Summit again where we need your help in establishing the program committee to review CFP submissions.  Given the new format of Summits this year, we will also look to our program chairs to help structure the content in the best way suited for our community.

I've written up a quick post [1] that explains it and hopefully answers all your questions (if there are more questions, please don't hesitate to ask here or on in #summit or #cff-forum channels on slack).

Get nominating today [2]!  The nominations close on Feb 18, 11:59PM US PST.


--

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


Re: New lead for Community (CAB) meetings

Swarna Podila
 

Hi Friends,
Please join me in welcoming @Troy Topnik as the Cloud Foundry Community Advisory Board (CAB) Meeting host.  Please also join me in thanking Dr. Max for his gracious, thoughtful, and inspiring leadership through these years in not establishing (the call and more importantly, the momentum) and leading CAB meetings to such great success.  We will sorely miss him as the host but we will continue to see him as a participant.

A huge thank you to @Neil MacDougall as well, for offering to support Troy as and when needed.

I would also like to take this opportunity to thank the awesome folks at Stark & Wayne (especially Ashley!) for diligently hosting this meeting on their zoom bridge and recording every meeting.  The recordings[1] are so much more helpful for those who cannot join these meetings live.  Thank you, Ashley and the S&W crew, for continuing to do this.

I would also like to thank the awesome folks at Altoros for diligently writing a summary of each call on their website[2].  These are extremely useful for those who are unable to either attend live or watch the recording.  Thank you, Team Altoros.

Looking forward to seeing you all in the next CAB meeting on Wednesday, February 19th at 11AM US Eastern. 
(You can add this and other regular community meetings to your own calendar from the community calendar posted here[3])

Cheers,
Swarna.


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


On Thu, Jan 23, 2020 at 7:54 AM Swarna Podila <spodila@...> wrote:
Dear CF Community,
Max (popularly known as "Dr. Max", cc'd here) has been running Cloud Foundry Community Advisory Board (CAB) meetings for the past 4-ish years now.  As he mentioned during the recent calls, 2020 is a great opportunity for any of you in the community to nominate yourself (or someone you know is interested) to take the baton from Max.  Max will continue being an active member of our community; we just think that other members may want to take an opportunity to step up and make their mark in our community.  

The responsibilities will be to host 
  • the monthly CAB calls by sourcing interesting topics/demos for the meetings
  • in-person CAB meetings at Cloud Foundry Summits (we, from the Foundation, can help you with that)
If you are unsure of the responsibilities or if you would like to talk to Max directly, please feel free to reach out to him.

Please send us your nominations no later than February 5th. 

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


New lead for Community (CAB) meetings

Swarna Podila
 

I just realized I didn't include the bosh mailing list :) My apologies, y'all.

If you're interested in hosting (or giving it a try) the CAB calls, please reach out to me or @Michael Maximilien

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


---------- Forwarded message ---------
From: Swarna Podila <spodila@...>
Date: Mon, Feb 3, 2020 at 8:16 AM
Subject: Re: New lead for Community (CAB) meetings
To: CF Developers Mailing List <cf-dev@...>
Cc: Michael Maximilien <maxim@...>


Hi Everyone,
Bringing this to the top of your inboxes, y'all.  

Please send in your nominations by Wednesday, February 5th.

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


On Thu, Jan 23, 2020 at 7:54 AM Swarna Podila <spodila@...> wrote:
Dear CF Community,
Max (popularly known as "Dr. Max", cc'd here) has been running Cloud Foundry Community Advisory Board (CAB) meetings for the past 4-ish years now.  As he mentioned during the recent calls, 2020 is a great opportunity for any of you in the community to nominate yourself (or someone you know is interested) to take the baton from Max.  Max will continue being an active member of our community; we just think that other members may want to take an opportunity to step up and make their mark in our community.  

The responsibilities will be to host 
  • the monthly CAB calls by sourcing interesting topics/demos for the meetings
  • in-person CAB meetings at Cloud Foundry Summits (we, from the Foundation, can help you with that)
If you are unsure of the responsibilities or if you would like to talk to Max directly, please feel free to reach out to him.

Please send us your nominations no later than February 5th. 

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


Re: [cf-dev] [CF-RFC] 030: Use Consistent Human Readable Timestamps for CF Component Logs

Daniel Jones
 

As someone who has had to debug live CF systems for many years, I'm very pleased to see this.

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


On Mon, 13 Jan 2020 at 16:54, Amelia Downs <adowns@...> wrote:
Hi All,

Here is a link for a request for comment #030. This is targeted towards teams that provide releases to cf-deployment and to consumers of cf-deployment who read logs.

INTENTION

We intend to have all component jobs to use, or have the option to use, the same human-readable timestamp format for its logs (RFC3339) so that it’s easier for a human to skim logs to find entries for a given time and so that less toil is required to correlate log entries generated by different sub-components.

FEEDBACK

Please add comments or suggested edits inside the RFC document for convergent discussion, rather than replying to this email. Please use the Slack channel (#cf-rfc-030) for information conversation about the RFC and related subjects that may or may not result in suggesting an edit to the document.

DATES

We are planning to start working on this soon. This RFC will be open starting today, and will be closed in two weeks, receiving comments through January 24, 2020.

Thanks,
Amelia Downs and Josh Collins

21 - 40 of 2725