diff --git a/README.md b/README.md index 585d10e..99b9884 100644 --- a/README.md +++ b/README.md @@ -28,3 +28,4 @@ git push origin master # Troubleshoot `Invalid format`: Try to use double quotes to wrap the string which contained some special char. + diff --git a/blog/source/close_hyper_sh.md b/blog/source/close_hyper_sh.md new file mode 100644 index 0000000..4aa5ba4 --- /dev/null +++ b/blog/source/close_hyper_sh.md @@ -0,0 +1,22 @@ +title: "Farewell from Hyper Crew" +date: 2019-01-16 13:00:00 +0800 +author: Hyper Crew +tags: + - Hyper +preview: As of Jan 16, 2019, we have officially shut down the Hyper.sh platform. + +--- + +As of Jan 16, 2019, we have officially shut down the Hyper.sh platform. + +Over three years ago, we set out to create an open secure container-native platform. We believed that containers represented a sea change in how software would be developed, deployed, and maintained. + +Along the way, we created one of the first container-native cloud offerings, the [Hyper.sh](http://hyper.sh/) platform, which utilized our open source technology, called runV, which last year was merged with Intel’s Clear Containers project to become [Kata Containers](http://www.katacontainers.io/). We’re proud of the platform we built, and the influence we have had on the overall container industry. We are even more grateful to you, our customers, who have deployed hundreds of thousands of containers and built out new businesses on our platform. + +The [Hyper.sh](http://hyper.sh/) platform, while trailblazing, is not where Hyper’s future efforts lie. Moving forward, Hyper is focusing all our attention and efforts towards the upstream Kata Containers project. + +Thank you for your business and support of our platform. It has been a privilege to serve you. + +Sincerely, + +The Hyper Crew diff --git a/blog/source/introducing-clusterless-kubernetes-job.md b/blog/source/introducing-clusterless-kubernetes-job.md new file mode 100755 index 0000000..1f133e2 --- /dev/null +++ b/blog/source/introducing-clusterless-kubernetes-job.md @@ -0,0 +1,93 @@ +title: Introduce Clusterless Kubernetes Job and Large Pod Size +date: 2018-07-13 9:48:12 +author: Peng Zhao +preview: Today, we are excited to announce to support Kuberentes Job feature in Pi. Also, we add more large pod size for bigger workload requirements. +--- + +> NOTE: Please download the latest CLI build. See [here](https://docs.hyper.sh/pi/Quickstart/install_cli.html) for details. + +# Clusterless Kubernetes Job + +Today we are happy to announce the release of [Kubernetes Job](https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/) support in [Pi](https://hyper.sh/pi). + +The same as in Kubernetes, a job creates one or more pods and ensures that a specified number of them successfully terminate. As pods successfully complete, the job tracks the successful completions. When a specified number of successful completions is reached, the job itself is complete. + +With Pi however, you can run any job without the need of Kubernetes cluster. Also you only pay (per second!) when the job is running, just as with any other resource on __Pi__. + +### Create a job which computes π to 2000 places and prints it out: + +``` +$ pi create job pi --image=perl --restart=Never --backoff-limit=4 -- perl -Mbignum=bpi -wle "print bpi(2000)" +job "pi" created +``` + +Remember, although the commands looks just like `kubectl`, there is no Kubernetes cluster nor node in Pi. Simply use our CLI to launch jobs. + +### Check on the status of the job using this command: + +```shell +$ pi describe jobs/pi +Name: pi +Namespace: default +Selector: controller-uid=b1db589a-2c8d-11e6-b324-0209dc45a495 +Labels: controller-uid=b1db589a-2c8d-11e6-b324-0209dc45a495 + job-name=pi +Annotations: +Parallelism: 1 +Completions: 1 +Start Time: Tue, 03 Jul 2018 15:02:53 +0800 +Pods Statuses: 0 Running / 1 Succeeded / 0 Failed +Pod Template: + Labels: controller-uid=b1db589a-2c8d-11e6-b324-0209dc45a495 + job-name=pi + Containers: + pi: + Image: perl + Port: + Command: + perl + -Mbignum=bpi + -wle + print bpi(2000) + Environment: + Mounts: + Volumes: +Events: + FirstSeen LastSeen Count From SubobjectPath Type Reason Message + --------- -------- ----- ---- ------------- -------- ------ ------- + 1m 1m 1 {job-controller } Normal SuccessfulCreate Created pod: pi-dtn4q +``` + +To view completed pods of a job, use `pi get pods`. + +### List all the pods that belong to a job in a machine readable form: + +```shell +$ pods=$(pi get pods --selector=job-name=pi --output=jsonpath={.items..metadata.name}) +$ echo $pods +pi-aiw0a +``` + +Here, the selector is the same as the selector for the job. The `--output=jsonpath` option specifies an expression that just gets the name from each pod in the returned list. + +### View the standard output of one of the pods: + +```shell +$ pi logs $pods +3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326459958133904780275901 +``` + +# More Large Pod Size + +There has been a lot of interest from our customers to use large pod size to both CPU and memory intenive workload. Now, we add the support of the following new pod sizes: + +| Size | vCPU | RAM (GB) | +|---|---|---| +| L3 | 8 | 30 | +| L4 | 16 | 50 | +| L5 | 32 | 110 | +| L6 | 64 | 230 | + +If you need even larger spec, please feel free to [let us know](contact@hyper.sh)! + +Want to try _Pi_ now? Enjoy your access here: https://hyper.sh diff --git a/blog/source/introducing-pi-on-gcp.md b/blog/source/introducing-pi-on-gcp.md index dc68ae2..a3bbb5d 100755 --- a/blog/source/introducing-pi-on-gcp.md +++ b/blog/source/introducing-pi-on-gcp.md @@ -1,79 +1,22 @@ -title: Introduce Pi (Free Beta) - Expanding Serverless Container Platform to Google Cloud -date: 2018-04-23 17:25:00 +title: Introduce Pi - Expanding Serverless Container Platform to Google Cloud +date: 2018-05-10 17:25:00 author: Peng Zhao -preview: Today, we are excited to announce Pi, the new serverless container platform on Google Cloud. Pi provides the Kubernetes interface (pod), which allows allow direct integration with GKE and other GCP services. +preview: Today, we are excited to announce Pi, our new serverless container platform on Google Cloud. Pi provides the Kubernetes interface (pod). You will now be able to take advantage of advanced features of Kubernetes right from Pi. --- -Today, we are very excited to announce [_Pi_](https://hyper.sh/pi), our new serverless container platform on Google Cloud. We believe that it is a new evolution of [_Serverless_](https://en.wikipedia.org/wiki/Serverless_computing), which enables more applicartion patterns and use cases. +We are very excited to announce Hyper [Pi](https://hyper.sh/pi) platform! Our new serverless container offering with a native Kubernetes API interface. You will now be able to take advantage of advanced features of Kubernetes right from Pi. -Let me explain. +Since we launched our serverless container offering 2 years ago, a lot has developed within the industry. We have seen the dramatic rise of containerized workloads taking over the cloud ecosystem, and at the forefront of this seachange has been Kubernetes, the open source container orchestration platform. -## FaaS, Container and Serverless +While our customers love the simplicity and ease of use that our current Docker-native platform brought in getting their containers up and running quickly and efficiently, there has been a growing number of our customers asking for more advanced micro-service capabilities provided by Kubernetes. Our Pi platform delivers these advanced capabilities along with the same great features our customers love like: -_Serverless_, as a new pattern of application development and computing service, is pioneered by [AWS Lambda](https://aws.amazon.com/lambda/). Technically, _Lambda_ is defined as Function-as-a-Service, in which developers deploys individual functions (as source code) in AWS, who is responsible to handle function invocation, function input/output, scaling (in terms of concurrent requests), etc. +- Serverless Container +- 5-second Provisioning +- Persistent Volumes +- Built-in Load-balancer +- Per-second Billing -Comparing with traditional long-running "Servers", _FaaS_ +Also, Pi platform is a strategic step closer to our goal of a multi-cloud serverless container solution. We are initially launching Pi on Google Cloud, with the intent over the next year to expand the platform to AWS, Azure and other major cloud providers. Our customers will enjoy the ease of serverless containers, with the single standard workflow of Kubernetes, and the breadth of deploying containers to any region on any cloud! - - -Different from the current [_Hyper_](https://hyper.sh/hyper) service, - -- _Pi_ runs on top of Google Cloud -- It provides the Kubernetes sematics (pod), which allows direct and easy integration with GKE and other GCP services - - - -You can sign up get your free access by following this link: https://hyper.sh/ . We are bringing new users on to the platform as quickly as possible and you’ll be updated by email as we proceed. - -### Secure Container -Hyper.sh is built on [HyperContainer](https://github.com/hyperhq/hyper) , a virtualized container technology we open-sourced. HyperContainer addresses the security problem in Linux Containers by replacing: - -- `Cgroup + Namespace` ---> `Hypervisor (KVM, Xen, etc)` -- `Host Kernel` ---> `Guest Kernel` - -![](https://trello-attachments.s3.amazonaws.com/5694785e124f36d746f5c7be/1511x393/b8b5cd31b59af44c0c86349e150438fb/HyperContainer_vs_LinuxContainer.png) - -As for performance, **a HyperContainer is able to boot in less than a second (~100ms)**, giving similar performance to a Linux Container. - -### Docker Native Workflow - -![](https://trello-attachments.s3.amazonaws.com/55545e127c7cbe0ec5b82f2b/879x320/5471e40d4a519c3d31f455bdccc978ca/upload_2_3_2016_at_3_50_31_PM.png) - -Thanks to the built-in isolation, HyperContainer replaces VMs as the building block of Hyper.sh. More importantly, without the underlying VM hosts, the need for a cluster is gone, along with things like capacity planning, VM configuration, COE, and cluster utilization rates. Thus, **Hyper\_ works like one single remote Docker host with unlimited capacity**. - -There is no need to learn a new set of commands. The Docker native workflow makes working with Hyper.sh as simple as running containers on your own laptop: - -- `hyper pull`: pull images from Docker hub to your Hyper.sh account -- `hyper run`: launch a HyperContainer without VM or scheduling -- `hyper run --link`: link multiple containers as they run on one machine -- `hyper exec`: login your container or execute commands -- `hyper fip attach`: attach floating public IPs to enable Internet access and mask application failures - -### Pay Per Second - -We charge by the Container and We charge by the Second. - -We charge you for the individual container, NOT a long running VM typically used to run your containers. Unlike AWS and Google, Hyper.sh is capable of directly launching a secure container without a VM, providing true agility and cost optimization. - -We charge you by the second. You can spin up a container in 3 seconds, crunch some data or run parallel builds on the latest commit for 10s, destroy the container in 1s, and Hyper.sh will only charge for 3+10+1=14s. - -This Per Second model not only promises cost saving, also advocates event-driven patterns such [AWS Lambda](https://aws.amazon.com/lambda), [Spark Streaming](http://spark.apache.org/streaming/), and [CD/CI](https://10second.build/). - -![](https://trello-attachments.s3.amazonaws.com/56b19c6e5bb4a89f92d0e71f/903x472/2ccb5880a4286dd6d4c14eb19b3dab99/upload_2_3_2016_at_2_21_34_PM.png) - -### Persistent Storage -We've built a distributed, replicated, reliable block storage system in Hyper.sh to offer you the persistent volume/snapshot features you need to run your stateful workloads. And it is powered by full high-performance SSD! - -### 10Gbps Network for FREE! -We use the latest 10Gbps network to run your container. The best part is that all traffic (in, out, inter-container) is FREE! - -### Make the cloud run like your laptop - -We’re extremely excited to make Hyper.sh available to the world via this public beta and we’re looking forward to learning how people use the platform and where we can improve. - -By repurposing the hypervisor from traditional full-blown VMs to the application-centric container, we think we’ve brought much-needed isolation to multi-tenancy, while keeping the signature tune of a Linux container: sub-second boot, with upgraded immutability and portability. - -We believe that this is the nirvana for Cloud Native Applications. Developers can finally concentrate on the code, not being distracted by the server, because there is simply no such thing. - -Want to try _Pi_ now? Get your access here: https://hyper.sh +Want to try _Pi_ now? Enjoy your access here: https://hyper.sh diff --git a/blog/theme/_header.html b/blog/theme/_header.html index d933a6a..ad2a39c 100755 --- a/blog/theme/_header.html +++ b/blog/theme/_header.html @@ -7,17 +7,11 @@
HOME - FEATURES - HOW TO - PRICING - DOCS - FORUM
RSS - SIGN IN • UP