the fwmanager name does not accurately reflect what this component is or will become.
I propose naming this Device Resiliency Orchestrator with a number of subcomponents under it. I'm thinking something like the following, though we should discuss and agree before implementation:
services/
|---device_resiliency_orchestrator/
|---boot_orchestrator/
|---device_fwupdate/
|---device_fwrecovery/
The above is an example of how I see this, not necessarily how it should definitely be organized.
I would like to see a high-level design and block diagram of the overall orchestrator so we can revise/fine-tune this.
the fwmanager name does not accurately reflect what this component is or will become.
I propose naming this Device Resiliency Orchestrator with a number of subcomponents under it. I'm thinking something like the following, though we should discuss and agree before implementation:
The above is an example of how I see this, not necessarily how it should definitely be organized.
I would like to see a high-level design and block diagram of the overall orchestrator so we can revise/fine-tune this.