PROJET AUTOBLOG


Shaarli - Les discussions de Shaarli

Archivé

Site original : Shaarli - Les discussions de Shaarli

⇐ retour index

GFX::Monk - NixOS and Stateless Deployment

vendredi 9 janvier 2015 à 14:51
@jeekajoo shaarlinks 09/01/2015
L'article montre les limites des systèmes de déploiement déclaratifs comme puppet
"""
...
And obviously, the entire problem of server deployment is deeply stateful - your server is quite literally a state machine, and each deployment attempts to modify its current state into (hopefully) the expected target state.

Unfortunately, in such a system it can be difficult to predict how the current state will interact with your deployment scripts. Performing the same deployment to two servers that started in different states can have drastically different results. Usually one of them failing.

Puppet is a little different, in that you don’t specify what you want to happen, but rather the desired state. Instead of writing down the steps required to install the package foo, you simply state that you want foo to be installed, and puppet knows what to do to get the current system (whatever its state) into the state you asked for.

Which would be great, if it weren’t a pretty big lie.
...
"""
NixOS fait également parti de ces systèmes mais son approche différente permet de s'astreindre des principaux défauts de ses 'concurrents'.
Plutôt que de tenter d'ammener le serveur (dans un état X) vers un état Y, NixOS part de zéro.
(Permalink)