Build Performance Requirements into the Logical Design

Build Manageability Requirements into the Logical Design

RabbitMQ causes join cluster process to hang when adding new vRA nodes.

Build Availability Requirements into the Logical Design

Map Service Dependencies

Determine Use Cases for Multi-Tenancy

Map Business Requirements to the Logical Design

Differentiate requirements, risks, constraints and assumptions

Gather and analyze use cases

As part of the VCAP7-CMA Design study guide, I have put together a use case which will be used to provide context when addressing each of the exam objectives. The study guide can be found Here Use Case Mega-Awesome Transit have identified a need to increase the reliability and reduce the complexity when updating their dispatching system during update periods. Currently updates to the dispatch system cause interruptions for up to 12 hours.

Gather and analyze business requirements

vRA uses Custom properties to help define parameters and the behaviour of requests. In the previous post CHEF: vRA Integration, Property Groups and Blueprints we used custom properties to define the properties of our Chef deployment. In this post, we look at using custom properties to assign the node environment. The Chef default client deployment workflows form the basis of the examples. A brief on custom properties We use custom properties to manipulate many aspects of workflow execution.

The Chef plugin provides some workflows to help with getting the vRA integration up and running with minimal effort. I would suggest treating them as samples to build functionality on top of. There are some limitations from the default state which might not provide sufficient flexibility for production usage. Setting up the Property Groups: Launch the vRO Client and navigate to the Chef workflow ‘Create Property Group for Chef EBS Workflows’.