vRealize Automation 7.0 was released late last year. It introduced several new features and one of the major ones was converged blueprint model. The converged blueprint model provides a single place to design and manage any kind of blueprint. You have can create blueprints for consumption by different IT or make them available to your DevOps teams. It can be a simple OS image to be consumed by IT, a single blueprint with a software component on it, a multi machine pattern for developers to consume, or an application.
There are many ways to create blueprints and many types of blueprints that can be created, and while the documentation does a good job of explaining what can and can’t be done, there is no better way to show these capabilities than to provide examples.
We are going to provide fully functional blueprints, that will demonstrate provisioning different types of OSs on different type of endpoints and different types of software components. The samples will also include built in properties to enable customization and reuse of these blueprints.
We are very excited about this initiative and have already released 4 samples. We are going to publish more in the coming weeks, and expect to update the existing ones once we get some of the initial feedback.
The full list of the blueprints that VMware provides is always available at the VMware Solution Exchange. Here is a shortcut to the VMware created blueprints. As you can see below right now there are 4 posted but by the time you will read this post there may already be more.
As I wrote above there are currently 4 blueprint available.
Each sample has its own documentation and downloads to make things very clear and easy to consume.
- Microsoft SQL Server sample deployment on a single vSphere VM. This can be used as is out of the box or as a basis for your standard MSSQL in house deployments.
Note: Microsoft SQL Server license and binaries are required
2. Microsoft Sharepoint Server sample deployment on a single vSphere VM. This can be used as is out of the box or as a basis for your standard MSSQL in house deployments.
3. LAMP Stack Pattern that includes all the components in a LAMP stack ready for consumption by a developer.
4. LAM Java Stack pattern and sample application. This blueprint has two variants. One is a pattern that can be consumed by a developer and the other is an example that uses the pattern and adds a very simple app by installing a WAR on Tomcat and configures a specific schema on the DB. This provides a more comprehensive example of how to actually use the pattern.
Hope these are helpful to you, and hope to hear some feedback about what we already did and what blueprint samples you would like to see next.