Hello Nik, Ahamad, I've asked on the list what API implementation to use [1] . From my experience, when working with API's you end up writing a client. So if one is already provided I choose to use that. It tends to be tested and makes development easy and the code maintainable. Nobody wants code that's hard to maintain. I could add a few more arguments but it's not the point.
Regarding the expunge time, I've tested with a cloud that kept machines in 'Destroyed' state for as long as 20 minutes or more. I never stayed so long as to see how long, but the idea is that I can't clean up networks and maybe other stuff in that time. This is not something that you would like when you wish to automate stuff around CloudStack. You NEED to be able clean on demand. Ahamad: I'm using [2] fot documentation. I have tests that create and delete[3] networks and work fine [4]. The network does not get deleted when there are VM's associated with it. The delete network operation fails, the VM's can be destroyed, or expunging, it doesn't matter. Cheers, [1] http://markmail.org/message/eeobo37hyqilya6g [2] http://download.cloud.com/releases/3.0.0/api_3.0.0/TOC_User.html [3] https://github.com/ieugen/axemblr-provisionr/blob/run-instance/providers/cloudstack/src/main/java/com/axemblr/provisionr/cloudstack/activities/DeleteNetwork.java [4] https://github.com/ieugen/axemblr-provisionr/blob/run-instance/providers/cloudstack/src/test/java/com/axemblr/provisionr/cloudstack/activities/EnsureNetworkExistsLiveTest.java -- Ioan Eugen Stan / CTO / http://axemblr.com
