Hi Adron,
Thank you for the reply. The licensing is a concern, but that was for
later.
I think there will have to be a cluster of some sort on the remote dcs as
the connection between the edge dcs and the central dc is limited to a
small 1-2mbps link that is shared with many other higher priority
I think with Chef Cookbooks it is reasonable. Most people look at what the
cookbook is doing before using it. This is different from packages where
people usually don't rip apart a .deb with dpkg-deb before installing it.
-Jared
On Thu, May 16, 2013 at 8:28 AM, Hector Castro wrote:
> Sligh
For the cookbook, I think that's fine. It's not the actually package itself
doing the change. In fact, I expect that the cookbook and puppet modules
(or ansible playbooks...whatever) probably should do that. I'm making
a conscious decision to use those to manage the configuration. I think
that's th
Slightly related, we just recently updated file descriptor limit
support in the Riak cookbook [0]. As of right now, ulimits
automatically get increased (4096 by default) for the `riak` and
`riak-cs` users based on what cookbook you use.
Perhaps we should make that increase conditional?
--
Hector
As an opposing viewpoint, I'd argue that it's NOT the requirement of Riak
to go automatically changing things outside of its domain. Ulimits and
tunables in the same class are not things that should be blindly tweaked by
an incoming package. These are things the system administrator needs to be
awa
Toby,
It seems to me like it would be nice if Riak "just worked" when you
> installed it, instead of requiring each and every user to have to track
> something down in the docs and then configure it in their chef/puppet
> manifests. Don't you agree that is a desirable feature of good software?
> (
