Associate Software Test Solution Architect at AFour Technologies
Real User
Top 10
2023-09-29T12:10:00Z
Sep 29, 2023
The documentation for various distributions is helpful, but I would recommend placing more emphasis on documenting permissions and scripting the deployment process. Consistency in deployment and maintenance procedures is important, and having automation in place would be a valuable addition. I would rate the overall solution an eight out of ten.
Software Engeenir at Cardiff University / Prifysgol Caerdydd
Real User
Top 20
2023-05-31T10:42:00Z
May 31, 2023
I recommend looking into it first thoroughly. It's not a website or, you know, an application that you'd want to use from the get-go. If you're unused to doing DevOps, you'd probably want to get some experience with it first because it's not completely clear how to get around it when you first start using it. I rate the overall solution a six out of ten.
I give the solution an eight out of ten. Maintenance can be carried out with a really low number of resources. However, if somebody requests 24/7 monitoring or other similar services, we would need a bigger team. Generally, we don't require many resources. Two or three people can maintain a reasonably large cloud deployment. We don't use any Rackspace OpenStack distribution such as Red Hat or Mirantis. We use the community version of Rackspace OpenStack, which has strong community support. Anyone planning to invest in VMware or Nutanix, which are both at least ten times more expensive than Rackspace OpenStack, should start thinking about this Rackspace OpenStack alternative. A lot of organizations are already using Rackspace OpenStack, which is less popular than VMware and Nutanix, but it's definitely a viable option for anyone planning to set up a private cloud infrastructure.
OpenStack is an open and scalable cloud operating system for building public and private clouds. It provides both large and small organizations an alternative to closed cloud environments, reducing the risk of lock-in associated with proprietary platforms.
As an approved service product, I am in favor of OpenStack. I would rate it a nine out of ten.
Overall, I rate the solution between eight and nine out of ten.
The documentation for various distributions is helpful, but I would recommend placing more emphasis on documenting permissions and scripting the deployment process. Consistency in deployment and maintenance procedures is important, and having automation in place would be a valuable addition. I would rate the overall solution an eight out of ten.
I recommend looking into it first thoroughly. It's not a website or, you know, an application that you'd want to use from the get-go. If you're unused to doing DevOps, you'd probably want to get some experience with it first because it's not completely clear how to get around it when you first start using it. I rate the overall solution a six out of ten.
I give the solution an eight out of ten. Maintenance can be carried out with a really low number of resources. However, if somebody requests 24/7 monitoring or other similar services, we would need a bigger team. Generally, we don't require many resources. Two or three people can maintain a reasonably large cloud deployment. We don't use any Rackspace OpenStack distribution such as Red Hat or Mirantis. We use the community version of Rackspace OpenStack, which has strong community support. Anyone planning to invest in VMware or Nutanix, which are both at least ten times more expensive than Rackspace OpenStack, should start thinking about this Rackspace OpenStack alternative. A lot of organizations are already using Rackspace OpenStack, which is less popular than VMware and Nutanix, but it's definitely a viable option for anyone planning to set up a private cloud infrastructure.
OpenStack is great for being able to create a stable private cloud. I'd rate it eight out of ten.
One a scale of one to ten, I would rate Rackspace OpenStack a seven.