|
Re: v3 cc api style guide feedback requested
James Bayer
the example used for actions uses the v2 api instead of v3:
toggle quoted message
Show quoted text
https://github.com/cloudfoundry/cc-api-v3-style-guide#example-4 i like the idea of a unique error code. ideally the CAPI team maintains public documentation of an error code dictionary https://github.com/cloudfoundry/cc-api-v3-style-guide#issues-with-v2-error-format the async proposal seems like a big improvement. On Wed, Sep 2, 2015 at 8:53 AM, James Bayer <jbayer(a)pivotal.io> wrote:
the collections example [1] does not actually include the required --
Thank you, James Bayer |
|
|
|
docker-push failed with crashing and got the following stack trace in grarden-linux
Shaozhen Ding
Anyone can help with interpreting the error log here
garden-linux.pool.vl5hraecvg1.stream-in.command.failed cf-213 and diego/0.1353.0 {"timestamp":"1441209896.800271988","source":"garden-linux","message":"garden-linux.garden-server.create.created","log_level":1,"data":{"request":{"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","rootfs":"docker:///datianshi/cf-docker-music#latest","properties":{"executor:allocated-at":"1441209893185279557","executor:cpu-weight":"4","executor:disk-mb":"1024","executor:log-config":"{\"guid\":\"cb6ac15a-c3a0-4b5d-9716-e99934c35953\",\"index\":0,\"source_name\":\"CELL\"}","executor:memory-mb":"512","executor:metrics-config":"{\"guid\":\"cb6ac15a-c3a0-4b5d-9716-e99934c35953\",\"index\":0}","executor:owner":"executor","executor:result":"{\"failed\":false,\"failure_reason\":\"\",\"stopped\":false}","executor:rootfs":"docker:///datianshi/cf-docker-music#latest","executor:start-timeout":"60","executor:state":"created","tag:domain":"cf-apps","tag:instance-guid":"397eef75-bf73-46d3-6ba2-6a3737ea3d5e","tag:lifecycle":"lrp ","tag:process-guid":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0","tag:process-index":"0"},"env":["INSTANCE_GUID=397eef75-bf73-46d3-6ba2-6a3737ea3d5e","INSTANCE_INDEX=0"]},"session":"4.247804"}} {"timestamp":"1441209896.811697721","source":"garden-linux","message":"garden-linux.garden-server.net-in.port-mapped","log_level":1,"data":{"container-port":8080,"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","host-port":61055,"session":"4.247809"}} {"timestamp":"1441209896.818696976","source":"garden-linux","message":"garden-linux.garden-server.net-in.port-mapped","log_level":1,"data":{"container-port":2222,"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","host-port":61056,"session":"4.247810"}} {"timestamp":"1441209896.842704535","source":"garden-linux","message":"garden-linux.garden-server.limit-memory.limited","log_level":1,"data":{"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","resulting-limits":{"limit_in_bytes":536870912},"session":"4.247818"}} {"timestamp":"1441209896.843993425","source":"garden-linux","message":"garden-linux.garden-server.limit-disk.limited","log_level":1,"data":{"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","resulting-limits":{},"session":"4.247819"}} {"timestamp":"1441209896.844884396","source":"garden-linux","message":"garden-linux.garden-server.limit-cpu.limited","log_level":1,"data":{"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","resulting-limits":{"limit_in_shares":40},"session":"4.247820"}} {"timestamp":"1441209896.845991373","source":"garden-linux","message":"garden-linux.garden-server.info.got-info","log_level":1,"data":{"handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","session":"4.247821"}} {"timestamp":"1441209896.857844830","source":"garden-linux","message":"garden-linux.pool.vl5hraecvg1.stream-in.command.failed","log_level":2,"data":{"argv":["/var/vcap/data/garden-linux/depot/vl5hraecvg1/bin/nstar","11856","vcap","/tmp/lifecycle"],"error":"exit status 1","exit-status":1,"session":"2.67.7.1","stderr":"chdir to user home: No such file or directory\n","stdout":"","took":"2.959157ms"}} {"timestamp":"1441209896.858107328","source":"garden-linux","message":"garden-linux.garden-server.stream-in.failed","log_level":2,"data":{"destination":"/tmp/lifecycle","error":"exit status 1","handle":"cb6ac15a-c3a0-4b5d-9716-e99934c35953-2669bf25-c226-4908-bbba-63e00a6a4fa0-397eef75-bf73-46d3-6ba2-6a3737ea3d5e","session":"4.247823"}} |
|
|
|
Re: v3 cc api style guide feedback requested
James Bayer
the collections example [1] does not actually include the required
toggle quoted message
Show quoted text
*resources* field [1] https://github.com/cloudfoundry/cc-api-v3-style-guide#example-2 On Wed, Sep 2, 2015 at 8:16 AM, James Bayer <jbayer(a)pivotal.io> wrote:
should the PUT example that updates the app name and space guid actually --
Thank you, James Bayer |
|
|
|
CF CLI Release v 6.12.3
Greg Oehmen
The CF CLI team just cut 6.12.3. Release notes and binaries are available
at: https://github.com/cloudfoundry/cli/releases Highlights of this release include: Bug Fix: runtime error: index out of range originally reported here https://github.com/cloudfoundry/cli/issues/509 and in many subsequent Github issues - https://www.pivotaltracker.com/story/show/98672332 - The root problem for this particular crash is because v2/apps/GUID/instances reports 0 instance for a newly stopped app, but GetContainerMetrics() from noaa library will continue to report instances metrics for a while, and eventually be consistent with v2/apps/GUID/instance. This causes the CLI’s 'index out of range error'. The bug is fixed by not gathering metrics unless instance>0, but GetContainerMetrics() should be consistent with what CC endpoint reports. Pull Requests - Merge pull request #544 <https://github.com/cloudfoundry/cli/pull/544> from cloudfoundry/code-tidy Code tidy: Code cleanup: remove unused variables, remove orphan functions, shadowing reserved word - Merge pull request #523 <https://github.com/cloudfoundry/cli/pull/523> from zachgersh/master Unmarshal the extra field, get documentation url - Merge pull request #540 <https://github.com/cloudfoundry/cli/pull/540> from cloudfoundry/use_go_yaml Support yaml '<<' merge type - Merge pull request #534 <https://github.com/cloudfoundry/cli/pull/534> from cloudfoundry/feature/commands-restart-and-create Move commands to new command pattern. - Merge pull request #505 <https://github.com/cloudfoundry/cli/pull/505> from zhang-hua/bug-93578300 Reduce API calls when CRU operations of service keys - Merge branch 'story-87481016' of https://github.com/zhang-hua/cli into zhang-hua-story-87481016 - Merge pull request #514 <https://github.com/cloudfoundry/cli/pull/514> Fix create-app-manifest only includes one host [92530254] Also notable: We deprecated the use of CodeGangsta within the CF CLI. Previously, CodeGangsta had been used for managing help and flags within the CLI. We now manage those functions natively in the CLI. This is a precursor to the work we will begin soon of refactoring help, restructuring command syntax and abstracting admin-only commands out into some separate manifestation; perhaps a plugin. Greg Oehmen Cloud Foundry Product Manager |
|
|
|
Re: v3 cc api style guide feedback requested
James Bayer
should the PUT example that updates the app name and space guid actually be
toggle quoted message
Show quoted text
a PATCH since it updates the resource? https://github.com/cloudfoundry/cc-api-v3-style-guide#put On Wed, Sep 2, 2015 at 1:40 AM, Dieu Cao <dcao(a)pivotal.io> wrote:
Hi All, --
Thank you, James Bayer |
|
|
|
Re: stdout.log and stderr.log not show in CF197 with loggregator enabled
Erik Jasiak
Dan is correct - "cf file" for getting stdout/stderr files directly was
toggle quoted message
Show quoted text
deprecated some time ago. I'll try to locate when that happened (it was before my time.) From the cli, "cf logs" for streaming, and "cf logs --recent" for a quick dump are the way to go. Erik PM - loggregator Daniel Mikusa wrote:
|
|
|
|
Re: stdout.log and stderr.log not show in CF197 with loggregator enabled
Daniel Mikusa
Have you tried running `cf logs` instead? Anything written to STDOUT or
STDERR should be visible there for some period of time. For long term storage, you should look at setting up a log drain on your application. http://docs.cloudfoundry.org/devguide/services/log-management.html Dan On Wed, Sep 2, 2015 at 9:08 AM, Shruthi Ravindra <Shruthi.ravindra(a)ge.com> wrote: Hi, |
|
|
|
Re: stdout.log and stderr.log not show in CF197 with loggregator enabled
Shruthi Ravindra
Hi,
we are also facing the same issue when we check the "cf files pfh-cos-dicomobjectstore-dev /logs" we are able to see only the staging logs and not the stdout.log abd stderror.log. we need to access these logs to debug the error. how do we enable the stdout and stderror logs |
|
|
|
Re: stdout.log and stderr.log not show in CF197 with loggregator enabled
Shruthi Ravindra
Hi ,
We are having the same problem where we are not able to see the stdout.log and stderror.log for all the application deployed in the cloud. Could you please let me know how do we access the logs other than cf logs "appname" command which is not giving us the full logs. Thanks, Shruthi |
|
|
|
Correcting CF Docs
Daniel Jones
Hi all,
The CF docs for deploying CF to an AWS VPC <https://docs.cloudfoundry.org/deploying/ec2/bootstrap-aws-vpc.html> have a broken link to a Gist of Dan Highham's, that presumably talks about deploying to regions other than us-east-1. Does anyone know where the instructions for non-US regions are now? Regards, Daniel Jones EngineerBetter.com |
|
|
|
Re: Announcing Experimental support for Asynchronous Service Operations
Thanks Dieu for your response.
toggle quoted message
Show quoted text
We have successfully implemented an async service broker for out internal dbaas [1], [2] which db farms provisionning sometimes takes longer than 30s. Concerning improvement suggestions on the documentation, I could only spot an inconsistency on the sequence diagram, where the last operation description is mismatching between broker response (1/3 nodes") and CC api response ("40% complete") whereas the 'description' is a string which should be returned as is. Hard to propose a PR on that since the source file for this diagram does not seem available under docs-services [4]. BTW, It would be great if bookbinder would support rendering diagrams from a text format such as plantuml [5], or rely on plantuml public service [6] for such rendering. Wouldn't is make sense to exit the experimental status of the async api, even if it's not feature complete ? i.e. considering the api is stable enough and won't change in an incompatible maneer soon, thereby enabling clients such as cf-java-client to rely on them. One other potential improvement I see to the API would be to support localized user-facing operation status description. Having the CLI being I18Ned but brokers enable to return user facing messages in the user language seems limiting. Maybe it could be the case of having the CLI add a usual 'Accept-Language: zh_Hans" matching the current CLI locale, and the CC propagating this header in the last_operation broker endpoint [7] so that they can return the status message in the smae language when translations are available. Thanks, Guillaume. [1] https://github.com/Orange-OpenSource/elpaaso-brokers/blob/master/cf-service-broker-dbaas/src/main/java/com/orange/clara/cloud/cf/servicebroker/dbaas/service/DbaasServiceInstanceService.java#L60 [2] https://github.com/Orange-OpenSource/elpaaso-brokers/blob/a3f150fc7d3bb889875aac202496a4f63efc3595/cf-service-broker-dbaas/src/main/java/com/orange/clara/cloud/cf/servicebroker/dbaas/service/DbaasServiceInstanceService.java#L67-L73 [3] http://docs.cloudfoundry.org/services/images/async-service-broker-flow.png [4] https://github.com/cloudfoundry/docs-services/blob/master/images/async-service-broker-flow.png [5] http://plantuml.com/sequence.html [6] http://plantuml.com/plantuml/ [7] http://docs.cloudfoundry.org/services/asynchronous-operations.html#polling On Tue, Sep 1, 2015 at 5:50 PM, Dieu Cao <dcao(a)pivotal.io> wrote:
Hi Guillaume, |
|
|
|
v3 cc api style guide feedback requested
Dieu Cao <dcao@...>
Hi All,
The CAPI team has created a style guide for v3 of the cloud controller api and would like to share this again with the wider cf community for feedback after initial review within the team. [1] Issues/PRs are welcome and appreciated! Thanks, Dieu CF CAPI PM [1] https://github.com/cloudfoundry/cc-api-v3-style-guide |
|
|
|
Re: How to set cc.info with cf-release spiff templates ?
Thanks Joseph for your response. Any chance that the OSS build pipeline
toggle quoted message
Show quoted text
would update the spiff template with the current version number of the cf release being built, as to avoid each consummers of the release to manually update version number when updating cc.info.version ? Ideally by having the spiff templates override the default value (yet-to-be-specified in the release's spec file, see [3]) by the current cf release number ? I was trying to manually assign this value with meta.releases[0].version, but I see that meta.releases[0].version seems to always specify 'latest' [2]. One possibility would have to specify the current release number (e.g. '215') Thanks in advance, Guillaume. [2] https://github.com/cloudfoundry/cf-release/blob/90d730a2d13d9e065a7f348e7fd31a1522074d02/templates/cf-deployment.yml#L10 [3] https://github.com/cloudfoundry/cf-release/issues/774 On Tue, Sep 1, 2015 at 11:29 PM, CF Runtime <cfruntime(a)gmail.com> wrote:
Unfortunately those properties don't actually do what they say. A story |
|
|
|
Re: Which kind of resources stored in cc-resources container?
Matt Reider
You can refer to this discussion for some understanding of what is stored
in the cc-resources container: https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/nTQSn8spBPE It's basically stores larger files to speed up subsequent app push. An initial push will be slow, as all files are uploaded. A second push will be faster, as the larger files (over 64k by default, but can be adjusted up), are stored in the cc-resources container for re-use. On Tue, Sep 1, 2015 at 6:40 PM Guangcai Wang <guangcai.wang(a)gmail.com> wrote: Hi, |
|
|
|
Re: diego questions: default memory and passing env variables
Amit Kumar Gupta
Responses inline.
On Tue, Sep 1, 2015 at 7:13 PM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote: What is the default memory size of an app deployed in diego? cf appsYes. This isn't a diego thing, this is a CC thing. cf set-env doesn't appear to be getting the environment variableYou likely need to restage the application for ENV var changes to take effect. Unless I'm mistaken, this too is not diego-specific, and applies to DEA containers as well. Thanks!Best, Amit |
|
|
|
Re: Self-signed cert for registry failing on stager
Tom Sherrod <tom.sherrod@...>
Thank you. The pointer to the code is excellent. I was looking in the right place. An odd part was I actually added the CA to the machine itself and it still did not work.
I finally opted for a mirror registry with a public cert. Now working. |
|
|
|
diego questions: default memory and passing env variables
Tom Sherrod <tom.sherrod@...>
What is the default memory size of an app deployed in diego? cf apps indicate 1GB.
cf set-env doesn't appear to be getting the environment variable information to the running container. Is cf set-env the correct method to use? Thanks! Tom |
|
|
|
Which kind of resources stored in cc-resources container?
iamflying
Hi,
I am using Swift as Cloud Foundry blobstore. I noticed there are four containers: cc-buildpacks cc-droplets cc-packages cc-resources For the first three containers, I can find the relationship between the object in containers and the records in postgres database. I also noticed that some objects will be stored in cc-resources when I push applications. They seem related to the type of application (ruby, java, etc). However, I cannot find what should be stored in cc-resources container. Are they uploaded automatically by buildpack? Is it decided by buildpack or application? How to configure them if it is decided by application? Thanks. |
|
|
|
Re: Generic data points for dropsonde
Benjamin Black
great questions, dwayne.
toggle quoted message
Show quoted text
1) the partition key is intended to be used in a similar manner to partitioners in distributed systems like cassandra or kafka. the specific behavior i would like to make part of the contract is two-fold: that all data with the same key is routed to the same partition and that all data in a partition is FIFO (meaning no ordering guarantees beyond arrival time). this could help with the multi-line log problem by ensuring a single consumer will receive all lines for a given log entry in order, allowing simple reassembly. however, the lines might be interleaved with other lines with the same key or even other keys that happen to map to the same partition, so the consumer does require a bit of intelligence. this was actually one of the driving scenarios for adding the key. 2) i expect typical points to be in the hundreds of bytes to a few KB. if we find ourselves regularly needing much larger points, especially near that 64KB limit, i'd look to the JSON representation as the hierarchical structure is more efficiently managed there. b On Tue, Sep 1, 2015 at 4:42 PM, <dschultz(a)pivotal.io> wrote:
Hi Ben, |
|
|
|
Re: Generic data points for dropsonde
Dwayne
Hi Ben,
toggle quoted message
Show quoted text
I was wondering if you could give a concrete use case for the partition key functionality. In particular I am interested in how we solve multi line log entries. I think it would be better to solve it by keeping all the data (the multiple lines) together throughout the logging/metrics pipeline, but could see how something like a partition key might help keep the data together as well. Second question: how large do you see these point messages getting (average and max)? There are still several stages of the logging/metrics pipeline that use UDP with a standard 64K size limit. Thanks, Dwayne On Aug 28, 2015, at 4:54 PM, Benjamin Black <bblack(a)pivotal.io> wrote: |
|
|