|
Question about PROXY protocol support in gorouter
王小锋 <zzuwxf at gmail.com...>
Hi, there
I am reading cf 238 release note and find that Gorouter now supports the PROXY protocol. Given proxy protocol is supported in gorouter, is there any change in AWS ELB configuration? Previously, we use different port to support both websocket and http/https*. *If we upgrade cf release to 238, could we use one port (443) in AWS ELB to support both https and websocket? If not, I guess the puropose of proxy protocol support is only to get client info for websockt? |
|
|
|
CAB call for July @ 8:00a PDT on Wednesday July 13th, 2016
Michael Maximilien
Hi, all,
It's summer and its time to resume our friendly CAB calls. So quick reminder that the next call is next week on Wednesday, July 13th @ 8a PDT. All info in link: https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit#heading=h.o44xhgvum2we Remember, no more status updates but rather discussions, so come ready with your questions. Join the http://slack.cloudfoundry.org and join the #CAB channel for previous and future discussions. Talk to you all next week. We'll send one more reminder on this list. Best, Chip, James, and Max dr.max ibm cloud labs sillicon valley, ca Sent from my iPhone |
|
|
|
Re: Set CF env var to include instance index
Eric Malm <emalm@...>
If your app is running on a recent version of the Diego backend (0.1474.0
toggle quoted message
Show quoted text
or later), buildpack-based apps also now have support for sourcing a `.profile` script at the root of the app directory before running the app's start command. If your library expects one particular environment variable, you could export the value of CF_INSTANCE_INDEX (or any other identifier, or whatever you want) as that env var. Further documentation of this feature is present at http://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.html#profile. Thanks, Eric, CF Runtime Diego PM On Wed, Jul 6, 2016 at 9:50 AM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
Can you use a `.profile.d` script? You can set environment variables in |
|
|
|
Re: Set CF env var to include instance index
Daniel Mikusa
Can you use a `.profile.d` script? You can set environment variables in
toggle quoted message
Show quoted text
that and they'll be accessible by your app. Dan On Wed, Jul 6, 2016 at 4:19 AM, Stevo Slavić <sslavic(a)gmail.com> wrote:
Java app, java buildpack, reporting metrics to riemann/graphite - nothing |
|
|
|
Re: FQDN for Application Security Groups
Kris Hicks <khicks@...>
Anthony,
toggle quoted message
Show quoted text
They do not. It must be an IP address, an IP range (e.g. "192.168.1.0-192.168.1.4"), or a CIDR. See the updated Application Security Groups docs for more: http://docs.cloudfoundry.org/adminguide/app-sec-groups.html#creating-groups (I've just noticed that the "destination" doesn't mention the IP range in the docs, and will update it accordingly.) Cheers, KH On Wed, Jul 6, 2016 at 6:46 AM, Anthony Lee <lee.apc(a)gmail.com> wrote:
Does anyone know if application security groups support fully qualified |
|
|
|
Re: feedback request: deprecate nats_stream_forwarder job from cf-release
Aaron Huber
We are currently using this component to stream all NATS activity to syslog
where it is then forwarded to our common logging infrastructure. We're required to log all system activity so if this were to go away we'd just need some assurance that any activity that shows up in the NATS stream is duplicated somewhere else (CC logs, etc.). Aaron -- View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-feedback-request-deprecate-nats-stream-forwarder-job-from-cf-release-tp5334p5348.html Sent from the CF Dev mailing list archive at Nabble.com. |
|
|
|
FQDN for Application Security Groups
Anthony
Does anyone know if application security groups support fully qualified domain names as destination? For instance, `destination: maps.googleapis.com`.
Thanks! Anthony |
|
|
|
cf-release release note changes for buildpacks and stacks
Danny Rosen
Hello,
The buildpacks and stacks team is considering changing release notes within cf-release [1 <https://github.com/cloudfoundry/cf-release/releases#buildpacks-and-stacks>] to only link to releases and mentions of high-severity CVEs and new important changes (Note, this is only for buildpacks and stacks.) We wanted to check in to see if anyone in the community would find issue with this approach as we currently list all changes including medium and low patched CVEs. Please let us know as we intend to make this change for the next upcoming cf-release [1] - https://github.com/cloudfoundry/cf-release/releases#buildpacks-and-stacks |
|
|
|
Re: Set CF env var to include instance index
Stevo Slavić <sslavic at gmail.com...>
Java app, java buildpack, reporting metrics to riemann/graphite - nothing
special. I guess this behavior, providing preprocessed environment variable values based on some expression language constructs in CF manifest, should be common/applicable for any buildpack, and happen at the same time when CF_INSTANCE_INDEX value for instance is determined. On Wed, Jul 6, 2016 at 10:08 AM, Graham Bleach < graham.bleach(a)digital.cabinet-office.gov.uk> wrote: On 6 July 2016 at 09:03, Stevo Slavić <sslavic(a)gmail.com> wrote:I was hoping that this glue code would be in one place only, and alreadyI think if you give details of the language, runtime and library you |
|
|
|
Re: Set CF env var to include instance index
Graham Bleach
On 6 July 2016 at 09:03, Stevo Slavić <sslavic(a)gmail.com> wrote:
I was hoping that this glue code would be in one place only, and alreadyI think if you give details of the language, runtime and library you use people are more likely be able to suggest practical ways to achieve what you want. |
|
|
|
Re: Set CF env var to include instance index
Stevo Slavić <sslavic at gmail.com...>
I was hoping that this glue code would be in one place only, and already
there - in Cloud Foundry. On Wed, Jul 6, 2016 at 10:00 AM, Graham Bleach < graham.bleach(a)digital.cabinet-office.gov.uk> wrote: On 6 July 2016 at 06:32, Stevo Slavić <sslavic(a)gmail.com> wrote:Hello CF community,You may know of this already, since you specifically mentioned the |
|
|
|
Re: Set CF env var to include instance index
Graham Bleach
On 6 July 2016 at 06:32, Stevo Slavić <sslavic(a)gmail.com> wrote:
Hello CF community,You may know of this already, since you specifically mentioned the manifest, but CF_INSTANCE_INDEX is set in each app instance https://docs.cloudfoundry.org/devguide/deploy-apps/environment-variable.html#CF-INSTANCE-INDEX Specifically, in a metric reporting library that knows nothing about CF I'dHow you'd do this is probably fairly language and library specific; if your application configuration format doesn't support expansion of environment variables you'll probably need a small bit of glue code. |
|
|
|
Set CF env var to include instance index
Stevo Slavić <sslavic at gmail.com...>
Hello CF community,
Is it possible in CF app manifest to define an environment variable value using an expression that will get expanded differently for each app instance, e.g. to include instance index? Specifically, in a metric reporting library that knows nothing about CF I'd like to set metrics prefix to be instance specific so that metrics from different instances are cleanly separated from each other. Kind regards, Stevo Slavic. |
|
|
|
Proposal for enhanced load balancing in GoRouter
Mark St.Godard
Hello All,
The GoRouter currently supports only round-robin load balancing and this proposal below aims to start adding a new option for load balancing strategies. Please feel free to comment and provide feedback at link below: https://docs.google.com/document/d/1EKzq7Bh0_7e8iwT8ikjlLMvq7prEyuBFysWCLSolBnY/edit?usp=sharing Note, this proposal is aiming to introduce a new load balancing strategy, however the work would very likely lay the groundwork for future alternative strategies. Cheers Mark St.Godard (IBM && CF Routing Team) and Bo Yang (IBM) |
|
|
|
Update on CF manifests and "BOSH 2.0"
Amit Kumar Gupta
Hey folks,
As new features are being added, and hardened, in BOSH around making manifests simultaneously simpler and more flexible [0], the Release Integration team in engaged in a track of work to start to leverage these features and provide manifests for the core Cloud Foundry platform for others to use. We're currently in the very early stages of this work, but I've tried to outline some of the planned work [1]. Anyone looking to get their hands on some examples to play with can check out an experimental repo I have [2], which has leveraged another experimental tool, bosh-bootloader [3], to do the environment setup. With "BOSH 2.0" features like Cloud Config and AZs, together with what bosh-bootloader does, a lot of the initial burden of setting up your AWS environment, configuring BOSH, and getting your IaaS-specific details into your manifest goes away already. But getting to the final manifest is still not as easy as we'd like. There are a few IaaS specific things in the example manifest around picking static IPs, but this will go away with "BOSH links" [4]. A lot of the repetition in the manifest should also go away with "BOSH links". A lot of the messy credentials can be cleaned up with BOSH config server [5]. There are a lot of useless "null"s in that manifest which are carried over from a spiff-generated manifest, and there are a small handful of values in the manifest that are specific to my deployment, e.g. my system and app domains "mega-test.cf-app.com". Both of these issues that are currently handled with tools like spiff or spruce [6] will become manageable with simpler templating and overriding logic that is planned to be built right into BOSH itself. [0] https://github.com/cloudfoundry/bosh-notes [1] https://docs.google.com/document/d/1x9hyQwu_dSnE2MUG-hUpEo2ehHdhFkcNo_85qXjASiY/edit?usp=sharing [2] https://github.com/Amit-PivotalLabs/bbl-cf-diego-bosh-2.0/blob/master/cf-manifest.yml [3] https://github.com/pivotal-cf-experimental/bosh-bootloader [4] https://github.com/cloudfoundry/bosh-notes/blob/master/links.md <https://github.com/cloudfoundry/bosh-notes/blob/master/links.md> [5] https://github.com/cloudfoundry/bosh-notes/blob/master/config-server.md [6] https://github.com/geofffranks/spruce Best, Amit |
|
|
|
Re: Status of cf-mysql-release v27
Mike Youngstrom <youngm@...>
The main issue I need a release for is the package rename work so I can
toggle quoted message
Show quoted text
colocate the mysql job with some other cf-release jobs. Thanks, Mike On Tue, Jul 5, 2016 at 5:11 PM, Marco Nicosia <mnicosia(a)pivotal.io> wrote:
Hi Mike, |
|
|
|
Re: Status of cf-mysql-release v27
Marco Nicosia
Hi Mike,
toggle quoted message
Show quoted text
I know it's been a bit longer than usual, but we're finally winding down. We're shooting for roughly the end of July. Love to hear what changes (aside from audit logs, which you've already talked with us about), you're anticipating? I'm always looking to hear more from the community about what's top of mind. -- Marco Nicosia Product Manager Pivotal Software, Inc. mnicosia(a)pivotal.io On Tue, Jul 5, 2016 at 10:41 AM, Mike Youngstrom <youngm(a)gmail.com> wrote:
There are a number of changes pending in v27 that I'm waiting for. Any |
|
|
|
cf-release Release Notes Feedback
Amit Kumar Gupta
I've invited you to fill out the following form:
cf-release Release Notes Feedback To fill it out, visit: https://docs.google.com/forms/d/1m8Z0nQ99WVgbaS9eygj9GdCK2SVXyKGGraX_4_GLfFE/viewform?c=0&;w=1&usp=mail_form_link Hey folks, I wanted to gather a quick little bit of feedback about the cf-release Release Notes, primarily around the quality and quantity of the content contained in each set of notes. If you're a regular consumer of these notes as you upgrade through versions of cf-release, your feedback would be much appreciated. Thanks, Amit Google Forms: Create and analyze surveys. |
|
|
|
feedback request: deprecate nats_stream_forwarder job from cf-release
Amit Kumar Gupta
Hey folks,
There's an old job in cf-release called nats_stream_forwarder that we want to potentially deprecate. It was intended in the past to help with debugging, but isn't currently seeing much active use. Would there be any objections to removing this from cf-release completely? (It currently lives in nats-release which is submoduled into cf-release: https://github.com/cloudfoundry/nats-release/blob/219e93bdb8a8e9fc0734fb0640b8b8d6edc14c3f/jobs/nats_stream_forwarder/spec#L4 ) Best, Amit |
|
|
|
Re: Gorouter handling 503
Mark St.Godard
Vinod
toggle quoted message
Show quoted text
The short answer is if the gorouter can dial / make a connection to the IP and port, then it will NOT fail over and retry a different node (if you have multiple backend endpoints) https://github.com/cloudfoundry/gorouter/blob/master/proxy/round_tripper/proxy_round_tripper.go#L61 The gorouter (currently) does NOT look at HTTP response codes and make any decisions based on that, such as trying different endpoints. For example: If you have a route that has 2 backend endpoints "foo.example.com": [ { "address": "10.244.0.26:60000", "ttl": 0 }, { "address": "10.244.0.26:60001", "ttl": 0 } ] If a request is made to http://foo.example.com and if the first endpoint selected during round robin is: 10.244.0.26:60000 if the gorouter instance CANNOT connect to that IP and port, then it will try the next endpoint: 10.244.0.26:60001 Hope that clears things up. However feel free to provide feedback to CF Routing team (slack channel or Github) if you had some enhancements in mind. Cheers Mark On Tue, Jul 5, 2016 at 10:57 AM, Kris Hicks <khicks(a)pivotal.io> wrote:
Given this and the previous discussion about gorouter returning 404 for an |
|
|