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 'secstorage.allowed.internal.sites' setting, similar to how the NFS template registration works.
I'm not highly versed in the object storage, so perhaps someone who is can verify or deny this. On Thu, May 7, 2015 at 11:31 PM, Andrija Panic <andrija.pa...@gmail.com> wrote: > 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 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 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 Swift. > > > > > > Question: > > > > > > Who/What is actually moving data from NFS Staging to Swift and over > what > > > path/network? > > > > > > Is SSVM moving data from NFS to Swift - if so, over what Network - does > > it > > > use Secondary Storage Gateway maybe, or not) - it certainly does not > use > > > default routing (over Public Network) > > > > > > Any hints - I need to enable some NFS-to-Swift connectivity :) > > > > > > Thx, > > > > > > -- > > > > > > Andrija Panić > > > > > >
