This is more of a request for enhancing the capability rather than an issue with it.
IBM CloudCollection version 1.23.0
Terraform provider version 1.23.0
When I time the deployment of a new VSI using ibm_pi_instance module, it takes a very long time for execution that module returns; at time well over 20 min; even though the VSI has already completed in the neighborhood of 5min and I can login to it and work with it.
I think it is highly valuable for clients using this collection to return the module execution as soon as the deployment is complete even if the VSI state is still in warning state.
If the reason is to wait long enough for the VSI to turn to green/OK (i.e. to wait for the RMC to be active) to protect RMC-dependent operations (DLPAR, add volume, NIC etc), then I think the collection would be better off checking for the RMC state at beginning of each of such operation. I would argue that would be a better practice even later in the VSI lifecycle stages (such as immediately after a reboot, while a similar operation is already in flight or just RMC is failing) and not just create.
This is more of a request for enhancing the capability rather than an issue with it. IBM CloudCollection version 1.23.0 Terraform provider version 1.23.0
When I time the deployment of a new VSI using ibm_pi_instance module, it takes a very long time for execution that module returns; at time well over 20 min; even though the VSI has already completed in the neighborhood of 5min and I can login to it and work with it. I think it is highly valuable for clients using this collection to return the module execution as soon as the deployment is complete even if the VSI state is still in warning state. If the reason is to wait long enough for the VSI to turn to green/OK (i.e. to wait for the RMC to be active) to protect RMC-dependent operations (DLPAR, add volume, NIC etc), then I think the collection would be better off checking for the RMC state at beginning of each of such operation. I would argue that would be a better practice even later in the VSI lifecycle stages (such as immediately after a reboot, while a similar operation is already in flight or just RMC is failing) and not just create.