It works!. Thanks!

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

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

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.

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/>

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)

You have an example here:

https://github.com/prosociallearnEU/cf-nodejs-client/blob/master/lib/model/Logs.js
https://github.com/prosociallearnEU/cf-nodejs-client/blob/master/test/lib/model/LogTests.js

it is possible to not use websockets replacing some parts in the URL:
https://loggregator.YOUR_IP.xip.io + '/recent?app=' + app_guid

Juan Antonio

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

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

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

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.

Hi Ponraj,

For #1
The guid that gets printed out is the boundary for the multi-part message. When we serve the recent logs we create a multipart writer here(https://github.com/cloudfoundry/loggregatorlib/blob/master/server/handlers/http_handler.go#L23) which creates a random boundary here (https://golang.org/src/mime/multipart/writer.go?s=470:505#L29). You can see this in the headers if you run the curl command with a -v flag.

For #2
I'm guessing since the content type is set to "multipart/x-protobuf", the data might not be getting decoded properly. However, if you use the noaa library we unmarshal the data correctly here (https://github.com/cloudfoundry/noaa/blob/master/consumer.go#L333)

For #3
The error you are getting is from the net/url package here (https://golang.org/src/net/url/url.go#L417) which is called when we do a ParseURIRequest here (https://github.com/cloudfoundry/noaa/blob/master/consumer.go#L212). I even tried various ways to get that error in the playground (http://play.golang.org/p/tOeuyTxnb_). The only way I could replicate your error easily was to include the quotes in the doppler address. I'm hoping this is not a Windows thing because my testing happens to be on Mac OS X.

Hope this helps.

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

Oh, the upload feature seems nice..
How do you manage it ?

On Tue, Oct 20, 2015 at 12:33 AM, Juan Antonio Breña Moral <
bren(a)juanantonio.info> wrote:

Hi Chris,

Many thanks for the Introduction.
The Node Application:
https://github.com/prosociallearnEU/cf-nodejs-dashboard

is a WebApp to deploy in an easy way applications and bind later User
provided Services.
We are testing the solution with a Local CF instance (
https://github.com/yudai/cf_nise_installer/) and Pivotal API.

Currently, the WebApp is running in Pivotal for testing purposes.

Maybe, the project could be used for this purpose:

https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/message/6RSTWQISQVSIPJL7HURVMVBUT7Q6BRT2/

Cheers

Juan Antonio

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

Hi,



Would you like to acquire our recently compiled global data for Big Data &
Business Intelligence users email list with all information fields for your
marketing and new product launch events, we have Geography segmented data
base available with us.



The data set will have current user of various providers:



HortonWorks, Hadoop, Amazon EMR, EMC, Greenplum, mongoDB, Cloudera, Actian,
Splunk, QlikView, MicroStrategy, JasperSoft, Tibco, Oracle, SAP, IBM, MapR,
Tableau.



Also, we can connect you to the Datacenter users, Colocation users, CDN
users, Hosting users, Virtualization users, Storage users, Security users
and many other users...

Please let me know if you would like to receive more information about some
of our targeted lists out of thousands of tailored lists for your company.



Thank you for your time and consideration in advance.

Warm regards,

Sheri Price

Marketing Specialist



We respect your privacy. If you want to stop receiving emails from us,
please send a reply with the email subject line as "UNS"

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

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(a)de.ibm.com>
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)

*
https://docs.google.com/spreadsheets/d/1C1raorozKrf_RO-fiS5Nw38GPsMMgAegyw5iCxO8VT0/

** https://github.com/suhlig/jruby-scalability

Hi Piotr,

A resource provider or another system component can present a client token
with abacus.usage.read to read back the usage submitted to Abacus.

I wouldn't recommend giving that scope to users of the Abacus reporting
service as it'll give them too much power and visibility on usage from all
orgs.

The reporting service does not require the abacus.usage.read scope. Instead
it delegates the authorization to get a report for a particular org to the
account service (which you're responsible for implementing, as an
integrator of Abacus). Any user token from the report request is passed to
your account service, giving you a way to check that user's membership to
the org and any groups you've defined in that org and the roles that user
is entitled to.

HTH

- Jean-Sebastien

- Jean-Sebastien

On Mon, Oct 19, 2015 at 12:53 PM, Piotr Przybylski <piotrp(a)us.ibm.com>
wrote:

Does the user who would like to see their usage (e.g. services in the
organization they own) need to have 'abacus.usage.read' scope as discussed
below?

Piotr


-----Saravanakumar A Srinivasan/Burlingame/IBM(a)IBMUS wrote: -----
To: "Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
From: Saravanakumar A Srinivasan/Burlingame/IBM(a)IBMUS
Date: 10/15/2015 10:20PM
Subject: [cf-dev] Re: Re: Re: Re: Re: Re: Re: [cf-dev][abacus] Usage
submission authorization

what will be the scope for securing internal Abacus pipeline that Assk

describes as system token ?

It is 'abacus.usage.write'.

Updated my previous statements to make it more specific:

We have enabled scope based authorization for REST endpoints at usage
collector and usage reporting service. While we are working on using system
OAuth bearer access token at internal Abacus pipeline, Submitting usage to
a secured Abacus needs a OAuth bearer access token with
'abacus.usage.write' system scope in addition to the resource provider
specific scope(s) - 'abacus.usage.<resource_id>.write'.

Thanks,
Saravanakumar Srinivasan (Assk),


-----Piotr Przybylski/Burlingame/IBM(a)IBMUS wrote: -----
To: cf-dev(a)lists.cloudfoundry.org
From: Piotr Przybylski/Burlingame/IBM(a)IBMUS
Date: 10/15/2015 09:50PM
Subject: [cf-dev] Re: Re: Re: Re: Re: Re: [cf-dev][abacus] Usage
submission authorization

Makes sense, and just to complete - what will be the scope for securing
internal Abacus pipeline that Assk describes as system token ?

Piotr



----- Original message -----
From: Jean-Sebastien Delfino <jsdelfino(a)gmail.com>
To: "Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
Cc:
Subject: [cf-dev] Re: Re: Re: Re: Re: [cf-dev][abacus] Usage submission
authorization
Date: Thu, Oct 15, 2015 9:11 PM

Hey Piotr,

To read usage I believe you'll need 'abacus.usage.read', as
'abacus.usage.write' is for, well... writing.

P.S. That reminds me of a period of my life long time ago when I was a
contractor for some big company and they had hired me to write code for
them but had not given me the authorization to read the confidential code I
was writing :)

- Jean-Sebastien

On Thu, Oct 15, 2015 at 7:28 PM, Piotr Przybylski <piotrp(a)us.ibm.com>
wrote:

Assk,
can you confirm that the same scope (abacus.usage.write) is sufficient to
retrieve usage ?

Piotr

< ... snip ...>