Date   

FINAL REMINDER: CAB call for April is Wednesday 05/16 @ 8a PST or 11a EST

Michael Maximilien
 

FYI...

Please remember to join Wednesday morning for QAs, highlights, and three presentations:

1. Brief update on App Auto Scaler project by Bo Yang of IBM

2. Brief update on Service Fabrik by Ashish Jain of SAP

3. Presentation and live demo of BOSH Kube CPI by Dmitriy Kalinin of Pivotal and myself

Zoom soon. Best,

dr.max
ibm ☁ 
silicon valley, ca



dr.max
ibm ☁ 
silicon valley, ca


On May 10, 2018, at 4:07 PM, Michael Maximilien <maxim@...> wrote:

FYI...

 

Reminder that the CAB call for May is scheduled for next Wednesday 05/16 @ 8a PST / 11a EST. Zoom Details here [1].

 

I have spot for one more presentation. Please contact me directly here or via slack so I can consider.


I’ll send one more reminder with details early next week.

 

Best,

 

------

dr.max

ibm  

silicon valley, ca

maximilien.org

 

[1] https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI 



Re: TCP Upgrade issue

Eric Malm <emalm@...>
 

Hi, Kunal,

Since you're still using a cf-release-based deployment manifest, I expect you also have a separate diego-release-based manifest to deploy the Diego cells and control-plane components, including the route-emitter. If that's correct, you should set the `tcp.enabled` BOSH property in your Diego manifest (for example, https://github.com/cloudfoundry/diego-release/blob/v1.31.0/manifest-generation/diego.yml#L264). This will configure the route-emitters (in either the cell-local or global modes) also to send TCP route registrations to the Routing API component, in addition to their original job of registering HTTP routes to the gorouters over the NATS message bus.

The README in routine-release v0.164.0 does mention at https://github.com/cloudfoundry/routing-release/tree/0.164.0#optional-redeploy-diego-to-enable-tcp-routes that this configuration is required to enable TCP route registrations and that you can enable it through the property-override input file to the spiff-based manifest generation script in diego-release.

Best,
Eric, CF Diego PM


On Mon, May 14, 2018 at 5:30 AM, Bagwe, Kunal <kunal.bagwe@...> wrote:
Hello Team,
 
We are aware that cf release is no longer supported by community but we are using cf release in production environment. Migration to cf deployment is under progress.
We are using cf release v283 and routing release v163.When we upgrade routing from v163 to v164, we are getting error "Empty Reply from Server" when we curl the TCP application.
While upgrading routing release from v163 to v164, we have commented out "tcp_emitter" jobs, just kept the oauth_secret property for tcp_emitter inside routing manifest as mentioned in below specified link :
As mentioned in link "https://lists.cloudfoundry.org/g/cf-dev/attachment/7102/0/attachment.html",
also added following properties in CF manifest file :
tcp.enabled: true
routing_api.url: defaults to http://routing-api.service.cf.internal
routing_api.port: defaults to 3000
routing_api.auth_enabled: defaults to true
We also checked the logs inside tcp_router, found an error as "tcp-router.watcher.failed-to-get-next-routing-api-event".
Also checked the logs for routing_api which stats following errors:
Lost lock 'v1/locks/routing_api_lock'
Exit trace for group:\n lock-releaser exited with error: Exit trace for group:\n lock-maintainer exited with error: lock lost\n\nsql-route-pruner exited with nil\n metrics exited with nil\n route-register exited with nil\n conn-stopper exited with nil\n api-server exited with nil\n seed-router-groups exited with nil\n lock-acquirer exited with nil\n migration exited with nil\n.
Also set the log_level to debug for routing_api and tcp_router.
As tcp_emitter support has been removed from routing release version 164, so what configuration has to be done in place of it.
Please suggests configurations, modifications to be performed.
Thanks & Regards,
Kunal Bagwe
Atos Cloud Foundry
Atos
 
 



TCP Upgrade issue

Bagwe, Kunal <kunal.bagwe@...>
 

Hello Team,
 
We are aware that cf release is no longer supported by community but we are using cf release in production environment. Migration to cf deployment is under progress.
We are using cf release v283 and routing release v163.When we upgrade routing from v163 to v164, we are getting error "Empty Reply from Server" when we curl the TCP application.
While upgrading routing release from v163 to v164, we have commented out "tcp_emitter" jobs, just kept the oauth_secret property for tcp_emitter inside routing manifest as mentioned in below specified link :
As mentioned in link "https://lists.cloudfoundry.org/g/cf-dev/attachment/7102/0/attachment.html",
also added following properties in CF manifest file :
tcp.enabled: true
routing_api.url: defaults to http://routing-api.service.cf.internal
routing_api.port: defaults to 3000
routing_api.auth_enabled: defaults to true
We also checked the logs inside tcp_router, found an error as "tcp-router.watcher.failed-to-get-next-routing-api-event".
Also checked the logs for routing_api which stats following errors:
Lost lock 'v1/locks/routing_api_lock'
Exit trace for group:\n lock-releaser exited with error: Exit trace for group:\n lock-maintainer exited with error: lock lost\n\nsql-route-pruner exited with nil\n metrics exited with nil\n route-register exited with nil\n conn-stopper exited with nil\n api-server exited with nil\n seed-router-groups exited with nil\n lock-acquirer exited with nil\n migration exited with nil\n.
Also set the log_level to debug for routing_api and tcp_router.
As tcp_emitter support has been removed from routing release version 164, so what configuration has to be done in place of it.
Please suggests configurations, modifications to be performed.
Thanks & Regards,
Kunal Bagwe
Atos Cloud Foundry
Atos
 
 


UAA on Compose for MySQL

Paul Bakare
 

Hi,

Caught something looking like a bug when UAA is faced with a clustered MySQL. Error details below:

2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT Migration V2_4_1__Zonify_Group_Memberships.sql failed

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT Statement  : UPDATE group_membership SET identity_zone_id = (SELECT identity_zone_id FROM users where users.id = group_membership.member_id)

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) ~[spring-beans-4.3.16.RELEASE.jar!/:4.3.16.RELEASE]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312) ~[spring-beans-4.3.16.RELEASE.jar!/:4.3.16.RELEASE]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308) ~[spring-beans-4.3.16.RELEASE.jar!/:4.3.16.RELEASE]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.16.RELEASE.jar!/:4.3.16.RELEASE]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     ... 49 common frames omitted

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT Statement  : UPDATE group_membership SET identity_zone_id = (SELECT identity_zone_id FROM users where users.id = group_membership.member_id)

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.flywaydb.core.internal.command.DbMigrate.access$800(DbMigrate.java:53) ~[flyway-core-4.2.0.jar!/:na]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.flywaydb.core.internal.metadatatable.MetaDataTableImpl.lock(MetaDataTableImpl.java:174) ~[flyway-core-4.2.0.jar!/:na]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:146) ~[flyway-core-4.2.0.jar!/:na]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.flywaydb.core.Flyway$1.execute(Flyway.java:1010) ~[flyway-core-4.2.0.jar!/:na]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.flywaydb.core.Flyway$1.execute(Flyway.java:971) ~[flyway-core-4.2.0.jar!/:na]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.flywaydb.core.Flyway.execute(Flyway.java:1464) ~[flyway-core-4.2.0.jar!/:na]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_172]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_172]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_172]

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT Caused by: java.sql.SQLException: (conn:32607) The table does not comply with the requirements by an external plugin.

   2018-05-11T22:06:17.47+0100 [APP/PROC/WEB/0] OUT     at org.mariadb.jdbc.internal.util.ExceptionMapper.throwAndLogException(ExceptionMapper.java:77) ~[mariadb-java-client-1.5.9.jar!/:na]



