Per our recent subgroup meeting, split the Device Random service into a separate Open Horizon service definition file residing in the same pattern, and list the main EdgeX service as a dependency.

Once that is working, templatize the pattern for an external service so that others can be added or removed as needed.

Objective is to stand-up the example RNG-EXF container/service as an open-horizon service; the existing OH example for EdgexX, does not break out the RNG example; need to understand how to parameterize that container to run independently of the other services, i.e. not using the bind statements in the existing example:

1. Split existing edgex OH service into two OH services; one w/ random alone and the second with the remaining containers (e.g. exfrandom and edgex)
2. Modify OH edge pattern to include both exfrandom and edgex OH services
3. Parameterize random service (and edgex pattern) with appropriate variables and values to utilize/access the OH edgex services API(s), etc..

Subsequent work would provide template or software library (or both) to enable OH services to utilize EXF services via API (n.b. authenticate, authorize, etc..)

Potential utilization of existing OH capabilities (n.b. metadata, API, ..) may obviate need to provide variable:values, but that is TBD.