VMware Cloud on AWS

It was announced during October 2016, and later at the AWS re:Invent 2016 stage in November, that VMware and Amazon Web Services (AWS) would join a partnership. Thus providing VMware Cloud on AWS.

Brief History of VMware Cloud/vCloud Air

During the previous 10 years a lot of companies have been migrating/transitioning into public cloud. This change in technology resulted in VMware on-premise solution to lose much needed revenue. Then VMware announced in 2013 that they would start vCloud Air, but refreshing the hardware turned out to be costly.  Earlier this year vCloud Air would close its public cloud offerings. Which to me makes sense, because VMware has been joining parterships with other public cloud providers to stay in the market.

Fast forward to August during VMworld 2017. It was announced that VMware after a year of beta testing, and countless feedback from the vast VMware community. Would publicly start providing VMware Cloud on AWS in the US West (Oregon) region.  UPDATE: US EAST (Virgina) region is now available.

Networking

VMware has also been working on NSX networking virtual layer. VMware NSX is a virtual networking and security software product family created from VMware’s vCloud Networking and Security (vCNS) and Nicira Network Virtualization Platform (NVP) intellectual property. VMware states that you do not need to have NSX enabled on your on-premise infrastructure to leverage NSX inside VMC (VMware Cloud). That is great news for organizations who haven’t played with NSX.

The ESXi hosts are connected to AWS VPC created by VMware or added to an existing VPC. This allows the bandwidth to be maintained by AWS Elastic Networking Adapter (ENA). ENA can support a throughput up to 25 Gbps, making it fully managed by you.

The downside of using VMware inside AWS is that you currently can’t create Elastic IP (EIP), but EIPs are reserved for the NSX Edge Gateway. You are also not able to separate the load between availability zones or link multiple AWS accounts.

VMware Current Hardware/Compute on AWS

VMware ESXi host run on a bare-metal server, but still utilize the Amazon VPC. This could be the key reason why VMware is taking a while to role out to the other regions. VMware’s deal with AWS starts with you off with a bare-metal server that work with the AWS VPC. VMware Cloud on AWS uses SDDC (Software-Defined Data Center). This consist of 36 cores, 72 hyper-threads, 512GB RAM, NVMe attached flash storage (3.6 TB cache plus 10.7 TB raw capacity tier).
Region:US West (Oregon) and US East (Virgina)
On-Demand (hourly) 1 Year Reserved 3 Year Reserved
List Price ($ per host) $8.3681/hour $51,987/year $109,366/3 year
Effective Hourly* $8.3681/hour $5.9346/hour $4.1616/hour
Savings Over On-Demand 30% 50%

From

Support and Billing

AWS support doesn’t support VMware Cloud on AWS, because VMware controls the selling, delivery, billing, and support. The only way you can be charged by AWS is by using AWS services, and therefore meaning you do not need to pay for AWS support.

Payment can be by credit card or by an existing VMware.

VM Management

The VMware Cloud on AWS console allows you to deploy where you want AWS. Inside the console you will see the SDDC, organization, API OAuth tokens. Within the SDDC you can see the summary, network, connection info, and live support.

Connection info has the vSphere login info and connection string.
Network tab has an interactive design workflow that will create a tickets to VMware Support.
You can also use vCenter to manage both on-premise and VMC on AWS.
Here is some screenshots of the VMware Cloud on AWS Console, but I do suggest that you try out the free demo.

 

DEMO

You can now demo it yourself here 

 

Advertisements

PowerShell Script: Bulk install MSP or MSI without zipped folder

This is another version of Installing MSP or MSI files, but with the manual unzip. You can read about how to do it with the zipped folders here.

write-host "Install bulk MSI"
## Location of the msi files
## PARAM ##
$path="C:\PROGRAM\Experiance Packs\"


## DO NOT EDIT ##
cd $path
$iisreset = Read-Host 'Do you want to stop IIS: Yes or No'

## IIS STOP ##
If (($iisreset -eq "yes") -or ($iisreset -eq "Yes") -or ($iisreset -eq "Y") -or ($iisreset -eq "y"))
{
	invoke-command -scriptblock {iisreset /stop}
}
Elseif (($iisreset -eq "no") -or ($iisreset -eq "No") -or ($iisreset -eq "N") -or ($iisreset -eq "n"))
{
	 write-host "IIS wasn't stopped, but IIS restarts automatically at 24:00"
}

## Installs MSI from Unzipped ##
$files = Get-ChildItem -Path $path -Recurse -File -Filter '*.ms*' 
foreach ($msifile in $files)
    {
        write-host "Finished msi "$msifile
        $arguments= "/qn /norestart"
        Start-Process  -file  $msifile.FullName -arg $arguments -passthru | wait-process
    }
    write-host "Finished applying all msi's"

## IIS Start##
If (($iisreset -eq "yes") -or ($iisreset -eq "Yes") -or ($iisreset -eq "Y") -or ($iisreset -eq "y"))
{
	invoke-command -scriptblock {iisreset /start}
}
Elseif (($iisreset -eq "no") -or ($iisreset -eq "No") -or ($iisreset -eq "N") -or ($iisreset -eq "n"))
{ 
}