Dynamic DataStorage device set up and fallback mechanism

[suresh-lc]

Is your feature request related to a problem? Please describe.
Currently all the devices get to know about the EdgeX server (Datastorage) by reading the toml file.

Problems in this approach:

1. The information about Data Storage device needs to be predefined.
2. If the pre-defined Data Storage device fails, we should a mechanism to setup Data Storage in another device dynamically

Describe the solution you'd like

1. All the devices, say device A,B,C would be running Home Edge
2. If we start EdgeX in say Device A.
3. The Home Edge in all devices would check is EdgeX services are running in regular intervals.
4. When any device finds the service, it would broadcast to all other devices saying it has the Edgex services running. In our example case it would be device A broadcasting.
5. In response all the devices can share there yaml file.
6. If primary data storage device fails, EdgeX can be enabled in other device and above steps would take place.

Merging of devices db when the primary device comes back need to be taken care.

This is just initial thoughts of proposal request the opinion.

[tiokim]

@suresh-lc Thanks for the idea!

Is your feature request related to a problem? Please describe. Currently all the devices get to know about the EdgeX server (Datastorage) by reading the toml file.

Problems in this approach:

1. The information about Data Storage device needs to be predefined.

2. If the pre-defined Data Storage device fails, we should a mechanism to setup Data Storage in another device dynamically

I would like to ask for the meaning of predefined since DataStorage generates the toml files automatically at the moment.
If Device A has the configuration file in the apps folder, Device A broadcasts the service to other devices. [ref]
Other devices also automatically generate the configuration files once they receive the broadcast.