Date   

Re: CF CLI v6.16.0 Released Today

Shannon Coen
 

Congratulations, and thank you CLI team!

Documentation for Route Services has been published:
- For app developers:
http://docs.cloudfoundry.org/devguide/services/#route-services
- For service authors:
http://docs.cloudfoundry.org/services/route-services.html (updates coming
soon to replace curls with the new CLI commands!)

Looking forward to your feedback.

Best,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Wed, Feb 24, 2016 at 3:42 PM, Koper, Dies <diesk(a)fast.au.fujitsu.com>
wrote:

The CF CLI team just cut 6.16.0. Binaries and link to release notes are
available at:



https://github.com/cloudfoundry/cli#downloads



Highlights of this release include:


Route Services

Various commands have been enhanced to support route services.
Route services are services such as filters and content transformations
for applications. Examples include rate limiting, metering, authorization,
and caching.
This feature requires the target CF release to be v231 (CC API v2.51.0) or
greater.


Space-Scoped Service Brokers

create-service-broker now enables a Space Developer to create a service
broker with service plans scoped to the space.
This feature requires the target CF release to be v228 (CC API v2.47.0) or
greater.


New Commands

- bind-route-service allows binding of a route service instance to a
route
- unbind-route-service allows unbinding of a route service instance
from a route

Updated Commands

