Date   

Re: Update on Mailman 3 launch

Marco Nicosia
 

Hi Marco V,

Thanks for remembering to keep on this.

Now that you mention it, I haven't gotten any cf-bosh digests till I
suddenly got two this morning.

But less recent e-mails ("Bosh target password." from Sept 2) have never
appeared in my inbox.


--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io
c: 650-796-2948

On Thu, Sep 10, 2015 at 8:07 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote:

Bump & adding Eric and Marco Nicosia directly, just in case. Any updates
on this?




On 28/08/15 11:23, "Marco Voelz" <marco.voelz(a)sap.com> wrote:

Hi Eric,

Just to confirm, did you leave it enabled in "mime digest" mode for
longer than
a day so that there was list traffic to bundle and digest for you? I
don't see any
errors in the error log related to MIME digest sends, but see about
reproducing this today
and submit a bug.
Yes, I can confirm that I left mime digest on for several days and there
were mails which I didn't receive. Note that regular digests aren't working
for me, either. Currently the only working setting seems to be single mail
delivery, which is not my preferred setting.

Did you manage to reproduce that?

The preference lookup appears to give precedence to the settings on the
subscription, then
on the address, then on the user ("global"), and finally on the system
default—it stops at the first defined value it sees. I'll file a bug
to have some
better clarification in the UI.
Great, thanks for the bug and the explanation!

Warm regards
Marco


Re: UAA user dynamic properties

Sree Tummidi
 

Just wanted to add that we could collaborate on the design front and we are open to pull requests !!

-sree

Sent from my iPad

On Sep 10, 2015, at 6:45 AM, Sree Tummidi <stummidi(a)pivotal.io> wrote:

Hi,
We do have plans to support custom attributes and is a roadmap item. This is however not in the immediate future.

Thanks,
Sree

Sent from my iPhone

On Sep 10, 2015, at 4:13 AM, Viktor Khoroshko <oceansize(a)tut.by> wrote:

Hello everyone,

