|
Unconference at CF Summit Basel 2018
Hi all,
We're pleased to confirm that there'll be an Unconference at Basel again this year at 6pm on Tuesday 9th October.
We're planning on the same rough schedule as last year, so talks interspersed
Hi all,
We're pleased to confirm that there'll be an Unconference at Basel again this year at 6pm on Tuesday 9th October.
We're planning on the same rough schedule as last year, so talks interspersed
|
By
Daniel Jones
·
#8166
·
|
|
Re: [CAUTION] Re: [cf-dev] Proposed BOSH logging interface
We haven't done anything beyond proposing the interface and implementing the option to respect permissions.
Since the time of this proposal, BPM has implemented a feature that should allow us to run
We haven't done anything beyond proposing the interface and implementing the option to respect permissions.
Since the time of this proposal, BPM has implemented a feature that should allow us to run
|
By
Jesse T. Alford
·
#8165
·
|
|
Re: cf-deployment 3.0
Thanks Geoff, Marco, Chip, Jesse, Bernd, and David for sharing your feedback and thoughts. You’ve expressed valid concerns and provided valuable context that I take to heart. I really appreciate the
Thanks Geoff, Marco, Chip, Jesse, Bernd, and David for sharing your feedback and thoughts. You’ve expressed valid concerns and provided valuable context that I take to heart. I really appreciate the
|
By
Josh Collins
·
#8164
·
|
|
Re: cf-deployment 3.0
Another point: most (certainly not all, but most) CVEs are stemcell, buildpack, or rootfs bumps that can be consumed safely/have minimal integration concerns. Even those that are in more substantive
Another point: most (certainly not all, but most) CVEs are stemcell, buildpack, or rootfs bumps that can be consumed safely/have minimal integration concerns. Even those that are in more substantive
|
By
Jesse T. Alford
·
#8163
·
|
|
Re: cf-deployment 3.0
As the previous project lead for RelInt, I want to speak to Marco's concerns directly. We _definitely_ considered the operator as an important persona during any decision-making; if anything, we were
As the previous project lead for RelInt, I want to speak to Marco's concerns directly. We _definitely_ considered the operator as an important persona during any decision-making; if anything, we were
|
By
David Sabeti
·
#8162
·
|
|
[High Severity CVE] UAA accepts refresh token as access token on admin endpoints
CVE-2018-11047: UAA accepts refresh token as access token on admin endpoints
Severity
HighVendor
Cloud Foundry FoundationAffected Cloud Foundry Products and Versions
You are using uaa versions 4.19
CVE-2018-11047: UAA accepts refresh token as access token on admin endpoints
Severity
HighVendor
Cloud Foundry FoundationAffected Cloud Foundry Products and Versions
You are using uaa versions 4.19
|
By
Dan Jahner
·
#8161
·
|
|
Re: cf-deployment 3.0
I was about to mention that I indeed enjoyed the existing CF model of releases which roughly translated to “you better run fast” for consumers.
The thing I found needed some tweaking in the
I was about to mention that I indeed enjoyed the existing CF model of releases which roughly translated to “you better run fast” for consumers.
The thing I found needed some tweaking in the
|
By
Krannich, Bernd
·
#8159
·
|
|
Re: cf-deployment 3.0
I don't agree with the claim that we didn't introduce major breaking changes in the past - we did. Routinely.
`cf-release` was sem-ver only insofar as every version was a major version. Changes just
I don't agree with the claim that we didn't introduce major breaking changes in the past - we did. Routinely.
`cf-release` was sem-ver only insofar as every version was a major version. Changes just
|
By
Jesse T. Alford
·
#8158
·
|
|
Re: cf-deployment 3.0
Food for thought: One of the challenges here is that maintaining patches for past coordinated releases is expensive (both in time and CI costs). In the CF ecosystem, this has traditionally been the
Food for thought: One of the challenges here is that maintaining patches for past coordinated releases is expensive (both in time and CI costs). In the CF ecosystem, this has traditionally been the
|
By
Chip Childers <cchilders@...>
·
#8157
·
|
|
CF/K8S SIG Calls
All,
We held our last CF/K8S SIG call today, which is great news. They served the purpose of getting a bunch of the interesting work that's happening out into the open, and now most of the efforts are
All,
We held our last CF/K8S SIG call today, which is great news. They served the purpose of getting a bunch of the interesting work that's happening out into the open, and now most of the efforts are
|
By
Chip Childers <cchilders@...>
·
#8156
·
|
|
FINAL REMINDER: CAB call for July is Wednesday (tomorrow) 07/18 @ 8a PST or 11a EST
FYI...
Zoom soon. Best,
dr.max
ibm ☁
silicon valley, ca
dr.max
ibm ☁
silicon valley, ca
FYI...
Zoom soon. Best,
dr.max
ibm ☁
silicon valley, ca
dr.max
ibm ☁
silicon valley, ca
|
By
Michael Maximilien
·
#8155
·
|
|
Re: CF Application Runtime PMC - CF Bits-Service Project Lead Call for Nominations
Hello all,
IBM is nominating Peter Goetz for theCF Bits Service Project Lead in the Application Runtime PMC.
Peter is a Software Engineer at IBMworking both as a core contributor to the Cloud Foundry
Hello all,
IBM is nominating Peter Goetz for theCF Bits Service Project Lead in the Application Runtime PMC.
Peter is a Software Engineer at IBMworking both as a core contributor to the Cloud Foundry
|
By
Simon D Moser
·
#8154
·
|
|
CF Application Runtime PMC - CF Bits-Service Project Lead Call for Nominations
Hello All,
Simon Moser, the Project Lead for the Bits-Service team within the Application Runtime PMC, is rotating into a different role within IBM. We thank him for his time serving as the
Hello All,
Simon Moser, the Project Lead for the Bits-Service team within the Application Runtime PMC, is rotating into a different role within IBM. We thank him for his time serving as the
|
By
Dieu Cao <dcao@...>
·
#8153
·
|
|
Re: Proposal for weighted routing user experience in Cloud Foundry
Use case: I want v1-stable to receive 5 times more traffic than each individual upgrade version I deploy
Phase 1: Deploy alpha 1
Proposed (sum MUST add up to a 100):
v1-stable: 83
v2-alpha1:
Use case: I want v1-stable to receive 5 times more traffic than each individual upgrade version I deploy
Phase 1: Deploy alpha 1
Proposed (sum MUST add up to a 100):
v1-stable: 83
v2-alpha1:
|
By
Filip Hanik
·
#8152
·
|
|
Re: cf-deployment 3.0
I’m going to agree with Marco’s concerns here. Making life harder and less stable for the end users of CF has a real potential to alienate and push away the CF userbase altogether, even if it’s
I’m going to agree with Marco’s concerns here. Making life harder and less stable for the end users of CF has a real potential to alienate and push away the CF userbase altogether, even if it’s
|
By
Franks, Geoff
·
#8151
·
|
|
Re: Deprecate route-sync from CFCR to CFAR
Hi Arghya,
You have mentioned in Github that you were able to overcome this issue.
For everyone else, here is the context and a bit more information.
History
In very early CFCR days, we did not
Hi Arghya,
You have mentioned in Github that you were able to overcome this issue.
For everyone else, here is the context and a bit more information.
History
In very early CFCR days, we did not
|
By
Oleksandr Slynko
·
#8150
·
|
|
Re: cf-deployment 3.0
Dear Josh,
Thanks for the context, I wasn't aware of what happened before the release of networking 2.0. To stick with your example, though: From what you are saying I have understood that you would
Dear Josh,
Thanks for the context, I wasn't aware of what happened before the release of networking 2.0. To stick with your example, though: From what you are saying I have understood that you would
|
By
Marco Voelz
·
#8149
·
|
|
Re: Proposal for weighted routing user experience in Cloud Foundry
aaarrgh, there is a bug in my psuedo code
clusterWeight = [v1,v1,v1,v1,v1,v1,v2,v2,v2,v3,v3] should be
clusterWeight = [v1,v1,v1,v1,v1,v1,v2,v2,v2,v3,v4]
Full solution:
Implementation: "Randomized
aaarrgh, there is a bug in my psuedo code
clusterWeight = [v1,v1,v1,v1,v1,v1,v2,v2,v2,v3,v3] should be
clusterWeight = [v1,v1,v1,v1,v1,v1,v2,v2,v2,v3,v4]
Full solution:
Implementation: "Randomized
|
By
Filip Hanik
·
#8148
·
|
|
Re: Proposal for weighted routing user experience in Cloud Foundry
I put a long comment in the doc, maybe comments are good for short notes. here is the spiel
"The sum of weights must add to 100"
I would say this is where being user friendly ends. If I add reviews-v4
I put a long comment in the doc, maybe comments are good for short notes. here is the spiel
"The sum of weights must add to 100"
I would say this is where being user friendly ends. If I add reviews-v4
|
By
Filip Hanik
·
#8147
·
|
|
Proposal for weighted routing user experience in Cloud Foundry
The CF Routing team has received feedback from many users that support for weighted routing would make it easier to accomplish their goals. We have a proposal on the preferred user experience for
The CF Routing team has received feedback from many users that support for weighted routing would make it easier to accomplish their goals. We have a proposal on the preferred user experience for
|
By
Shubha Anjur Tupil
·
#8146
·
|