The overall infrastructure-as-a-service platform has reduced customers' reliance on public clouds. It provides a private and consistent logging center, which is critical for some data types.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
The overall infrastructure-as-a-service platform has reduced customers' reliance on public clouds. It provides a private and consistent logging center, which is critical for some data types.
The product can enhance the physical capacity for delivering 15 computers. It can be extended to 150. The product has enabled virtualization wherein people can have their OpEx go down.
We make telecommunications-specific customizations. For us, network utilization is the primary factor. We joined the network virtualization functions to understand how they are managed and how the underlying cloud supports them. There are specific parameters that we can add to a checklist. The seamless integration between MySQL services and the rabbitMQ database can be revised during debugging.
I have been using Rackspace OpenStack for more than nine years.
The solution is stable.
Rackspace OpenStack scalability allows you to scale up without downtime, even for critical applications. We have Windows to scale it over ten days with issues or as seamless scaling. In the end, answer your code if everything is written correctly and there is no temporary cache or very few unpredictable things that pop up. Generally, things work well; if they don't, you'll have to leave a gate.
If the customer has access to Rackspace, We use the ticket. If they don't, they have to go to the open-source community.
We use VMware, which is as easy to install as any software on a laptop. You need to customize for Red Hat or Rackspace versions. That's where the architect's and deployer's knowledge and skills come in. With the flexibility to use hundreds of parameters, the right knowledge help will help to choose the right ones and when to use them. If you do, it will work seamlessly 80% of the time. 20% of the time, you will need support from the community or someone who knows what is happening. You may even need to check the code to see if it works properly.
Overall, I rate the solution an eight out of ten.
OpenStack is a cloud provider with several vendors, which have all been used.
Apart from the main features, I really appreciate OpenStack's microservices architecture and its flexibility for deployment with different tools. Scaling up and down is easy, and the support for authentication, policies, encryption, and other features is commendable.
OpenStack's UI, while user-friendly, could be improved to offer a more intuitive experience. Additionally, the storage solutions, aside from S3, seem to be limited or restricted in their options, and expanding these choices could be beneficial.
I have been working with OpenStack for around two years.
While issues do arise, we have become adept at resolving them due to our familiarity with the environment and our troubleshooting skills. I would rate the stability an eight out of ten.
It is a scalable solution.
The community support and resources available for different open-source distributions have been quite helpful. While we managed to address many issues through community forums and articles, technical support has also provided valuable assistance when needed.
The initial setup of OpenStack can be challenging, especially for those not accustomed to it. However, the documentation provided by OpenStack is quite helpful. Despite some deployment issues, once users become familiar with it, the platform becomes more manageable. We've experimented with various flavors, including Red Hat OSB and Canonical. To streamline the process, we incorporated deployment automation and scripting. One notable challenge we faced was the extended deployment time, especially with Red Hat, which could take around 30-45 minutes. Despite the challenges, the platform offers scalable resources and infrastructure, making it suitable for creating private cloud environments.
Maintenance is similar to deployment, and it can be time-consuming without any additional procedures.
Our client had PostNL, so we couldn’t evaluate the existing options.
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.