--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde


Re: CF Container Networking 2.0!

Shannon Coen
 

Kudos to the Networking team!

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Fri, May 11, 2018 at 11:11 AM, Amelia Downs <adowns@...> wrote:

Hello all,


The CF Container Networking team has released cf-networking-release 2.0.0 and silk-release 2.0.0.


The releases do not contain major new features, but do include breaking changes for how the Cloud Foundry container networking system is packaged, versioned and deployed.


The biggest change is that the Silk container networking fabric, which may be swapped out for other CNI-compatible network integrations, is now provided in a dedicated BOSH release.  That leaves cf-networking-release with only those "core" components (Network Policy API and CNI compatibility layer) that serve as extension points for network integrations.  The split is intended to simplify the development and deployment of 3rd party network integrations in Cloud Foundry Application Runtime.


More detail

  • To maintain existing container networking features in Cloud Foundry, operators will need to deploy both cf-networking-release and silk-release.  This is a breaking change for operators.

  • We've "de-namespaced" many of the BOSH manifest properties and renamed some bosh jobs.  For manifest authors, these are breaking changes.

  • Starting now and going forward, we plan to release both cf-networking-release and silk-release at the same time, with the same version numbers.  Operators using silk-release should plan to deploy both releases together; we won't support mixed-version deployments.

  • We continue to provide upgrade guarantees from cf-networking-release 1.x to the 2.x versions.

  • To deploy these releases with cf-deployment, we recommend using the use-cf-networking-2.yml experimental ops-file.  Longer term, we're intending for the 2.x versions to become default in cf-deployment.


