|
Re: CF Job Failure
Gupta, Abhik
Hi Nick, Hi Daniel,
The app push using the CLI works. I haven’t had the chance to check the cloud controller logs yet—that’s the next thing on my plate. Best Regards, Abhik From: Nicholas Calugar [mailto:ncalugar(a)pivotal.io] Sent: Tuesday, April 19, 2016 2:31 AM To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org> Subject: [cf-dev] Re: Re: CF Job Failure Hi Abhik, Another bit of information that would be interesting is whether or not you can push your app using the CLI. Thanks, Nick On Mon, Apr 18, 2016 at 6:13 AM, Daniel Mikusa <dmikusa(a)pivotal.io<mailto:dmikusa(a)pivotal.io>> wrote: On Mon, Apr 18, 2016 at 7:10 AM, Gupta, Abhik <abhik.gupta(a)sap.com<mailto:abhik.gupta(a)sap.com>> wrote: Hi, We are trying to push a node.js application using the Cloud Controller REST APIs. The flow that we follow is similar to the flow followed by CF CLI: Create Application Metadata > Create Route Metadata > Associate Route with Application > Get cached resources from Cloud Foundry using the Resource Match API > Upload the bits (sending the fingerprints + application.zip) asynchronously > Poll for the Job Status This flow works perfectly fine till the last step but the polling for the job status gives back an error response like: { "metadata": { "guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77", "created_at": "2016-04-18T10:55:29Z", "url": "/v2/jobs/cd5bf18d-249b-4f00-9ee9-6328081d3d77" }, "entity": { "guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77", "status": "failed", "error": "Use of entity>error is deprecated in favor of entity>error_details.", "error_details": { "error_code": "UnknownError", "description": "An unknown error occurred.", "code": 10001 } } } Does the app actually push and get started? i.e. if you run `cf apps` after you get this message is the app up and running? Also, do you see similar issues when you push with `cf push`? Apparently, this error is also pretty well-known because it’s documented in the API documentation as well here: http://apidocs.cloudfoundry.org/228/jobs/retrieve_job_with_unknown_failure.html What could be the reason for this error from the Controller? Take a look at the cloud controller logs, `/var/vcap/sys/log/cloud_controller_ng`. There should be more information about the problem there. Dan
|
|
|
|
Re: [PROPOSAL]: Removing ability to specify npm version
Shawn Nielsen
We have had a few use cases where users have requested to stay on nodejs
toggle quoted messageShow quoted text
version 4 (LTS), while taking advantage of npm 3's new flat dependency tree. Node 4 by default bundles witn npm 2. Node 5 defaults to npm 3. In all of these use cases we are using online buildpacks. I would say this use case isn't as common, but we definitely get requests for it.
On Mon, Apr 11, 2016 at 1:10 PM, John Shahid <jshahid(a)pivotal.io> wrote:
Hi all,
|
|
|
|
Re: CF Job Failure
Nicholas Calugar
Hi Abhik,
toggle quoted messageShow quoted text
Another bit of information that would be interesting is whether or not you can push your app using the CLI. Thanks, Nick
On Mon, Apr 18, 2016 at 6:13 AM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
On Mon, Apr 18, 2016 at 7:10 AM, Gupta, Abhik <abhik.gupta(a)sap.com> wrote:Hi,Does the app actually push and get started? i.e. if you run `cf apps`
|
|
|
|
pushing docker image to CF.
sangeeus <sangeetha081315@...>
hi, I am pushing jboss/drools-workbench-showcase docker image to cloudfoundry
from my CLI. This is the command, cf push workbench -o jboss/drools-workbench-showcase:6.2.0.Final But I get an error Failed to talk to docker registry: Get http://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection. How to add docker insecure registry to cloud foundry. This image works fine in my local -- View this message in context: http://cf-dev.70369.x6.nabble.com/pushing-docker-image-to-CF-tp4649.html Sent from the CF Dev mailing list archive at Nabble.com.
|
|
|
|
Re: app guid uniqueness
Nicholas Calugar
Hi John,
toggle quoted messageShow quoted text
An application's guid will never change. If you delete an app, and push the code again, you are creating a new app with another guid. Thanks, Nick
On Mon, Apr 18, 2016 at 9:53 AM, John Wong <gokoproject(a)gmail.com> wrote:
Based on my brief testing and observation, the guid of an app sticks
|
|
|
|
app guid uniqueness
John Wong
Based on my brief testing and observation, the guid of an app sticks around
for as long as the app remains running (whether we restart or restage). But removing the app, then cf push a new guid is generated. Is this a true statement? Thanks. John
|
|
|
|
Re: CF Job Failure
Daniel Mikusa
On Mon, Apr 18, 2016 at 7:10 AM, Gupta, Abhik <abhik.gupta(a)sap.com> wrote:
Hi,Does the app actually push and get started? i.e. if you run `cf apps` after you get this message is the app up and running? Also, do you see similar issues when you push with `cf push`? Take a look at the cloud controller logs, `/var/vcap/sys/log/cloud_controller_ng`. There should be more information about the problem there. Dan
|
|
|
|
Re: Maven: Resolve Dependencies on Platform?
Daniel Mikusa
On Sat, Apr 16, 2016 at 11:30 PM, Josh Long <starbuxman(a)gmail.com> wrote:
I'm not sure if this is the right forum. I doubt it.As an experiment, I created a build pack that would do this. It hasn't been updated in a while, I don't plan to update it and it was never very solid to begin with. It was more to just see if I could make it work. It did, but the benefit was very small. I wouldn't recommend using it, but it's there if you want to look at it. https://github.com/dmikusa-pivotal/cf-maven-buildpack * that said, this is a TERRIBLE idea. Instead, prefer that one build be+1 - It's also worth mentioning that when you `cf push` something, your platform will cache any resources that are larger than 65k (default threshold, your platform's actual value may differ). The cache is global so it's not just per app or per user. Once any user pushes a file, it will be cached. This helps a ton with Java apps since JAR files are generally over the threshold and the same JAR files are used across many users & apps. Long story short, when you go to push your app you likely won't need to upload as much data as you think. Hope that helps! Dan
|
|
|
|
How can i configure HA Doppler at cf.yml?
inho cho
I read "Overview of the Loggregator System " - https://docs.cloudfoundry.org/loggregator/architecture.html
In that document, metron_agent can forward metrics or logs to N doppler. But i don't know how to do it. Would you let me know how to configure it at cf.yml. Thanks & Regards
|
|
|
|
CF Job Failure
Gupta, Abhik
Hi,
We are trying to push a node.js application using the Cloud Controller REST APIs. The flow that we follow is similar to the flow followed by CF CLI: Create Application Metadata > Create Route Metadata > Associate Route with Application > Get cached resources from Cloud Foundry using the Resource Match API > Upload the bits (sending the fingerprints + application.zip) asynchronously > Poll for the Job Status This flow works perfectly fine till the last step but the polling for the job status gives back an error response like: { "metadata": { "guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77", "created_at": "2016-04-18T10:55:29Z", "url": "/v2/jobs/cd5bf18d-249b-4f00-9ee9-6328081d3d77" }, "entity": { "guid": "cd5bf18d-249b-4f00-9ee9-6328081d3d77", "status": "failed", "error": "Use of entity>error is deprecated in favor of entity>error_details.", "error_details": { "error_code": "UnknownError", "description": "An unknown error occurred.", "code": 10001 } } } Apparently, this error is also pretty well-known because it's documented in the API documentation as well here: http://apidocs.cloudfoundry.org/228/jobs/retrieve_job_with_unknown_failure.html What could be the reason for this error from the Controller? Thanks & Regards Abhik
|
|
|
|
Re: How can we customized "404 Not Found"
Stefan Mayr
Hi Amit,
Am 17.04.2016 um 21:10 schrieb Amit Gupta: Hi Stefan, Mike,For my current use case we need the 503 page as a catch-all for stopped applications in all application domains. It displays a "nice" generic message and tries not to break marketings seo efforts :-) For more specific customer information (down till monday hh:mm) we can deploy another staticfile application and map the application domain to it. If the latter, then you probably wouldn't have the wildcard route on theI'm thinking about a correct answer since I've read the source code last friday. Regardless of my preference of a 503 service unavailable to a 404 file not found - having a feature (wildcard for default application domain) breaking a general smoke tests feels wrong. At the moment I like the idea how some applications do domain validation: they require you to put a file with some kind of key or uuid onto your webserver or into a dns txt record. For cloud foundry we could use something similar: deploy a file containing a specific id. If we try to fetch the content of this url and it doesn't contain this id the application is gone. It is basically like a negated version of the current test. Instead of expecting a specific string when the application is deleted (404) we expect a specific string (0xdeadbeef?) not to be in the response string. Amit Regards, Stefan Mayr
|
|
|
|
Re: How can we customized "404 Not Found"
Amit Kumar Gupta
Hi Stefan, Mike,
toggle quoted messageShow quoted text
For real applications, would you want a common 503 page for all applications on the platform, or would your different applications have different custom domains, with custom 503 pages for each domain. If the latter, then you probably wouldn't have the wildcard route on the same domain as the default app domain used in the smoke tests. If the former, then what sort of assertion do you think the smoke tests should make to assert that the app has been cleaned up and is no longer routable (without introducing false positives where the app is still routable but returning a bad response code for some other reason)? Thinking about the smoke tests in isolation, you might think to make the response-code-check injectible as configuration to the smoke tests. But from the perspective of the operator setting up the whole system and maybe deciding whether or not to run smoke tests, they might not even have deployed CF yet, let alone set up a 503 page, so it would be awkward to have the operator decide and configure up front what output/response code the smoke tests look for. Not sure what the optimal answer is here, any thoughts? Amit
On Sun, Apr 17, 2016 at 11:43 AM, Stefan Mayr <stefan(a)mayr-stefan.de> wrote:
Hi,
|
|
|
|
Re: How can we customized "404 Not Found"
Stefan Mayr
Hi,
Am 14.04.2016 um 18:14 schrieb Mike Youngstrom: We passed the smoke tests by:I verified this today: only the the text "404" is required to pass the smoke tests. So I created a 503 service unavailable page containing an html comment: <!-- CF: 404 --> Good enough as a temporary workaround. I'd still consider this as a bug in the smoke tests. When you use wildcard routes for real applications this won't work. Regards, Stefan
|
|
|
|
Re: Maven: Resolve Dependencies on Platform?
Josh Long <starbuxman@...>
I'm not sure if this is the right forum. I doubt it.
* you could achieve what you want by forking the buildpack used. If you're using the Java buildpack then it's https://github.com/cloudfoundry/java-buildpack. the `cf push` command supports providing an override URL for the buildpack. * that said, this is a TERRIBLE idea. Instead, prefer that one build be promoted from development to staging, QA, and production. Ideally, that promotion should be automatic, the result of a continuous delivery pipeline that sees code committed to version control, then run through continuous integration, then pushed to a testing environment where it's certified and smoke-tested, validated by QA, and ultimately promoted to production. You can support this process with continuous integration tools like Jenkins, Travis, Spinnaker, or Concourse.CI, which will monitor version control and can be scripted to package and cf push code.. On Sat, Apr 16, 2016 at 7:15 PM Matthew Tyson <matthewcarltyson(a)gmail.com> wrote: Please let me know if there is a more appropriate forum for this type of
|
|
|
|
Re: Maven: Resolve Dependencies on Platform?
Matthew Tyson
Please let me know if there is a more appropriate forum for this type of question.
|
|
|
|
Maven: Resolve Dependencies on Platform?
Matthew Tyson
Is anyone aware of a way to deploy a maven application via cloud foundry that will:
1) Take only the application bits and upload them 2) Run the maven build based on the pom.xml 3) pull down the defined dependencies on the platform Thereby NOT uploading the dependencies from the client to the platform?
|
|
|
|
Help needed building CF Certifications
Timothy Harris <tharris@...>
Hello Cloud Foundry Experts -
As you may know, the Cloud Foundry Foundation is working on building a certification program for professionals who use Cloud Foundry. Initially we are tackling a CF Developer certification, and a bit later will be tackling a CF Operator certification. Thanks to the contributors who helped us define the scope, domains and tasks, we know what we want to cover in the exam. The next step in our process is taking the tasks and turning them into good test questions. We need your help in with item writing! We are looking for pairs of Cloud Foundry contributors to help us develop the test. Specifically, we need help in building out test questions - taking an initial summary of a task and creating a specific question, with associated pre-requisites and final correct answers. Some questions will have a coding component, as we also need some sample (very simple) applications as part of the question. We expect this activity to require roughly one full day per question, and we’d like to have volunteers work on 2-4 of the questions. (If you plan to take the test, you’ll need to limit the number of questions you work on - let us know in advance!) So the ideal pair of volunteers would have 3-4 days in May to dedicate to this task, and we’d like to all work on it together so we can get it done quickly. We’ll start out with a 2 hour training session to explain how to write scorable test questions. Are you someone that could help us with this important task? At this point we are looking for interested and knowledgeable volunteers who likely can help, and we’ll work together to detail the logistics of specifically how and when we work together on the effort. So simply reply to this email (and perhaps share your specialty in CF if you have one) and we’ll take it from there... Thanks in advance to those that can help! Tim and Stormy -- Tim Harris | Director of Certification Programs Cloud Foundry Foundation (415) 518-6807
|
|
|
|
Re: openstack / CF v234 deployment
Amit Kumar Gupta
Hi William,
toggle quoted messageShow quoted text
Yes, this looks like a mixup between domain and system_domain. Both should be the same value, system.domain.com. The two separate properties exist for historical reasons, we plan to reduce back down to 1 to avoid these confusions in the future. Cheers, Amit
On Fri, Apr 15, 2016 at 11:43 AM, Bean William R <BeanWilliamR(a)johndeere.com
wrote: We've ventured through
|
|
|
|
CF CLI v6.17.0 Released Today
Koper, Dies <diesk@...>
The CF CLI team just cut 6.17.0. Binaries and link to release notes are available at:
https://github.com/cloudfoundry/cli#downloads The command reference guide on http://cli.cloudfoundry.org is being updated now. Built with Golang 1.6.1 which addresses two security vulnerabilities Golang 1.6.1 has just been released, addressing two vulnerabilities that could affect cf CLI users. See https://groups.google.com/forum/#!topic/golang-nuts/9eqIHqaWvck for details. TCP Routing Various commands have been enhanced to support TCP routes for apps deployed to the Diego runtime. This feature requires the target CF release to be v234 (CC API v2.53.0) or higher and Diego and the Routing API to be enabled. App Instance Quotas Quota related commands have been enhanced to expose app instance quotas. This feature requires the target CF release to be v214 (CC API v2.33.0) or higher for org quotas and v221 (CC API v2.40.0) or higher for space quotas. Native build on Mac OS Prevents a fatal runtime error on certain Mac OS versions and Anti-Virus/Security software. See #783<https://github.com/cloudfoundry/cli/issues/783>,#789<https://github.com/cloudfoundry/cli/issues/789> New Commands * cf router-groups lists the router groups available to your targeted Cloud Foundry. Once an admin creates a new shared domain associated with a TCP router group, developers may create TCP routes from this domain. * cf version shows the cf CLI version. cf --version and cf -v will remain offering the same functionality but are omitted from cf help's GLOBAL OPTIONS section in favor of the new command. Updated Commands * create-shared-domain now accepts a router group to create a domain for (http://cli.cloudfoundry.org/en-US/cf/create-shared-domain.html) * domains now displays the routing type of each domain * create-route, map-route, unmap-route, delete-route and push now support an additional option to specify a TCP route's port number * create-route and map-route now support an additional option to request a random port for a TCP route * routes output now includes the port number and type of route * create-space help output now doesn't incorrectly indicate there is a default space quota (#774<https://github.com/cloudfoundry/cli/issues/774>) * create-space now correctly looks for the specified quota in the specified org (#775<https://github.com/cloudfoundry/cli/issues/775>) * create-service-broker now has an alias, csb * curl now defaults to performing a POST when the -d option is specified (#788<https://github.com/cloudfoundry/cli/issues/788>) * curl no longer displays a message that you should be logged in * buildpacks no longer tries to retrieve information from the CF endpoint after displaying you are not logged in * map-route and unmap-route now map and unmap routes with paths correctly (#792<https://github.com/cloudfoundry/cli/issues/792>) * app now reports the correct URL when using routes with paths (#809<https://github.com/cloudfoundry/cli/issues/809>) * create-app-manifest now doesn't wrap an extra set of quotes around environment variables (#800<https://github.com/cloudfoundry/cli/issues/800>) * copy-source usage in its help page now correctly reflects that specification of a space also requires specification of the space's org Updated Global Options * -h is now accepted also after the command to display help, e.g. cf push myapp -h * -v when used with a command, e.g. cf apps -v, prints API request diagnostics. This makes enabling trace for a single command much easier, particularly on Windows * --version and -v when used by themselves still display the CLI version, but are omitted from thecf help listing in favor of the new version command * --build, -b still display the Golang version the cf CLI was built with, but is omitted from the cf help listing as it's not relevant to most users Updated Plugins: * cf willitconnect v1.1.0: https://github.com/gambtho/cf_will_it_connect_plugin * Diego Enabler v1.1.0: http://github.com/cloudfoundry-incubator/Diego-Enabler<https://github.com/cloudfoundry-incubator/Diego-Enabler> * Usage Report v1.3.0: http://github.com/krujos/usagereport-plugin<https://github.com/krujos/usagereport-plugin> Enjoy! Regards, Dies Koper Cloud Foundry CLI PM
|
|
|
|
openstack / CF v234 deployment
Bean William R
We've ventured through https://docs.cloudfoundry.org/deploying/openstack/index.html and have CF deployed on OpenStack.
[root(a)cfinstaller my-bosh]# bosh deployments ... +------------------+--------------+------------------------------------------------+--------------+ | Name | Release(s) | Stemcell(s) | Cloud Config | +------------------+--------------+------------------------------------------------+--------------+ | cloudfoundry-lab | cf/234+dev.1 | bosh-openstack-kvm-ubuntu-trusty-go_agent/3215 | none | +------------------+--------------+------------------------------------------------+--------------+ After a bosh deploy, we are able to login with the admin credentials, and cf push a staticfile app: [root(a)cfinstaller billhello-project]# cf push billhello -m 64M ... requested state: started instances: 1/1 usage: 64M x 1 instances urls: billhello.domain.com last uploaded: Fri Apr 15 18:30:38 UTC 2016 stack: unknown buildpack: staticfile 1.3.5 state since cpu memory disk details #0 running 2016-04-15 06:30:50 PM 0.0% 3.6M of 64M 5.4M of 1G However we are not able to use the loggregator service from the cf-cli: [root(a)cfinstaller billhello-project]# export CF_TRACE=true [root(a)cfinstaller billhello-project]# cf logs billhello ... WEBSOCKET REQUEST: [2016-04-15T18:35:22Z] GET /tail/?app=d0a97a19-4794-4584-82ce-1b2fe596cf78 HTTP/1.1 Host: wss://loggregator.system.domain.com:4443 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Version: 13 Sec-WebSocket-Key: [HIDDEN] Origin: http://localhost Authorization: [PRIVATE DATA HIDDEN] WEBSOCKET RESPONSE: [2016-04-15T18:35:22Z] HTTP/1.1 404 Not Found Content-Length: 91 Content-Type: text/plain; charset=utf-8 X-Cf-Routererror: unknown_route X-Content-Type-Options: nosniff X-Vcap-Request-Id: c8a05edd-a6b9-48d0-6f05-1c0aaa76f45f Date: Fri, 15 Apr 2016 18:35:23 GMT FAILED Error dialing loggregator server: websocket: bad handshake. Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint is wss://loggregator.system.cflab.deere.com:4443). We've already tried just restarting the services on the loggregator_trafficcontroller_z1/0 instance, and logging out & back in with the cf-cli... neither helps. How does this wss://loggregator.system.domain.com:4443 get added to nats? From the loggregator_trafficcontroller_z1/0 instance, the only routes in /var/vcap/jobs/route_registrar/config/registrar_settings.yml are: routes: [{"name":"doppler","port":8081,"registration_interval":"20s","uris":["doppler.domain.com"]},{"name":"loggregator","port":8080,"registration_interval":"20s","uris":["loggregator.domain.com"]}] Should there be one for loggregator.system.domain.com? Is this just a mismatch between system_domain and domain? Any troubleshooting tips? Thanks, William Bean
|
|
|