[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

punith updated CLOUDSTACK-6173:
-------------------------------

    Description: 
The new plugin will follow the design principles abstracted by CloudStack API 
for implementing a storage plugin.

This new enhancement will try to reuse the QoS params ( i.e. max IOPs) exposed 
in the modified Disk-Offering UI page.
 
 The basic behavior of this plugin will be to :
 - Allow CloudStack(CS) Admin to invoke CS API to add Primary Storage based on 
Elastistor's plug-in.
    This will create a volume (Storage IP:/path)  in the Elastistor.
    The newly created volume will be attached as a SR in Xen Hypervisor.
 - Allow CS Admin to create a desired Disk Offering. The access control 
followed for creation of Disk Offering will be maintained in this feature too.
 - Allow an end user to use above created Disk Offering to add a new Volume.
 - Allow an end user to attach the above created volume (i.e. DataDisk) to a 
VM. 
 - Allow an end user to detach a volume from a VM.
 - Allow an end user to delete a volume from a VM.
 - Allow and end user to edit the iops of the data disk on fly without 
detaching it.
 - support for both nfs and iscsi at primary storage.
 

  was:
The new plugin will follow the design principles abstracted by CloudStack API 
for implementing a storage plugin.

This new enhancement will try to reuse the QoS params ( i.e. max IOPs) exposed 
in the modified Disk-Offering UI page.
 
 The basic behavior of this plugin will be to :
 - Allow CloudStack(CS) Admin to invoke CS API to add Primary Storage based on 
Elastistor's plug-in.
    This will create a volume (Storage IP:/path)  in the Elastistor.
    The newly created volume will be attached as a SR in Xen Hypervisor.
 - Allow CS Admin to create a desired Disk Offering. The access control 
followed for creation of Disk Offering will be maintained in this feature too.
 - Allow an end user to use above created Disk Offering to add a new Volume.
 - Allow an end user to attach the above created volume (i.e. DataDisk) to a 
VM. 
 - Allow an end user to detach a volume from a VM.
 - Allow an end user to delete a volume from a VM.

Note - The plugin will be tested initially on Xen Hypervisor with NFS based 
Storage Repository. 


> Implement a CloudByte storage plugin.
> -------------------------------------
>
>                 Key: CLOUDSTACK-6173
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6173
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API, Management Server
>    Affects Versions: Future, 4.4.0
>         Environment: All supported CloudStack platforms
>            Reporter: punith
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> The new plugin will follow the design principles abstracted by CloudStack API 
> for implementing a storage plugin.
> This new enhancement will try to reuse the QoS params ( i.e. max IOPs) 
> exposed in the modified Disk-Offering UI page.
>  
>  The basic behavior of this plugin will be to :
>  - Allow CloudStack(CS) Admin to invoke CS API to add Primary Storage based 
> on Elastistor's plug-in.
>     This will create a volume (Storage IP:/path)  in the Elastistor.
>     The newly created volume will be attached as a SR in Xen Hypervisor.
>  - Allow CS Admin to create a desired Disk Offering. The access control 
> followed for creation of Disk Offering will be maintained in this feature too.
>  - Allow an end user to use above created Disk Offering to add a new Volume.
>  - Allow an end user to attach the above created volume (i.e. DataDisk) to a 
> VM. 
>  - Allow an end user to detach a volume from a VM.
>  - Allow an end user to delete a volume from a VM.
>  - Allow and end user to edit the iops of the data disk on fly without 
> detaching it.
>  - support for both nfs and iscsi at primary storage.
>  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to