ing userInfo,
>>>>> StoragePoolType type) {
>>>>>
>>>>>
>>>>> ** **
>>>>>
>>>>> may be implemented like this:
>>>>>
>>>>> storageadaptor adaptor = getstorageadaptor(type);*
t;>> ** **
>>>>
>>>> may be implemented like this:
>>>>
>>>> storageadaptor adaptor = getstorageadaptor(type);
>>>>
>>>> adaptor.createPool(…)
>>>>
>>>> ** **
>>>>
>>>> getStorageA
t;
>>> return this._storageAdaptor.getStoragePool(uuid);
>>>
>>> }
>>>
>>> ** **
>>>
>>> // pluggable getStoragePool
>>>
>>> public KVMStoragePool getStoragePool(String storageAdaptorType,
>>> S
aptor getStorageAdaptor(StoragePoolType type) {
>>
>> storageadaptor adaptor = storageMapper.get(type.toString());
>>
>>if (adaptor == null) {
>>
>> adaptor = storageMapper.get(“libvirt”);
>>
>>}
>>
&g
n adaptor;
>
> }
>
> *From:* Marcus Sorensen [mailto:shadow...@gmail.com]
> *Sent:* Monday, December 10, 2012 4:25 PM
>
> *To:* Edison Su
> *Cc:* cloudstack-dev@incubator.apache.org
> *Subject:* Re: pluggable storage implementation
>
> ** **
>
>
eMapper.get("libvirt");
}
return adaptor;
}
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, December 10, 2012 4:25 PM
To: Edison Su
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: pluggable storage implementation
I'm not quite sure what you mean on
}
On Mon, Dec 10, 2012 at 2:05 PM, Edison Su wrote:
> ** **
>
> ** **
>
> *From:* Marcus Sorensen [mailto:shadow...@gmail.com]
> *Sent:* Monday, December 10, 2012 3:37 PM
>
> *To:* Edison Su
> *Cc:* cloudstack-dev@incubator.apache.org
> *Subject:* Re: pluggable storage im
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, December 10, 2012 3:37 PM
To: Edison Su
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: pluggable storage implementation
Ok, that makes sense. So this will be a part of the storage refactor? If you're
not already worki
t;
> ** **
>
> ** **
>
> ** **
>
> *From:* Marcus Sorensen [mailto:shadow...@gmail.com]
> *Sent:* Monday, December 10, 2012 3:06 PM
> *To:* Edison Su
> *Cc:* cloudstack-dev@incubator.apache.org
> *Subject:* Re: pluggable storage implementation
>
> ** **
>
PM
To: Edison Su
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: pluggable storage implementation
Yeah, but I'm not seeing an easy/pluggable way to implement a storage adaptor,
where LibvirtComputingResource relies exclusively on KVMStoragePoolManager,
which is implementing LibvirtS
Yeah, but I'm not seeing an easy/pluggable way to implement a storage
adaptor, where LibvirtComputingResource relies exclusively on
KVMStoragePoolManager, which is implementing LibvirtStorageAdaptor. I don't
see how to switch between storage adaptors in KVMStoragePoolManager.java
based on what prim
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, December 10, 2012 2:06 PM
To: Edison Su
Cc: cloudstack-dev@incubator.apache.org
Subject: pluggable storage implementation
Just curious, hadn't thought about this before but it seems that at least on
KVM (probably similar in Xen an
12 matches
Mail list logo
