I wrote recently about testing AWS auto scaling policies. Before you can test auto scaling policies however, you need an auto scaling configuration to test! This post will look at building a simple auto scaling configuration, to provide a scale-able and highly available web site.  Before starting on the configuration, there are a bunch of services that need to be in place for the auto scaling group to function. These include:

  • A VPC to launch our instances into
  • A ELB to attach our auto-scaled instances to
  • An AMI to launch. Either a custom AMI or one provided by Amazon, depending on the use case
  • CloudWatch – used to monitor the performance of the AS group, and to trigger auto-scaling activities

The autoscaling configuration itself is composed of two parts. Firstly there is the launch configuration, which is the config template that the Auto Scaling group will use to launch instances. Then there is the Auto Scaling group itself, which defines how many instances you want to run and how the group will scale under certain conditions: [click to continue…]

{ 0 comments }

After creating a new auto scaling group recently, I was looking for an easy way to test the auto scaling policies I’d associated with the group. This is just quick post to cover what I did as a quick way to test auto scaling policies. I configured my group to scale up when it breached a 50% usage threshold, then scale down again once usage dropped below that value. One way to test it was working as desired is to use the Stress tool, which can be installed on Linux instances. Note that I was using the micro instances available in the free tier to ensure not to incur any unnecessary costs, whilst testing. Stress can be installed on Linux instances by running:

# yum install stress -y

Once installed, CPU load can be generated using Stress by running: [click to continue…]

{ 0 comments }

Creating a new VPC on AWS – Walkthrough

August 25, 2017

I’ve recently been working towards AWS certification – and took the first step in passing the AWS Certified Solutions Architect Associate exam a few weeks ago. After a short break I now aim to take the Professional cert later in the year – as such I’ll be putting some articles together covering some of the […]

0 comments Read the full article →

VCAP6-DCV Design Journey – Objective 2.2 – Map Service Dependencies

August 17, 2017

This post is intended to cover the VCAP design objective around mapping service dependencies. At the time of writing, the required ‘Skills and Abilities’ listed by VMware for this topic are: Evaluate dependencies for infrastructure and application services that will be included in a vSphere design Create Entity Relationship Diagrams that map service relationships and […]

0 comments Read the full article →

VCAP6-DCV Design Journey – Objective 2.1 – Map Business Requirements to a vSphere 6.x Logical Design

August 14, 2017

This post is intended to cover the VCAP design objective around mapping business requires to a vSphere 6.x logical design. At the time of writing, the required ‘Skills and Abilities’ listed by VMware for this topic are: Analyze requirements for functional and non-functional elements Build non-functional requirements into a specific logical design Translate stated business […]

0 comments Read the full article →

Using Vagrant to Deploy Multiple VMs on vSphere

July 28, 2017

I wrote an article recently looking at how to deploy virtual machines on vSphere using Vagrant. On that post I covered how to deploy a single Photon OS virtual machine using Vagrant. Here, I wanted to do a quick post on how to deploy multiple VMs from a single Vagrant file. One way to do […]

0 comments Read the full article →

VCAP6-DCV Design Journey – Objective 1.3 – Determine Risks, Requirements, Constraints and Assumptions

June 28, 2017

This post is intended to address the VCAP design objective around determining risks, requirements, constraints and assumptions. At the time of writing, the required ‘Skills and Abilities’ listed by VMware for this topic are: Differentiate between the concepts of risks, requirements, constraints and assumptions Given a statement, determine whether it is a risk, requirement, constraint […]

0 comments Read the full article →

Vagrant, vSphere and Photon OS

June 26, 2017

I wanted to have a look at using Vagrant with vSphere to help provision a dev environment, mainly for an excuse to have a look at Vagrant. This post will cover the steps I used to get Vagrant up and running, and able to provision a VM on an ESXi host, via vCenter. To start […]

0 comments Read the full article →

VCAP6-DCV Design Journey – Objective 1.2 – Gather and Analyze Application Requirements

June 14, 2017

This post is intended to address the VCAP design objective around gathering and analyzing application requirements. At the time of writing, the required ‘Skills and Abilities’ listed by VMware for this topic are: Gather and analyze application requirements for a given scenario Determine the requirements for a set of applications that will be included in […]

0 comments Read the full article →

VCAP6-DCV Design Journey – Objective 1.1 – Gather and analyze business requirements

June 9, 2017

This post is intended to address the VCAP design objective around gathering and analyzing business requirements. At the time of writing, the required ‘Skills and Abilities’ listed by VMware for this topic are: Associate a stakeholder with the information that needs to be collected. Utilize inventory and assessment data from a current environment to define […]

0 comments Read the full article →