You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today the standard topology only includes 1 Manager instance. But we see more and more requests for Cluster tests, and hence an ask to be able to easily stand up an topology with a 3 node cluster.
Please describe the problem to be addressed by the proposed feature.
Proposed Solution
Lets either add a flag to deploy a default topology with 3 node cluster and 1 vbond 1 controller.
Or add an entire new "deploy_cluster" task in the tool that deploys that cluster topology.
Please describe what you envision the solution to this problem would look like.
Alternatives Considered
An alternative could be to create a flag for the "deploy" task that will allow us to deploy various topologies in the future.
Something like
Deploy --topology
and then we can over time expand the topology types, it could MRF toplogies, SD-Routing Topologies with DM-VPN or Flex. Or simila use cases.
Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and
tradeoffs being made.
Additional Context
Please provide any other information that may be relevant.
The text was updated successfully, but these errors were encountered:
Problem Statement
Today the standard topology only includes 1 Manager instance. But we see more and more requests for Cluster tests, and hence an ask to be able to easily stand up an topology with a 3 node cluster.
Please describe the problem to be addressed by the proposed feature.
Proposed Solution
Lets either add a flag to deploy a default topology with 3 node cluster and 1 vbond 1 controller.
Or add an entire new "deploy_cluster" task in the tool that deploys that cluster topology.
Please describe what you envision the solution to this problem would look like.
Alternatives Considered
An alternative could be to create a flag for the "deploy" task that will allow us to deploy various topologies in the future.
Something like
Deploy --topology
and then we can over time expand the topology types, it could MRF toplogies, SD-Routing Topologies with DM-VPN or Flex. Or simila use cases.
Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and
tradeoffs being made.
Additional Context
Please provide any other information that may be relevant.
The text was updated successfully, but these errors were encountered: