|
|
|
Compute |
|
|
|
VMware Cloud Foundation bundles vSphere which includes the ESXi virtualization platform for creating and running virtual machines and virtual appliances
https://docs.vmware.com/en/VMware-Cloud-Foundation/3.0/rn/VMware-Cloud-Foundation-30-Release-Notes.html
|
Virtual servers are called EC2 instances
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
Azure Stack allows for the deployment of virtual servers called virtual machines
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-compute-overview
|
|
VM Type - General Purpose
Details
|
You can configure the virtual machine hardware to take advantage of the underlying hosts hardware
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html
|
The SBE1 EC2 instance is the general purpose offering
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
General purpose VMs are Basic A, Standard A, Av2-series, D-series, DS-series, Dv2-series, DSv2-series
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-sizes#general-purpose
|
|
VM Type - Compute Optimized
Details
|
You can configure the virtual machine hardware to take advantage of the underlying hosts hardware. For compute optimized instances, you would increase the CPU resources
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html
|
The SBE-C EC2 instance is the compute optimized offering
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
Computed optimized VMs are F-series, Fs-series, Fsv2-series
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-sizes#compute-optimized
|
|
VM Type - Memory Optimized
Details
|
You can configure the virtual machine hardware to take advantage of the underlying hosts hardware. For memory optimized instances, you would increase the memory resources
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html
|
There is no memory optimized offering
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
Memory optimized VMs are D-series, DS-series, Dv2-series, DSv2-series
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-sizes#memory-optimized
|
|
VM Type - Accelerated (GPU)
Details
|
You can configure the virtual machine hardware to take advantage of the underlying hosts GPU hardware
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-74A657D9-52F7-4F92-AB86-9039A90A028D.html
|
The SBE-G EC2 instance is the accelerated GPU offering
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
There are no accelerated VM offerings with a GPU
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-sizes
|
|
|
There is no built-in way to access this functionality. (see details)
There is no built-in way to access this functionality. You may be able to get it using the vSphere SDK for Perl within the VM to access the vSphere API but this requires the customer to build the functionality
|
You get access to a subset of metadata typically available to EC2 instances through an internal URL
https://docs.aws.amazon.com/snowball/latest/developer-guide/edge-compute-instance-metadata.html
|
While Azure has an Instance Metadata service, this functionality is not currently supported on Azure Stack
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-vm-considerations
|
|
Rapid Provisioning
Details
|
You can easily deploy VMs using a wizard, template, or cloning another VM
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-39D19B2B-A11C-42AE-AC80-DDA8682AB42C.html
|
You can specify the job and resources and Amazon will configure the device for you and ship it out to you
https://docs.aws.amazon.com/snowball/latest/developer-guide/how-it-works.html
|
You can easily and quickly deploy virtual machines using the Azure Stack console
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-compute-overview
|
|
Resize existing VM
Details
|
You can easily resize an existing VM by changing its virtual hardware after creation such as CPU and memory
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html
|
Typically resize an instance using CLI modify-instance-attribute on instanceType attribute but Snowball Edge only allows you to modify userdata
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2-endpoint.html#cli-support-ec2-edge
|
This functionality is supported in Azure Stack as well
https://azure.microsoft.com/en-us/blog/resize-virtual-machines/
|
|
Resource Management
Details
|
Resources can be managed from either the vSphere Web Client or the vSphere Client
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-588861BB-3A62-4A01-82FD-F9FB42763242.html
|
Resources such as EC2 instances cannot be managed through the console after the device is created and must instead be managed through the CLI/API adding a level of complexity
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
The Azure Resource Manager provides a platform to manage all resources deployed within the Azure Stack
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-overview#how-is-azure-stack-managed
|
|
|
There is no vSphere functionality to easily scale up or down VMs from the console
|
A cluster of 5-10 Snowball Edges can be created to offer increased durability and locally scale up or down storage on demand
https://docs.aws.amazon.com/snowball/latest/developer-guide/UsingCluster.html
|
Azure Stack includes scale sets which allow for automatic scaling of instances based on load
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
|
|
|
You can clone a virtual machine to a template which can then be used to deploy other virtual machines later
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-FE6DE4DF-FAD0-4BB0-A1FD-AFE9A40F4BFE_copy.html
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
You can create and publish a custom marketplace item
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-create-and-publish-marketplace-item
|
|
|
You can import and export virtual machines in the OVF and OVA formats
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-AFEDC48B-C96F-4088-9C1F-4F0A30E965DE.html
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
You can import and export a disk used by a VM. In addition, you may be able to import/export a VM state but this is not confirmed (see details)
You can import and export a disk used by a VM Link to uploading Link to downloading. In addition, you may be able to import/export a VM state but this is not confirmed Link to export state Link to import state
|
|
VM live migration
Details
|
You can perform a live migration of a virtual machine without affecting availability, called a hot migration, using vMotion
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-FE2B516E-7366-4978-B75C-64BF0AC676EB.html
|
AWS does not support live VM migration and as such we shouldnt expect Snowball Edge to do this
AWS does not support live VM migration and as such we shouldnt expect Snowball Edge to do this
|
Azure Stack supports live VM migration as a preventative measure to protect resources from failing hardware
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-network
|
|
VM to host affinity
Details
|
You can create VM to host affinity rules within a DRS cluster
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-2FB90EF5-7733-4095-8B66-F10D6C57B820.html
|
When deploying a cluster, you can select which nodes an instance runs on
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
This capability is not supported by Azure Stack
|
|
VM to host anti-affinity
Details
|
You can create VM to host anti-affinity rules within a DRS cluster
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-2FB90EF5-7733-4095-8B66-F10D6C57B820.html
|
When deploying a cluster, you can select which nodes an instance runs on thus also choosing which nodes it does not run on
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2.html
|
Azure Stack provides Availability Sets which replicate the VM across different hosts for high availability thus enforcing host anti-affinity
https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-vm-considerations
|
|
|
|
Networking |
|
|
Cloud virtual networking
Details
|
VMware Cloud Foundation bundles NSX Data Center for vSphere which provides a platform programmatically managing software-defined virtual networks
https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-10944155-28FF-46AA-AF56-7357E2F20AF4.html
|
The EC2 instances can have virtual network interfaces attached to them which allows them to communicate with each other and outside devices
https://docs.aws.amazon.com/snowball/latest/developer-guide/network-config-ec2-edge.html
|
The Network Resource Provider delivers a series of Software Defined Networking (SDN) and Network Function Virtualization (NFV) features
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-overview
|
|
Cross-premises connectivity
Details
|
The VCF platform is integrated into the customer datacenter and provides cross-premises connectivity to other customer networks
https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.3/com.vmware.nsx.install.doc/GUID-2482B032-F420-432F-A6D0-6CD91506BFCC.html
|
The Snowball Edge connects into the datacenter and allows for transfer of data between the datacenter and AWS albeit in a slow snail-mail fashion
https://docs.aws.amazon.com/snowball/latest/developer-guide/whatisedge.html
|
Cross-premises connectivity can be established in Azure Stacks which are deployed in the connected mode
https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-vpn-gateway-about-vpn-gateways
|
|
DNS hostname resolution
Details
|
You can install NSX Edge as an Edge Services Gateway (ESG) between networks which will then allow you to configure external DNS servers. (see details)
You can install NSX Edge as an Edge Services Gateway (ESG) between networks which will then allow you to configure external DNS servers. The ESG ill forward requests from internal clients to the DNS servers for name resolution and will cache lookups DNS Configuration
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
Azure Stack supports DNS hostname resolution
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-dns
|
|
DNS zone management
Details
|
No mention in documentation. Functionality would need to be built up by the end-user and then VMware components can take advantage of it
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
Azure Stack supports the creation and management of DNS zones and records using both the console and the API
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-dns
|
|
|
You can statically set an VMs IP address from vSphere as well as specify a network protocol which is a pool of IPv4 and IPv6 addresses that vCenter will assign to virtual machines
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-D24DBAA0-68BD-49B9-9744-C06AE754972A.html
|
You can delete the virtual network interface attached to an EC2 instance and then create a new virtual network interface for that EC2 instance with a new static IP address
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2-edge-client.html
|
You can reassign an IP by modifying the virtual network interface or by deleting it and creating a new one (Experience)
|
|
|
You can install NSX Edge as an Edge Services Gateway (ESG) and take advantage of the logical load balancer
https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-152982CF-108F-47A6-B86A-0F0F6A56D628.html
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
The Azure Stack provides load balancing functionality
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-network-differences
|
|
Network Interfaces
Details
|
Virtual machines can have a variety of different network adapters added and configured
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-AF9E24A8-2CFA-447B-AC83-35D563119667.html
|
The device has a set of external network interfaces for connectivity into the customer datacenter (see details)
The device has a set of external network interfaces for connectivity into the customer datacenter link to getting started as well as the ability to create limited virtual network interfaces for EC2 instances link to network configuration
|
You can create and modify network interfaces attached to virtual machines (Experience)
|
|
Outbound Network Connectivity
Details
|
You can connect virtual machines to the physical network
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-F3F5E069-9A75-467A-93FC-800F37104A7E.html
|
The device has a set of external network interfaces for connectivity into the customer datacenter (see details)
The device has a set of external network interfaces for connectivity into the customer datacenter link to getting started as well as the ability to create limited virtual network interfaces for EC2 instances link to network config. Once connected into the datacenter, the customer can further expose the device to either his/her own network as well as larger networks like the Internet
|
The Azure Stack is integrated into the customers datacenter and has outbound network connectivity to the customers border
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-datacenter-integration
|
|
Public IP Address
Details
|
You can connect virtual machines to the physical network
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-F3F5E069-9A75-467A-93FC-800F37104A7E.html
|
Can attach a virtual network interface to your EC2 instance and specify a public IP address for use
https://docs.aws.amazon.com/snowball/latest/developer-guide/network-config-ec2-edge.html
|
Azure Stack supports IPv4 public addresses
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-network-differences
|
|
|
There is a specific network adapter type (SR-IOV passthrough) designed to enable and support SR-IOV networking
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-AF9E24A8-2CFA-447B-AC83-35D563119667.html
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
No mention of this capability for Azure Stack
|
|
VM Security Groups
Details
|
Virtual Machines can be added to a security group which has a specific network security policy applied to it
https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-16B3134E-DDF1-445A-8646-BB0E98C3C9B5.html
|
Security groups exist and can be configured for EC2 instances similar to the way they work in AWS with limitations
https://docs.aws.amazon.com/snowball/latest/developer-guide/edge-security-groups.html
|
VM Security groups are provided as network security groups
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-overview
|
|
Virtual Network Peering
Details
|
You can set up cross-vCenter deployments as well as implement VPNs to access corporate and other cloud networks securely
https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-FB4BEB23-6A87-4291-A90B-826F69C1F7B6.html
|
Virtual Private Clouds (VPCs) are not supported in Snowball Edge and thus you cannot make virtual networks to peer
https://docs.aws.amazon.com/snowball/latest/developer-guide/edge-security-groups.html
|
Not supported as of 20190124
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-network-differences
|
|
|
|
Storage |
|
|
|
No mention in the documentation
|
The Snowball Edge supports S3 (object storage) as its primary purpose is downloading customer data from a remote datacenter which can then later be transferred to S3 in AWS
https://docs.aws.amazon.com/snowball/latest/developer-guide/whatisedge.html
|
Azure Stack provides blob storage for object storage
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-storage-overview
|
|
|
vSphere provides a variety of different storage options and functionalities
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-F602EB17-8D24-400A-9B05-196CEA66464F.html
|
Block storage must exist as the Snowball Edge is capable of hosting EC2 instances but end-users have no access to block storage and cannot attach volumes themselves to EC2 instances
https://docs.aws.amazon.com/snowball/latest/developer-guide/using-ec2-endpoint.html#unsupported-features-ec2-adapter
|
Azure Stack supports page blobs which are the equivalent of block storage
Link to storage overview, Link to services
|
|
Shared file storage
Details
|
VMWare provides NFS but not SMB storage solutions
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-E3B77DE4-7525-47D3-B2D7-BC71CCD7992D.html
|
Once connected to the datacenter, the S3 Adapter for Snowball or NFS mount point can be used to upload data from the datacenter into the Snowball Edge
https://docs.aws.amazon.com/snowball/latest/developer-guide/how-it-works.html
|
Azure Stack does not provide a SMB or NFS solution
|
|
|
VCF provides backup and restore capability of components
https://docs.vmware.com/en/VMware-Cloud-Foundation/2.3/com.vmware.vcf.admin.doc_23/GUID-FD14EA32-3FCC-48B8-A42A-FD276DE43925.html
|
By its nature, the device offers data backup for data stored within a datacenter albeit in a slower process
https://docs.aws.amazon.com/snowball/latest/developer-guide/whatisedge.html
|
Microsoft Azure Backup Server can be used to back up data within Azure Stack (see details)
Microsoft Azure Backup Server can be used to back up data within Azure Stack Link to backup. In addition, data store on Azure Stack is replicated using the locally redundant storage methodology Link to storage cheat sheet
|
|
Local Data Protection
Details
|
Virtual Volumes support replication capabilities for disaster recovery
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-6346A936-5084-4F38-ACB5-B5EC70AB8269.html
|
The Snowball Edge employs defense-in-depth for data protection including a ruggedized tamper-reistant enclosure, 256-bit encrpytion, and a TPM
https://docs.aws.amazon.com/snowball/latest/developer-guide/security-considerations.html
|
Local data is encrypted and replicated across nodes in case of hardware failure
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-acs-differences#cheat-sheet-storage-differences
|
|
Remote Replication
Details
|
Virtual Volumes support replication capabilities for disaster recovery
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-6346A936-5084-4F38-ACB5-B5EC70AB8269.html
|
By its nature, the device offers remote replication for data stored within a datacenter albeit in a slower process
https://docs.aws.amazon.com/snowball/latest/developer-guide/whatisedge.html
|
The only replication option available is locally redundant storage
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-acs-differences#cheat-sheet-storage-differences
|
|
|
Virtual volumes provide snapshot capability to preserve the state and data of a virtual machine at a given point in time
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-B3A59A35-8CDF-4DD6-A069-29927E65684C.html
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
Snapshots are supported for blobs (limited to 1000 per blob) but not for page blobs
https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-acs-differences
|
|
Storage Architecture
Details
|
VMware provides for a very flexible storage architechture
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-F602EB17-8D24-400A-9B05-196CEA66464F.html
|
Each Snowball Edge node provides betwee 42TB and 80TB (see details)
Each Snowball Edge node provides betwee 42TB and 80TB (depending on type) of usable space with an additional 7.68TB of dedicated SSD storage for instances (compute). Snowball Edges can be clustered for additional storage space and durability Link to cluster info Link to specifications
|
Azure Stack provides for either a hybrid or all-flash storage architechture
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-storage-infrastructure-overview
|
|
|
You can configure the vSAN cluster (shared storage pool) to be either hybrid or all-flash (see details)
You can configure the vSAN cluster (shared storage pool) to be either hybrid where magnetic disks are used for capacity or all-flash where flash disks are used for capacity and then specify clusters from which hosts can use storage Link to vSAN documentation
|
No mention in the developer guide
https://docs.aws.amazon.com/snowball/latest/developer-guide/
|
Azure Stack supports standard and premium storage
https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-acs-differences
|
|
Storage Scalability
Details
|
You can expand an existing vSAN cluster by adding hosts or devices to existing hosts without disrupting ongoing operations
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.virtualsan.doc/GUID-51AEE927-91A9-4B04-BF3F-DD7956D841A8.html
|
Multiple Snowball Edges can be clustered to increase data durability as well as locally grow and shrink storage on demand
https://docs.aws.amazon.com/snowball/latest/developer-guide/whatisedge.html
|
Azure Stack operators can increase the overall capacity of an existing scale unit by adding additional scale unit nodes
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-add-scale-node
|