Re: Proposal: DNS for Juju Charms

2016-09-24 Thread Casey Marshall
Awesome idea! Probably more of a wishlist thing at this point.. but can we also add SSHFP records for all the units? -Casey On Sat, Sep 24, 2016 at 11:47 AM, Marco Ceppi wrote: > Hey everyone, > > I'm currently working on a charm for NS1, which is a DNS service > accessible via API. There are q

Re: Feedback wanted: Changes to the Ubuntu Charm

2016-09-24 Thread Cory Johns
On Thu, Sep 22, 2016 at 10:40 AM, Ryan Beisner wrote: > On Thu, Sep 22, 2016 at 8:47 AM, Cory Johns > wrote: > >> For clarity, I'd just like to note that https://jujucharms.com/ubuntu/8 >> is the candidate revision, and you can deploy this on 1.25.6 (without >> --channel support) by being specif

Proposal: DNS for Juju Charms

2016-09-24 Thread Marco Ceppi
Hey everyone, I'm currently working on a charm for NS1, which is a DNS service accessible via API. There are quite a few of these types of services available and I'd like to develop a best practice about how the Juju model is presented as DNS. My hope is this would eventually be something that Juj

Re: Proposal: display-name for charm metadata

2016-09-24 Thread Marco Ceppi
On Sat, Sep 24, 2016 at 11:34 AM Alex Kavanagh wrote: > Why not allow the display of the name to be case sensitive, but all usage > to be case insensitive? So name is MySQL, but you can juju deploy mYSqL if > you really wanted to. > I expect display names may also include unicode characters in

Re: Proposal: display-name for charm metadata

2016-09-24 Thread Alex Kavanagh
Why not allow the display of the name to be case sensitive, but all usage to be case insensitive? So name is MySQL, but you can juju deploy mYSqL if you really wanted to. On Sat, Sep 24, 2016 at 2:50 PM, Marco Ceppi wrote: > Hey everyone, > > I know we're rocking towards 2.0 but this is a probl

Re: Proposal: display-name for charm metadata

2016-09-24 Thread Tom Barber
Yeah sounds reasonable but I would be wary of over engineering. Tom On 24 Sep 2016 14:59, "José Antonio Rey" wrote: > As long as it's an optional field, I would say this is one worth having. > Makes it easy to follow naming guidelines. > > However, it would be nice for charm names to not be cas

Re: Proposal: display-name for charm metadata

2016-09-24 Thread José Antonio Rey
As long as it's an optional field, I would say this is one worth having. Makes it easy to follow naming guidelines. However, it would be nice for charm names to not be case sensitive. That way, one would be able to deploy `juju deploy mysql` or `juju deploy MySQL` without troubles, since when one

Proposal: display-name for charm metadata

2016-09-24 Thread Marco Ceppi
Hey everyone, I know we're rocking towards 2.0 but this is a problem I've seen voiced a few times now. To date, the `name` field in charm has always been [a-z-0-9_-] where you can't end with `-#`. This makes sense, simple flat names that are all lowercase make it easy to do `juju deploy wordpress`