In that case: * In your first point, we need the blob store api to copy the image to the new storage, right? We'd need the blob store dependency outside the image extension. And to do that, we need the keys from the original vm. Is this right? * To list all vms, we need the blob store api too. Do we need to use the credentials of *each* vm (thus creating N blobstore contexts)? And then, how do we know which contexts to create? Do we have to list all blobs or sonething like that?
If we end up needing to create N contexts, which is expensive, or depending always on the blobstore api in the adapter, I'd perhaps consider adding a blob store api in the arm provider directly. * Which different azure api calls are needed to cover the cases above? If they are not many, I think the best approach is to add just those methods to a new api in arm, and let those methods get thw VM credentials as parameters. A particular endpoint can be configured too. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/960#issuecomment-221194553
