Rackspace OpenStack Reviews

I mainly use Rackspace OpenStack for my virtual environment, for the KVM environment, such as hosting VMs. That is what we use it mainly for. You can say it is just like VMware; we are using Rackspace OpenStack; however, VMware is on a little higher ground. Rackspace OpenStack is kind of medium to high, you can say, but not high. It is not as good as vCenter.

The most useful opinion about Rackspace OpenStack is that it is very flexible, first of all. It is very flexible and the most important feature is that it is feature-rich. All over the KVM environment, I have played with many, but Rackspace OpenStack is built on many third-party applications, like Nova, Cinder, and many things. So it supports a lot of vendors, first of all. The far most important point is that it can be certified for the SAP HANA database.

Most of the things are already available in Rackspace OpenStack. It was easy to integrate a few things, but I did not find much of the backup solution; it is not there. The backup solutions are not proper for it, and that was the main layoff for me. You can say, there were also integration issues, but it depends on what you are trying to integrate. If you are trying to integrate some major products, you will be able to. But for cheaper products, you will not be able to integrate. We tried very hard to integrate a certain backup solution. We used Acronis, and the other one we tried, we worked with them for approximately six months, but we were not able to integrate that properly.

There are two front-ends for Rackspace OpenStack. One is what Core-edge provided us; that is a customized one, which is never finished customizing. The second one is the official one, that is Horizon. Horizon comes in the older version of Rackspace OpenStack, and what we used is currently end-of-life. In that, Horizon was there. In the new version, there is a Skyline dashboard. I do not have any complaints with Horizon, as well as Skyline. Skyline is also good; it is very much improved and very good. People are selling that product as a service, directly on the dashboard without much editing, only some white labeling. So I think the dashboard is very good, the latest one, Skyline.

The advantages are that it is stable; it is very integratable because most of the people will integrate most of the things with it. But new products might have issues. It depends; it is 50-50 on integration, you can say. But it has lots of moving parts, that is a disadvantage. There are lots of resource requirements, such as human resources. Other things like that, you have to constantly train people about it, how to utilize it at L1, L2 levels. Then the end user will not appreciate it as a SaaS platform or as a PaaS platform or as an IaaS platform. So Infrastructure as a Service, it is a little bit good with Skyline, the new version, but it is still not appealing because they know what they are going through. But Rackspace OpenStack in Virtuozzo is very good. Virtuozzo has created a layer and made it simple.

For Rackspace OpenStack security features, we currently opted for ShapeBlue one, which will be installing CloudStack. ShapeBlue is helping us in training. So, we are moving away from Rackspace OpenStack to CloudStack because CloudStack has most of the features that we require, and it is also lightweight.

Rackspace OpenStack does not provide that thing. The product has all the things included, you can say like that. But the thing is, if you are a company, if you are a hosting company, you will require at least three to four people with higher expertise to install and get going with Rackspace OpenStack. It is very hard; you have to understand bits and many things about it, how it works. It is not something you just tinker around with. The second thing is we are moving to CloudStack because it comes as just a single package that I can install in a VM and I am done with it. I just need to configure it the first time, and everything, the experience out-of-the-box is very good with CloudStack. But Rackspace OpenStack is very assembled parts, you can say. Would you prefer an assembled PC or would you prefer an HP-provided PC, a branded PC? It depends on you.

The main thing about Rackspace OpenStack is that it is totally built on many modules. It is approximately 30 to 40 modules, you can say. You have to learn and understand that, which there is a very steep learning curve. If I am not wrong, there is a very steep learning curve. There is not one way to install Rackspace OpenStack; there are several ways, approximately three to four ways. But it depends on who deployed it. Suppose a person deployed it in a different style; after one or two years, he got changed, and another person comes. He does not know about that style, then it will be very hard to navigate. Currently, Kolla-ansible, which we have, is very hard to navigate for me. Although it is very easy to install, it is very hard to operate because it works on Docker. So, there are too many moving parts. If you say to me, there are too many moving parts, and the visibility is low on that.

It is very hard to have any issue with it. It is a very stable product.

I am currently using Rackspace OpenStack, and it has been approximately 2.5 years that I have used Rackspace OpenStack.

For stability, I would rate Rackspace OpenStack eight.

For scalability, I would again rate Rackspace OpenStack eight.

