Øystein Bedin
Øystein Bedin
Unfortunately we don't have access to a VMware environment as-is, so can't really provide the coding / support on it. If someone can provide a VMware environment that can be...
Related info captured in my PR a few weeks ago: https://github.com/redhat-cop/casl-ansible/pull/229#issuecomment-379980660
This is most likely a "won't fix" as we're moving away from using CASL to provision DNS and NFS is really up to the user (we have no plans to...
@garethahealy yes, that's correct
@InfoSec812 as you may have heard me refer to a few times, we are planning to introduce "custom steps" as part of the `openshift-applier`. These will be able to accommodate...
@makentenza @InfoSec812 this is already handled. The "custom steps" mentioned earlier is the pre/post steps. We already have examples of using this to "wait" till something is ready for consumption....
@tylerauerbeck yeah, it's a bit of a challenge to utilize the "downstream" code for this, so we may just need to move it back into `casl`, but still keep it...
@jtudelag this is a low priority issue as you can just use the `openstack stack delete` command (or the OSP web console).
@jtudelag one additional piece of info - before you delete the cluster with the above mentioned command, make sure any PVs are deleted to avoid leaving Cinder volumes behind (+...
@jtudelag the the DNS, host registration., etc. isn't handled by the delete playbook anyway. That's a different issue. The `openshift-ansible` delete functionality takes care of (some) of that.