[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Support for distributed applications

That REST api sounds very sensible and very useful have this in the platform. I'm afraid there are no timelines for this feature yet, so if I want to start work on prototyping Erlang applications internally, what should I do? It's not difficult to create a temporary gearfinder application after all.

Assuming we have solved both the intra-app distribution and inter-app discovery/connections, the next problem will be that we want to specify ensembles of applications. For example a product exists of appa + appb + appc. Each app lists it's internal requirements (endpoints / events) as usual. A meta-repository where you can specify that certain applications should be deployed together. Other users could then pick from this meta-repository a logical bundle that works well together and start to develop on it.

On Wed, Jul 10, 2013 at 7:36 PM, Clayton Coleman <ccoleman redhat com> wrote:
It's a bit difficult to get endpoints today from the REST API.  You can listen to the publish-http-endpoint-url event sent to HAProxy in order to collect those on the gear, but it's harder to get from externally.  The gear_groups API lists the gears, but not the ports.

As part of the HA pep, we will expose an endpoints REST API call that returns a hostname, port, protocol, type, cart, and gear id for each visible endpoint.  That'll assist in getting that info.  (https://github.com/openshift/openshift-pep/blob/master/openshift-pep-005.md#routing-table-data-model-wip)

For now, there is no great option.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]