I have been using CDT for about three years now. I originally posted on this thread above back in 2019. We recently upgraded our MDS servers to R80.40 last March and shortly after that I started upgrading all the GW's from R80.20 to R80.40. I had to wait on some custom HFA's that R&D...so I would have started sooner.
I have upgraded since this May, 140 firewalls / 70 clusters using CDT - i am almost done!
Our "CDT Deployment scripts", do more than just the upgrade, push HFA's...We are pushing down different "fwkern.conf" files depending on the cluster in our env.; pushing custom scripts, un-taring them, and running them.
I just recently used CDT to push out the new v1.6 GAIA API to the GW's. I have also used CDT to rotate passwords on all the GW's.
So what i am trying to say is that I am using CDT for other things than just doing an upgrade or installing an HFA. I am not sure how this is going to be done in when you add CDT to the GUI. I am just worried that turning CDT into a GUI may impact other features or how I am using it. Our MDS env has 70+ domains, I have all my files structured on the MDS and rsync'ed between the MDS servers. For GW upgrades I have multiple sessions opened and just do a 'mdsenv" and run the deployment plans.
As for the other items that we use CDT for (not upgrades) I have bash scripts that loop through the domains, dynamically does the "-generate for the csv file" and then does the "execute", once completes loops to the next domain.
I am sure in the future, some of this can be moved over to Ansible...but that is another story because I am having issues with v1.5 of the API and I am using CDT to push out v1.6.
I am not sure how all of this will work in the GUI. I really do not want be opening a SmartConsole to each domain and making sure the upgrades are configured the same, or maintaining configuration in all the domains. If we only had a handful them maybe...but we have over 70 domains. Is this going to in the Global view of the MDS?
Please don't break CDT.