CSA needs an option to change the default behavior of all server builds in a server group being launched asynchronously. This really causes contention with accessing shared resources like IP Address Management, etc. The only way to work around this issue currently is to use semiphores which have their own issues.
There really should be a way to make server builds queue up in CSA and build serially. The server group components are processed serially, so it makes sense to give the option of having the server components build serially too.
It would also be nice if there was some sort of internal CSA property (i.e. SVC_Component_Instance) that corresponds to server build order so that if you need to process an operation on only the first server, or only the last server there was a way to track programatically which server number is currently being built.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.