Multimachine blueprint design example

Creating a blueprint for a single VM containing just the OS is one thing. But the real value comes with blueprints containing multiple VMs and also preinstalling a complete application landscape, all on demand. These are the high-value services in a catalog since the user can request an outcome, a ready to use application. Typically fully integrated into the environment.

However, these are also the complex designs and configurations. They need multiple networks (possibly also NSX), also they require user settable parameters which might be provided from one software tool to another. If there is a client-server connection involved like in a DB-App server relationship, the IP or hostname needs to be configured in the application VM, otherwise, it can't access the DB. Users and software configs need to be set as well as OS security settings need to be changed.

Before a valid multimachine blueprint design might be started, it is important to understand all...