[chef] Re: Re: Re: API Interaction from node

[Adam Jacob < >]

Man I hope so.

Be kind of awesome if he's packing actual binlogs into a JSON value,
though.

Adam

On 1/8/13 5:57 PM, "AJ Christensen" 
<
 >
 wrote:

>I think he means storing the bin log position in a data-bag (quite a
>common approach to allowing slaves to find the correct position)
>
>
>No?
>
>
>--AJ
>
>
>
>On 9 January 2013 14:54, Jay Feldblum 
><
 >
> wrote:
>
>Anthony,
>
>
>I would say "You're Doing It Wrong."
>
>
>Chef is for configuration, not bulk storage. Storing backups in
>chef-server is Doing It Wrong. There are plenty of other approaches. You
>can run backups on a schedule (or on demand) separately from chef-client
>runs. Chef-client can provision the backup
> script and everything necessary to get it running so that it's a
>one-liner in the crontab or a one-liner from SSH. If the script is
>copying data to remote storage, it should not be to chef-server. Instead,
>chef can provision a remote storage node with replicated
> disks and can provision the slave's backup script to know about it, or
>you can use a storage service like S3 and chef can provision the slave's
>backup script to know about that instead.
>
>
>Cheers,
>Jay
>
>On Tue, Jan 8, 2013 at 4:49 PM, Anthony Goddard
><
 >
> wrote:
>
>Hi all,
>I'm writing a little script to populate a databag each time it's run -
>the purpose is to store mysql bin log data in a databag when a slave is
>backed up. I was originally thinking of using the API from the node and
>just using the local client.pem for authentication,
> but while I can read databags this way, I get a 403 when writing to
>them, so I'm looking for a breakdown of what objects the client is able
>to modify.
>I could also just change where I'm storing the data, or if that doesn't
>work, some middleware with another key will work, but I'd be interested
>in hearing about any other approaches if I'm Doing It Wrong.
>
>fwiw, the script that's interacting with chef is run from cron.
>
>
>Cheers,
>Ant
>
>
>
>
>
>
>
>
>
>
>
>