gnawux

You may login to your console, and the overview page 'https://console.hyper.sh/overview' shows all what you have.

Currently, hyper.sh supports credit card backed by stripe.com

It's really a popular name...

Another thing to remind you is, E5-2630v4 was released in Q1 2016, which is not an old CPU

http://ark.intel.com/products/92981/Intel-Xeon-Processor-E5-...

In Los Angels

Based on AWS v4 does not means aws v4 is employed, on the contrary, the docs explains the signature of hyper, which uses different literatures.

At last, you can try it. Then you will found it is totally different from AWS.

You can try the api address us-west-1.hyper.sh

Not on aws at all.

The hyper.sh API address is us-west-1.hyper.sh, which looks like the AWS style, however, it is not an AWS address and it is located in an independent IDC around Los Angels.

Does the CPU model matter?

VMware has a similar project. The HyperContainer project is opensourced in May last year, same as Intel clear linux, and is prior to the VMware project.

The most significant improvement comes from the BootFromTemplate, which improves speed and saves memory. And the boot sequence and guest kernel have been optimized.

With HyperContainer, we make the performance/overhead of virtualized container similar to linux container --- 130ms launch time, and sharing the read-only part of memory (kernel and init). As a result, we can use it as a more secure container.

yep, the containers are encapsulated by hyper container

What's the policy mean here? Does it include some actions, such as do migration if a zone is out of service?

yes, we do not support overlayfs yet, but will. overlayfs is the future of unionfs, and aufs is the current. :)

you can try it now ;) cheers

A pod on a kernel/initrd, contains one or more docker images in different mount namespaces. The "containers" in pod share network and ipc namespace each other.

Hi,

It does not run a full guest OS on the hypervisor, instead, initrd itself launches a group of docker images, aka Pod on it.

Similar by some means, from my point, visualops.io is closer to AWS VPC resources.