Date   

Re: Open sourcing our S3 service broker

Gwenn Etourneau
 

Maybe as the same we have for bosh release (bosh.io) we can create
brokers.cloudfoundry.org

On Wed, Oct 21, 2015 at 6:29 AM, David Ehringer <david.ehringer(a)gmail.com>
wrote:

I think discovery mechanism would be very valuable, especially in cases
like this where there was already an S3 service broker open sourced last
year: https://github.com/cloudfoundry-community/s3-cf-service-broker .
Not sure if this meets the same needs but it would be great for people to
be able to find existing broker projects they can contribute enhancements
to if it makes sense rather than duplicate effort, let alone those just
interested in running brokers.

I would be interested in working on something although I'm not sure how
much bandwidth I have to contribute at the moment. I'm assuming whatever
is built could be hosted in a public CF instance just like
plugins.cloudfoundry.org? If dynamic features like reviews were desired
and to be supported, would any specific database services be available for
use?


Re: Defining a singular plan for all services

Shannon Coen
 

Hello Kayode,

So glad to hear you're building a broker for your API Gateway!

If your broker offers multiple services, and/or multiple plans of a
service, it is up to you as the broker author to expose all of these plans
individually in the catalog endpoint [1]. The Service Broker API doesn't
support the notion of a "default plan" shared by multiple services because,
while plans may have metadata in common, every plan must have a unique
identifier.

As Cloud Foundry is not prescriptive about implementation or deployment of
your broker, mention of settings.yml is a bit confusing. While you may use
a configuration file called settings.yml, another service broker author may
use a very different mechanism for configuration.

[1] http://docs.cloudfoundry.org/services/api.html#catalog-mgmt

Warm regards,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Mon, Oct 19, 2015 at 6:17 AM, Kayode Odeyemi <dreyemi(a)gmail.com> wrote:

A custom built service.

We're building a custom API Gateway for our apps.


On Fri, Oct 16, 2015 at 11:29 PM, CF Runtime <cfruntime(a)gmail.com> wrote:

What services do you want to define this default plan for?

Natalie & Mikhail
Runtime & OSS Integration

On Wed, Oct 14, 2015 at 2:22 AM, Kayode Odeyemi <dreyemi(a)gmail.com>
wrote:

Hi,

How can I define a default plan to be used by more than one services
without repeating the same plan definition in settings.yml file?

Appreciate your help.


Re: Open sourcing our S3 service broker

David Ehringer
 

I think discovery mechanism would be very valuable, especially in cases like this where there was already an S3 service broker open sourced last year: https://github.com/cloudfoundry-community/s3-cf-service-broker . Not sure if this meets the same needs but it would be great for people to be able to find existing broker projects they can contribute enhancements to if it makes sense rather than duplicate effort, let alone those just interested in running brokers.

I would be interested in working on something although I'm not sure how much bandwidth I have to contribute at the moment. I'm assuming whatever is built could be hosted in a public CF instance just like plugins.cloudfoundry.org? If dynamic features like reviews were desired and to be supported, would any specific database services be available for use?


Re: Open sourcing our S3 service broker

Shannon Coen
 

Awesome! Thank you for the contribution.

Would love to see brokers be more easily discoverable. Would someone from
the community have the bandwidth to develop a site to make brokered
services for CF discoverable? I'm thinking reviews, commercial vs OSS,
logos, deployment strategy, links to install instructions, etc.


Best,
Shannon

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Tue, Oct 20, 2015 at 11:58 AM, Eric Poelke <epoelke(a)gmail.com> wrote:

Throwing our S3 service broker out there for others that may find it
useful --

https://github.com/epoelke/s3-service-broker

Currently has default plans for most regions as well as location
constraint support for buckets created in those regions. IAM users get
created for each bucket, as well as a access policy that restricts the user
to only the bucket created for the user. API keys and endpoints are
returned as VCAP credentials when binding the service to an app.


Open sourcing our S3 service broker

