> -Original Message-
> From: Min Chen
> Sent: Monday, April 22, 2013 10:15 AM
> To: dev@cloudstack.apache.org
> Cc: Edison Su
> Subject: Re: [DIscuss]Storage image store plugin framework refactoring
>
> See my comments inline.
>
> -min
>
> On
ces like templates, iso and snapshots residing in it?
>[Min] Deletion of an image store will check if it has resources like
>template, snapshots, and volumes. If there are resources residing in it,
>we will throw error.
>>
>>-Thanks
>>Sangeetha
>>
>>--
ril 10, 2013 12:42 PM
>To: dev@cloudstack.apache.org
>Subject: Re: [DIscuss]Storage image store plugin framework refactoring
>
>On Tue, Apr 09, 2013 at 09:19:11AM -0700, Min Chen wrote:
>> Not yet at this moment. But we are planning to provide a sample plugin
>> implementation f
-
From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna
Santhanam
Sent: Wednesday, April 10, 2013 12:42 PM
To: dev@cloudstack.apache.org
Subject: Re: [DIscuss]Storage image store plugin framework refactoring
On Tue, Apr 09, 2013 at 09:19:11AM -0700, Min Chen wrote:
> Not
AM
To: dev@cloudstack.apache.org
Subject: Re: [DIscuss]Storage image store plugin framework refactoring
Hi Sangeetha,
See my answers inline.
Thanks
-min
On 4/9/13 2:48 PM, "Sangeetha Hariharan"
wrote:
>Can image stores from different providers (NFS,SWIFT,S
On Tue, Apr 09, 2013 at 09:19:11AM -0700, Min Chen wrote:
> Not yet at this moment. But we are planning to provide a sample plugin
> implementation for this effort. If you are looking at object_store branch,
> you will see a plugin called "cloud-plugin-storage-image-sample", which
> will be the pla
>
>-Original Message-
>From: Edison Su [mailto:edison...@citrix.com]
>Sent: Tuesday, April 09, 2013 2:01 PM
>To: dev@cloudstack.apache.org
>Subject: RE: [DIscuss]Storage image store plugin framework refactoring
>
>
>
>> -Original Message-
>&
resources like templates, iso and snapshots residing in it?
-Thanks
Sangeetha
-Original Message-
From: Edison Su [mailto:edison...@citrix.com]
Sent: Tuesday, April 09, 2013 2:01 PM
To: dev@cloudstack.apache.org
Subject: RE: [DIscuss]Storage image store plugin framework refactoring
> ---
> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Monday, April 08, 2013 11:33 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DIscuss]Storage image store plugin framework refactoring
>
> We can't deprecate APIs unl
On 09/04/13 11:03 PM, "Min Chen" wrote:
>It may not be that simple to just use api name alias. For example, we
>currently have listS3sCmd, with new image store plugin framework, we
>introduced a new API "listImageStoresCmd" to cover image stores from
>various providers, not only S3. We also int
It may not be that simple to just use api name alias. For example, we
currently have listS3sCmd, with new image store plugin framework, we
introduced a new API "listImageStoresCmd" to cover image stores from
various providers, not only S3. We also introduced a new response
ImageStoreResponse for th
We can have alias for an existing API. See the other ML discussion.
On 4/9/13 9:27 AM, "Min Chen" wrote:
>Yes, I will include more api change details in FS in next few days.
>According to Chiradeep, it seems that we cannot simply deprecate old API
>in 4.2, Edison and I will discuss this and upda
Yes, I will include more api change details in FS in next few days.
According to Chiradeep, it seems that we cannot simply deprecate old API
in 4.2, Edison and I will discuss this and update FS with details on how
to handle these old APIs.
Thanks
-min
On 4/8/13 6:34 PM, "Sangeetha Hariharan"
wro
Not yet at this moment. But we are planning to provide a sample plugin
implementation for this effort. If you are looking at object_store branch,
you will see a plugin called "cloud-plugin-storage-image-sample", which
will be the placeholder for a sample image store implementation.
Thanks
-min
On
On Mon, Apr 08, 2013 at 04:45:23PM -0700, Min Chen wrote:
> Hi All,
>
> Currently CloudStack does not offer a flexible pluggable framework
> for users to easily integrate and configure any 3rd-party object
> stores for such backup services as registering templates, taking
> snapshots, etc. Along w
We can't deprecate APIs unless we are changing to 5.0
AFAIK the next release in plan is 4.2
How does an upgrade from 4.0/4.1 to 4.2 work with this proposal?
- what happens to existing SSVMs?
- if there are multiple SSVMs?
- current cache-like deployments for S3 and Swift
The SSVM code also does d
Min,
Could you also include the details of the API changes (new parameters) that
will be proposed as part of this feature?
Also it would be helpful if you list the request and response parameters for
the new API calls.
For all the API calls that are being deprecated , is there any specific err
17 matches
Mail list logo
