Page History

...

• Summary:
  • CloudByte storage (i.e. Elastistor) plug-in will be designed to support a one to one mapping between a NFS iSCSI volume and a data disk (i.e. volume associated to a VM instance).
  • Setting the volume QoS can be done via Add Disk Offering and Add Volume dialogs. This has already been implemented as part of ACS 4.2 release.
  • This storage plug-in is intended to support at least XenServer initially. Other hypervisor support will be implemented eventually.
• Logging/Debug:
  • Nothing new. The logs will be generated in the existing log files of cloudstack management server.
• Possible Fallback/Workaround routes:
  • This plugin is intended to automate the volume creation steps at elastistor & use the created volume to be provisioned by the cloudstack admin. The workaround will be to do these manually. In other words admin need to login to elastistor’s UI (i.e. ElastiCenter) and follow necessary steps to create a volume of desired IOPs, create a SR (w.r.t XenCenter) with appropriate tags, create a disk offering (w.r.t cloudstack management UI), and finally create a data disk associated with these tags.
• Configuration characteristics:
  • A new provider bean will be added to the client/tomcatconf/applicationContext.xml.in file. The provider bean will point to the new CloudByte provider plugin class.
• Deployment requirements (fresh install vs. upgrade):
  • applicationContext.xml.in file should have modifications w.r.t. CloudByte
  • new storage plugin jar(s) related to CloudByte should be in management server’s classpath
• system requirements: memory, CPU, disk space, etc.:
  • Nothing new
• interoperability and compatibility requirements:
  • Supports XenServer
• list localization and internationalization specifications:
  • Nothing new
• explain the impact and possible upgrade/migration solution introduced by the feature:
  • There should not be any impact w.r.t database upgradation as there are no schema changes till now.
  • It is assumed that upgrade/migrate script etc.utilize the pom.xml of cloudstack project. Hence it should not cause any impact.
  • Note - The cloudstack/plugins project will have a new module that has the cloudbyte’s storage plugin code base. All the build & dependency management are controlled via the pom.xml files.
• explain performance & scalability implications when feature is used from small scale to large scale:
  • Same as with current Disk Offerings/New Volumes
• explain marketing specifications:
  • This feature is being marketed actively by CloudByte.
  • This should help improve and standardize on CloudStack’s pluggable storage plugins.
• explain levels or types of users communities of this feature (e.g. admin, user, etc):
  • Impacts admins and users (only impacts users if admins allow this).

...