For details, look at our release notes for cf-networking-release and silk-release.  If you have a non-standard BOSH manifest, be sure to read the cf-networking-release manifest changelog and silk-release manifest changelog.


As always, we welcome your questions and feedback in our Slack channel #container-networking or in reply to this message.


Try it out!

These new releases will be included by default in cf-deployment 2.0. Until then, you can use the opsfile cf-deployment/operations/experimental/use-cf-networking-2.yml


We have also duplicated and fixed other affected opsfiles, and suffixed them with ‘with-networking-2.yml’.


Best,

The CF Container Networking Team





CF Container Networking 2.0!

Amelia Downs
 

Hello all,


The CF Container Networking team has released cf-networking-release 2.0.0 and silk-release 2.0.0.


The releases do not contain major new features, but do include breaking changes for how the Cloud Foundry container networking system is packaged, versioned and deployed.


The biggest change is that the Silk container networking fabric, which may be swapped out for other CNI-compatible network integrations, is now provided in a dedicated BOSH release.  That leaves cf-networking-release with only those "core" components (Network Policy API and CNI compatibility layer) that serve as extension points for network integrations.  The split is intended to simplify the development and deployment of 3rd party network integrations in Cloud Foundry Application Runtime.


More detail

  • To maintain existing container networking features in Cloud Foundry, operators will need to deploy both cf-networking-release and silk-release.  This is a breaking change for operators.

  • We've "de-namespaced" many of the BOSH manifest properties and renamed some bosh jobs.  For manifest authors, these are breaking changes.

  • Starting now and going forward, we plan to release both cf-networking-release and silk-release at the same time, with the same version numbers.  Operators using silk-release should plan to deploy both releases together; we won't support mixed-version deployments.

  • We continue to provide upgrade guarantees from cf-networking-release 1.x to the 2.x versions.

  • To deploy these releases with cf-deployment, we recommend using the use-cf-networking-2.yml experimental ops-file.  Longer term, we're intending for the 2.x versions to become default in cf-deployment.


For details, look at our release notes for cf-networking-release and silk-release.  If you have a non-standard BOSH manifest, be sure to read the cf-networking-release manifest changelog and silk-release manifest changelog.


As always, we welcome your questions and feedback in our Slack channel #container-networking or in reply to this message.


Try it out!

These new releases will be included by default in cf-deployment 2.0. Until then, you can use the opsfile cf-deployment/operations/experimental/use-cf-networking-2.yml


We have also duplicated and fixed other affected opsfiles, and suffixed them with ‘with-networking-2.yml’.


Best,

The CF Container Networking Team




Voting is open! (Re: Summit EU: CFP and Co-Chair Nominations)

Swarna Podila
 

Love the number of nominations we received for the track co-chairs!  Great job, everyone.

Please look at the nominations for each track and cast your vote today!  The deadline to submit your vote is May 15th 11.59pm US pacific time.

If you have any questions, unicast me here or ping me on slack.

Thank you,
Swarna.


CAB call for April is Wednesday 05/16 @ 8a PST or 11a EST

Michael Maximilien
 

FYI...

 

Reminder that the CAB call for May is scheduled for next Wednesday 05/16 @ 8a PST / 11a EST. Zoom Details here [1].

 

I have spot for one more presentation. Please contact me directly here or via slack so I can consider.