I do not think they provide the technical support. I have not taken any vendor management system. I was having Core-edge-related support. Core-edge was building the upper layer and they are also supporting us. In that case also, it is so complex that you will get lost in the contract because it is so vast. What is included in the support, what is not included, I think that will eat you up. So I will give it a five.

I just want to confirm, currently, I am not working with Morpheus because Morpheus was taken over by HP.

I am currently working with Rackspace OpenStack. Additionally, I am now also moving from Rackspace OpenStack to ShapeBlue, which is CloudStack.

I am working with CloudStack. Now, we are implementing CloudStack. For the last two years, we worked with Rackspace OpenStack.

We are moving from Rackspace OpenStack to CloudStack due to the requirement of human resources and technicality. There are lots of moving parts in Rackspace OpenStack.

Rackspace OpenStack has three to four setup procedures. Some are very easy, while some are very hard.

I am not currently using HP solutions because we have to drop Morpheus due to our requirement for some customizations, and Morpheus was not entertaining that.

I help my clients with Rackspace OpenStack as a consultant. I work with my clients as a consultant with Rackspace OpenStack. I am not involved in the purchase process of the platform. The pricing for Rackspace OpenStack is free. Rackspace OpenStack is good, but I think it is complicated in its own sense. To be adopted by a company, it is harder to operate, but easier to implement. The final assessment is that it is not that everything is good or bad. There are certain things which are very good, but there are certain things which are very bad, such as the dependency of the person. I would give this review an overall rating of eight.

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 main use case for Rackspace OpenStack involves large data management, as it provides a reliable database service.

A quick specific example of a task where Rackspace OpenStack helps me is in handling the database and assisting with backups in my organization. It also hosts my applications, managing cloud infrastructure services while I create multiple servers. In my product area, I operate three to four servers, including a development server, testing server, UAT site server, and solution expert server, managing these servers effectively.

The infrastructure level concept is strong, making it easy to handle everything and adaptable for customization based on my organization's specific terms, conditions, and needs.

Rackspace OpenStack positively impacts my organization by making processes easier since I do not need to manage all servers manually because it efficiently manages server operations and maintains proper data, which saves time.

As a beginner, I find some difficulties in understanding Rackspace OpenStack, as it can be complex without a foundational grasp of cloud and networking concepts. To improve, I suggest providing proper documentation aimed at new users or beginners, which would help them understand how public and private clouds operate.

I have been using Rackspace OpenStack since my college study where I had one subject on cloud computing, and in my organization, I have been using it for the last three months.

I advise others looking into using Rackspace OpenStack to have a solid understanding of cloud concepts, as managing these aspects in Rackspace OpenStack requires a good knowledge foundation. I have rated this product a seven overall.

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.

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.

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. 

Rackspace OpenStack is more suitable for enterprises that are looking for private cloud solutions and who are thinking of offloading some of their auxiliary workloads from the public cloud and saving money. Rackspace OpenStack can fit in that use case where enterprises are thinking of a hybrid model of the cloud. We are a product and solutions company that builds a private cloud infrastructure based on Rackspace OpenStack for our customers. We are not a system integrator. We provide the product and solutions on top of Rackspace OpenStack.

The first benefit of Rackspace OpenStack is that it can be a direct alternative to VMware for implementations. VMware is expensive, but Rackspace OpenStack can save companies money in comparison. Additionally, Rackspace OpenStack is scalable, making it a good choice for companies with growing needs. The Rackspace OpenStack community is large and has been around for 10-plus years. This maturity means that there are many companies that can provide support for enterprises switching to Rackspace OpenStack solutions. Additionally, Rackspace OpenStack is free, except for the cost of support. This makes it a more affordable option than VMware.

There are many services that can be directly used which are not available in VMware. These include data analytics solutions and services, services specific to big data, and Container as a Service. Therefore, there are many additional services which are available in Rackspace OpenStack. VMware probably does not have as many services as Rackspace OpenStack does.

There are always new improvements being made to different aspects of Rackspace OpenStack.

Another advantage of Rackspace OpenStack is its flexibility. we can run the cloud on our commodity servers, which brings in more flexibility and customization options. This includes being able to customize the architecture to our specific needs.

Rackspace OpenStack is constantly changing with new services and features being released every six months. This quick release cycle makes it difficult to keep up with all of the changes. 

