Closed abessiari closed 3 weeks ago
Work In Progress.
Phase 1: Allow the framework to notify a provider that a resource that depends on a resource from that provider has been created. Recall that chameleon network and fabric network depend on each other. To break the cycle, this added notification call helps with that. Things as is. That is fabric network depends on chameleon network explicitly and the the other direction is not explicit. This is a quick workaround to handle this issue.
Phase 2: Add fabnet v4 support to chameleon network. In progress.
a depends on b. a gets the notification that b got created. explicit in the config b gets the notification that a got created.
conditional dependencies or this idea a strong dependency and a weak dependency
Not a priority.
Chameleon nodes can now use fabnet v4. Add the support for this feature in fabfed.