I’ll send one more reminder with details early next week.

 

Best,

 

------

dr.max

ibm  

silicon valley, ca

maximilien.org

 

[1] https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI 



Re: BookInfo app demo with Envoy as the edge router in CF

Chip Childers <cchilders@...>
 

Outstanding progress. This is really great to see Shubha and team!

On Thu, May 10, 2018 at 12:15 PM Shubha Anjur Tupil <sanjurtupil@...> wrote:

[Edited Message Follows]

Hello all, 
 
The routing team has been working on integrating Envoy and Istio in the routing control plane. Yesterday we were able to run the BookInfo demo with Envoy as the edge router ( still using DNS load balancing for E-W traffic). See the attached GIF for a micro-demo and see the requests load balanced between the three versions of the reviews app (the black stars, red stars, and no stars with a written review). 
 
While this is test-driven and CI'd functionality, we want to clarify that istio-release is considered experimental/alpha.
 
For more on our initiative to leverage Istio and Envoy, see https://docs.google.com/document/d/1LgLY0g39fzpg1_4zTckbH1mOuuSKGvYwp2tkakoe9ys/edit
 
​​
Routing team

--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815


BookInfo app demo with Envoy as the edge router in CF

Shubha Anjur Tupil
 
Edited

Hello all, 
 
The routing team has been working on integrating Envoy and Istio in the routing control plane. Yesterday we were able to run the BookInfo demo with Envoy as the edge router ( still using DNS load balancing for E-W traffic). See the attached GIF for a micro-demo and see the requests load balanced between the three versions of the reviews app (the black stars, red stars, and no stars with a written review). 
 
While this is test-driven and CI'd functionality, we want to clarify that istio-release is considered experimental/alpha.
 
For more on our initiative to leverage Istio and Envoy, see https://docs.google.com/document/d/1LgLY0g39fzpg1_4zTckbH1mOuuSKGvYwp2tkakoe9ys/edit
 
​​
Routing team


Re: How to check validity of access token in UAA? #cf

Tian Wang
 

Hi Shilpa,

The introspection endpoint was added in UAA 4.9.0. From your Postman, it shows your UAA version is 4.3.0. If you check out the latest UAA, you should see the endpoint work. Prior to 4.9.0, UAA has the check_token endpoint but it does not include the active flag, and returns 4XX errors for invalid tokens.

Regards,

Tian

On Tue, May 8, 2018 at 4:08 AM, shilpa kulkarni <shilpakulkarni91@...> wrote:
Hello,

I am using cloud foundry UAA APIs.  I want to check whether the access token has expired or not . In the API documentation,  I am getting Introspect token API[Active flag is responsible for showing the validity of the token].
Reference link:
http://docs.cloudfoundry.org/api/uaa/version/4.12.0/#introspect-token

But while testing this Introspect token API in postman, I am getting 404 Not found error. Following is my test documentation:
https://documenter.getpostman.com/view/1991110/introspect-token/RW1gFHma

How to check validity of access token? 

Thanks & Regards
Shilpa Kulkarni



NOTICE: [python-buildpack] End of Python 3.3.x support after 2018-06-08

Scott Sisil
 

Support for Python 3.3.x will be removed in the first release of the Python buildpack after 2018-06-08.


Per Python Development policy, all support for the 3.3 series of releases ended on 2017-09-29, five years after the initial release[1]. We are giving users a 30 day notice before support for Python 3.3.x is officially removed from the Python buildpack. Because 3.3.x has long been in security-fix mode, 3.3.7 may no longer build correctly on all current operating system releases and some tests may fail.  If you are still using Python 3.3.x, we strongly encourage you to upgrade to a more recent, fully supported version of Python 3.


[1] https://www.python.org/downloads/release/python-337/




Scott


CF Buildpacks PM




How to check validity of access token in UAA? #cf

shilpa kulkarni
 

Hello,

I am using cloud foundry UAA APIs.  I want to check whether the access token has expired or not . In the API documentation,  I am getting Introspect token API[Active flag is responsible for showing the validity of the token].
Reference link:
http://docs.cloudfoundry.org/api/uaa/version/4.12.0/#introspect-token

