See Blitzer in action
need to know about Blitzer
Blitzer simply gives visibility and control over large amounts of nodes and lets you work as if it was only one. Under the hood is a sophisticated engine taking care of parallel processing for running distributed scripts and file transfers.
In Blitzer typically (not only) all nodes get accessed via ssh. So a passwordless logon by ssh key has to be set before your nodes can be used with Blitzer.
There are only a few variables to know in order to work in Blitzer scripts:
$cred: holds the username@ for ssh login
$node: IP or hostname
$comp: name of the software component
file: the filename to distribute from the local tmp directory The ui is designed to write, test, persist and run scripts in one place.
instant action with Blitzer here
Unzip, open a terminal, cd to that folder and run the blitzer binary.
Connect with a browser to the address shown on startup.
IP and port can be set, run
blitzer -hto see how.
Since the lack of posix, bash scripting and more there is no windows version available in the near future. It is actually possible to add posix functionality to windows and try to use blitzer, but be aware it's untested.
give Blitzer the chance to thrive
is streamlining the management of systems and distribution of software to many servers like in cloud environments, iot, big data, or in general any datacenter. Blitzer features: parallel execution realtime progress visualisation cascading distribution rolling updates Besides taking care of the complicated parallel execution and distribution, Blitzer provides a simple, immersive web interface, wich lets users write, test, persist and run scripts in one place. Model: Blitzer is build around the fundamental resource model contsisting of: server nodes along with their access credentials components of payload software Scope: Users define this model and can then run scripts against all or selected parts in the three scopes: per node, per component or per instance (node-component pair) Execution modes: single: to run once on the Blitzer node parallel: run all at the same time sequential: one node/instance/comp after the other rolling or 2/3 available: only on one thrid of all nodes/instances at a time in order to keep the other two thirds up Distribution modes: Blitzer introduces a cascading distribution mode similar to bittorrent in order to maximize the network utilisation. This speeds up file transfer jobs substantially in contrary to the bottleneck when simply serving a file from one node to all others. With Blitzers distribution mode each node wich received the file acts as a server to the next nodes until all nodes have it. There are two modes, linear and random. In linear mode the nodes wich receive first are evenly spread and the next ones are close to these. This resembles the strategy to transfer first to a node in each rack and then between the nodes inside each rack. Also Blitzer offers the random distribution when topology suits this, i.e. connects all nodes similarly near/fast.