We deploy layer three managed services, and our customers manage layer two services. We combine the two-layer services and deliver them to our customers.

The open-source nature of OpenStack provides significant value. It allows for three-word cloud management, maintaining a stable customer environment, and offers additional services like migration and optimization. OpenStack excels in guiding customers with transitioning from traditional setups to modern cloud environments.

The pricing of Rackspace is quite high in the Vietnam market. It would be beneficial to see developments in features like threat prevention and analytics tools for network security within OpenStack.

I have been using the solution for over ten years.

Rackspace OpenStack is stable and reliable, often compared favorably against other solutions. It is very stable, and its services are highly valued.

OpenStack on the platform is scalable. It is very easy to scale everything as needed.

Customer support at Rackspace is excellent, available 24/7, providing very good assistance.

Positive

When compared to other commercial products, Rackspace OpenStack is much cheaper, especially when compared to solutions like Red Hat OpenStack or VMware. The licensing costs are beneficial.

Rackspace OpenStack offers a much cheaper licensing model compared to alternatives like VMware or other commercial solutions.

Other commercial solutions such as Red Hat OpenStack and VMware Cloud version have been considered, however, in comparison, Rackspace OpenStack is cheaper.

I would rate Rackspace OpenStack an eight out of ten. This solution effectively maintains a stable environment and provides excellent customer support.

My clients use it for the virtual platform and to utilize existing hardware or infrastructure. They want to migrate current workloads, specifically test and development, to OpenStack, not production.

We have certain projects where we adapt to the bank, MDM, and other companies.

It's pretty good. One thing is that you can use any infrastructure for OpenStack. That's not a challenge. 

It helps give customers the same functionality as costly solutions like VMware or IBM. 

And thirdly, it's easy to manage for day-to-day functionality. Administrators are very comfortable with the functionality and services OpenStack offers.

OpenStack is a wonderful product, and it should have a single dashboard for cloud management and on-premises systems, similar to VMware. Multiple windows are currently used. If one orchestration table was available, that would be a great improvement.

The platform could be enhanced to be easier to use, especially in report generation for complex Rackspace, strategic  management, and other small things that could be added to the system.

I have been using it for four years. 

Stability is good. I would rate the stability a nine out of ten. 

I would rate the scalability an eight out of ten. I approach all kinds of companies. Currently, I have some enterprise customers. We try to be a great contributor to the Open Source, OpenStack, and OpenShift deployment communities. We even run internal training for our service teams.

It is easy to scale, but we either need some expertise or support from the product team. 

Rackspace OpenStack needs to provide better support, services, or enterprise licensing to gain more customer interest. When I approach customers, they are hesitant about this solution. 

As a service provider, I need to give them confidence and assure them that we will help resolve any problems. There is a lack of OEM or partner licensing or enterprise support, and people are not aware of the available support.

Until now, we have done our own R&D and relied on community support. We have not contacted the Rackspace team.

VMware was the major player, but this market was captured since the merger and acquisition with Broadcom. 

Now, OpenStack has very good features. In the future, if we develop OpenStack in the right direction, we will be able to capture a good market share in the future.

The initial setup is not overly complex. It requires expertise.

We work on-premises. All the opportunities I've had so far have been on-premises.

With expertise, it can be done.

It's a low price compared to other solution providers and any other licensing options in the market.

As an approved service product, I am in favor of OpenStack. I would rate it a nine out of ten. 

We use OpenStack for my company for maybe 14 virtual machines. 

The principal use of Rackspace OpenStack was for virtual machines. It has a different architecture, which can be based on a single machine or a group of machines. The scope of the application varied, from GitHub to asset management and other uses. We worked on infrastructure as code, which was fascinating because it allowed us to use architecture-like software.

It was a very flexible and scalable solution. It was very useful because we were not dependent on a single vendor's solution. Increasing the number of machines or changing the hardware configuration was very easy.

The deployment process could be easy.

I have been using Rackspace OpenStack for five years.

The solution is stable.

The initial setup is complicated. There are many components, so you have to ensure that every part is running correctly. 

Our cluster has about eight nodes, and it took about a week. Two skilled engineers are required for the solution's deployment.

You were using the free version of OpenStack. You didn't have the license for it.

Overall, I rate the solution between eight and nine out of ten.

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.

We developed a website using Rackspace OpenStack. We then had to figure out how to configure it using Jenkins, so we had to write the shell scripts. And the whole purpose of it was to show that we could update the website to the live website on the server and show that we could push updated staff from the Git repository.

I like its integration with GitLab and its simplicity. OpenStack has a lot of third-party libraries that it uses.

There are a lot of things you can do depending on what you want to, you know, handle, whether it's your pipeline or whether it's some third-party libraries that you use in your application to make sure that they're all taken well on your live site, the kind of configuration you can do from within OpenStack and Jenkins is very extensive.

Compared to Microsoft Azure, Rackspace OpenStack lacks an ecosystem and needs to have one. Azure has everything that comes along with the Microsoft ecosystem. Whereas the problem with OpenStack is the fact that it is not commonly used. Also, it's not easy to get into and understand. In contrast, with something like Azure, there's a massive community around it. It's a very quick and easy thing to learn in comparison. That's one of the biggest drawbacks of Rackspace OpenStack.

.I have been using Rackspace OpenStack for half a year.

It is a stable solution. The kind of software used for maintaining it went down at one point because they were up-updating it.

So for the main stability, there have been a couple of issues that I've experienced. Still, we've yet to be able to make updates to our website.

It is a scalable solution. If you were a small project and you were expanding rapidly, I would see no reason to move. Suppose you were using other stuff within Microsoft or even the Amazon ecosystem. In that case, you may choose to go to them. Five users are using the solution.

I rate the scalability an eight out of ten.

If you can have a preconfigured server, the installation's probably very simple. It took a while, and it was very fiddly to get the shell script to do what I wanted to do to push my desk database and server over onto OpenStack.It was fast and had a lot of tech to deploy. So it's a matter of hours, not days.

I had a relatively small application from the start, so configuring the server took about an hour. Two people are required for the deployment.

We never had to maintain it, only for about a week. We had to upload various stuff to the live server. And it was just those two again because there wasn't a lot.

It depends on how much work is being done on the application and how much stuff is being pushed to GitHub. Because maintaining that if you have a group of, you know, a project using fifty people is obviously a large project. And you're all pushing your work to GitLab to control that version, ensuring everything's in the right format. I can imagine it expands as the project gets bigger.

I use it as an open-source tool.

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.