[rudder-users] Move Rules/Directives and Techniques between Servers

[Nicolas Charles]

Hi Waldo,

You have several approaches for synchronizing different Rudder 
environments. The most commonly used rely on the underlying git which 
archive all configurations (in /var/rudder/configuration-repository). 
Options are:

  * Set all the configurations in the Dev environment only, and force
    synchronize it to the QA and Prod environments: with this approach,
    you have 3 Rudder Servers, *in exactly the same version*, and
    prohibit any changes of configuration in QA & Prod. When you are
    happy with configuration in Dev environment, you manually promote it
    through git to the QA server, and load the configuration from git
    (like in
    https://docs.rudder.io/reference/5.0/administration/server.html#_importing_configuration).
      o The main issue with this approach is that you can't do changes
        in QA or Prod, and when you want to promote configurations to
        QA, you need to make sure that nobody are doing any changes on
        the Dev Rudder
  * Cherry pick the configuration from Dev to import them in QA. All
    modifications of Groups, Directives, Rules and Techniques are stored
    in git, they can be tracked, and you can pick them by importing them
    in the QA & Prod environment. This is a fine-grained approach.
      o Here, detecting possible dependencies can be tricky: you'll need
        to cherry-pick also Directives that are within a Rule for
        instance. But since it is in a "human-readable" (understand:
        XML) format, you can use diff, or even better meld to see
        differences.

You can also use the API (see documentation https://docs.rudder.io/api/ 
) to synchronize between environments - GET on the DEV, POST on the QA - 
which is probably the most convenient way to do.

Does it help you to see how to do it?

Nicolas

Le 20/11/2018 à 09:35, Waldo Delport a écrit :
>
> Hi
>
> We are planning to use Rudder and really like the tool. The problem we 
> are experiencing is with multi-environment.
>
> We want segregated dev, QA and prod environments. With this in mind we 
> cannot have a single server serving all three enviroments, the 
> configuration eends to follow the dev,qa and prod route. Where once 
> tested on QA we can move it to prod. How can we do this on Rudder?
>
> 	
>
> *Waldo Delport*
>
> *Group HOD: Development*
>
> A close up of a logo Description generated with high confidence
>
> 	
>
> +27 (0)12 111 7000
>
> 	
>
> 	
>
> +27 (0)82 567 7220
>
> 	
>
> 	
>
> A close up of a logo Description generated with high confidence
>
> 	
>
> waldod at pqfgroup.co.za
>
> 	
>
> 	
>
> This message and any attachments and or links are confidential and 
> intended solely for the addressee. If you have received this message 
> in error, please notify PQF Group Services (Pty) Ltd immediately, 
> e-mail info at pqfgroup.co.za <mailto:info at pqfgroup.co.za>. Any 
> unauthorized use; alteration or dissemination of the contents of this 
> email is strictly prohibited. In no event will PQF Group Services 
> (Pty) Ltd or the sender be liable in any manner whatsoever to any 
> person for any loss or any direct, indirect, special or consequential 
> damages arising from use of this email or any linked website, 
> including, without limitation, from any lost profits, business 
> interruption, loss of programs or other data that may be stored on any 
> information handling system or otherwise from any assurance that this 
> email is virus free even if PQF Group Services (Pty) Ltd is expressly 
> advised of the possibility of such damages.
>
>
> _______________________________________________
> rudder-users mailing list
> FAQ: https://faq.rudder.io/
> Bug Tracker: https://issues.rudder.io/
> rudder-users at lists.rudder-project.org
> https://www.rudder-project.org/mailman/listinfo/rudder-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20181122/44862d6e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 6921 bytes
Desc: not available
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20181122/44862d6e/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 724 bytes
Desc: not available
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20181122/44862d6e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 509 bytes
Desc: not available
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20181122/44862d6e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 643 bytes
Desc: not available
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20181122/44862d6e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 6464 bytes
Desc: not available
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20181122/44862d6e/attachment-0003.jpg>