Hi,
the upgrade path is currently something we are still working on. For
drop-in upgrades you could simply replace the .jar files of Graylog but we
want to offer a more
complete way to do this. You can follow this ticket:
https://github.com/Graylog2/graylog2-images/issues/35

For a clustered production setup is maybe an installation via Chef cookbook
or Puppet manifest a better approach at the moment:
https://github.com/Graylog2/graylog2-cookbook

On 19 February 2015 at 15:27, AB <[email protected]> wrote:

> Hello,
>
> We just took a look at deploying a few Graylog2-images and it is a very
> simple & easy process to deploy your graylog2 cluster. Great work! We
> currently have a single server setup and were looking go to a clustered
> setup. But before we switch to a production setup using the templates we
> were hoping someone could guide us on some doubts.
>
>
>
>    1.
>
>    What is the upgrade path between version using the templates? Is there
>    a way we can migrate data going from one version to another?
>    2.
>
>    How are operating system security patches handled with this scenario?
>    Can we apply the regular OS updates?
>    3.
>
>    How would we go about migrating existing log data into the new
>    template based clustered setup?
>
>
>
> Thanks,
>
> Ab.
>
> --
> You received this message because you are subscribed to the Google Groups
> "graylog2" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Developer

Tel.: +49 (0)40 609 452 077
Fax.: +49 (0)40 609 452 078

TORCH GmbH - A Graylog Company
Steckelhörn 11
20457 Hamburg
Germany

https://www.graylog.com <https://www.torch.sh/>

Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175
Geschäftsführer: Lennart Koopmann (CEO)

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to