Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hakuna Cloud – Stop cloud servers when they are not in use

hakuna.cloud

Post reply on HN
Print view View original

41–50 of 64 posts

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#41

Post by cristyansv »

nine_k wrote: post #6

Now that we have CGI scripts in the cloud (lambdas), there ought to appear an implementation of inetd, too! Jokes aside, I wonder when cloud providers will add something like this as a native feature.

google Kubernetes engine, alerts you when a cluster is under used and shows the amount you could save if you reduce the number of machines.

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#42

Post by scjody »

Related: if you're looking for a service that starts/stops instances on a schedule (we find this really good for QA and development instances), check out https://www.parkmycloud.com/ . You can also set an instance to "always parked" and unpark it for a certain number of hours or until a certain date/time.

(No affiliation, just a satisfied customer.)

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#43

Post by scjody »

gregmac wrote: post #8

> Hakuna Cloud is a software-as-a-service HTTPS proxy. You don't need to change existing software or infrastructure, and you don't need to install additional tools on your servers. > Each cloud server must have an FQDN/DNS name configured as a CNAME to our load balancers. > When your server stops receiving requests, it will be stopped. As soon as a new request arrives, Hakuna will start it. Interesting idea. It's lik…

For time-based server start/stop, we use https://www.parkmycloud.com/ .

I'm looking forward to checking out Hakuna Cloud - looks like the two services are pretty complimentary.

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#45

Post by dharmab »

najarvg wrote: post #11
dharmab wrote: post #3

Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by: - Using the Kubernetes Vertical Pod Autoscaler ( https://github.com/kubernetes/autoscaler/tree/master/vertica... ) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling - Collecting metrics on container CPU and memory allocation vs utilization - Writin…

Would love to see a more detailed write-up, if one exists, on your experience. We're nowhere near your scale but will probably ramp up in the next year or so.

I'm going to try to convince the lead on this project to present at an upcoming Kubecon :)

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#46

Post by opportune »

It seems like it does exactly (or a subset) of what Google Cloud Run already does. Just shove an application into a container and scale up/down depending on use. Other cloud providers probably have this too. So is the value add that this is less expensive or what?

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#47

Post by sharadov »

grepthisab wrote: post #28
tlarkworthy wrote: post #12

It's pretty cool that utility computing is large enough to spawn 3rd party companies that further increase effeciency of the pool. It's layers upon layers of technical progress in parallel.

Maybe. This is a bit of a cottage industry that shouldn't need to exist. It's so hard to get data and visibility into these things in AWS right now. Billing is hard, it's impossible to easily tell what is costing me what in every region, etc. AWS should do all this natively as part of their service, but everything is so poorly designed from a user standpoint that it's very time consuming to do, so third-party service…

Of course they do this on purpose, it does not require a lot to give you metrics on usage and tell you if you are over provisioned, when mint.com can suggest a lower interest credit card or a higher yielding account based on my financial history, AWS cab easily do the same. But, why would they. They rather laugh all the way to the bank!

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#48

Post by dharmab »

totomz wrote: post #4
dharmab wrote: post #3

Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by: - Using the Kubernetes Vertical Pod Autoscaler ( https://github.com/kubernetes/autoscaler/tree/master/vertica... ) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling - Collecting metrics on container CPU and memory allocation vs utilization - Writin…

Actually, HakunaCloud works on cloud servers, not containers. With Kubernetes you pay for the worker nodes, not for running containers. HakuaCloud starto&stop cloud servers, so you actually pay only for the time the servers are needed

The number of running nodes is a direct function of the number and size of your containers. The cluster autoscaler stops and and start servers based on how many containers are desired, which is in turn based on the Horizontal Pod Autoscaler inputs (e.g. incoming requests).

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#50

Post by mnutt »

I had long wondered if it would be possible to have a custom autoscaler that just stopped/started instances rather than terminating and re-creating, in order to respond to load increases more quickly than amazon's autoscaling groups. You still pay for the EBS even when it's stopped and deploys involve briefly starting all of the stopped instances, but EBS is a fraction of the overall spend and maybe in some cases the complexity is worth it?
Post reply on HN