Eric Poelke
 

Throwing our S3 service broker out there for others that may find it useful --

https://github.com/epoelke/s3-service-broker

Currently has default plans for most regions as well as location constraint support for buckets created in those regions. IAM users get created for each bucket, as well as a access policy that restricts the user to only the bucket created for the user. API keys and endpoints are returned as VCAP credentials when binding the service to an app.


region qualifier for organizations

Bharath Sekar
 

Hi,
account service implementations could need additional qualifiers to uniquely identify an organization. For example, the implementation I'm working on needs a region along with the guid of the org.
The API to get an account given org information looks like this

GET /v1/orgs/:org_id/account

How do we want to support the additional qualifier in abacus? One solution that I can think of is including the region in the guid. org_id could be 'guid_region'. ex:
GET /v1/orgs/86d0482c-7208-4f2f-8606-935c080cad41_us/account
Thoughts?


Action Required : UAA Backwards Compatibility for OpenID Connect ID Token Response Type

Sree Tummidi
 

Hi All,

Starting with *CF Release 220*, we have added OpenID Connect ID Token
support in UAA.

Currently this feature is *disabled* by default to remain fully backwards
compatible.


uaa.id_token.disable

description: When set to true, requests to /oauth/authorize will ignore the
response_type=id_token parameter

*default: true*


Our plan is to provide a *30 Day window *(roughly cf-release slated for 2nd
week of November) for Service Authors and other integrators using UAA as
the token server. We will be removing the feature flag and support ID token
response by default after 2nd week of November

*Action Required:*

