Originally posted by Rodrigo Baldasso
The deployment, operation, automation and delivery under OpenStack have been my full time job for over 7 years. So I can give you some information about this.
you want an alternative to solusvm .. but do not make that the only argument to choose an equivalent equivalent to open source because you go anyway to a new technology .. for example, what do you want to sell, what control do you want on the users? have, how much background administration you need to do, etc. Do not think of today's need.
It all depends on your goals and the way you see yourself in the market. If your goal is simply to have an open source system with the same features as solusVM, then proxmox is a very good choice. Highly recommended.
With OpenStack, you will no longer have a license .. and the new version and new features will be published every 6 months .. so it is always possible new products for sale.
As for features, in addition to self-service hosting, you can easily start selling products such as DNS as a service, Load Balancers as a service, Storage of objects, Volumes, Containers, etc.
If you want to sell as a cloud provider – where users can create a site-to-site VPN on your cloud, deploy their virtual instances and routers and run their workload, or if you want to provide solutions to companies or colleges, with their AD / LDAP system, site-to-site tunnelset VPN, then surely OpenStack. Openstack has grown a lot and is now a stable and robust product. That's why, if you look at the popular companies providing cloud solutions – redhat, suse, canonical, cisco, dell …, the reference architecture of these clouds is based on openstack and ceph. You can go to https://www.openstack.org/user-stories/ to check who already uses OpenStack and why. It stands out for its stability and reliability, but above all for its flexibility.
It is true that there are many modules, but it is because it is very flexible and the modules you select and how you build them depend entirely on your needs of tomorrow (and not today) . If you look at the needs of today, more than 6 months later, you could be "oops … we built it badly …" or "we could have chosen a different technology," and so on. Will you just be IaaS or do you want to do PaaS, SaaS, etc.? all the way … what your customers might look like … do you plan to be just a supplier … or a supplier … .. what price segment you want to pack and sell your products and solutions .. what kind of workload do you expect … these are all the questions you should ask yourself .. The link will show you how it is used and how it can be used .. so you can see how you can do it. If you have a lot of customers, you may already have data on upsell opportunities.
Your position is indicated from Brazil .. you should also take into account .. what benefit would I have on my region / city / country depending on the degree of flexibility and wealth of your service provider? cloud computing .. what kind of business etc can use your cloud etc ..
Once you have solved the problem, all you have to do is indicate how you will install it and what modules, network, number of servers, start to boot, where to find support, how to build it, how to use it, how to do it. support him, etc. the subjects and all the architecture of it ..
using it just for a solusvm replacement will underutilize its potential and could also be an overload for your team that is trying to implement, support, upgrade, understand it, keep it up to date, etc. You'd better migrate to proxmox.