And my axe! Er, I mean, +1!
On Wed, Jun 1, 2016 at 3:32 AM, Konstantinos Tsakalozos <
kos.tsakalo...@canonical.com> wrote:
> Thank you both for the vote of confidence. Lets go charming!
>
> On Tue, May 31, 2016 at 11:32 PM, Kevin Monroe > wrote:
>
>> Since last
Yeah, we should see if we can do the same with YARN...
2016-06-01 14:42 GMT+02:00 Marco Ceppi :
> +1 to using % logic to make it scale across any sized instance. Awesome
> stuff!
>
> On Wed, Jun 1, 2016 at 6:28 AM Tom Barber wrote:
>
>> Okay
+1 to using % logic to make it scale across any sized instance. Awesome
stuff!
On Wed, Jun 1, 2016 at 6:28 AM Tom Barber wrote:
> Okay latest "stable" build has RAM config options.
>
> Drill ships with defaults of 8GB and 3GB but I didn't want it to die on
> EC2 Large
Okay latest "stable" build has RAM config options.
Drill ships with defaults of 8GB and 3GB but I didn't want it to die on EC2
Large etc boxes that dont have that much. So I added a bit of logic, you
can (I hope) add XXG and it will use that fixed amount, or you can, as it
ships, tell it you want
Yes, this is super interesting. Thanks!
On 01/06/16 10:58, James Beedy wrote:
> I've "conjured-up" what I think would be a great enhancement to the current
> user mgmt capability in 2.0.
>
> As things stand, one can add a user to a model, and set a permission category
> of either read
Good start. I would add
* external AAA connectivity (LDAP/AD) to find where the actual data is
stored.
* add user to units only (no access to Juju)
* share
++
Sam
--
Samuel Cozannet
Cloud, Big Data and IoT Strategy Team
Business Development - Cloud and ISV Ecosystem
Changing the Future of
I've "conjured-up" what I think would be a great enhancement to the current
user mgmt capability in 2.0.
As things stand, one can add a user to a model, and set a permission category
of either read (read), or write (read/write). This functionality is awesome,
and a huge step for juju
I've "conjured-up" what I think would be a great enhancement to the current
user mgmt capability in 2.0.
As things stand, one can add a user to a model, and set a permission category
of either read (read), or write (read/write). This functionality is awesome,
and a huge step for juju
Yeah I saw that on the Drill list, apologies for not mentioning that
earlier! :)
RAM config in the charm will be available shortly, although I've got a
meeting in 5 minutes so it'll probably be an hour or so.
--
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
Thanks for this Charm! I've sent it to my colleagues who are working with
Drill. We got a lot better performance by storing the data in Parquet
format. Drill wasn't able to distribute the queries because the data was
stored as json in HDFS.
2016-05-31 17:29 GMT+02:00 Tom Barber
Hello,
What is then the recommendation for monitoring / logging / (...) agents
that run independently on the units and are loosely connected to the local
charms, but potentially still need to know about the apps running?
Wouldn´t colocation make them cumbersome? Still encoded as subordinate
Thank you both for the vote of confidence. Lets go charming!
On Tue, May 31, 2016 at 11:32 PM, Kevin Monroe
wrote:
> Since last December, I've been on 18 tours through the Review Queue with
> Kostas. We've seen the good, the bad, and a little bit of ugly together.
>
12 matches
Mail list logo