|
|
|
Compute |
|
|
|
Virtual servers are called cloud instances (equivalent to EC2 instances in AWS)
https://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#user-guide/understanding_instances.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
|
Virtual machine hardware can be configured to take full advantage of the underlying hosts hardware. A collection of instance types can be customized in terms of vCPUs, memory, and disk.
https://libvirt.org/formatdomain.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
|
Compute-optimized instance types can be customized by modifying the instance type
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/euca-modify-instance-type.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
|
Memory-optimized instance types can be customized by modifying the instance type
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/euca-modify-instance-type.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
|
GPU instance types can be customized through advanced configuration only. No official documentation.
https://libvirt.org/formatdomain.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
|
|
|
Metadata URL, featuring EC2-compatible information and thus compatible with cloud-init, is reachable from instances.
https://docs.eucalyptus.cloud/eucalyptus/4.4.5/image-guide/ig_task_prepare_image.html
|
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
|
System components enable fast provisioning, particularly of EBS-backed instances.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/euca-run-instances.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
|
EBS-backed instances can be resized after stopping by modifying InstanceType attribute via ModifyInstanceAttribute request (in CLI or Console).
|
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 Console or CLI/API
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#admin-guide/manage_resources.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
|
|
|
AWS AutoScaling APIs are supported, with performance-based triggers for up- and down-scaling.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#admin-guide/manage_resources_as.html
|
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
|
|
|
Images (akin to AMIs and AKIs) can be created and shared with other cloud users. Existing instances can be saved into an image.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/image_section.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
|
|
|
Instances can be imported using raw disk or VHD formats. Exports done manually at hypervisor level. No API support for the operation exists.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/euca-import-instance.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
|
VMs can be live-migrated using CLI / API. In the event of a host failure instances to not automatically restart.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/euserv-migrate-instances.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
|
Not supported. Can only be achieved by backend administration using instance migration.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#admin-guide/manage_nodes.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
|
Not supported. Can only be achieved by backend administration using instance migration.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#admin-guide/manage_nodes.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
|
Overlays a virtual network on top of your existing network. Supports EDGE (EC2 Classic) and VPCMIDO (AWS VPC) modes.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#install-guide/configure_network_modes.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
|
Support for AWS VPN Gateway is available but only when using VPCMIDO network mode.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/vpc_euca2ools_intro.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
|
DNS names for VM instances is supported automatically
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/setting_up_dns.html
|
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 the documentation
|
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
|
|
|
Elastic IP and Elastic Network Interface functionality enables flexible IP address assignment.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/console_manage_eips.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)
|
|
|
Elastic Load Balancer is an included service.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#troubleshooting-guide/ts_elb.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
|
Elastic Network Interface functionality allows attaching and detaching of virtual NICs to instances
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#user-guide/vpc_concepts_elastic_net_interfaces_eni.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
|
Can be configured to connect to external networks with both EDGE (EC2 Classic) and VPCMIDO (Amazon VPC) networking modes.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#ops-guide/ops_networking.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
|
Public IP addresses can be assigned to instances either automatically or from a pool of Elastic IP addresses.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#ops-guide/ops_networking.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
|
|
|
Can be customized to use SR-IOV for instance networking by advanced configuration only. No official documentation.
https://wiki.libvirt.org/page/Networking
|
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
|
Instances can be added to a security group which has a specific network security policy applied to it.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#user-guide/networking_security.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
|
Ability to create a peering connection between two VPCs is supported.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#euca2ools-guide/euca-create-vpc-peering-connection.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 |
|
|
|
Supports S3-compatible object storage using its Object Storage Gateway (OSG)
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#install-guide/config_object_storage.html
|
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
|
|
|
Elastic Block Storage (EBS) provides block-level storage volumes that you can attach to instances.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/using_block_storage.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
|
Shared file storage is not supported.
|
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
|
|
|
Procedures for backing up and restoring everything except root disks of instance-store (ephemeral) instances are documented.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#ops-guide/ops_recovery.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
|
Relies on replication features of underlying software and hardware (RAID and Ceph) for local data protection from hardware failures.
|
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
|
No special functionality for automatic remote replication are provided, but backup process can include transfer of backed up data offsite for disaster recovery.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#admin-guide/backup_euca.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
|
|
|
EBS snapshots are supported in both Web console and via CLI/API.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/console_manage_snapshots.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
|
Deployed as customer configurable two-level storage system. Support for HCI not documented.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#install-guide/config_storage.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
|
|
|
Supports only a single storage class for both block and object storage.
|
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
|
The Storage Controller (SC) and Object Storage Gateway (OSG) are molular and enable storage capacity to be dynamically allocated independent of the system.
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#install-guide/config_storage.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
|