Hi,
I am working on charms for the Quobyte Storage System. These charms make
use of the Juju Storage support,
but unfortunately juju storage does not behave as expected:
In my charms block-type storage is defined (metadata.yaml):
> [...]
> storage:
> registry-storage:
> type: block
> description: registry storage
> minimum-size: 10G
> multiple:
> range: '1'
>
When I deploy this charm to ec2 I assume that juju will create an
ebs-volume [1].
What it does instead is creating a loop-device?
After 'juju switch amazon' and 'juju bootstrap' [2] my storage pool is
initialized to
> ubuntu@bruno:~$ juju storage pool list
> ebs-ssd:
> provider: ebs
> attrs:
> volume-type: ssd
>
When deploying this charm
> ubuntu@bruno:~$ juju deploy --repository=. local:quobyte-registry
> Added charm "local:trusty/quobyte-registry-1" to the environment.
>
already the agent deployment fails with:
> $ juju debug-log --replay
> [...]
> machine-1[14401]: 2016-04-05 12:06:01 ERROR juju.worker runner.go:223
> exited "deployer": cannot create agent
> config dir "/var/lib/juju/agents/unit-quobyte-registry-0": mkdir
> /var/lib/juju/agents/unit-quobyte-registry-0: no space left on device
>
Debugging into the deployed machine (and ec2-console) shows that no
ebs-volume was created but an image on the local disk:
> $ juju ssh 1
> ubuntu@ip-x.y.z.a:~$ df -h
> Filesystem Size Used Avail Use% Mounted on
> udev 1.9G 12K 1.9G 1% /dev
> tmpfs 375M 204K 375M 1% /run
> /dev/disk/by-label/cloudimg-rootfs 7.8G 7.8G 0 100% /
> none 4.0K 0 4.0K 0% /sys/fs/cgroup
> none 5.0M 0 5.0M 0% /run/lock
> none 1.9G 0 1.9G 0% /run/shm
> none 100M 0 100M 0% /run/user
> /dev/xvdb 3.9G 8.1M 3.7G 1% /mnt
>
I'm aware that it is possible to control the storage usage during
service-deploment on the command-line
using '--storage registry-storage=ebs', but I do not think that this is the
correct solution? Currently I am working on tests
for the 'juju test' -runner. There I cannot hard-wire storage to ebs, since
these tests should be independent form a specific provider.
Any ideas what is possible wrong I my setup?
Thanks and Regards,
Bruno Ranieri
[1] 'If pool is not specified, then Juju will select the default storage
provider for the current environment
(e.g. cinder for openstack, ebs for ec2, loop for local)'
https://jujucharms.com/docs/1.25/storage
[2] $ cat ~/.juju/environments.yaml
> default: local
> environments:
> local:
> type: local
> admin-secret: xyz
> lxc-clone: true
> allow-lxc-loop-mounts: true
> default-series: trusty
>
> amazon:
> type: ec2
> region: eu-central-1
> access-key: xyz
> secret-key: xyz
> admin-secret: xyz
> default-series: trusty
>
>
--
Quobyte GmbH
Hardenbergplatz 2 - 10623 Berlin - Germany
+49-30-814 591 800 - www.quobyte.com
Amtsgericht Berlin-Charlottenburg, HRB 149012B
management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