VMware has a side-to-side replication feature, which is still more mature than Rackspace OpenStack's which can't be used in a production environment. By making this feature called Freezer more mature, enterprises may be more likely to adopt Rackspace OpenStack.

I have been using the solution for over eight years.

Rackspace OpenStack is becoming more mature with each cycle and is quite stable. We have had a few implementations without any issues in the last four or five years. Our implementation is also enterprise-grade, and we don't have a single point of failure.

Hyperconverged infrastructure is scalable, and Rackspace OpenStack can be deployed on it. This means that if a customer needs to scale, they can just add more hardware to the back of the system and it will be added to the cluster in a few hours.

Rackspace OpenStack's initial setup is complex, but it has a lower cost than VMware. I believe that if the setup was easier the cost of the solution would be higher. 

Deployment can take a long time if done manually, but with the help of tools like Ansible, the process can be automated. A more mature organization can take a few weeks to deploy the grid, but no more than that.

The first step in creating a cloud is capacity planning. This involves figuring out the amount of cloud capacity a customer needs. Once this is determined, the necessary hardware is procured. The hardware must have the specifications to meet the customer's capacity requirements. Once the customer agrees with the filing, we go ahead with the provisioning of the hardware. The hardware is provisioned, the next step is to stack the hardware inside the rack and plug it on. Then we start deploying the Rackspace OpenStack on their servers and building all the applications which are required to support, maintain, and monitor the complete cloud infrastructure. We then proceed with the testing of the entire stack. We deliver, ship the hardware to the customer's place and deploy it. 

The deployment requires a lot of people. We do refer the resources to other departments because it will be mostly on-site in the customer's location. We have to be there helping their IT team get set with the deployment and after that, we can complete the rest remotely.

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 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.

I primarily use it for personal use inside an enterprise. I use it to deploy a private cloud. 

The enterprise that I work with already uses OpenStack. They demanded I learn it and I was able to find classes online to get started. In general, OpenStack is more useful in the public, in the world, instead of other tools that are used to implement private clouds.

The initial setup isn't too difficult. 

It's scalable. 

The stability is excellent. 

You do not have to pay anything to use it. 

OpenStack is difficult for the novice in terms of beginning to use cloud tools. If you want to do some tasks, for example, if you want to create a domain in OpenStack, you must do that in command line. There isn't any GUI available, and new users might find the command line difficult to understand. OpenStack isn't so easy for people who don't practice. They need to simplify the product and make it more visual for beginners. 

I've used the solution for maybe a month so far. I took lessons on Youtube and Udemy. 

I've found the stability to be quite good. I'd rate it eight out of ten. I haven't dealt with bugs or glitches, and it doesn't crash or freeze. 

The scalability is okay. I would rate it six out of ten in terms of its ability to scale. It's easy to expand as needed.

The solution isn't too complicated to set up. If you follow some good training documentation, the deployment will be straightforward. It helps if you have a technical background, however. A novice might find it a bit hard. 

The solution is free to use. 

OpenStack is great for being able to create a stable private cloud. I'd rate it eight out of ten. 

Our primary use case for the OpenStack is for migrating data from the cloud to on-premises. We want to migrate some of the open source OpenStack components to customize our work with our applications. Our main use is video streaming on Openstack.

The most valuable feature is the customization. With the customization you can really give the customers what they want.

In terms of what needs to be improved, I would say the support.

You're asking for the Rackspace OpenStack and I'm working on the open source OpenStack. Rackspace might have some good support but the open source OpenStack doesn't have support because there are too many versions coming and too many people are customizing it. That's why the support is a problem for open source versions.

It needs to develop a very good user interface which can compete with the public cloud.

In the next release, I would like to see more of the load balancing technologies and applications from the public cloud which OpenStack doesn't have right now.

I have been using Rackspace OpenStack for three years. 

The OpenStack application version we use is Nexus Prime.

The stability is okay but there too many versions coming out. The line migration is a problem.

The scalability is good. The application is deployed in the OpenStack, so actually the user number is in lakhs, like with the application server.

I would rate the technical support a 6 or 7 out of ten.

In terms of the initial setup, currently we have multiple scripts. These scripts can deploy if you come back to feed them.

One a scale of one to ten, I would rate Rackspace OpenStack a seven.