Given the hierarchical nature of the Mobility Master/Conductor, how would you recommend doing configuration management via a ci/cd pipeline? Since different configuration segments would be homed in different level of the hierarchy, I am having trouble wrapping my brain around it as it compares to a switch configuration (e.g. ArubaOS-CX or another vendor), where everything is all in one hierarchy level. Normally, I would just update the data model/host vars file, and the playbook would generate the config updates from a jinja2 template, etc.
Thanks in advance.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.