|
Re: How to start my app in http and https ports?
Ushani Balasooriya
Thanks Daniel
|
|
|
|
Re: I keep on getting 502 Bad Gateway: Registered endpoint failed to handle the request.
Ronak Banka
Ushani , if you have a git repo for your code and can share, it would be
very easy to debug. ᐧ On Wed, Sep 13, 2017 at 5:18 PM, Ushani Balasooriya <ushanib(a)gmail.com> wrote: Hi Ronak, |
|
|
|
Re: I keep on getting 502 Bad Gateway: Registered endpoint failed to handle the request.
Ushani Balasooriya
Hi Ronak,
That is a context path of my application. But meantime I also just tried without the "/carbon" and just only with "/". But still no luck. |
|
|
|
Re: I keep on getting 502 Bad Gateway: Registered endpoint failed to handle the request.
Ushani Balasooriya
Hi Lucas,
Thanks can you guide me how to enable tcp route to the app? I tried below and it failed. sudo cf map-route is5.3.0 local.pcfdev.io --port 5000 Creating route local.pcfdev.io:5000 for org pcfdev-org / space pcfdev-space as admin... FAILED Error resolving route: Server error, status code: 400, error code: 210001, message: The route is invalid: Port is supported for domains of TCP router groups only. |
|
|
|
Re: [abacus] Abacus v1.0.0 available
To try Abacus out you can simply run it locally with the in-memory PouchDB:
toggle quoted message
Show quoted text
npm run build npm start npm run demo npm stop We use a limited set of DB operations to support CouchDB 1 & 2 and MongoDB 2 & 3. You can deploy Abacus as BOSH release or as a set of applications. Therefore we allow the database to be simply an URL in Abacus applications environment or to be bound as a service. IBM use CouchDB/Cloudant with the URL approach afaik. In SAP we use custom BOSH release MongoDB and ServiceFabrik's service broker. 2017-09-13 0:27 GMT+03:00 Mike Youngstrom <youngm(a)gmail.com>: Great! I haven't attempted to use Abacus yet. Is there a |
|
|
|
Re: I keep on getting 502 Bad Gateway: Registered endpoint failed to handle the request.
Ronak Banka
Hi Ushani,
From logs what I can see is that application is trying to access "/carbon" route instead of "/", which is https://is530.local.pcfdev.io/carbon how are the application routes configured? you can configure the path during cf push Thanks Ronak ᐧ On Wed, Sep 13, 2017 at 4:31 PM, Lucas Reginato <lucas.reginato(a)gmail.com> wrote: Hi Ushani, |
|
|
|
Re: I keep on getting 502 Bad Gateway: Registered endpoint failed to handle the request.
Lucas Reginato
Hi Ushani,
I have the same experience, and this is what I found: 1) If your application uses HTTP, everything works just fine. You will access the HTTPS endpoint (provided by the Load Balancer) and you can access your app. 2) If your application uses HTTPS, you will receive a 502 (Bad Gateway) when you try to access it. This happens because the GoRouter only talks HTTP to the application. I mean, PCF Dev will provide you a HTTPS endpoint, but that is the HTTPS Load Balancer endpoint. The Load Balancer will send the HTTPS request to the GoRouter layer, and GoRouter will only talk HTTP to the application. So, if the application talks HTTPS, nahhhh, bad communication, and the request fails with a 502. I was able to enable HTTPS in my application by creating a TCP route to my application. I hope that helps. And I would like to listen what others engineers done to fix this. Thanks, -Lucas Reginato On Wed, Sep 13, 2017 at 11:58 AM, Ushani Balasooriya <ushanib(a)gmail.com> wrote: I started to access http and https bpth. But it gives me the below error -- Lucas Reginato |
|
|
|
I keep on getting 502 Bad Gateway: Registered endpoint failed to handle the request.
Ushani Balasooriya
I started to access http and https bpth. But it gives me the below error when I browse the app.
I have installed PCF dev in my local machine. This is my route: Routeshttps://is530.local.pcfdev.io 2017-09-13T15:21:45.139+05:30 [RTR/0] [OUT] is530.local.pcfdev.io - [2017-09-13T09:51:45.137+0000] "GET /carbon HTTP/1.1" 502 0 67 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0" "192.168.11.1:60550" "10.0.2.15:60055" x_forwarded_for:"-" x_forwarded_proto:"https" vcap_request_id:"66256b25-32b9-4769-72f0-add0592e0b59" response_time:0.002344385 app_id:"faf5b9d6-a48f-499e-a5f8-35286c921714" app_index:"0" 2017-09-13T15:22:15.846+05:30 [RTR/0] [OUT] is530.local.pcfdev.io - [2017-09-13T09:52:15.845+0000] "GET /carbon HTTP/1.1" 502 0 67 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0" "192.168.11.1:60550" "10.0.2.15:60055" x_forwarded_for:"-" x_forwarded_proto:"https" vcap_request_id:"524a30a6-8cb4-44cc-7937-96a7fcae20f5" response_time:0.000872472 app_id:"faf5b9d6-a48f-499e-a5f8-35286c921714" app_index:"0" 2017-09-13T15:22:19.309+05:30 [RTR/0] [OUT] is530.local.pcfdev.io - [2017-09-13T09:52:19.308+0000] "GET /carbon HTTP/1.1" 502 0 67 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0" "192.168.11.1:41342" "10.0.2.15:60055" x_forwarded_for:"-" x_forwarded_proto:"http" vcap_request_id:"c32925f5-d994-4e42-606a-86b5f52159f4" response_time:0.000675021 app_id:"faf5b9d6-a48f-499e-a5f8-35286c921714" app_index:"0" 2017-09-13T15:22:25.925+05:30 [RTR/0] [OUT] is530.local.pcfdev.io - [2017-09-13T09:52:25.924+0000] "GET /carbon HTTP/1.1" 502 0 67 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0" "192.168.11.1:41342" "10.0.2.15:60055" x_forwarded_for:"-" x_forwarded_proto:"http" vcap_request_id:"183c95fe-2619-4ecb-7739-585f7763d9f1" response_time:0.000756516 app_id:"faf5b9d6-a48f-499e-a5f8-35286c921714" app_index:"0" |
|
|
|
Website Solution
amily sen <amily.sen@...>
Hi There,
This is *Amily**,* I’m an (Online Marketing Executive) We are an India base IT company. We have a good creative team to design & develop a eye catching website for your business. We are offering a great offer to get a new business website. Please let me know if you are interested so that we can provide you more details. You can give me your *Skype Id / Phone Number* to discuss more. Regards, *Amily* Online Marketing Executive |
|
|
|
Re: [abacus] Abacus v1.0.0 available
Mike Youngstrom <youngm@...>
Great! I haven't attempted to use Abacus yet. Is there a
toggle quoted message
Show quoted text
recommended/preferred Mongo or Couch bosh release to use with abacus? Mike On Tue, Sep 12, 2017 at 9:06 AM, Hristo Iliev <hsiliev(a)gmail.com> wrote:
I'm happy to announce the availability of CF Abacus v1.0.0. |
|
|
|
Re: [abacus] Abacus v1.0.0 available
Dr Nic Williams <drnicwilliams@...>
Congrats team!
________________________________ From: Michael Maximilien <mmaximilien(a)gmail.com> Sent: Wednesday, September 13, 2017 3:39:34 AM To: Discussions about Cloud Foundry projects and the system overall. Subject: [cf-dev] Re: Re: [abacus] Abacus v1.0.0 available +1 Let me add to this and emphasize the terrific job Hristo and the team at SAP have been doing to help take CF-Abacus to the next level. As Hristo mentioned there is a wiki* with ongoing list of features and ideas for the next version. An inception for that is up coming soon. All are welcome and join us in Basel for office hours if you want to have one on one chat. Congrats again team. Cheers, Max * https://github.com/cloudfoundry-incubator/cf-abacus/wiki/Abacus-v2-features On Tue, Sep 12, 2017 at 10:20 AM, Chip Childers <cchilders(a)cloudfoundry.org<mailto:cchilders(a)cloudfoundry.org>> wrote: Hristo, Congratulations to the team! On Tue, Sep 12, 2017 at 8:07 AM Hristo Iliev <hsiliev(a)gmail.com<mailto:hsiliev(a)gmail.com>> wrote: I'm happy to announce the availability of CF Abacus v1.0.0. Abacus provides usage metering and aggregation for Cloud Foundry services and app runtimes. The v1.0.0 release comes bundled with: * MongoDB and CouchDB support * Improved data format & processing * 2 new components to measure resource consumption of applications and service instances in Cloud Foundry * Concourse deploy pipeline * Performance & Security improvements You can find the full release notes on Github: https://github.com/cloudfoundry-incubator/cf-abacus/releases/tag/v1.0.0 npm modules are available on: https://www.npmjs.com/search?q=cf-abacus Please feel free to ask any questions on this list or via Github issues. Pull requests are always welcome as well! For more info on Abacus please visit: * source code: https://github.com/cloudfoundry-incubator/cf-abacus/tree/v1.0.0 * documentation: https://github.com/cloudfoundry-incubator/cf-abacus/wiki Thanks to Abacus committers and contributors who helped with this release! We are already gathering requirements and looking forward to version 2 features. Check what we have so far here: https://github.com/cloudfoundry-incubator/cf-abacus/wiki/Abacus-v2-features [https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif] Hristo Iliev -- Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815<tel:(267)%20250-0815> -- max http://maximilien.org |
|
|
|
Re: [abacus] Abacus v1.0.0 available
Michael Maximilien
+1
Let me add to this and emphasize the terrific job Hristo and the team at SAP have been doing to help take CF-Abacus to the next level. As Hristo mentioned there is a wiki* with ongoing list of features and ideas for the next version. An inception for that is up coming soon. All are welcome and join us in Basel for office hours if you want to have one on one chat. Congrats again team. Cheers, Max * https://github.com/cloudfoundry-incubator/cf-abacus/wiki/ Abacus-v2-features On Tue, Sep 12, 2017 at 10:20 AM, Chip Childers <cchilders(a)cloudfoundry.org> wrote: Hristo, -- max http://maximilien.org |
|
|
|
Re: [abacus] Abacus v1.0.0 available
Chip Childers <cchilders@...>
Hristo,
toggle quoted message
Show quoted text
Congratulations to the team! On Tue, Sep 12, 2017 at 8:07 AM Hristo Iliev <hsiliev(a)gmail.com> wrote:
I'm happy to announce the availability of CF Abacus v1.0.0. --
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815 |
|
|
|
Re: How to start my app in http and https ports?
Daniel Mikusa
Your app doesn't need to start both. It should generally just listen on
port 8080 (but technically should be the port listed in the env variable $PORT) for HTTP requests. HTTPS/TLS is handled at the platform layer. Usually, there would be a load balancer in front of your CF installation which accepts HTTPS/TLS requests and terminates them. It would then proxy requests to the GoRouter & ultimately your application via HTTP. There are some variations on this as you can have your LB send requests via HTTPS to the GoRouter which is capable of terminating HTTPS/TLS too (if it's configured as such). In this way, you can make sure encryption is in use for one additional hop of the request. For small environments that don't have LB's, it's also possible to have GoRouter handle incoming requests directly and terminate HTTPS/TLS. This only works for small envs though, because it limits you to having one GoRouter. I don't know how this is handled in PCFDev, but I suspect it might be done this way. If you require HTTPS/TLS all the way to your application, the current solution is to use TCP routing instead of a web application. TCP routing has a different request path which results in your application receiving the TCP connection from the client. This allows you to configure HTTPS/TLS at the application level and have traffic encrypted all the way to the app. Hope that helps! Dan On Tue, Sep 12, 2017 at 8:55 AM, Ushani Balasooriya <ushanib(a)gmail.com> wrote: My app should start in https:9443 ports. How can I achieve this? |
|
|
|
[abacus] Abacus v1.0.0 available
I'm happy to announce the availability of CF Abacus v1.0.0.
Abacus provides usage metering and aggregation for Cloud Foundry services and app runtimes. The v1.0.0 release comes bundled with: - MongoDB and CouchDB support - Improved data format & processing - 2 new components to measure resource consumption of applications and service instances in Cloud Foundry - Concourse deploy pipeline - Performance & Security improvements You can find the full release notes on Github: https://github.com/ cloudfoundry-incubator/cf-abacus/releases/tag/v1.0.0 npm modules are available on: https://www.npmjs.com/search?q=cf-abacus Please feel free to ask any questions on this list or via Github issues. Pull requests are always welcome as well! For more info on Abacus please visit: - source code: https://github.com/cloudfoundry-incubator/cf- abacus/tree/v1.0.0 - documentation: https://github.com/cloudfoundry-incubator/cf-abacus/wiki Thanks to Abacus committers and contributors who helped with this release! We are already gathering requirements and looking forward to version 2 features. Check what we have so far here: https://github.com/ cloudfoundry-incubator/cf-abacus/wiki/Abacus-v2-features Hristo Iliev |
|
|
|
How to start my app in http and https ports?
Ushani Balasooriya
My app should start in https:9443 ports. How can I achieve this?
This should be my login url : https://localhost:9443/carbon/ If I use Diego container, should it always be port 8080? Please point me to a proper document where I can deploy my image in PCF to start on https port? This is my log: 2017-09-12T18:14:55.382+05:30 [API/0] [OUT] Created app with guid fd8a0ddd-06ba-441a-94c7-73a0099589ad 2017-09-12T18:14:57.446+05:30 [API/0] [OUT] Updated app with guid fd8a0ddd-06ba-441a-94c7-73a0099589ad ({"route"=>"7d708d12-35fa-4fc2-9a87-3d4f8e8fac17", :verb=>"add", :relation=>"routes", :related_guid=>"7d708d12-35fa-4fc2-9a87-3d4f8e8fac17"}) 2017-09-12T18:15:01.708+05:30 [API/0] [OUT] Updated app with guid fd8a0ddd-06ba-441a-94c7-73a0099589ad ({"state"=>"STARTED"}) 2017-09-12T18:15:01.723+05:30 [STG/0] [OUT] Creating container 2017-09-12T18:15:01.928+05:30 [STG/0] [OUT] Staging... 2017-09-12T18:15:01.928+05:30 [STG/0] [OUT] Successfully created container 2017-09-12T18:15:01.986+05:30 [STG/0] [OUT] Staging process started ... 2017-09-12T18:15:06.062+05:30 [STG/0] [OUT] Staging process finished 2017-09-12T18:15:06.066+05:30 [STG/0] [OUT] Exit status 0 2017-09-12T18:15:06.066+05:30 [STG/0] [OUT] Staging Complete 2017-09-12T18:15:06.095+05:30 [STG/0] [OUT] Destroying container 2017-09-12T18:15:06.260+05:30 [CELL/0] [OUT] Creating container 2017-09-12T18:15:06.378+05:30 [STG/0] [OUT] Successfully destroyed container 2017-09-12T18:15:20.061+05:30 [API/0] [OUT] Updated app with guid fd8a0ddd-06ba-441a-94c7-73a0099589ad ({"memory"=>2048, "disk_quota"=>1024}) 2017-09-12T18:15:20.157+05:30 [API/0] [OUT] Updated app with guid fd8a0ddd-06ba-441a-94c7-73a0099589ad ({"state"=>"STOPPED"}) 2017-09-12T18:15:20.382+05:30 [API/0] [OUT] Updated app with guid fd8a0ddd-06ba-441a-94c7-73a0099589ad ({"state"=>"STARTED"}) 2017-09-12T18:15:20.391+05:30 [CELL/0] [OUT] Creating container ======= { "staging_env_json": {}, "running_env_json": {}, "environment_json": "invalid_key", "system_env_json": { "VCAP_SERVICES": {} }, "application_env_json": { "VCAP_APPLICATION": { "cf_api": "http://api.local.pcfdev.io", "limits": { "fds": 16384, "mem": 2048, "disk": 1024 }, "application_name": "is5.3.0", "application_uris": [ "is530.local.pcfdev.io" ], "name": "is5.3.0", "space_name": "pcfdev-space", "space_id": "a725ead6-283c-481d-b727-251865593e67", "uris": [ "is530.local.pcfdev.io" ], "users": null, "application_id": "fd8a0ddd-06ba-441a-94c7-73a0099589ad", "version": "d4a02bd7-e358-490a-9498-1c359882e5cd", "application_version": "d4a02bd7-e358-490a-9498-1c359882e5cd" } } } |
|
|
|
Re: Syslog drain binder job being replaced by cf-syslog-drain release
Altenhofen, Michael <michael.altenhofen@...>
Hi Adam,
sorry to nag you again (see [1]) with this, but will that release then implement the existing reconnection logic? Thanks Michael [1] https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/message/FSD2FITNMDHSIB2ZB2QV2GZMOJTHOV44/ Am 11.09.17, 20:05 schrieb "Adam Hevenor" <ahevenor(a)pivotal.io>: Hi All - In the next few packages of cf-release we are going to be introducing a new release called cf-syslog-drain release [1]. This release handles this functionality and was proposed as the Scalable Syslog feature proposal [2]. Properties for drain specific functionality like blacklisting will be moving to this new release. Specific mapping of these properties will be documented in a future version of cf-release notes. This release is also already available in cf-deployment with the experimental operations file titled disable-etcd. Thanks Adam [1] - http://bosh.io/releases/github.com/cloudfoundry/cf-syslog-drain-release?all=1 [2] - https://docs.google.com/document/d/1B31BWuPVGYIbQaEVfFhmTmp8_5t8RwGGHY_4q4unojI/edit |
|
|
|
Re: Recommendations for Service parameters
Matt McNeeney
Hi Aniruddha,
A new feature has just been merged into the Open Service Broker API specification that allows service brokers to use JSON schemes in their catalogs to define the configuration parameters they accept for creating a service instance, updating a service instance and creating a service binding: https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#schema-object If you are new to JSON schema, this excellent guide should help you: https://spacetelescope.github.io/understanding-json-schema/ This feature will be supported very soon in Cloud Foundry when the next version of the spec is released. Let me know if you have any further questions, Matt On Tue, 12 Sep 2017 at 06:20, Aniruddha Kulkarni <aquila.25(a)gmail.com> wrote: Hello, |
|
|
|
Recommendations for Service parameters
Aniruddha Kulkarni
Hello,
CF provides support for specifying service parameters during: 1. Service instance creation (cf cli: -c option) 2. Service instance bind to an application. 3. Service key creation. The format of these parameters is owned by the individual services. My question is what is the recommendation regarding how to "publish" the service parameter's format to the end-developers who will be using a Service? i.e. how will an end developer know about what parameters are to be provided? Is there any guidance w.r.t to using the service/service plan metadata for providing this information? Regards, -- -Aniruddha Kulkarni |
|
|
|
Re: Syslog drain binder job being replaced by cf-syslog-drain release
Mike Youngstrom <youngm@...>
Great! Do you have a timeline for removal of the old syslog
toggle quoted message
Show quoted text
functionality? Some of our loggregator syslog integrations are not compatible with the new release. If the old functionality could remain in place for a couple of months after the complete integration of the new syslog drain that would be optimal. Thanks, Mike On Mon, Sep 11, 2017 at 12:01 PM, Adam Hevenor <ahevenor(a)pivotal.io> wrote:
Hi All - |
|
|