ModiPy Documentation
Quick Links
- Frequently Asked Questions
- The ModiPy Architecture
- Introduction to ModiPy XML configuration syntax
- The ModiPy XML configuration DTD
Overview
If you work with computers, you know that a large amount of your time is spent managing their configuration. You have patches to apply, parameters to change, new servers to build, and so on. This problem gets worse as the number of computers (and switches, and storage) gets larger. Wouldn't it be great if you could automate everything?
You've probably already automated some things by writing your own scripts in shell, Perl, Python or some other language. You might have noticed that checking for errors and handling them is really important. If you don't do this well, things go wrong with your automation scripts, and now you have to spend time maintaining your automation scripts as well as actually managing all the changes. To paraphrase Jamie Zawinski: "Now you have two problems".
ModiPy makes this all much easier. It has inbuilt error handling, and makes it easier to define how changes should happen in a set of logical steps. The changes are defined in a modular way, meaning that you can build up a set of components to do standard things, and then join these components together to do different things, but always in a standard way. Just like building blocks.