But while testing this Introspect token API in postman, I am getting 404 Not found error. Following is my test documentation:
https://documenter.getpostman.com/view/1991110/introspect-token/RW1gFHma

How to check validity of access token? 

Thanks & Regards
Shilpa Kulkarni


Re: Proposed BOSH logging interface

Marco Voelz
 

Dear Jesse,


Thanks for putting this proposal out there. We would be happy to see an automated logfile forwarding mechanism. Here's a couple of comments on your initial points:

* Including the filename in the syslog metadata is very useful and something we'd really like to have. Currently it is something we're working around a bit.

* The appname/tag field should probably contain the release's name as well as a prefix. My proposal here is `<deployment name>.<instance group name>.<job name>`. wdyt?

* We haven't made any particular use of the priority field, so losing control over this field wouldn't matter for out use-cases. Severity is usually something that the actual log message needs to contain, as the logger's severity can only be set on its initial creation, afaik.

* Restricting the depth of recursion seems reasonable. So far, I don't think we're using bosh releases which have more than 1 folder below their /var/vcap/sys/log/<job name>/ folder.


Concerning the requirements about permissions on the logfiles you'd want to forward: Did you talk to Dmitriy/the BOSH team about this? With stemcell series 3541.x the permissions on the standard folders below /var/vcap were tightened a bit, so just wanted to make sure that your assumptions are in line with the upcoming changes in the stemcells.


Warm regards

Marco


From: cf-dev@... <cf-dev@...> on behalf of Jesse T. Alford <jalford@...>
Sent: Tuesday, April 3, 2018 12:55:38 AM
To: cf-dev@...
Subject: [cf-dev] Proposed BOSH logging interface
 
Hello! We're the CF Platform Logging team. We maintain `syslog-release` and have been working to improve and regularize platform logging behavior.

This is a proposal intended to establish reasonable expectations about what should be logged and what should be forwarded in bosh-deployed cloud systems.

Historically, it has been up to each release to provide for their log forwarding, if any. We intend `syslog-release` to provide a consistent interface useful enough to replace all other provisions for the forwarding of logs from bosh jobs.

## Proposed Interface
If log forwarding is enabled, some files in `/var/vcap/sys/log` (and its subdirectories, recursively), will have any line written to them forwarded as the MSG portion of an RFC5424 compliant syslog message. Which files are forwarded is governed first by file extension, and secondarily by file permissions.

`syslog-release` attempts to read any file ending in `.log`.
(This allows us to avoid forwarding rotated logs, swapfiles, etc.)
It will forward from such files if either of the following are true:
- it is world-readable
- it is readable to the `vcap` group

In particular, this means that logs will not be forwarded from files where:
- user and group are root:root
- user and group are vcap:root or vcap:none
- user and group are vcap:vcap, but it is not group-readable

…unless they are world-readable.

We think that this interface will allow us to avoid running a log forwarder with elevated permissions, while also allowing jobs to, for instance, write DEBUG or similar logs to a file that is not group-readable, thus improving their security and reducing the load on the logging system while still making them available on the ephemeral disk for debugging purposes.

## Questions
There are a couple of things around this interface we're especially interested in feedback on, in addition to the obvious "will this be a problem for you" overall question.

We may have to have a proviso that the depth of this is not unlimited. This depends somewhat on what is inexpensive to implement and maintain, and is an area we'd appreciate feedback on. Is three levels deep from `/var/vcap/sys/log` (i.e. `/var/vcap/sys/log/jobname/processname/*`) enough? Would four be?

In the old way of doing things, more control over the PRI information and other syslog fields was available to release authors. Logs forwarded from files currently all come out as PRI 14, which translates to Facility: User, Severity: Info. Additionally, the appname/tag field is set to the name of the directory containing the log file. Is this enough/good info? If we were to include the filename, too, would that be useful? Sufficient?

## Testing with the Proposed Interface
We have recently implemented a feature to help release authors evaluate the proposed interface. If you set `syslog.respect_file_permissions: true`, blackbox will not be run with elevated capabilities, and you'll be able to see what is and isn't forwarded under the proposed interface.


Re: Equivalent API to adding member to a group

Paul Bakare
 

Nevermind. UAA /Groups does it.

On Mon, May 7, 2018 at 11:09 PM, Paul Bakare <dreyemi@...> wrote:
Hi,

