From fc6e59c719e30f4e7e49df4f8abf029726e7ff25 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Sun, 30 Mar 2014 19:37:33 +0200 Subject: [PATCH] -that repeatition Signed-off-by: Nico Schottelius --- blog/treat-virtual-machines-like-hardware.mdwn | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/blog/treat-virtual-machines-like-hardware.mdwn b/blog/treat-virtual-machines-like-hardware.mdwn index c5f81a78..37f383af 100644 --- a/blog/treat-virtual-machines-like-hardware.mdwn +++ b/blog/treat-virtual-machines-like-hardware.mdwn @@ -65,13 +65,13 @@ In my opinion (I believe in the [[!kiss]]), managing large scale infrastructures as managing small infrastructures - given you take the right approach. From a technical point of view, to manage an infrastucture you need - * an inventory management tool (like [[cinv|software/cinv]]) - * that is the central tool to record all your hosts - * that defines IP address mapppings (mac<->ip, f.i. [[!dhcp]] and ip<->name, like [[!dns]]) + * an inventory management tool (like [[cinv|software/cinv]]) that + * is the central tool to record all your hosts + * defines IP address mapppings (mac<->ip, f.i. [[!dhcp]] and ip<->name, like [[!dns]]) * assists you with lifecycle management of your hosts - * a configuration management system (like [[cdist|software/cdist]]) - * that realises your centrally defined configurations - * that manages all your configurations (including VMs!) + * a configuration management system (like [[cdist|software/cdist]]) that + * realises your centrally defined configurations + * manages all your configurations (including VMs!) ## Summary