Externalize storm.yaml file

[Neha Jain <Ne...@persistent.co.in>]

Hello,

I have created a storm cluster on Amazon EC2 machines. The requirement we have is to save Storm configuration file to Amazon S3.
There would be a bucket in S3 where storm config file would be placed and Storm cluster should access that file.

Is it possible to configure config file location in Storm. By default it refers to $STORM_DIR/conf/strom.yaml
Can we configure conf directory in Storm to point it to a different location so as jobs to know where to pick the config file from.

Thanks in advance

Regards,
Neha

DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.

Re: Externalize storm.yaml file

[P Ghosh <ja...@gmail.com>]

Use soft links.....

Prasun

Sent from Galaxy Nexus
On May 14, 2014 6:50 AM, "Neha Jain" <Ne...@persistent.co.in> wrote:

>  Hello,
>
>
>
> I have created a storm cluster on Amazon EC2 machines. The requirement we
> have is to save Storm configuration file to Amazon S3.
>
> There would be a bucket in S3 where storm config file would be placed and
> Storm cluster should access that file.
>
>
>
> Is it possible to configure config file location in Storm. By default it
> refers to $STORM_DIR/conf/strom.yaml
>
> Can we configure conf directory in Storm to point it to a different
> location so as jobs to know where to pick the config file from.
>
>
>
> Thanks in advance
>
>
>
> Regards,
>
> Neha
>
> DISCLAIMER ========== This e-mail may contain privileged and confidential
> information which is the property of Persistent Systems Ltd. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Persistent Systems Ltd. does not accept any liability for
> virus infected mails.
>