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 Beedy <jamesbe...@gmail.com> wrote: >> >> Yes, deploying without —storage results in a successful deploy. >> >>> On Oct 31, 2017, at 7:52 PM, Ian Booth <ian.bo...@canonical.com> 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 <ian.bo...@canonical.com> >>>>> 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 <ian.bo...@canonical.com> >>>>> 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
