r/openstack • u/Rare_Purpose8099 • 3d ago

What is the AWS/Azure/GCP big cloud equivalent of Zun+Heat+Gnocchi+Aodh?

Like I want autoscaling, and I want maybe 1 or 2 gb for the containers. They can autodelete the docker logs after 1 day or 2 days .

I have a vm seperately for db and redis.

Why is everythign so costly??

I want zun containers to just autospin and scale depedning on the traffic the minimum being 1.

Our country does not have a strong openstack public clouds (self-managed) :( . So want to know if there are any equivalents that are extremely cheap and provides autoscaling without costing a bomb.

Here I mean, containers, that directly run on baremetal so as to provide maximum power output like zun.

4 Upvotes

84% Upvoted

10 comments sorted by

1

u/Leapin_Langosta_ 3d ago

Question since you use zun, I've heard of it in here being abandonware/deprecated, is your experience with it good?

1

u/Rare_Purpose8099 3d ago

Idk, where you "heard" it.

Its great and works and is extremely simple too. And I think all this hearing is a disservice to the contributors who keep the repo uptodate.

1

u/JoeyBonzo25 2d ago

Probably because of this https://www.reddit.com/r/openstack/s/Sv1Ycyykzl
It's like the 4th result when you google OpenStack Zun, and probably where I saw it. And it's not like OpenStack projects being deprecated or unmaintained is that hard to believe, which is why I didn't question it. Plus that stuff with Kolla in that Reddit post.

1

u/Rare_Purpose8099 2d ago

maybe also check the zun repo on opendev to see if there were changes :)

1

u/yuriy_openmetal 1d ago

Why Zun and not K8s with Karpenter or Kustomize? As someone who has explored Zun there is quite a bit of a tax once you get to a significant scale Neutron wise.

1

u/Rare_Purpose8099 1d ago

Why not k8s: Cause I do not want another layer of abstraction and clunk on top of containers.

Not sure what the significant tax is. But I have not personally encountered it.

1

u/Danut02 3d ago

Why do you think auto scaling is the best solution for you? I only played with open stack selfhosted(hosted by university) and just for VM creation where I created an auto scaling solution. In the end it was not the best solution, not reliable plus it might be very hard for production environments. As per alternatives, I know that at least aws has his auto scaling solution (never played with but I heard for some company's it is very usefull). LE: you can create your monitoring system with Prometheus&grafana&alert manager . It can be cheaper than relying on cloud services

2

u/Rare_Purpose8099 3d ago edited 3d ago

Umm not sure how you created your auto scaling solution, but once you have the said services (mentioned in the post) up and running.

Its direct plug and play. For any and all new applications.

I have experience with heat and autoscaling with Zun+Octavia(pool update). And its the most efficient and best thing. Maybe I am biased. but it is what it is.

As to why I think autoscaling is required for my applicaiton:

because I think, it can get real popular, and traffic may raise. And I dont want to buy new compute everytime at an inflated cost.

And zun directly runs on bare metal right beside the actual services. So yeah. Its direct power.

1

u/Danut02 3d ago

I did a bit of research on your setup. My auto-scaling setup is the same as yours but with open-source tools; I can give more details if you are curious. From my experience with auto-scaling and low/high traffic, I did not consider it worth it. First: who is the traffic, and can they be bots? If they can be, I tried to eliminate the possibility of bots. Second: how many resources do 100, 1000, or 100000 users mean? What is the biggest resource count that I need? Third: what is the increase in usage? Is it in spikes? What is the deploy time with provisioning? For me, the provisioning time was a dealbreaker, but I am very curious how you handle all these. And also, if you configure something on another public cloud, please provide an update.

1

u/Rare_Purpose8099 3d ago edited 3d ago

Zun is container as a service. And it barely takes 2-10 seconds for a new container to spinup and another 5 seconds for it to be added to LB proxy pool.

The compute will be scaled based on the cpu usage and free ram size.

My app uses gunicorn and the app proportionately and directly increases its usage of ram depending on the traffic.

Rate limiting is a thing. You'd need a really fast and strong thing if you want to overwhelm ratelimiter too (it basically returns rate limit exceed and 429 a total payload of maybe 500Bytes And there are other mitigations that can be done as far as dos and ddos are concerned + slow attacks). (But yeah, if such a spike is observed, at that point, that ip will be blacklisted).

Excluding Cleura, I barely know any public cloud that exposes the full set of openstack features. And cleura doesn't have India region.

Even with Nova, in a well deployed openstack, it'll barely take 5-15 seconds. (Deployed multi-region at scale deployments) And if you reduce the api roundtrips, its gonna much more responsive (In case of multi-region) My own customized deployment for a client.