We use swift as Secondary Storage with XenServer, did not test with KVM.
So you need a staging NFS share that is used by the SSVM-hypervisor,
staging NFS is used to temporary store template while creating a new
Instance from a template.
SSVM VM communicate to Swift via the MGT interface and
Thanks for the info Pierre !
1 Question thought - we are setting up Swift as Secondary - with new zone,
from scrath.
What is the proper order of steps - my understadning is as folowing:
- deploy normal NFS secondary storage
- wait for SSV/CPVM to be provisioned etc...
- call the API required to
Yes, for that matter - I place question for any S3 style storage :)
Just need some integration guidelines...
Thx
On May 8, 2015 2:58 AM, Marcus shadow...@gmail.com wrote:
Not entirely sure, but is there anything about the other object stores(S3)?
They should all work the same with NFS
Looking at the code, it seems the SwiftImageStoreDriverImpl selects an
SSVM(EndPoint) and issues a DownloadCommand to it. So the SSVM would need
access to it, most likely via the public interface, but you could also
probably get to it via the management interface via the
Thx Marcus - we might go than over Public S3/Swift URL - its all local
network and over 10G - so would work for us fine - I will check.
Otherwise, I might trunk secondary storage network to Swift nodes as well,
so no routing, local attached swiftSSVM.
Thanks again
On 8 May 2015 at 09:10,
Not entirely sure, but is there anything about the other object stores(S3)?
They should all work the same with NFS staging.
On May 7, 2015 4:00 AM, Andrija Panic andrija.pa...@gmail.com wrote:
Hi guys,
I cant find any docs on this topic, so...posting a question here.
We are going to use
Hi guys,
I cant find any docs on this topic, so...posting a question here.
We are going to use Swift as region wide Secondary Storage.
My understadning: KVM hosts will still move i.e. templates from Primary
Storage to Secondary NFS Staging storage - and then this template needs to
be moved to