What's the equivalent UAA API to:

uaac member add custom.report xyz@...

--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde




--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde


Equivalent API to adding member to a group

Paul Bakare
 

Hi,

What's the equivalent UAA API to:

uaac member add custom.report xyz@...

--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde


NOTICE : [ruby-buildpack] End of Node.js 4.x support after 2018-06-07

Scott Sisil <ssisil@...>
 

Support for Node.js 4.x will be removed in the first release of the Ruby buildpack after 2018-06-07.


The Node.js Release Working Group ended support for Node.js 4.x on 2018-04-30 [1][2]. We are giving users a 30 day notice before support for Node.js 4.x is officially removed from the Ruby buildpack.  We recommend migrating any applications using release 4.x to LTS release 6.x.


Scott Sisil


CF Buildpacks PM


[1] https://github.com/nodejs/Release

[2] https://medium.com/the-node-js-collection/april-2018-release-updates-from-the-node-js-project-71687e1f7742


Re: Call for Demos - CF / K8S Integration SIG Meeting

Chip Childers <cchilders@...>
 

Also: for Wednesday I forgot that Dobromir also was preparing to demo the service manager project!

On Sun, May 6, 2018 at 6:56 PM Chip Childers <cchilders@...> wrote:
Outstanding response to this request folks!

For this Wednesday, I'd like to ask for:

(1) Sree to demonstrate UAA + k8s
(2) Julz to demonstrate Erini

Along with both of those, we should do a round up of updates from anyone working in related areas / projects.

I'll work with the other proposals to find a good slot in the coming meetings. I have proposals from Jeenal, Dr Max, Adam H and Ashish. Should if I missed an email or you want to be on the list too!

-chip


On Thu, Apr 26, 2018 at 5:53 PM Chip Childers <cchilders@...> wrote:
During yesterday's CF/K8S SIG meeting, several speakers proposed demo'ing their various efforts during a future call.

I'd like to formally request replies from anyone interested in giving a demo, and we'll work out an agenda for the next (and future) SIG calls based on responses.

So far, I have an offer from SAP for Dobromir Zahariev to demo the work around service catalog sync between CFAR and K8S.

Anyone else willing?

-chip
--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815
--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815
--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815


Re: Call for Demos - CF / K8S Integration SIG Meeting

Chip Childers <cchilders@...>
 

Outstanding response to this request folks!

For this Wednesday, I'd like to ask for:

(1) Sree to demonstrate UAA + k8s
(2) Julz to demonstrate Erini

Along with both of those, we should do a round up of updates from anyone working in related areas / projects.

I'll work with the other proposals to find a good slot in the coming meetings. I have proposals from Jeenal, Dr Max, Adam H and Ashish. Should if I missed an email or you want to be on the list too!

-chip

On Thu, Apr 26, 2018 at 5:53 PM Chip Childers <cchilders@...> wrote:
During yesterday's CF/K8S SIG meeting, several speakers proposed demo'ing their various efforts during a future call.

I'd like to formally request replies from anyone interested in giving a demo, and we'll work out an agenda for the next (and future) SIG calls based on responses.

So far, I have an offer from SAP for Dobromir Zahariev to demo the work around service catalog sync between CFAR and K8S.

Anyone else willing?

-chip
--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815
--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815


Re: How can we customized "404 Not Found"

David McClure
 

Nice! Love the gif demo :)

On Wed, May 2, 2018 at 6:32 PM, Shannon Coen <scoen@...> wrote:

[Edited Message Follows]

Today the CF Routing team added the ability for an Envoy proxy deployed as the edge router for CF (using istio-release) to return a 503 instead of a 404 for a requested route when the mapped app is stopped or crashing. 

We are thrilled as this represents the first new routing feature in Cloud Foundry enabled by our next-gen routing subsystem based on Istio and Envoy. See the attached GIF for a micro-demo. 

While this is test-driven and CI'd functionality, I want to clarify that istio-release is considered experimental/alpha. 

For more on our initiative to leverage Istio and Envoy, see https://docs.google.com/document/d/1LgLY0g39fzpg1_4zTckbH1mOuuSKGvYwp2tkakoe9ys/edit


1381 - 1400 of 9377