1. If you have a custom implementation of OAuth client, please update
the parsing logic to handle the response of the /oauth/authorize endpoint.
The main change is that the Location header will have a Fragment (#) and
not a Query String (?). *See [1] below*
2. If you are using the cf-uaa-lib
<https://github.com/cloudfoundry/cf-uaa-lib>, Please update to version
*3.2.4*
3. If you are using a third party library for OAuth/OpenID Connect, most
likely it already supports parsing the response properly and there is no
action required.



Please test your Services or Application using UAA with the
*uaa.id_token.disable* set to *false*



*[1] Details*

During invokation of the /oauth/authorize URL, the normal process is to
specify response_type=code

Some libraries have been specifying response_type=code+id_token

This is a OpenID Connect extension. Previously the UAA ignored the id_token
response_type, but now we have added support. This changes the response of
the /oauth/authorize. The main change is that the Location header will have
a Fragment (#) and not a Query String (?)

$ uaac target http://login. <http://login.identity.cf-app.com/>
{system-domain}

$ uaac token owner get cf marissa -s "" -p koala

$ uaac curl "
<http://login.identity.cf-app.com/oauth/authorize?grant_type=authorization_code&>
http://login. <http://login.identity.cf-app.com/>{system-domain}
/oauth/authorize?grant_type=authorization_code&response_type=code
&client_id=ssh-proxy&redirect_uri=http://localhost"

$ uaac curl "http://login. <http://login.identity.cf-app.com/>
{system-domain}/oauth/authorize?grant_type=authorization_code&
<http://login.identity.cf-app.com/oauth/authorize?grant_type=authorization_code&>
response_type=code+id_token&client_id=ssh-proxy&redirect_uri=
http://localhost"

Location: http://localhost?code=5G9Rm1


*response_type=code+id_token*

Location: http://localhost#
token_type=bearer&id_token=eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiIwMjJmMGUzOC0xNTZlLTRjY2EtYTFmMS1kMGMwNTNkMDY1ZGMiLCJ1c2VyX25hbWUiOiJtYXJpc3NhIiwib3JpZ2luIjoibGRhcCIsImlzcyI6Imh0dHBzOi8vdWFhLmlkZW50aXR5LmNmLWFwcC5jb20vb2F1dGgvdG9rZW4iLCJjbGllbnRfaWQiOiJzc2gtcHJveHkiLCJhdWQiOlsic3NoLXByb3h5Il0sInppZCI6InVhYSIsImdyYW50X3R5cGUiOiJhdXRob3JpemF0aW9uX2NvZGUiLCJ1c2VyX2lkIjoiMDIyZjBlMzgtMTU2ZS00Y2NhLWExZjEtZDBjMDUzZDA2NWRjIiwiYXpwIjoic3NoLXByb3h5Iiwic2NvcGUiOlsib3BlbmlkIl0sImV4cCI6MTQ0MjQ2NDM5MSwiaWF0IjoxNDQyNDIxMTkxLCJqdGkiOiI2ZTBmOThlZS02YzNjLTQzN2UtOGYzZi0yNjE2ZDZhM2U2NzkiLCJlbWFpbCI6Im1hcmlzc2FAdGVzdC5jb20iLCJyZXZfc2lnIjoiZGJlYjYxN2UiLCJjaWQiOiJzc2gtcHJveHkifQ.AQtGa5N9QW47jAehCEIz9K46yNTIJpK5SKrp5IqAZ2AqZhNLzwryLw0wJmZkZ3v3wXqpwm_IryJnJmzui0hsM8ZYsyeDjtGtmd35QjxBe785nVGe2GZeyVQ0CqLNW1C7w34VCnvSfIxo8ecstaS4O0MkBxjQR0CQRQ3XHS4RIJg&
code=aGp5Ig
&expires_in=43199&scope=cloud_controller.read%20cloud_controller.write%20openid&jti=6e0f98ee-6c3c-437e-8f3f-2616d6a3e679


Thanks,
Sree Tummidi
Sr. Product Manager
Identity - Pivotal Cloud Foundry


Re: How to specify "no default shared domain" in the cf-deployment-manifest.yml?

Amit Kumar Gupta
 

Hi Jim,

Try setting the `app_domains` property in your manifest to an empty array.

Cheers,
Amit

On Mon, Oct 19, 2015 at 7:05 PM, Jim Lin <jimlintw922(a)gmail.com> wrote:

Hi all

I don't need the default shared domain (i.e., ${CF_IP}.xip.io). I can use
command line to remove it after CF deployment. However, every time I
re-deploy CF, I need manually remove it again. My question is how to
specify "no default shared domain" in the cf-deployment-manifest.yml?

Thanks all.

Sincerely,
Jim


Re: Some results running CloudController under JRuby

Steffen Uhlig
 

Hi,
 
Dieu wrote:
 
> Would be interested to see how this performs on aws or on soft layer.
 
Good point  - is there an AWS envrionment we could use? We'll look into Softlayer.
 
> Also, were you able to run CATS? 
 
We did not attempt to run CATS, because we focused on one endpoint. There others would probably not have functioned.
 
> Or is more work needed to deal with NATS etc?
 
More work is certainly needed for that. We haven't bothered so far to update the depencencies we have 'patched' for the spike. 
 
> Other pros/cons that you've found?
 
Pros not mentioned yet:
 
- There are a lot more tools to run and monitor JVM based applications.
- JRuby in interpreted mode did not seem to be slower, in terms of development workflow.
 
Cons:
 
- JRruby is an additional layer (of complexity) on top of Ruby
- JRuby is still more in a niche
 
Amit wrote:
 
> what are differences to pre-packaging dependencies?
> any differences in pre-packaging time?
> what differences for packaging/compilation dependencies?
 
Our approach was minimal; we captured code changes to CC and dependencies that need updates on a branch. Those changes would need to be translated into packaging.
From our spike, we think that the (pre-) packaging would be similar to how UAA handles the OpenJDK. JRuby itself goes on top of that, and is simply an additional unzip command.
Some gems will need updates to work with JRuby, (see Gemfile in the branch). Mostly around yaml support, thin, and NATS. 
 
> any difference in packaging/compilation time?
 
We did not measure times. From a Ruby perspective, JRuby did not feel different. The Ruby-to-Java compilation can happen in two modes; interpreted and compiled. We only worked in the interpreted mode. In compiled, the Ruby code is compiled to Java upfront, which should lead to further improvements.
 
> there are going to be some new job and packages blobs, and maybe some old ones go away? what are the size differences?
 
We can re-use OpenJDK from UAA. JRuby is a 40 MiB download, where we can eliminate samples etc., so probably 30 MiB in addition.
 
> any changes to start-up or update times during bosh deploy/update?
 
Sorry, we did not measure this, either ;-)
 
 
Regards
 
Marc & Steffen
 
 

----- Original message -----
From: Amit Gupta <agupta@...>
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Cc:
Subject: [cf-dev] Re: Re: Some results running CloudController under JRuby
Date: Mon, Oct 19, 2015 11:40 PM
 
Awesome!
 
Got some questions:
- what are differences to pre-packaging dependencies?
- any differences in pre-packaging time?
- what differences for packaging/compilation dependencies?
- any difference in packaging/compilation time?
- there are going to be some new job and packages blobs, and maybe some old ones go away? what are the size differences?
- any changes to start-up or update times during bosh deploy/update?
 
Amit
 
On Mon, Oct 19, 2015 at 2:06 PM, Dieu Cao <dcao@...> wrote:
Hi Steffen,
 
Cool stuff.  It's good to see there's some improvement under jruby.
Would be interested to see how this performs on aws or on soft layer.
Also, were you able to run CATS? 
Or is more work needed to deal with NATS etc?
Other pros/cons that you've found?
 
-Dieu
CF CAPI PM
 
 
 
On Mon, Oct 19, 2015 at 1:25 PM, Steffen Uhlig <Steffen.Uhlig@...> wrote:
Hi,
 
the Flintstone team recently spent some time researching the potential benefits of running the CloudController under JRuby. We were hoping to find evidence that JRuby (and the underlying JVM) would allow us to make better use of multiple cores, and maybe also lead to significant response time improvements when answering many parallel requests.
 
This exercise wasn't set up as a scientific benchmark; it is more of a spike that would allow us to judge whether it is worth investigating the next level of detail.
 
We would like to share some early results in the hope to get feedback from the community.
 
In our measurements, we saw 20..30% improvement in both average response time and throughput when 10 or more concurrent requests were made (using ApacheBench against the `/v2/orgs/*/spaces` endpoint).
 
Graphs:
    * Throughput: https://goo.gl/NuWkvf
    * Response Time: https://goo.gl/ItPBHN
 
We patched a CC VM to use JRuby 9000 under OpenJDK 8. WEBrick was used as we weren't able to quickly find a drop-in replacement for Thin (as used under MRI). All measurements were taken on a 2014 MacBook Pro running Cloudfoundry in a BOSH Lite environment. Simulating network latency by adding a 100 ms sleep to each request did not change the overall picture.
 
For more details see the spreadsheet* and our repository** with the test scripts.
 
Steffen
(on behalf of the Flintstone Team)
 
 
 


Re: How to explicitly specify the password for the account admin?

Jim Lin <jimlintw922@...>
 

It works!. Thanks!


Re: CF-RELEASE v202 UPLOAD ERROR

James Bayer
 

sometimes a message like that is due to networking issues. does the bosh
director and the VM it is creating have an available network path to reach
each other? sometimes ssh'ing in to the VM that is identified can yield
more debug clues.

On Tue, Oct 20, 2015 at 5:09 AM, Parthiban Annadurai <senjiparthi(a)gmail.com>
wrote:

Thanks Bharath and Amit for the helpful solutions. I have surpassed that
error. Now, bosh deploy strucks like in attached image. Could you anyone
please?

Regards

Parthiban A



On 20 October 2015 at 11:57, Amit Gupta <agupta(a)pivotal.io> wrote:

Bharath, I think you mean to increase the *disk* size on the compilation
VMs, not the memory size.

Parthiban, the error message is happening during compiling, saying "No
space left on device". This means your compilation VMs are running out of
space on disk. This means you need to increase the allocated disk for your
compilation VMs. In the "compilation" section of your deployment manifest,
you can specify "cloud_properties". This is where you will specify disk
size. These "cloud_properties" look the same as the could_properties
specified for a resource pool. Depending on your IaaS, the structure of
the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <bharathp(a)vedams.com>
wrote:

hi parthiban

It seems you are running out of space in your vm in which you are
compiling . try to increase the size of memory in your compilation vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions. Actually, now we r
facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <epoelke(a)gmail.com>
wrote:

You actually do not need to download it. if you just run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from bosh.io.

--
Thank you,

James Bayer


Re: CF-RELEASE v202 UPLOAD ERROR

Parthiban Annadurai <senjiparthi@...>
 

Thanks Bharath and Amit for the helpful solutions. I have surpassed that
error. Now, bosh deploy strucks like in attached image. Could you anyone
please?

Regards

Parthiban A

On 20 October 2015 at 11:57, Amit Gupta <agupta(a)pivotal.io> wrote:

Bharath, I think you mean to increase the *disk* size on the compilation
VMs, not the memory size.

Parthiban, the error message is happening during compiling, saying "No
space left on device". This means your compilation VMs are running out of
space on disk. This means you need to increase the allocated disk for your
compilation VMs. In the "compilation" section of your deployment manifest,
you can specify "cloud_properties". This is where you will specify disk
size. These "cloud_properties" look the same as the could_properties
specified for a resource pool. Depending on your IaaS, the structure of
the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <bharathp(a)vedams.com>
wrote:

hi parthiban

It seems you are running out of space in your vm in which you are
compiling . try to increase the size of memory in your compilation vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions. Actually, now we r
facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from bosh.io.


Re: Doubt: Filter 2 Service Bindings with 2 parameters

Juan Antonio Breña Moral <bren at juanantonio.info...>
 

Hi,

this is a possibility. I could find the information using this REST CALL. I have found another way:
http://apidocs.cloudfoundry.org/221/user_provided_service_instances/list_all_service_bindings_for_the_user_provided_service_instance.html

Many thanks for the clue.


Configured SSL/TLS for Cloud Foundry 170 release

Pravin Mishra <pravinmishra88@...>
 

Hello All,

We have deployed Cloudfoundry 170 and Configured SSL/TLS.
<https://johnpfield.wordpress.com/2014/09/10/configuring-ssltls-for-cloud-foundry/>

- Deployment is successful
- Able to login
- Able to create Organization/Space

When deploying a application then getting below Warning:

Warning: error tailing logs
Unauthorized error: You are not authorized. message:"Error: Invalid
authorization" message_type:ERR timestamp:1445336917813794880
app_id:"07841692-f22e-4caa-8a86-edf999d15817" source_name:"LGR"

Then Error:

FAILED
TIP: use 'cf logs railswithoutdb --recent' for more information

When tracing logs then:

FAILED
Unauthorized error: You are not authorized. message:"Error: Invalid
authorization" message_type:ERR timestamp:1445337478878348487
app_id:"07841692-f22e-4caa-8a86-edf999d15817" source_name:"LGR"

Note: I am pushing application using Admin user.

Best Regards,
Pravin Mishra
<https://johnpfield.wordpress.com/2014/09/10/configuring-ssltls-for-cloud-foundry/>


Re: Cloud Foundry being used for an EU social learning games platform

Juan Antonio Breña Moral <bren at juanantonio.info...>
 

Good morning Gwenn

Can you add more details about your question?

WebApp uploads to middleware the file and later it is sent to CF Instance using the API:
http://apidocs.cloudfoundry.org/221/apps/uploads_the_bits_for_an_app.html

You have many tests here:
https://github.com/prosociallearnEU/cf-nodejs-client/blob/master/test/lib/model/UploadAppsTests.js

I have tested the feature uploading large zips (applications with 300MB)

Currently,I have tested with static apps and node.js apps but I will add more tests for other buildpacks (python, java, php & ruby)


Re: REST API endpoint for accessing application logs

Juan Antonio Breña Moral <bren at juanantonio.info...>
 


Re: [cf-bosh] cf-services-contrib does not support cf v2

Dieu Cao <dcao@...>
 

Yes, we plan to fully remove support for v1 service brokers at the end of
the year.

On Mon, Oct 19, 2015 at 6:11 PM, Marco Nicosia <mnicosia(a)pivotal.io> wrote:

Hi Remi,

[I'm moving your post to cf-dev, and BCC'ing cf-bosh. The people you want
to reach are more likely hanging out on cf-dev.]

I just checked with Shannon, who was PM for services and harkens way back
to the VMWare days of Cloud Foundry. He confirmed that they only support
the v1 services API.

cf-services-contrib-release was the initial set of five services that
VMware had sponsored. They were deprecated and contributed to the community
some time back.

It looks like Ruben Koster has been gamely maintaining it for some time.

I believe that Dieu's proposal to remove support for v1 service brokers
would kill cf-services-contrib-release dead:

https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/BYNVNVTOI3PGCEP6MHF3A5EYY5UGMLL5/#TEKDER3QZXUNKTFFFWKQQGWWQREPHP43

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


On Mon, Oct 19, 2015 at 2:14 AM, Remi Tassing <tassingremi(a)gmail.com>
wrote:

Hi,
After managing to deploy cf and cf-services-contrib, I noticed issuing
the command "cf create-service-auth-token <label> core <token>" does not
throw any error but "cf marketplace" does not show any update. Most
importantly creating the service fails.

After connecting the dots, I believe cf-services-contrib is based on v1
and is not compliant with v2. Could anyone confirm?

If this is true then the wiki/README should be updated.

Remi


Re: Doubt: Filter 2 Service Bindings with 2 parameters

Dieu Cao <dcao@...>
 

Have you tried using the nested end point?
http://apidocs.cloudfoundry.org/221/apps/list_all_service_bindings_for_the_app.html

-Dieu
CF CAPI PM

On Mon, Oct 19, 2015 at 8:19 AM, Juan Antonio Breña Moral <
bren(a)juanantonio.info> wrote:

Hi,

I would like to filter using 2 criterias for this REST method:


http://apidocs.cloudfoundry.org/221/service_bindings/list_all_service_bindings.html

var filter2 = {
'q': 'app_guid:' + "65be2a2d-a643-4e01-b33d-8755d5934ae6",
'q': 'service_instance_guid:' +
"9e541381-b34d-4a0c-b7da-1ff00a0ffef5"

};

Currently, using this way, the REST method only filter for the latest
parameter.
Does exist a possibility for both criteria?

Juan Antonio


Re: CF-RELEASE v202 UPLOAD ERROR

Amit Kumar Gupta
 

Bharath, I think you mean to increase the *disk* size on the compilation
VMs, not the memory size.

Parthiban, the error message is happening during compiling, saying "No
space left on device". This means your compilation VMs are running out of
space on disk. This means you need to increase the allocated disk for your
compilation VMs. In the "compilation" section of your deployment manifest,
you can specify "cloud_properties". This is where you will specify disk
size. These "cloud_properties" look the same as the could_properties
specified for a resource pool. Depending on your IaaS, the structure of
the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <bharathp(a)vedams.com> wrote:

hi parthiban

It seems you are running out of space in your vm in which you are
compiling . try to increase the size of memory in your compilation vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions. Actually, now we r
facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from bosh.io.


Re: CF-RELEASE v202 UPLOAD ERROR

Bharath
 

hi parthiban

It seems you are running out of space in your vm in which you are compiling
. try to increase the size of memory in your compilation vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <senjiparthi(a)gmail.com>
wrote:

Hello All,
Thanks All for the helpful suggestions. Actually, now we r
facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from bosh.io.