Re: Juju Storage/MAAS
Thanks James, we'll get to it. We'll work with the MAAS folks as on the surface it looks like Juju is passing things correctly via the MAAS APIs. The fact that the deployment works minus the storage constraint is interesting. Initially I theorised it could have been a TB vs TiB mismatch but the disk size is large enough to count that out. We'll update bug from here on On 01/11/17 13:10, James Beedy wrote: > I’ve created this bug for further tracking > https://bugs.launchpad.net/juju/+bug/1729127 > >> On Oct 31, 2017, at 7:59 PM, James Beedywrote: >> >> Yes, deploying without —storage results in a successful deploy. >> >>> On Oct 31, 2017, at 7:52 PM, Ian Booth wrote: >>> >>> And just to ask the obvious: deploying without the --storage constraint >>> results >>> in a successful deploy, albeit to a machine with maybe the wrong disk? >>> >>> On 01/11/17 10:51, James Beedy wrote: Ian, So, I think I'm close here. The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H I have tagged the md0 device with the tag "raid0", then I have created the storage pool as you have specified. `juju create-storage-pool ssd-disks maas tags=raid0` Then ran the following command to deploy my charm [0], attaching storage as part of the command: `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` The result is here: http://paste.ubuntu.com/25862190/ Here machines 1 and 2 are deployed without the `--constraints`, http://paste.ubuntu.com/25862219/ Am I missing something? Possibly like one more input to the `--storage` arg? Thanks [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 > On Tue, Oct 31, 2017 at 3:14 PM, Ian Booth > wrote: > > Thanks for raising the issue - we'll get the docs updated! > >> On 01/11/17 07:44, James Beedy wrote: >> I knew it would be something simple and sensible :) >> >> Thank you! >> >> On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth > wrote: >> >>> Of the top of my head, you want to do something like: >>> >>> $ juju create-storage-pool ssd-disks maas tags=ssd >>> $ juju deploy postgresql --storage pgdata=ssd-disks,32G >>> >>> The above assumes you have tagged in MAAS any SSD disks with the "ssd" >>> tag. You >>> can select whatever criteria you want and whatever tags you want to use. >>> >>> The deploy command above selects a MAAS node with a disk tagged "ssd" >>> which is >>> at least 32GB in size. >>> >>> On 01/11/17 07:04, James Beedy wrote: Trying to check out Juju storage capabilities on MAAS I found [0], but can't quite wrap my head around what the syntax might be to make it > work, and what the extent of the capability of the Juju storage features are >>> when used with MAAS. Re-reading [0], and looking for anything else I can find on Juju > storage every day for a week now thinking it may click or I might find the > right doc, but it hasn't, and I haven't. I filed a bug with juju/docs here [1] . Does anyone have an example of how to consume Juju storage using the > MAAS provider? Thanks! [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) [1] https://github.com/juju/docs/issues/2251 >>> >> > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
I’ve created this bug for further tracking https://bugs.launchpad.net/juju/+bug/1729127 > On Oct 31, 2017, at 7:59 PM, James Beedywrote: > > Yes, deploying without —storage results in a successful deploy. > >> On Oct 31, 2017, at 7:52 PM, Ian Booth wrote: >> >> And just to ask the obvious: deploying without the --storage constraint >> results >> in a successful deploy, albeit to a machine with maybe the wrong disk? >> >> >>> On 01/11/17 10:51, James Beedy wrote: >>> Ian, >>> >>> So, I think I'm close here. >>> >>> The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H >>> >>> I have tagged the md0 device with the tag "raid0", then I have created the >>> storage pool as you have specified. >>> >>> `juju create-storage-pool ssd-disks maas tags=raid0` >>> >>> Then ran the following command to deploy my charm [0], attaching storage as >>> part of the command: >>> >>> `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 >>> public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` >>> >>> >>> The result is here: http://paste.ubuntu.com/25862190/ >>> >>> >>> Here machines 1 and 2 are deployed without the `--constraints`, >>> http://paste.ubuntu.com/25862219/ >>> >>> >>> Am I missing something? Possibly like one more input to the `--storage` arg? >>> >>> >>> Thanks >>> >>> [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 >>> On Tue, Oct 31, 2017 at 3:14 PM, Ian Booth wrote: Thanks for raising the issue - we'll get the docs updated! > On 01/11/17 07:44, James Beedy wrote: > I knew it would be something simple and sensible :) > > Thank you! > > On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth wrote: > >> Of the top of my head, you want to do something like: >> >> $ juju create-storage-pool ssd-disks maas tags=ssd >> $ juju deploy postgresql --storage pgdata=ssd-disks,32G >> >> The above assumes you have tagged in MAAS any SSD disks with the "ssd" >> tag. You >> can select whatever criteria you want and whatever tags you want to use. >> >> The deploy command above selects a MAAS node with a disk tagged "ssd" >> which is >> at least 32GB in size. >> >> >>> On 01/11/17 07:04, James Beedy wrote: >>> Trying to check out Juju storage capabilities on MAAS I found [0], but >>> can't quite wrap my head around what the syntax might be to make it work, >>> and what the extent of the capability of the Juju storage features are >> when >>> used with MAAS. >>> >>> Re-reading [0], and looking for anything else I can find on Juju storage >>> every day for a week now thinking it may click or I might find the right >>> doc, but it hasn't, and I haven't. >>> >>> I filed a bug with juju/docs here [1] . >>> >>> Does anyone have an example of how to consume Juju storage using the MAAS >>> provider? >>> >>> Thanks! >>> >>> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) >>> [1] https://github.com/juju/docs/issues/2251 >>> >>> >>> >> > >>> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
I’ve created this bug for further tracking https://bugs.launchpad.net/juju/+bug/1729127 > On Oct 31, 2017, at 7:59 PM, James Beedywrote: > > Yes, deploying without —storage results in a successful deploy. > >> On Oct 31, 2017, at 7:52 PM, Ian Booth wrote: >> >> And just to ask the obvious: deploying without the --storage constraint >> results >> in a successful deploy, albeit to a machine with maybe the wrong disk? >> >> >>> On 01/11/17 10:51, James Beedy wrote: >>> Ian, >>> >>> So, I think I'm close here. >>> >>> The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H >>> >>> I have tagged the md0 device with the tag "raid0", then I have created the >>> storage pool as you have specified. >>> >>> `juju create-storage-pool ssd-disks maas tags=raid0` >>> >>> Then ran the following command to deploy my charm [0], attaching storage as >>> part of the command: >>> >>> `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 >>> public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` >>> >>> >>> The result is here: http://paste.ubuntu.com/25862190/ >>> >>> >>> Here machines 1 and 2 are deployed without the `--constraints`, >>> http://paste.ubuntu.com/25862219/ >>> >>> >>> Am I missing something? Possibly like one more input to the `--storage` arg? >>> >>> >>> Thanks >>> >>> [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 >>> On Tue, Oct 31, 2017 at 3:14 PM, Ian Booth wrote: Thanks for raising the issue - we'll get the docs updated! > On 01/11/17 07:44, James Beedy wrote: > I knew it would be something simple and sensible :) > > Thank you! > > On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth wrote: > >> Of the top of my head, you want to do something like: >> >> $ juju create-storage-pool ssd-disks maas tags=ssd >> $ juju deploy postgresql --storage pgdata=ssd-disks,32G >> >> The above assumes you have tagged in MAAS any SSD disks with the "ssd" >> tag. You >> can select whatever criteria you want and whatever tags you want to use. >> >> The deploy command above selects a MAAS node with a disk tagged "ssd" >> which is >> at least 32GB in size. >> >> >>> On 01/11/17 07:04, James Beedy wrote: >>> Trying to check out Juju storage capabilities on MAAS I found [0], but >>> can't quite wrap my head around what the syntax might be to make it work, >>> and what the extent of the capability of the Juju storage features are >> when >>> used with MAAS. >>> >>> Re-reading [0], and looking for anything else I can find on Juju storage >>> every day for a week now thinking it may click or I might find the right >>> doc, but it hasn't, and I haven't. >>> >>> I filed a bug with juju/docs here [1] . >>> >>> Does anyone have an example of how to consume Juju storage using the MAAS >>> provider? >>> >>> Thanks! >>> >>> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) >>> [1] https://github.com/juju/docs/issues/2251 >>> >>> >>> >> > >>> -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage/MAAS
Yes, deploying without —storage results in a successful deploy. > On Oct 31, 2017, at 7:52 PM, Ian Boothwrote: > > And just to ask the obvious: deploying without the --storage constraint > results > in a successful deploy, albeit to a machine with maybe the wrong disk? > > >> On 01/11/17 10:51, James Beedy wrote: >> Ian, >> >> So, I think I'm close here. >> >> The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H >> >> I have tagged the md0 device with the tag "raid0", then I have created the >> storage pool as you have specified. >> >> `juju create-storage-pool ssd-disks maas tags=raid0` >> >> Then ran the following command to deploy my charm [0], attaching storage as >> part of the command: >> >> `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 >> public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` >> >> >> The result is here: http://paste.ubuntu.com/25862190/ >> >> >> Here machines 1 and 2 are deployed without the `--constraints`, >> http://paste.ubuntu.com/25862219/ >> >> >> Am I missing something? Possibly like one more input to the `--storage` arg? >> >> >> Thanks >> >> [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 >> >>> On Tue, Oct 31, 2017 at 3:14 PM, Ian Booth wrote: >>> >>> Thanks for raising the issue - we'll get the docs updated! >>> On 01/11/17 07:44, James Beedy wrote: I knew it would be something simple and sensible :) Thank you! On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth >>> wrote: > Of the top of my head, you want to do something like: > > $ juju create-storage-pool ssd-disks maas tags=ssd > $ juju deploy postgresql --storage pgdata=ssd-disks,32G > > The above assumes you have tagged in MAAS any SSD disks with the "ssd" > tag. You > can select whatever criteria you want and whatever tags you want to use. > > The deploy command above selects a MAAS node with a disk tagged "ssd" > which is > at least 32GB in size. > > >> On 01/11/17 07:04, James Beedy wrote: >> Trying to check out Juju storage capabilities on MAAS I found [0], but >> can't quite wrap my head around what the syntax might be to make it >>> work, >> and what the extent of the capability of the Juju storage features are > when >> used with MAAS. >> >> Re-reading [0], and looking for anything else I can find on Juju >>> storage >> every day for a week now thinking it may click or I might find the >>> right >> doc, but it hasn't, and I haven't. >> >> I filed a bug with juju/docs here [1] . >> >> Does anyone have an example of how to consume Juju storage using the >>> MAAS >> provider? >> >> Thanks! >> >> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) >> [1] https://github.com/juju/docs/issues/2251 >> >> >> > >>> >> -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
Yes, deploying without —storage results in a successful deploy. > On Oct 31, 2017, at 7:52 PM, Ian Boothwrote: > > And just to ask the obvious: deploying without the --storage constraint > results > in a successful deploy, albeit to a machine with maybe the wrong disk? > > >> On 01/11/17 10:51, James Beedy wrote: >> Ian, >> >> So, I think I'm close here. >> >> The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H >> >> I have tagged the md0 device with the tag "raid0", then I have created the >> storage pool as you have specified. >> >> `juju create-storage-pool ssd-disks maas tags=raid0` >> >> Then ran the following command to deploy my charm [0], attaching storage as >> part of the command: >> >> `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 >> public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` >> >> >> The result is here: http://paste.ubuntu.com/25862190/ >> >> >> Here machines 1 and 2 are deployed without the `--constraints`, >> http://paste.ubuntu.com/25862219/ >> >> >> Am I missing something? Possibly like one more input to the `--storage` arg? >> >> >> Thanks >> >> [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 >> >>> On Tue, Oct 31, 2017 at 3:14 PM, Ian Booth wrote: >>> >>> Thanks for raising the issue - we'll get the docs updated! >>> On 01/11/17 07:44, James Beedy wrote: I knew it would be something simple and sensible :) Thank you! On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth >>> wrote: > Of the top of my head, you want to do something like: > > $ juju create-storage-pool ssd-disks maas tags=ssd > $ juju deploy postgresql --storage pgdata=ssd-disks,32G > > The above assumes you have tagged in MAAS any SSD disks with the "ssd" > tag. You > can select whatever criteria you want and whatever tags you want to use. > > The deploy command above selects a MAAS node with a disk tagged "ssd" > which is > at least 32GB in size. > > >> On 01/11/17 07:04, James Beedy wrote: >> Trying to check out Juju storage capabilities on MAAS I found [0], but >> can't quite wrap my head around what the syntax might be to make it >>> work, >> and what the extent of the capability of the Juju storage features are > when >> used with MAAS. >> >> Re-reading [0], and looking for anything else I can find on Juju >>> storage >> every day for a week now thinking it may click or I might find the >>> right >> doc, but it hasn't, and I haven't. >> >> I filed a bug with juju/docs here [1] . >> >> Does anyone have an example of how to consume Juju storage using the >>> MAAS >> provider? >> >> Thanks! >> >> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) >> [1] https://github.com/juju/docs/issues/2251 >> >> >> > >>> >> -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage/MAAS
And just to ask the obvious: deploying without the --storage constraint results in a successful deploy, albeit to a machine with maybe the wrong disk? On 01/11/17 10:51, James Beedy wrote: > Ian, > > So, I think I'm close here. > > The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H > > I have tagged the md0 device with the tag "raid0", then I have created the > storage pool as you have specified. > > `juju create-storage-pool ssd-disks maas tags=raid0` > > Then ran the following command to deploy my charm [0], attaching storage as > part of the command: > > `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 > public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` > > > The result is here: http://paste.ubuntu.com/25862190/ > > > Here machines 1 and 2 are deployed without the `--constraints`, > http://paste.ubuntu.com/25862219/ > > > Am I missing something? Possibly like one more input to the `--storage` arg? > > > Thanks > > [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 > > On Tue, Oct 31, 2017 at 3:14 PM, Ian Boothwrote: > >> Thanks for raising the issue - we'll get the docs updated! >> >> On 01/11/17 07:44, James Beedy wrote: >>> I knew it would be something simple and sensible :) >>> >>> Thank you! >>> >>> On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth >> wrote: >>> Of the top of my head, you want to do something like: $ juju create-storage-pool ssd-disks maas tags=ssd $ juju deploy postgresql --storage pgdata=ssd-disks,32G The above assumes you have tagged in MAAS any SSD disks with the "ssd" tag. You can select whatever criteria you want and whatever tags you want to use. The deploy command above selects a MAAS node with a disk tagged "ssd" which is at least 32GB in size. On 01/11/17 07:04, James Beedy wrote: > Trying to check out Juju storage capabilities on MAAS I found [0], but > can't quite wrap my head around what the syntax might be to make it >> work, > and what the extent of the capability of the Juju storage features are when > used with MAAS. > > Re-reading [0], and looking for anything else I can find on Juju >> storage > every day for a week now thinking it may click or I might find the >> right > doc, but it hasn't, and I haven't. > > I filed a bug with juju/docs here [1] . > > Does anyone have an example of how to consume Juju storage using the >> MAAS > provider? > > Thanks! > > [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > [1] https://github.com/juju/docs/issues/2251 > > > >>> >> > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
And just to ask the obvious: deploying without the --storage constraint results in a successful deploy, albeit to a machine with maybe the wrong disk? On 01/11/17 10:51, James Beedy wrote: > Ian, > > So, I think I'm close here. > > The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H > > I have tagged the md0 device with the tag "raid0", then I have created the > storage pool as you have specified. > > `juju create-storage-pool ssd-disks maas tags=raid0` > > Then ran the following command to deploy my charm [0], attaching storage as > part of the command: > > `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 > public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` > > > The result is here: http://paste.ubuntu.com/25862190/ > > > Here machines 1 and 2 are deployed without the `--constraints`, > http://paste.ubuntu.com/25862219/ > > > Am I missing something? Possibly like one more input to the `--storage` arg? > > > Thanks > > [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 > > On Tue, Oct 31, 2017 at 3:14 PM, Ian Boothwrote: > >> Thanks for raising the issue - we'll get the docs updated! >> >> On 01/11/17 07:44, James Beedy wrote: >>> I knew it would be something simple and sensible :) >>> >>> Thank you! >>> >>> On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth >> wrote: >>> Of the top of my head, you want to do something like: $ juju create-storage-pool ssd-disks maas tags=ssd $ juju deploy postgresql --storage pgdata=ssd-disks,32G The above assumes you have tagged in MAAS any SSD disks with the "ssd" tag. You can select whatever criteria you want and whatever tags you want to use. The deploy command above selects a MAAS node with a disk tagged "ssd" which is at least 32GB in size. On 01/11/17 07:04, James Beedy wrote: > Trying to check out Juju storage capabilities on MAAS I found [0], but > can't quite wrap my head around what the syntax might be to make it >> work, > and what the extent of the capability of the Juju storage features are when > used with MAAS. > > Re-reading [0], and looking for anything else I can find on Juju >> storage > every day for a week now thinking it may click or I might find the >> right > doc, but it hasn't, and I haven't. > > I filed a bug with juju/docs here [1] . > > Does anyone have an example of how to consume Juju storage using the >> MAAS > provider? > > Thanks! > > [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > [1] https://github.com/juju/docs/issues/2251 > > > >>> >> > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage/MAAS
Ian, So, I think I'm close here. The filesytem/device layout on my node(s): https://imgur.com/a/Nzn2H I have tagged the md0 device with the tag "raid0", then I have created the storage pool as you have specified. `juju create-storage-pool ssd-disks maas tags=raid0` Then ran the following command to deploy my charm [0], attaching storage as part of the command: `juju deploy cs:~jamesbeedy/elasticsearch-27 --bind "cluster=vlan20 public=mgmt-net" --storage data=ssd-disks,3T --constraints "tags=data"` The result is here: http://paste.ubuntu.com/25862190/ Here machines 1 and 2 are deployed without the `--constraints`, http://paste.ubuntu.com/25862219/ Am I missing something? Possibly like one more input to the `--storage` arg? Thanks [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27 On Tue, Oct 31, 2017 at 3:14 PM, Ian Boothwrote: > Thanks for raising the issue - we'll get the docs updated! > > On 01/11/17 07:44, James Beedy wrote: > > I knew it would be something simple and sensible :) > > > > Thank you! > > > > On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth > wrote: > > > >> Of the top of my head, you want to do something like: > >> > >> $ juju create-storage-pool ssd-disks maas tags=ssd > >> $ juju deploy postgresql --storage pgdata=ssd-disks,32G > >> > >> The above assumes you have tagged in MAAS any SSD disks with the "ssd" > >> tag. You > >> can select whatever criteria you want and whatever tags you want to use. > >> > >> The deploy command above selects a MAAS node with a disk tagged "ssd" > >> which is > >> at least 32GB in size. > >> > >> > >> On 01/11/17 07:04, James Beedy wrote: > >>> Trying to check out Juju storage capabilities on MAAS I found [0], but > >>> can't quite wrap my head around what the syntax might be to make it > work, > >>> and what the extent of the capability of the Juju storage features are > >> when > >>> used with MAAS. > >>> > >>> Re-reading [0], and looking for anything else I can find on Juju > storage > >>> every day for a week now thinking it may click or I might find the > right > >>> doc, but it hasn't, and I haven't. > >>> > >>> I filed a bug with juju/docs here [1] . > >>> > >>> Does anyone have an example of how to consume Juju storage using the > MAAS > >>> provider? > >>> > >>> Thanks! > >>> > >>> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > >>> [1] https://github.com/juju/docs/issues/2251 > >>> > >>> > >>> > >> > > > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage/MAAS
Thanks for raising the issue - we'll get the docs updated! On 01/11/17 07:44, James Beedy wrote: > I knew it would be something simple and sensible :) > > Thank you! > > On Tue, Oct 31, 2017 at 2:38 PM, Ian Boothwrote: > >> Of the top of my head, you want to do something like: >> >> $ juju create-storage-pool ssd-disks maas tags=ssd >> $ juju deploy postgresql --storage pgdata=ssd-disks,32G >> >> The above assumes you have tagged in MAAS any SSD disks with the "ssd" >> tag. You >> can select whatever criteria you want and whatever tags you want to use. >> >> The deploy command above selects a MAAS node with a disk tagged "ssd" >> which is >> at least 32GB in size. >> >> >> On 01/11/17 07:04, James Beedy wrote: >>> Trying to check out Juju storage capabilities on MAAS I found [0], but >>> can't quite wrap my head around what the syntax might be to make it work, >>> and what the extent of the capability of the Juju storage features are >> when >>> used with MAAS. >>> >>> Re-reading [0], and looking for anything else I can find on Juju storage >>> every day for a week now thinking it may click or I might find the right >>> doc, but it hasn't, and I haven't. >>> >>> I filed a bug with juju/docs here [1] . >>> >>> Does anyone have an example of how to consume Juju storage using the MAAS >>> provider? >>> >>> Thanks! >>> >>> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) >>> [1] https://github.com/juju/docs/issues/2251 >>> >>> >>> >> > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
Thanks for raising the issue - we'll get the docs updated! On 01/11/17 07:44, James Beedy wrote: > I knew it would be something simple and sensible :) > > Thank you! > > On Tue, Oct 31, 2017 at 2:38 PM, Ian Boothwrote: > >> Of the top of my head, you want to do something like: >> >> $ juju create-storage-pool ssd-disks maas tags=ssd >> $ juju deploy postgresql --storage pgdata=ssd-disks,32G >> >> The above assumes you have tagged in MAAS any SSD disks with the "ssd" >> tag. You >> can select whatever criteria you want and whatever tags you want to use. >> >> The deploy command above selects a MAAS node with a disk tagged "ssd" >> which is >> at least 32GB in size. >> >> >> On 01/11/17 07:04, James Beedy wrote: >>> Trying to check out Juju storage capabilities on MAAS I found [0], but >>> can't quite wrap my head around what the syntax might be to make it work, >>> and what the extent of the capability of the Juju storage features are >> when >>> used with MAAS. >>> >>> Re-reading [0], and looking for anything else I can find on Juju storage >>> every day for a week now thinking it may click or I might find the right >>> doc, but it hasn't, and I haven't. >>> >>> I filed a bug with juju/docs here [1] . >>> >>> Does anyone have an example of how to consume Juju storage using the MAAS >>> provider? >>> >>> Thanks! >>> >>> [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) >>> [1] https://github.com/juju/docs/issues/2251 >>> >>> >>> >> > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage/MAAS
I knew it would be something simple and sensible :) Thank you! On Tue, Oct 31, 2017 at 2:38 PM, Ian Boothwrote: > Of the top of my head, you want to do something like: > > $ juju create-storage-pool ssd-disks maas tags=ssd > $ juju deploy postgresql --storage pgdata=ssd-disks,32G > > The above assumes you have tagged in MAAS any SSD disks with the "ssd" > tag. You > can select whatever criteria you want and whatever tags you want to use. > > The deploy command above selects a MAAS node with a disk tagged "ssd" > which is > at least 32GB in size. > > > On 01/11/17 07:04, James Beedy wrote: > > Trying to check out Juju storage capabilities on MAAS I found [0], but > > can't quite wrap my head around what the syntax might be to make it work, > > and what the extent of the capability of the Juju storage features are > when > > used with MAAS. > > > > Re-reading [0], and looking for anything else I can find on Juju storage > > every day for a week now thinking it may click or I might find the right > > doc, but it hasn't, and I haven't. > > > > I filed a bug with juju/docs here [1] . > > > > Does anyone have an example of how to consume Juju storage using the MAAS > > provider? > > > > Thanks! > > > > [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > > [1] https://github.com/juju/docs/issues/2251 > > > > > > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
I knew it would be something simple and sensible :) Thank you! On Tue, Oct 31, 2017 at 2:38 PM, Ian Boothwrote: > Of the top of my head, you want to do something like: > > $ juju create-storage-pool ssd-disks maas tags=ssd > $ juju deploy postgresql --storage pgdata=ssd-disks,32G > > The above assumes you have tagged in MAAS any SSD disks with the "ssd" > tag. You > can select whatever criteria you want and whatever tags you want to use. > > The deploy command above selects a MAAS node with a disk tagged "ssd" > which is > at least 32GB in size. > > > On 01/11/17 07:04, James Beedy wrote: > > Trying to check out Juju storage capabilities on MAAS I found [0], but > > can't quite wrap my head around what the syntax might be to make it work, > > and what the extent of the capability of the Juju storage features are > when > > used with MAAS. > > > > Re-reading [0], and looking for anything else I can find on Juju storage > > every day for a week now thinking it may click or I might find the right > > doc, but it hasn't, and I haven't. > > > > I filed a bug with juju/docs here [1] . > > > > Does anyone have an example of how to consume Juju storage using the MAAS > > provider? > > > > Thanks! > > > > [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > > [1] https://github.com/juju/docs/issues/2251 > > > > > > > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage/MAAS
Of the top of my head, you want to do something like: $ juju create-storage-pool ssd-disks maas tags=ssd $ juju deploy postgresql --storage pgdata=ssd-disks,32G The above assumes you have tagged in MAAS any SSD disks with the "ssd" tag. You can select whatever criteria you want and whatever tags you want to use. The deploy command above selects a MAAS node with a disk tagged "ssd" which is at least 32GB in size. On 01/11/17 07:04, James Beedy wrote: > Trying to check out Juju storage capabilities on MAAS I found [0], but > can't quite wrap my head around what the syntax might be to make it work, > and what the extent of the capability of the Juju storage features are when > used with MAAS. > > Re-reading [0], and looking for anything else I can find on Juju storage > every day for a week now thinking it may click or I might find the right > doc, but it hasn't, and I haven't. > > I filed a bug with juju/docs here [1] . > > Does anyone have an example of how to consume Juju storage using the MAAS > provider? > > Thanks! > > [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > [1] https://github.com/juju/docs/issues/2251 > > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju Storage/MAAS
Of the top of my head, you want to do something like: $ juju create-storage-pool ssd-disks maas tags=ssd $ juju deploy postgresql --storage pgdata=ssd-disks,32G The above assumes you have tagged in MAAS any SSD disks with the "ssd" tag. You can select whatever criteria you want and whatever tags you want to use. The deploy command above selects a MAAS node with a disk tagged "ssd" which is at least 32GB in size. On 01/11/17 07:04, James Beedy wrote: > Trying to check out Juju storage capabilities on MAAS I found [0], but > can't quite wrap my head around what the syntax might be to make it work, > and what the extent of the capability of the Juju storage features are when > used with MAAS. > > Re-reading [0], and looking for anything else I can find on Juju storage > every day for a week now thinking it may click or I might find the right > doc, but it hasn't, and I haven't. > > I filed a bug with juju/docs here [1] . > > Does anyone have an example of how to consume Juju storage using the MAAS > provider? > > Thanks! > > [0] https://jujucharms.com/docs/devel/charms-storage#maas-(maas) > [1] https://github.com/juju/docs/issues/2251 > > > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju Storage
On Tue, Apr 5, 2016 at 10:03 PM Bruno Ranieriwrote: > Hi, > Hi Bruno, 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? > The command line arguments for storage a little bit (too?) subtle. If you don't specify any constraints for a store, then you'll get "loop" for block-type, and "rootfs" for filesystem-type stores. If you want to get the provider's default, you need to specify at least one constraint for the store. For example, say you want an EBS volume of 10G. You would deploy with "--storage registry-storage=10G". For the ec2 provider, this will allocate an EBS volume of 10GiB. 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. > > Try one of the following: (1) juju deploy --repository=. local:quobyte-registry --storage registry-storage=10G (2) juju deploy --repository=. local:quobyte-registry --storage registry-storage=ebs (3) juju deploy --repository=. local:quobyte-registry --storage registry-storage=ebs-ssd (1) will allocate the provider's native volume type (if the provider has one; otherwise loop), of at least 10GiB (2) will allocate an EBS magnetic volume with the store's minimum size (3) will allocate an EBS SSD volume with the store's minimum size > 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 >> udev1.9G 12K 1.9G 1% /dev >> tmpfs 375M 204K 375M 1% /run >> /dev/disk/by-label/cloudimg-rootfs 7.8G 7.8G 0 100% / >> none4.0K 0 4.0K 0% /sys/fs/cgroup >> none5.0M 0 5.0M 0% /run/lock >> none1.9G 0 1.9G 0% /run/shm >> none100M 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. > Right, so as above, you'll just need to specify the size and let Juju take care of determining the appropriate storage provider. Let us know how you get on. Cheers, Andrew 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 > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Juju storage - early access
We have implemented support for creating volumes in the ec2 provider, via the ebs storage provider. By default, the ebs provider will create cheap and nasty magnetic volumes. There is also an ebs-ssd storage pool provided OOTB that will create SSD (gp2) volumes. Finally, you can create your own pools if you like; the parameters for ebs are: - volume-type: may be magnetic, ssd, or provisioned-iops - iops: number of provisioned IOPS (requires volume-type=provisioned-iops) We haven't tested yet, but there should also be support for encrypted ebs volumes eg juju storage pool create encrypted-ebs ebs encrypted=true If you do try it, let us know of any issues encountered. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev