You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bigtop.apache.org by "Jorge (JIRA)" <ji...@apache.org> on 2019/07/19 16:25:00 UTC

[jira] [Created] (BIGTOP-3218) Implement storage bindings

Jorge created BIGTOP-3218:
-----------------------------

             Summary: Implement storage bindings
                 Key: BIGTOP-3218
                 URL: https://issues.apache.org/jira/browse/BIGTOP-3218
             Project: Bigtop
          Issue Type: New Feature
          Components: deployment
            Reporter: Jorge


We have identified several issues with deploying hadoop + spark bundle and/or hbase + hadoop bundle due to the fact that Juju uses a single root ephemeral disk for installation.

It would be desirable for the Bigdata components to support deploying with additional Juju storage ([https://docs.jujucharms.com/storage]) by implementing the storage bindings, some issues that should be solved by the additional storage are
 # Ability to split application data from the operating system install.
 # Backup / Restore ability
 # For providers such as OpenStack as there is no Cinder volume, we cannot dynamically expand the volume, so dynamic storage will provide this ability.
 #  We cannot specify the size of the database at provision time unless we create specific machine flavors for every permutation of disk (eg database) size and cpu/ram

Thank you for your input on this bug.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)