First look at the Python SDK for USC Manager
Map Service Dependencies
On the 18th of March, VMware staff members from the Melbourne office will be taking part in the Run for the Kids charity race. By particiapting in the either the 5 or 15 KM events, we will be raising much needed funds for the Good Friday Appeal. The Good Friday Appeal is an annual charity drive to raise money for the Royal Children’s Hospital in Melbourne. Last year it managed to raise $17,605,665.
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
I recently updated my Ubuntu install from 17.04 to 17.10, which meant the kernel was updated to 4.13. As a result, I was no longer able to run VMs with VMware Workstation. I found some posts regarding the error and that it was due to a change in the way the Linux kernel handles paging. To resolve the issue I needed to replace the vmmon modules. I didn’;t take down the entire error message, but this post references the same error.
Today I came across the need to use PowerCLI on a computer without internet access. Thankfully I found this blog post detailing the steps that I needed to perform, however not all was rainbows and unicorns. I quickly ran aground when attempting to import the modules. After a bit of research, I learnt that Microsoft had changed the module directory structure in PowerShell v5. This new structure is not compatible with previous versions.
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’.