- create-user-provided-service now accepts a url to create a route
service
- create-user-provided-service now accepts credential parameters in a
JSON file (#650 <https://github.com/cloudfoundry/cli/issues/650>)
- update-user-provided-service now accepts a url to create a route
service
- update-user-provided-service now accepts credential parameters in a
JSON file (#650 <https://github.com/cloudfoundry/cli/issues/650>)
- curl now supports reading HTTP request data from a file (#629
<https://github.com/cloudfoundry/cli/issues/629>)
- service now also displays service tags
- login and other commands now display a tip to check HTTP proxy
settings when specific network errors occur
- login without -o option now returns faster on installations with
many orgs
- push no longer fails with an invalid query parameter error when
targeting CC 2.24.0 or older (#744
<https://github.com/cloudfoundry/cli/issues/744>,#768
<https://github.com/cloudfoundry/cli/issues/768>)
- push no longer fails on Windows with >260 character paths (#728
<https://github.com/cloudfoundry/cli/issues/728>)
- push no longer errors when invalid path is supplied (with -p) and
--no-start is specified (#733
<https://github.com/cloudfoundry/cli/issues/733>)
- push now returns a better error message when failing to create a
temporary file while preparing for the upload of app bits (#741
<https://github.com/cloudfoundry/cli/issues/741>)
- create-app-manifest now produces a valid manifest with 'no-host'
attribute for apps with routes with no host (#767
<https://github.com/cloudfoundry/cli/issues/767>)
- create-app-manifest now includes the stack the application is
deployed on in the generated manifest (#772
<https://github.com/cloudfoundry/cli/issues/772>)
- ssh-code no longer fails when run behind a configured HTTP proxy
- oauth-token now displays only the token to make it easier to embed
in scripting (#752 <https://github.com/cloudfoundry/cli/issues/752>)
- check-route now accepts a path without a slash
- cf config --locale error message (when invalid code is specified)
now displays locale codes with a hyphen as per RFC 5646 (codes with
underscores are still accepted)
- update-buildpack now has correct name for unlock option in help (PR
from Fabio Berchtold)
- api and login now display a more meaningful description for
--skip-ssl-validation option
- add-plugin-repo now displays arguments as mandatory in usage help
- repo-plugins now displays correct usage help
- install-plugin now displays correct usage help
- remove-plugin-repo now displays argument correctly in usage help
- delete-space-quota now displays missing -f option in usage help
- routes now displays missing --org-level option in usage help
- config now displays brackets around option values in usage help
- delete and delete-space now display a single hyphen for short
options in help
- Warnings returned in the X-Cf-Warnings header by CC APIs are now
displayed
- Command help now lists options in alphabetical order (#730
<https://github.com/cloudfoundry/cli/issues/730>)
- Japanese help text updated for all commands (PR from Hiroyuki Kaneko)

Deprecated Commands

- The following commands now return an error when targeting CF v228
(CC API version 2.47.0) or greater, which removes deprecated features that
these commands exposed:
- migrate-service-instances
- purge-service-offering's -p option
- service-auth-tokens
- create-service-auth-token
- update-service-auth-token
- delete-service-auth-token

Updated & New Plugins:

- Download Droplet v1.0.1:
https://github.com/krujos/download_droplet_plugin
- Doctor v1.0.2: https://github.com/emirozer/cf-doctor-plugin
- Fastpush v1.0.0: https://github.com/xiwenc/cf-fastpush-plugin



Enjoy!



Regards,

Dies Koper
Cloud Foundry CLI PM





CF CLI v6.16.0 Released Today

Koper, Dies <diesk@...>
 

The CF CLI team just cut 6.16.0. Binaries and link to release notes are available at:

https://github.com/cloudfoundry/cli#downloads

Highlights of this release include:

Route Services

Various commands have been enhanced to support route services.
Route services are services such as filters and content transformations for applications. Examples include rate limiting, metering, authorization, and caching.
This feature requires the target CF release to be v231 (CC API v2.51.0) or greater.



Space-Scoped Service Brokers

create-service-broker now enables a Space Developer to create a service broker with service plans scoped to the space.
This feature requires the target CF release to be v228 (CC API v2.47.0) or greater.



New Commands

* bind-route-service allows binding of a route service instance to a route
* unbind-route-service allows unbinding of a route service instance from a route

Updated Commands

* create-user-provided-service now accepts a url to create a route service
* create-user-provided-service now accepts credential parameters in a JSON file (#650<https://github.com/cloudfoundry/cli/issues/650>)
* update-user-provided-service now accepts a url to create a route service
* update-user-provided-service now accepts credential parameters in a JSON file (#650<https://github.com/cloudfoundry/cli/issues/650>)
* curl now supports reading HTTP request data from a file (#629<https://github.com/cloudfoundry/cli/issues/629>)
* service now also displays service tags
* login and other commands now display a tip to check HTTP proxy settings when specific network errors occur
* login without -o option now returns faster on installations with many orgs
* push no longer fails with an invalid query parameter error when targeting CC 2.24.0 or older (#744<https://github.com/cloudfoundry/cli/issues/744>,#768<https://github.com/cloudfoundry/cli/issues/768>)
* push no longer fails on Windows with >260 character paths (#728<https://github.com/cloudfoundry/cli/issues/728>)
* push no longer errors when invalid path is supplied (with -p) and --no-start is specified (#733<https://github.com/cloudfoundry/cli/issues/733>)
* push now returns a better error message when failing to create a temporary file while preparing for the upload of app bits (#741<https://github.com/cloudfoundry/cli/issues/741>)
* create-app-manifest now produces a valid manifest with 'no-host' attribute for apps with routes with no host (#767<https://github.com/cloudfoundry/cli/issues/767>)
* create-app-manifest now includes the stack the application is deployed on in the generated manifest (#772<https://github.com/cloudfoundry/cli/issues/772>)
* ssh-code no longer fails when run behind a configured HTTP proxy
* oauth-token now displays only the token to make it easier to embed in scripting (#752<https://github.com/cloudfoundry/cli/issues/752>)
* check-route now accepts a path without a slash
* cf config --locale error message (when invalid code is specified) now displays locale codes with a hyphen as per RFC 5646 (codes with underscores are still accepted)
* update-buildpack now has correct name for unlock option in help (PR from Fabio Berchtold)
* api and login now display a more meaningful description for --skip-ssl-validation option
* add-plugin-repo now displays arguments as mandatory in usage help
* repo-plugins now displays correct usage help
* install-plugin now displays correct usage help
* remove-plugin-repo now displays argument correctly in usage help
* delete-space-quota now displays missing -f option in usage help
* routes now displays missing --org-level option in usage help
* config now displays brackets around option values in usage help
* delete and delete-space now display a single hyphen for short options in help
* Warnings returned in the X-Cf-Warnings header by CC APIs are now displayed
* Command help now lists options in alphabetical order (#730<https://github.com/cloudfoundry/cli/issues/730>)
* Japanese help text updated for all commands (PR from Hiroyuki Kaneko)


Deprecated Commands

* The following commands now return an error when targeting CF v228 (CC API version 2.47.0) or greater, which removes deprecated features that these commands exposed:
* migrate-service-instances
* purge-service-offering's -p option
* service-auth-tokens
* create-service-auth-token
* update-service-auth-token
* delete-service-auth-token


Updated & New Plugins:

* Download Droplet v1.0.1: https://github.com/krujos/download_droplet_plugin
* Doctor v1.0.2: https://github.com/emirozer/cf-doctor-plugin
* Fastpush v1.0.0: https://github.com/xiwenc/cf-fastpush-plugin

Enjoy!

Regards,
Dies Koper
Cloud Foundry CLI PM


Re: Unable to login to CF command line

Nanduni Nimalsiri
 

Hi,

I also came up with this error once. I don't know the exact reason. But when I destroyed all the virtual machines, update the git scripts and redo the process, it worked for me.

Best regards,
Nanduni.


Exiting due to NATS error: Could not connect to server on nats

Wayne Ha <wayne.h.ha@...>
 

Hi,

I tried to deploy cf v230. It tries to update mysql_gateway but failed with errors:

root(a)e3a81540-03c7-4793-977e-b3bd2788ab44:/var/vcap# cut -c 40-200 ./data/sys/log/mysql_gateway/mysql_gateway.log | tail -5
":"MyaaS-Provisioner: Initializing","log_level":"info","source":"mysql_gateway","data":{},"thread_id":20416620,"fiber_id":30048460,"process_id":10797,"file":"/va
e":"Connecting with NATS","log_level":"debug","source":"mysql_gateway","data":{},"thread_id":20416620,"fiber_id":30048460,"process_id":10797,"file":"/var/vcap/pa
e":"status 400 /var/vcap/packages/mysql_gateway/mysql_service/vendor/bundle/ruby/1.9.1/gems/cf-uaa-lib-2.0.0/lib/uaa/token_issuer.rb:141:in `implicit_grant_with_
e":"Exiting due to NATS error: Could not connect to server on nats://user:password(a)IpAddress:4222","log_level":"error","source":"mysql_gateway","data":{},"thread_
e":"MyaaS-Provisioner: Shutting down","log_level":"info","source":"mysql_gateway","data":{},"thread_id":20416620,"fiber_id":30048460,"process_id":10797,"file":"/

Can someone give me pointers how to debug this problem?

Thanks,


Replacing mysql with mariadb in cflinuxfs2

Danny Rosen
 

Hi There,

We’ve received feedback from the community that applications being deployed
on Cloud Foundry may be linking to libmysqlclient, which is distributed
under a GPL license. As this was expressed as a potential legal concern
we’ve experimented with replacing the mysql client library with mariadb.

We’re happy to conclude that our experiments with Java, Ruby, PHP, Go,
Python and Nodejs proved a desired level of backwards compatibility and
would like to move forward with shipping the change.

Before we make the change we’d like to request feedback from the community
concerning backwards compatibility. If you have concerns and would like to
go through validation, we’ve created a docker image [1] for testing.

Our preference is to move forward with a change to the cflinuxfs2 by
3/16/2015. If you have any concerns or feedback please comment on this
issue [2].

[1] - https://hub.docker.com/r/cloudfoundry/cflinuxfs2/tags/
[2] - https://github.com/cloudfoundry/stacks/issues/30


Unable to login to CF command line

Stanley Goston
 

We are trying to login to our CF tool via the command line and are no longer able to do this. When we run a cloud check it states there is no errors however when we do a bosh vms we see that there are stopped servers and servers that are failing. When we do a bosh start on one of these vms we receive an error stating:
Error 400007: 'our vm' is not running after update

Any thoughts on how to remedy this?


Announcing cf-mysql-release v26, now with a slimmer VM footprint!

Marco Nicosia
 

Hello Cloud Foundry folks,

For those of you who are tired of deploying web apps without easy
integration with data services, cf-mysql is a great place to start. With
this release, I'm happy to tell you that it takes even less commitment than
ever to give cf-mysql a spin!

The theme for this release is the First Rule in Government Spending
<https://www.youtube.com/watch?v=Et4sMJP9FmM>. Wanna take a ride?

A single MySQL node is a Single Point of Failure. With the introduction of
the Arbitrator, we allow you to buy two at twice the price. Previously, we
made you buy *three* for the same sense of security. Upgrading to cf-mysql
v26 will *save you money*, with no sacrifice in performance!


If you like what we're doing with cf-mysql, click the thumbs up: 👍
<http://clickpoint.cfapps.io/click/mysql-v26?up>
If we're messing up your game, click the thumbs down: 👎
<http://clickpoint.cfapps.io/click/mysql-v26?down>
And if this just isn't your thing, at least give me a fist bump! 👊
<http://clickpoint.cfapps.io/click/mysql-v26?meh>

*Highlights*

- We've updated to *MariaDB 10.0.23*, enabled some important
behind-the-scenes features, and fixed several important bugs.
- For those of you who require audit access to all data, we've given you
the option to enable a *Read Only admin user*.
- We've introduced a new HA deployment option, *2+1: *two MySQL nodes and
an *Arbitrator*.
- And we've made significant updates to the *generate-deployment-manifest
script* and stubs.


You'll have to update your stubs to use the new release, but we hope with
the new Examples and Arbitrator feature, it'll be worth your time to
upgrade. Make sure to read the release notes for important information
about the upgrade process.

As always, for full disclosure, and links beyond that, please check
out the Release
Notes <https://github.com/cloudfoundry/cf-mysql-release/releases/tag/v26>.

*Introducing the Arbitrator*

With cf-mysql v26, we've replaced one of the MySQL nodes with a lightweight
Arbitrator node. Previously, the minimal HA configuration required three
full-size MySQL nodes.

For cf-mysql administrators who are careful with their infrastructure
resources, the Arbitrator feature is a new deployment topology that uses a
smaller VM footprint while maintaining high availability guarantees. Unlike
the old three node topology, the Arbitrator decreases spend with no impact
on performance.

Thanks, and make sure to give me your feedback to influence what we do for
future releases!

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io


Re: demo of support for multiple application ports and TCP routing

Amulya Sharma <amulya.sharma@...>
 

this is very cool and it will enable us take non http traffic

Thanks and Regards
Amulya Sharma


2016-02-23 9:04 GMT-08:00 Dr Nic Williams <drnic(a)starkandwayne.com>:

Thanks Dieu


Re: Failed to delete an app due to "gateway timeout" error in server broker

Guruprakash S <prakash.guru4@...>
 

Yes, You can log into the service broker machine and check the logs.

If your app is bound to more than one cf service, then please issue 'cf
services' command in your space to see what services your app is bound to.
check under 'bound apps' column.

And once you find out the services instances bound to the app, try to
delete those service instances one by one and that way you can nail down
the faulty service broker and check the logs further in that service broker
machine to see what is wrong.


Thanks,
Guru.

On Wed, Feb 24, 2016 at 1:27 AM, Yunlong Yang <bruce.yang(a)emc.com> wrote:

I am enabling CF_TRACE to see which service broker is complaining.

BTW, could you please advise how to check the service broker logs? Is it
by logging into the service broker VM in bosh and check the logs?


Re: How to pass client IP to subsequent requests

Christopher Piraino <cpiraino@...>
 

On Wed, Feb 24, 2016 at 2:40 AM, Stanley Shen <meteorping(a)gmail.com> wrote:

any suggestion on this?


Re: How to pass client IP to subsequent requests

Stanley Shen <meteorping@...>
 

any suggestion on this?


Re: Failed to delete an app due to "gateway timeout" error in server broker

Yunlong Yang
 

I am enabling CF_TRACE to see which service broker is complaining.

BTW, could you please advise how to check the service broker logs? Is it by logging into the service broker VM in bosh and check the logs?


Re: Failed to delete an app due to "gateway timeout" error in server broker

Guruprakash S <prakash.guru4@...>
 

Did you happen to check the server broker logs to see whats happening?

Thanks,
Guru.

On Tue, Feb 23, 2016 at 5:48 PM, Yunlong Yang <bruce.yang(a)emc.com> wrote:

I have tried with our own DNS server. However, the issue is still there.

I haven't met this issue in manual operation. But it happens in our CD
scripts. The scripts is designed for a blue green deployment. The sequence
where the issue happens is:
- stop the app with: cf stop <app_name>
- unbind services with: cf unbind-service <app_name> <service>
- unmap route with: cf unmap-route
- delete the app

The error code happens in the stop of :delete the app.


Does anyone have any idea?


Re: Failed to delete an app due to "gateway timeout" error in server broker

Yunlong Yang
 

I have tried with our own DNS server. However, the issue is still there.

I haven't met this issue in manual operation. But it happens in our CD scripts. The scripts is designed for a blue green deployment. The sequence where the issue happens is:
- stop the app with: cf stop <app_name>
- unbind services with: cf unbind-service <app_name> <service>
- unmap route with: cf unmap-route
- delete the app

The error code happens in the stop of :delete the app.


Does anyone have any idea?


Re: demo of support for multiple application ports and TCP routing

Dr Nic Williams
 

Thanks Dieu


Re: Automatic routing to maintenance pages

Jan Rudert
 

Hi Chris,

thank you for this information. We'll try it.

Jan


Cloud Foundry Foundation

Jordy White <jordy.white@...>
 

Hi,



I was going through your company's website and I can understand you are into
Events and Summits 2016.



would you be interested in reaching out to the following segmented list:



v CIOs, COOs, Data Scientists, LoB Managers, IT directors, IT managers,
Technical managers, IT Infrastructure managers, Business Intelligence and
Data Analytics managers, Purchasing managers, IT Architects and Project
Managers, IT Tech Services Operations, Data Center Facilities, Engineering
Professionals, Servers and Storage, Enterprise storage Manager, DevOps and
IT service management, Cloud Practice Director, Domain Leader, Cloud Ops,
Data Centre services, Network Engineer and many more..



Kindly let me know your thoughts for the same. Also, if you have any other
requirement please let me know and I can get back to you with the sample
file for your review along with counts and other related information.



Look forward for your response.



Best Regards,

Jordy White

Marketing Analyst | T +1 702-475-6672
US Data - European Data - Asia Pacific Data - Email Append - Data Append -
Technology Specific Data - Email Marketing



Apologize if this message reaches you in error. If you no longer wish to
receive our offers, please revert with a subject line "Opt Out.


Re: demo of support for multiple application ports and TCP routing

Dieu Cao <dcao@...>
 

Hi Dr. Nic,

The API call to say "yes I want a TCP route, but I don't care what
host:port it is?" was implemented in this story [1]
and looks like:
POST /v2/routes?generate_port=true
{
"domain_guid": "1234",
"space_guid": "1234"
}

The proposed cf CLI UX is specified in this story [2] and looks like:

$ cf create-route myspace example.com --random-port
Creating route for org scoen / space test as scoen(a)pivotal.io...
OK
Route example.com:5678 has been created

-Dieu
CF CAPI PM


[1] https://www.pivotaltracker.com/story/show/101460700
[2] https://www.pivotaltracker.com/story/show/101461184

On Tue, Feb 23, 2016 at 12:40 AM, Dr Nic Williams <drnic(a)starkandwayne.com>
wrote:

I understand that host:port is used for routing TCP requests.

What is the use case for some rare users of PWS or BlueMix or other large
CF deployments to expect that they can declare what port they should be
allowed to route?

Is this use case so common or important that we should allow it to leak
into CF?

Will we support the 95-99% case (afaict sorry), where users just want any
port (and to be able to look up what host:port they got - remembering that
there will be multiple tcp LBs due to port limitations)? It wasn't in the
demo - so its a question - what's the API call to say "yes I want a TCP
route, but I don't care what host:port it is?"


Cluster Discovery Service in Cloud Foundry with Diego

Malmee Weerasinghe
 

Hi,
Is there a cluster discovery service in Cloud Foundry with Diego
Architecture which can give a list of members (IP addresses) in a logical
cluster? I need to initialize a Hazelcast cluster in Cloud Foundry.
Thank you

--
Malmee Weerasinghe
WSO2 Intern
mobile : (+94)* 71 7601905* | email : <dehan.vithana(a)aiesec.net>
malmee(a)wso2.com


Re: demo of support for multiple application ports and TCP routing

Noburou TANIGUCHI
 

I was very impressed with and interested in the demo video and then I have
some questions.

Below is the command history that I have eye-copied from the video (GUIDs
are replaced as `$(guid)`):

```
cf p lattice --no-start --no-route -c 'lattice-app --ports=7777,8888'
cf app lattice --guid
cf curl /v2/apps/$(guid) -X PUT -d '{"ports":[7777,8888]}'
cf start lattice
cf create-route tcp-lattice superman.cf-app.com --hostname lattice
cf curl /v2/routes?q=host:lattice
cf curl /v2/route_mappings -X POST -d
'{"route_guid":$(guid),"app_guid":$(guid),"app_port":7777}'
curl lattice.superman.cf-app.com/port
cf space tcp-lattice --guid
cf curl /v2/domains
cf curl /v2/routes -X POST -d
'{"space_guid":$(guid),"domain_guid":$(guid),"port":60004}'
cf curl /v2/route_mappings -X POST -d
'{"route_guid":$(guid),"app_guid":$(guid),"app_port":8888}'
curl tcp.superman.cf-app.com:60004/port
```

And my questions are:

Q1: Which is the TCP port and which is the HTTP one? It seems for me that
the port 7777 is HTTP, and the port 8888 is TCP. Is this right?

Q2: When is the route `tcp.superman.cf-app.com` is created? The 11th command
`cf curl /v2/routes -X POST -d ..` seems so, but the result of the command
contained no "tcp" string.

Q3: Is there any difference between an HTTP route and a TCP route in
creation?

Q4: Is a CF system is aware that a route is HTTP or TCP? Or is the party who
deploys an app only aware of it, and is that duty of the party to use ports
properly?

Thanks in advance.




-----
I'm not a ...
noburou taniguchi
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-demo-of-support-for-multiple-application-ports-and-TCP-routing-tp3837p3906.html
Sent from the CF Dev mailing list archive at Nabble.com.

5401 - 5420 of 9330