We're currently evaluating UAA to be used as Central Identity Provider in our system. And the issue for us is that It's not allowed to store additional user properties (you're limited by users columns that are currently supported).
Therefore, we have a question - are there any plans to add user dynamic properties support in future releases? Or, at least, do you agree that this would be an useful feature (so we may contribute)?

Thanks in advance


Re: Stdout from Spring Boot app in CF

Qing Gong
 

Thanks James. It was my mistake in Spring Boot app configuration. The stdout did go to the firehose.

Sorry about this.


Re: Update on Mailman 3 launch

Marco Voelz
 

Bump & adding Eric and Marco Nicosia directly, just in case. Any updates on this?

On 28/08/15 11:23, "Marco Voelz" <marco.voelz(a)sap.com> wrote:

Hi Eric,

Just to confirm, did you leave it enabled in "mime digest" mode for longer than
a day so that there was list traffic to bundle and digest for you? I don't see any
errors in the error log related to MIME digest sends, but see about reproducing this today
and submit a bug.
Yes, I can confirm that I left mime digest on for several days and there were mails which I didn't receive. Note that regular digests aren't working for me, either. Currently the only working setting seems to be single mail delivery, which is not my preferred setting.

Did you manage to reproduce that?

The preference lookup appears to give precedence to the settings on the subscription, then
on the address, then on the user ("global"), and finally on the system
default—it stops at the first defined value it sees. I'll file a bug to have some
better clarification in the UI.
Great, thanks for the bug and the explanation!

Warm regards
Marco


Re: Stdout from Spring Boot app in CF

James Bayer
 

can you supply a simple sample example on github or similar that
demonstrates the issue? i haven't had issues with using spring boot logs on
CF before.

On Thu, Sep 10, 2015 at 5:56 AM, Qing Gong <qinggong(a)gmail.com> wrote:

I can get a simple Java app stdout (deployed using cf push JavaClass) to
go to firehose as logging messages. However, when I deployed a Spring Boot
app, I don't get the logging (to stdout) messages from the firehose. If I
just ran the Spring Boot app alone (using java -jar SpringBootApp.jar
instead of cf push SpringBootApp.jar), I could get the messages coming out
in the console or log file that I configured through log4j. System.out also
works fine in the console. So, why stdout doesn't work from a Spring Boot
app for firehose collection? How is it different from a plain Java app
which works fine for firehose?

Thanks!
--
Thank you,

James Bayer


Re: Java Buildpack v3.2

James Bayer
 

chris,

congrats on the release. this has lots of very nice improvements. i thought
Luna HSM was more about a hardware security module for establishing trust
instead of a way to add entropy to a system. does it also have capabilities
related to entropy?

On Thu, Sep 10, 2015 at 4:22 AM, Christopher Frost <cfrost(a)pivotal.io>
wrote:

I'm pleased to announce the release of the java-buildpack, version 3.2. This
release focuses on more options to configure JRE memory settings. It has
the following highlights:

- Memory calculator 2.0.0 which includes support for specifying
initial memory values and expected thread values.
- Support for Luna HSM service to provide entropy.
- Improved Dynatrace documentation. (via Josef Hoerandtner
<https://github.com/cloudfoundry/java-buildpack/pull/207>)
- Allow any additional New Relic configuration to be passed through to
the agent. (via Bryan Custer
<https://github.com/cloudfoundry/java-buildpack/issues/221>)
- Support for Spring Insight updated to version 2.0.0.

For a more detailed look at the changes in 3.2, please take a look at the commit
log <https://github.com/cloudfoundry/java-buildpack/compare/v3.1.1...v3.2>.
Packaged versions of the buildpack, suitable for use with create-buildpack
and update-buildpack, can be found attached to this release
<https://github.com/cloudfoundry/java-buildpack/releases/tag/v3.2>.
*Packaged Dependencies*

- AppDynamics Agent: 4.1.3_1
- GemFire 8.0.0
- GemFire Modules 8.0.0.1
- GemFire Modules Tomcat7 8.0.0.1
- GemFire Security 8.0.0
- Groovy: 2.4.4
- JRebel 6.2.3
- MariaDB JDBC: 1.2.0
- Memory Calculator (mountainlion): 2.0.0.RELEASE
- Memory Calculator (precise): 2.0.0.RELEASE
- Memory Calculator (trusty): 2.0.0.RELEASE
- New Relic Agent: 3.20.0
- OpenJDK JRE (mountainlion): 1.8.0_60
- OpenJDK JRE (precise): 1.8.0_60
- OpenJDK JRE (trusty): 1.8.0_60
- Play Framework JPA Plugin: 1.10.0.RELEASE
- PostgreSQL JDBC: 9.4.1202
- RedisStore: 1.2.0_RELEASE
- Spring Auto-reconfiguration: 1.10.0_RELEASE
- Spring Boot CLI: 1.2.5_RELEASE
- Tomcat Access Logging Support: 2.4.0_RELEASE
- Tomcat Lifecycle Support: 2.4.0_RELEASE
- Tomcat Logging Support: 2.4.0_RELEASE
- Tomcat: 8.0.26


Christopher Frost - Pivotal UK
Java Buildpack Team


--
Thank you,

James Bayer


Re: UAA user dynamic properties

Sree Tummidi
 

Hi,
We do have plans to support custom attributes and is a roadmap item. This is however not in the immediate future.

Thanks,
Sree

Sent from my iPhone

On Sep 10, 2015, at 4:13 AM, Viktor Khoroshko <oceansize(a)tut.by> wrote:

Hello everyone,

We're currently evaluating UAA to be used as Central Identity Provider in our system. And the issue for us is that It's not allowed to store additional user properties (you're limited by users columns that are currently supported).
Therefore, we have a question - are there any plans to add user dynamic properties support in future releases? Or, at least, do you agree that this would be an useful feature (so we may contribute)?

Thanks in advance


Stdout from Spring Boot app in CF

Qing Gong
 

I can get a simple Java app stdout (deployed using cf push JavaClass) to go to firehose as logging messages. However, when I deployed a Spring Boot app, I don't get the logging (to stdout) messages from the firehose. If I just ran the Spring Boot app alone (using java -jar SpringBootApp.jar instead of cf push SpringBootApp.jar), I could get the messages coming out in the console or log file that I configured through log4j. System.out also works fine in the console. So, why stdout doesn't work from a Spring Boot app for firehose collection? How is it different from a plain Java app which works fine for firehose?

Thanks!


Re: Add app monitoring agent framework in custom buildpack

Christopher Frost
 

Hi,

The Java Buildpack is under the Apache License so you can reuse the code as
you like but obviously you will need to rewrite it from Ruby to Java if
your buildpack is written in Java. The steps you will need to go through to
get New Relic or Wily working will be very similar regardless of the
language the buildpack is written in.


Christopher Frost - Pivotal UK
Java Buildpack Team

On Thu, Sep 10, 2015 at 9:07 AM, Swatz bosh <swatzron(a)gmail.com> wrote:

Hello,

I have a custom buildpack of my software and and I want to use NewRelic/CA
Wily agent frameworks which is added in java-buildpack [1].
So may I know what all components of these agents I can reuse from
java-buildpack? I found that these agents are written in Ruby, so can I
reuse them in my buildpack which is on java?

[1]
https://github.com/cloudfoundry/java-buildpack/blob/master/lib/java_buildpack/framework/new_relic_agent.rb


Thanks


Java Buildpack v3.2

Christopher Frost
 

I'm pleased to announce the release of the java-buildpack, version 3.2. This
release focuses on more options to configure JRE memory settings. It has
the following highlights:

- Memory calculator 2.0.0 which includes support for specifying initial
memory values and expected thread values.
- Support for Luna HSM service to provide entropy.
- Improved Dynatrace documentation. (via Josef Hoerandtner
<https://github.com/cloudfoundry/java-buildpack/pull/207>)
- Allow any additional New Relic configuration to be passed through to
the agent. (via Bryan Custer
<https://github.com/cloudfoundry/java-buildpack/issues/221>)
- Support for Spring Insight updated to version 2.0.0.

For a more detailed look at the changes in 3.2, please take a look at
the commit
log <https://github.com/cloudfoundry/java-buildpack/compare/v3.1.1...v3.2>.
Packaged versions of the buildpack, suitable for use with create-buildpack
and update-buildpack, can be found attached to this release
<https://github.com/cloudfoundry/java-buildpack/releases/tag/v3.2>.
*Packaged Dependencies*

- AppDynamics Agent: 4.1.3_1
- GemFire 8.0.0
- GemFire Modules 8.0.0.1
- GemFire Modules Tomcat7 8.0.0.1
- GemFire Security 8.0.0
- Groovy: 2.4.4
- JRebel 6.2.3
- MariaDB JDBC: 1.2.0
- Memory Calculator (mountainlion): 2.0.0.RELEASE
- Memory Calculator (precise): 2.0.0.RELEASE
- Memory Calculator (trusty): 2.0.0.RELEASE
- New Relic Agent: 3.20.0
- OpenJDK JRE (mountainlion): 1.8.0_60
- OpenJDK JRE (precise): 1.8.0_60
- OpenJDK JRE (trusty): 1.8.0_60
- Play Framework JPA Plugin: 1.10.0.RELEASE
- PostgreSQL JDBC: 9.4.1202
- RedisStore: 1.2.0_RELEASE
- Spring Auto-reconfiguration: 1.10.0_RELEASE
- Spring Boot CLI: 1.2.5_RELEASE
- Tomcat Access Logging Support: 2.4.0_RELEASE
- Tomcat Lifecycle Support: 2.4.0_RELEASE
- Tomcat Logging Support: 2.4.0_RELEASE
- Tomcat: 8.0.26


Christopher Frost - Pivotal UK
Java Buildpack Team


UAA user dynamic properties

Viktor Khoroshko
 

Hello everyone,

We're currently evaluating UAA to be used as Central Identity Provider in our system. And the issue for us is that It's not allowed to store additional user properties (you're limited by users columns that are currently supported).
Therefore, we have a question - are there any plans to add user dynamic properties support in future releases? Or, at least, do you agree that this would be an useful feature (so we may contribute)?

Thanks in advance


Add app monitoring agent framework in custom buildpack

Swatz bosh
 

Hello,

I have a custom buildpack of my software and and I want to use NewRelic/CA Wily agent frameworks which is added in java-buildpack [1].
So may I know what all components of these agents I can reuse from java-buildpack? I found that these agents are written in Ruby, so can I reuse them in my buildpack which is on java?

[1] https://github.com/cloudfoundry/java-buildpack/blob/master/lib/java_buildpack/framework/new_relic_agent.rb


Thanks


script cleanup in cf-release

Amit Kumar Gupta
 

Hi cf-dev,

This is a final reminder that we will be cleaning up the various scripts
that had sprawled across cf-release, deleting unused ones and moving the
rest to the scripts directory.

Moves:
* bosh-lite/make_manifest -> scripts/generate-bosh-lite-dev-manifest
* generate_deployment_manifest -> scripts/generate_deployment_manifest
* update -> scripts/update
* update.bat -> scripts\update.bat

Deletions:
* scripts/travis/install_spiff
* check_travis.rb
* outdated
* outdated_stats
* the entire "shared" submodule

Please update your workflows, dev tooling, and CI scripts to reflect the
upcoming changes.

Best,
Amit


Re: How to deploy a Web application using HTTPs

James Bayer
 

the standard way to do this is to terminate SSL at a load balancer, which
then forwards to the CF routing tier. the hop between the load balancer and
the cf router may be done with SSL. the network path from gorouter to the
DEA / Diego Cell backend is only supported with http today. the gorouter
must be able to inspect the request to see the http host header and cookies
(to evaluate session stickiness) to know which app the request is intended
for.

the TCP router which is coming soon and available to preview with lattice.cf
would open up the opportunity to use a random port to identify the app,
which could then pass through to the the backend that had a secure listen
port.

On Wed, Sep 9, 2015 at 1:45 AM, Juan Antonio Breña Moral <
bren(a)juanantonio.info> wrote:

Hi James,

Yes, you have reason, I returned to test:

https://nodejsssl.MY_IP.xip.io/

and I see the sreeen where Chrome advise the user about a
NET::ERR_CERT_AUTHORITY_INVALID so, the node application is running:


https://raw.githubusercontent.com/jabrena/CloudFoundryLab/master/Node_HelloWorld_ssl/docs/firstScreen.png

but if you click to continue, I receive this message:

404 Not Found: Requested route ('nodejsssl.MY_IP.xip.io') does not exist.

My question is CF could fix this issue to deploy applications which it
runs with https protocol.

Juan Antonio


--
Thank you,

James Bayer


Re: cf push hanged in after package donwload

Amit Gupta
 

Hi David,

Looks like this question is a duplicate of the issue you just opened here: https://github.com/cloudfoundry/cf-release/issues/783

Please look for our response to this question in the next few days over on the github issue.

Best,
Amit


Re: consolidated routing api

Shannon Coen
 

Some of the proposed changes to the Routing API are backward incompatible.
We don't believe anyone is using it yet, as adoption has generally be
blocked on securing connections to Consul, but we'd like to confirm.

Please raise your hand if you're using the routing API.

Thank you!

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Wed, Sep 9, 2015 at 12:10 PM, Shannon Coen <scoen(a)pivotal.io> wrote:

We currently have two routing APIs in CF.
1. HTTP Routing API in cf-release:
https://github.com/cloudfoundry-incubator/routing-api
2. TCP Routing API in cf-routing-release:
https://github.com/cloudfoundry-incubator/cf-routing-release

The TCP Routing API is quite basic and we want to extend it for high
availability, authentication, etc. However, instead of enhancing the
existing TCP Routing API, we plan to add support for TCP route registration
to the Routing API in cf-release, as it already supports many of the
desired features. We'll get rid of the current API in cf-routing-release
and submodule in the Routing API from cf-release. Eventually we'll move the
Routing API (along with GoRouter and HAProxy) from cf-release into
cf-routing-release and submodule them into cf-release.

This consolidation, along with our not having any API consumer besides
GoRouter yet, gives us the opportunity to consider a common behavior for
routing API endpoints. We welcome your comments in our design doc:


https://docs.google.com/document/d/1v941oy3Y7RRI80gmLfhPZlaahElK_Q0C3pCQewK8Z3g/edit?usp=sharing

Thank you,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.


Re: tcp-routing in Lattice

Marco Nicosia
 

Hi Jack,

In addition to Atul's suggestions, could you please give us the exact
command lines which you used to launch the two apps?

The CLI arguments are tricky, we may be able to see something about the way
you've tried to configure the routes by looking at how you've launched the
apps.

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io
c: 650-796-2948

On Wed, Sep 9, 2015 at 2:32 PM, Jack Cai <greensight(a)gmail.com> wrote:

I'm playing around with the tcp-routing feature in the latest Lattice
release. I started two node.js applications in the pushed image (listening
on two ports), one mapped to an http route and the other to a tcp route. I
can connect to the http route successfully in the browser, but when I try
to connect to the tcp port in the browser, I got connection refused. It
looks like the mapped public tcp port on 192.168.11.11 is not open at all.
Any advice on how to diagnose this? Thanks in advance!

Jack


Important changes in CF v217

Amit Kumar Gupta
 

This release introduces significant improvements to the security of the
consul cluster, however the operator must introduce these changes over the
course of multiple deployments. If you are not running any consul servers
as part of your deployment, you can ignore these instructions. Otherwise,
please do the following:

1. Scale the number of consul servers in your existing deployment down to 1
instance. The consul.agent.servers.lan property must be updated to reflect
this; this should happen for free if you are using the standard tooling for
manifest generation. If you are deploying Diego alongside CF, you must
redeploy Diego as well to pick up the consul.agent.servers.lan change;
again, this should happen for free if using the standard manifest
generation tooling.

2. Generate SSL certificates, keys, and a separate encryption key for the
gossip protocol used by consul (instructions:
https://docs.cloudfoundry.org/deploying/consul-security.html). Upload the
v217 release and generate your manifest for CF (and then Diego, if also
deploying Diego).

3. Deploy CF (and then Diego, if also deploying Diego).

4. Scale the number of consul servers back up to whatever you had it at
before. Regenerate all relevant manifests and deploy.

Best,
Amit


Re: tcp-routing in Lattice

Atul Kshirsagar
 

Its possible that HAProxy was not properly configured. Can you provide output of `ltc status <app name>`? This will tell if tcp route has been configured for the app.

Some things you can try:
1) You can then try doing `ltc update --tcp-route externalport:containerport` and see if that fixes the problem (this will result in reconfiguring HAProxy again).
2) If that doesn't work too...then try vagrant reload to make sure all the processes in lattice brain are restarted to rule out the problem that HAproxy is not in bad state.


Re: v3 cc api style guide feedback requested

Dieu Cao <dcao@...>
 

Thanks Guillaume!

On Wed, Sep 9, 2015 at 2:33 PM, Guillaume Berche <bercheg(a)gmail.com> wrote:

Hi Dieu,

Here are corresponding issues/comments submitted

https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/46
https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/47
https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/48
https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/49

https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/41#issuecomment-139050180

https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/41#issuecomment-139051114

Guillaume.

On Wed, Sep 9, 2015 at 10:39 AM, Dieu Cao <dcao(a)pivotal.io> wrote:

Hi Guillaume,

Just to ensure that it will be addressed, could you add it as github
issues on the repo? Hoping to do another pass at the remaining open issues
later this week.

-Dieu

On Mon, Sep 7, 2015 at 2:09 PM, Guillaume Berche <bercheg(a)gmail.com>
wrote:

Thanks for sharing this great spec.

Not sure if you're preferring feedback other the mailing list of GH
issue. Let me know.

General feedback:

+1 for a formal schema for the v3 api as to ease automatic client
generations (api explorer, java sdk, go sdk...) (e.g. swagger format)
Automated tests on the formal schema may also help checking the style guide
is respected. https://www.pivotaltracker.com/story/show/99237980 seems
to only consider documentation benefits so far and not yet client
generation benefits (e.g. https://github.com/swagger-api/swagger-codegen
https://github.com/swagger-api/swagger-codegen/issues/325 )

Would be nice to clarify support for non ascii characters in query
params, such as support for IRI
https://en.wikipedia.org/wiki/Internationalized_resource_identifier as
to avoid mojibake bugs such as the one presumed in
https://github.com/cloudfoundry/cli/issues/560

Would be nice to consider supporting gzip encoding for the json payload
responses as to speed up responses over internet connections
('Accept-Encoding' header)

It general it may make sense to clarify supported HTTP headers (+1 for
etag/if-modified-since support suggested at
https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/2 ).

https://github.com/cloudfoundry/cc-api-v3-style-guide#pagination
*"order_by: a field on the resource to order the collection by; each
collection may choose a subset of fields that it can be sorted by "*

Would be nice to illustrate/precise if multiple sort order can be
supported, e.g. order_by=-state,-created

https://github.com/cloudfoundry/cc-api-v3-style-guide#query-parameters
Precise character escaping on query param values e.g. containing comma:
filtering on name="a,b"


https://github.com/cloudfoundry/cc-api-v3-style-guide#pagination-of-related-resources

GET /v3/apps/:guid?include=space,organization

with pluralized resource name should be GET /v3/apps/:guid?include=space
*s*,organization*s*


https://github.com/cloudfoundry/cc-api-v3-style-guide#pagination-of-related-resources
would be nice to include an example of a pagination request on a related
resource inclusion request (e.g,

/v2/spaces/ab09cd29-9420-f021-g20d-123431420768?include=apps&*include_apps_order_by*=-state,-date)

https://github.com/cloudfoundry/cc-api-v3-style-guide#proposal
Would useful to consider I18N of user-facing messages. Cf related thread
for service broker error messages at
http://cf-dev.70369.x6.nabble.com/cf-dev-Announcing-Experimental-support-for-Asynchronous-Service-Operations-tp287p1471.html
May be the CC API could accept a "Accept-Language: zh_Hans" header and
try to return localized messages when available in the accepted locale.

Thanks,

Guillaume.

On Wed, Sep 2, 2015 at 6:44 PM, Zach Robinson <zrobinson(a)pivotal.io>
wrote:

Thanks James, I've just corrected the three issues you've noted so far

7801 - 7820 of 9425