Re: routing-api and cf-230?
Christopher Piraino <cpiraino@...>
Hi Tom,
The only features that the routing-api currently provides are all
experimental, mostly related to registering HTTP and TCP routes. This means
that it is not necessary at all for a working Cloud Foundry deployment,
which is a reason we removed it from the default manifests.
We are also in the process of moving the routing-api into the
cf-routing-release
<https://github.com/cloudfoundry-incubator/cf-routing-release> since it is
required fro TCP routing, another reason it was removed from default
cf-release manifests.
Hope that helps!
- Chris Piraino
toggle quoted message
Show quoted text
The only features that the routing-api currently provides are all
experimental, mostly related to registering HTTP and TCP routes. This means
that it is not necessary at all for a working Cloud Foundry deployment,
which is a reason we removed it from the default manifests.
We are also in the process of moving the routing-api into the
cf-routing-release
<https://github.com/cloudfoundry-incubator/cf-routing-release> since it is
required fro TCP routing, another reason it was removed from default
cf-release manifests.
Hope that helps!
- Chris Piraino
On Tue, Feb 16, 2016 at 11:09 AM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote:
Openstack, cf 230
Following a manifest for 225, routing-api is part of the api_z instance.
Generating the manifest for 230, routing-api is not included. Following on
what worked, I added it. Api would not start.
routing-api failed:
{"timestamp":"1455647513.437552214","source":"routing-api","message":"routing-api.uaa-key-fetcher.fetch-key-started","log_level":1,"d
ata":{"session":"1"}}
{"timestamp":"1455647513.450663328","source":"routing-api","message":"routing-api.uaa-key-fetcher.http-error-fetching-key","log_level
":2,"data":{"error":"http-error-fetching-key","session":"1"}}
{"timestamp":"1455647513.450931787","source":"routing-api","message":"routing-api.uaa-key-fetcher.fetch-key-completed","log_level":1,
"data":{"session":"1"}}
{"timestamp":"1455647513.451057196","source":"routing-api","message":"routing-api.Failed
to get verification key from UAA","log_level
":2,"data":{"error":"http-error-fetching-key"}}
{"timestamp":"1455647583.828899622","source":"routing-api","message":"routing-api.database","log_level":1,"data":{"etcd-addresses":["
http://192.168.20.19:4001"]}}
Removed routing-api. CF deploy works fine, all appears ok.
What features will I lose with this not being deployed? We have scripts
make rest calls for routes. I haven't taken a crack at those yet.
Any additional pointers welcome.
Thanks,
Tom