...
- Need to extend the type ‘filesystem storage’, currently only allows ‘Block Storage’ for non image usage.
- Same as in the NI case, the same VI name and UUID can be deployed onto each of the edge-nodes in the cluster.
- Same as in the NI case, may want to let users pick which edge-nodes need this VI or assign the ResourceLabel requirement.
- Same as in the NI case, if the ResourceLabel list exists, it does not need to be downloaded to the edge-nodes.
- Once each edge-node VI configuration is buildbuilt, it will be used in the device configuration for each edge-node selected
- If the VI does not need to be replicated by the cluster, then the user should only pick one edge-node
- Same as above NI question, should we reuse the same ‘VI’ object or create a new one for Edge-node Cluster VI?
- Normally once a VI is configured independent of the Application, it is downloaded onto the edge-node. This cluster case, we should allow users to pick up to three devices for this VI in the cluster. When the App is attached with this VI and if the App device selection does not match the VI device selection, we generate an error and ask user to modify. In the ‘Manual Migration’ case, only the DNId will get this VI configuration. In the ‘Auto-Migration’ of the App case, the other nodes may also get the VI configuration. A new DNId string is added to the ‘Volume’ API.
...