The initial setup is straightforward, if we follow the documentation and we download the OpenShift install, we can have a very small cluster up and running in less than an hour. However, we will have to do all the day two tasks ourselves. If we run an enterprise, we have a lot of complications. We need to have proxies, separate our infrastructure stack into different nodes, and move storage to storage nodes. This adds a lot of extra work.

The IPI will take about 45 minutes. The second part, if completely automated, will take about two and a half hours.

The installation is very good. There are a lot of options with which you can deploy OpenShift and you can deploy it on different environments. You can directly deploy it on a bare metal server, or if you already have a VMware-based infrastructure, you can deploy it there. That automation is very flexible.

The initial setup is straightforward, but for a first-time user, it might be a bit challenging because there are certain prerequisites that you need to follow. But if you follow the installation guide and you're able to do all the prerequisites, it's very straightforward. It takes less than an hour.

I used the Assisted Installer and did the IPI installation for OpenShift. I had all the infrastructure ready and deployed one cluster on bare metal. Then I deployed the OpenShift cluster on AWS.

For deployment and maintenance of OpenShift, a team of 10 should be fine. They can handle the installation and the post-installation operations for your day-to-day tasks.

OpenShift has several advantages over Kubernetes, one of which is the installation process. This process is much better integrated with VMware than Kubernetes, but it is not straightforward. We still need to understand what is required, especially the network layout and the addressing because once we make our selections and deploy, some settings cannot be changed. The solution requires careful planning before deployment otherwise the entire deployment may require scrapping and starting over.

The deployment process takes up to one afternoon but it can take weeks to understand our needs and to get the process right. The same decisions are required in deciding the best size for our cluster, or how to separate our environment, which can be difficult. We may want two active clusters for production, one in each data center, or two clusters in each data center. All of these architectural decisions come with time and experience.

When deploying, I recommend having a platform team of four to eight people who can cover all areas. This team should include one or two people from security, one or two people from infrastructure, one or two people from production who know how to handle alerts, and also some people from development. The platform team should consist of between four to eight people and cover all the customers within the company. Having a team of this size will ensure that all areas are covered, and if someone is unavailable, there is still somebody else to provide backup.

The setup for OpenShift was complex, and it can only be done by a consultant. My team can do an on-premise setup and automation, but a consultant has to certify the cluster, otherwise, you can't get support from RedHat.

Deployment for OpenShift can be completed within six to seven hours depending on the infrastructure. Otherwise, it could take more than one day.

My rating for the initial setup of OpenShift is three out of five. RedHat will check the setup or configuration, and if the customer is ready to take over the process, then it's good, but what's usually happening is that the vendor isn't providing detailed guidelines, so my rating is more on the neutral side.

It was straightforward. I had a perfect team with prior experience in OpenShift. They were able to do it without any hiccups. The community of OpenShift is very good. There are a lot of exchanges happening in the community space, which helped us in doing it in a seamless way. I would rate it a 5 out of 5 in terms of the ease of the setup.

There isn’t really any initial setup to worry about.

For the installation of OpenShift, we used the IPA method of installation in AWS. It's pretty straightforward and easy. It isn't complex, but you have to go through the documentation. You have to read the documentation before implementing it. Overall, the initial setup is good. There isn't any complexity in the installation.

We have a good procedure to implement it. We just followed our internal procedure and the OpenShift document, and we were able to install it.

When we deployed a cluster, it took us about one and a half hours to bring the cluster. It took us around two days to complete the setup. After installing OpenShift, we needed to do some peripheral installations, such as authentication, creation of objects such as resource quota limitations, creation of templates, etc. In a maximum of two days, we were able to bring the cluster back into the required state.

In terms of maintenance, we have five clusters that are being taken care of by four people. My team doesn't only take care of OpenShift. We also take care of GitLab, so that also takes some resources. Overall, four people are taking care of five clusters.

The initial setup was complex; it was pretty complicated to set up the master, replication, turn ingress and egress, router, and configure the worker nodes, particularly the automatic scaling part of the worker nodes.

Version 3 is very complex but it's 1,000 times better than five years ago, and it's even much better than it was a year ago. The deployment was a pain point for our company, but it's irrelevant for someone buying it now. They have fixed a lot of stuff.

We have huge deployments, hundreds of nodes in a cluster. The deployment time is relative to the size of the cluster, but the deployment time has gone from a week to a day for a 100-node cluster. Red Hat has improved the process considerably.

The initial setup was relatively straightforward.

It's straightforward. The setup took two to three days.

I wasn't involved in its initial setup, but I talked to a lot of the people who were involved. Compared to a simple or Vanilla Kubernetes, it requires lots more work and has a lot of default processes constantly running, but, in my opinion, it's something where OpenShift is getting better and better. It's getting quicker. It's going in the right direction.

The deployment took a few days.

The initial setup of OpenShift is straightforward if you are an experienced platform engineer. Installing on AWS or Azure could be more complex. The product has a Terraform command to install everything.

If all of the tools that are needed and all the hardware is there, the implementation should be straightforward. I would rate the initial setup a four out of five overall.

The product's initial setup is very easy, especially compared to AWS.

The solution is deployed on a public cloud since half of the deployment is in the data center and half of it is in the cloud.

Initially, the setup seemed to be complex, but the recommendations from Red Hat, and especially on the CoreOS systems, for quality, stability, and security purposes, it seems to be complex. However, once we get hands-on experience, it is very, very useful and easily maintainable as well.

The tool's deployment takes a matter of hours to complete. You need a team of three to four to maintain the solution. 

The initial setup of OpenShift is complex. We have two types we do, but active active does not work, only active passive does.

Initially, the deployment process was complex. However, with repeated use, it made more sense. Deploying TIBCO BusinessWorks Container Edition and optimizing it on Red Hat OpenShift is complex.

Setting up OpenShift is pretty straightforward, and you can do it in under 30 minutes if you know what to do. We have four admins who maintain it. It requires a lot of maintenance because the underlying platform moves quickly. Kubernetes moves quickly, so new versions are constantly coming out. Keeping current requires lots of maintenance. We do upgrades monthly.

The initial setup of the solution was hard, and took around three months to deploy completely.

The implementation is not as straightforward as VMware products. It requires prior experience for easier deployment.

The initial setup was not done by me. I only work with the solution. 

The initial setup was a bit complex because we needed to configure the work upload and the master mode. We also need to run many containers inside to run the OpenShift Platform, which is complex. The deployment was done in-house with the help of Red Hat as an OEM.

The initial setup is in between straightforward and complex. It's not so easy but not that tough. But we do require a lot of training.

Our deployment took one month.

Based on feedback from my colleagues, the initial setup is complex with a lot of dependencies to set up the environment.

The initial setup on the OpenShift platform took us a long time to complete for the whole department. It took approximately one and a half months to set it up properly. 

Once the implementation was complete we started looking at how we can achieve reusable scripts for the developers. In a way that they can create the scripts in a quick fashion, instead of them doing the configuration and deployment themselves. It takes time for the implementation, and then it's complex overall too. Once you learn it, then it's quite easy.

The setup is straightforward if you understand concepts from a Kubernetes cluster development. I have done CoreOS cluster development so I am familiar with much of the setup.

Setting up OpenShift 4.0 is simple. It takes between 45 minutes and one hour. 

The solution is easy to configure and run.

We have deployed OpenShift on the cloud. It is a one-time setup and can take longer to deploy. Once implemented, the rest of the deployment becomes easier. I rate the process a six out of ten.

The initial setup is okay because there is a straightforward installation process to follow. It is guided by their people and they know how to implement things. We only faced an issue when we started running the infrastructure and that's when support was not up to the mark for OpenShift.

Deployment is quite fast because we have a CI/CD pipeline and we use GitLab for the source code. It can be done within 30 minutes or an hour for the UAT stage. When going to production, there will be a software assessment and then the time needed depends upon change requests and the change window for the application.

We have an implementation strategy for OpenShift. We have prepared a baseline saying that if a given application comes onboard with OpenShift, the team has to learn some basic technical stuff. They have to create a Dockerfile and create the source-to-image. Then they have to use the repository and onboard or copy their source code into it. The baseline documentation exists for people to follow. We will then deploy their application to OpenShift and there will be a dedicated team to further support the onboarding process.

The initial setup was very complex, but that's because we were deploying v3.1 which was only the second release.

Now the Ansible installer is much more robust and offers more options to customize the deployments.

Installation documentation has also improved a lot.

The initial installation is trivial. Red Hat has automated the installation using Ansible.

The initial setup is simple, and OpenShift is open-source, so it's easy to install on any cloud platform.

The initial setup was not straightforward. You must understand every single component. Only then is everything clear and goes fast. Teaching developers how to implement the application with new methodology is problematic.

The initial setup was very simple. It was done by our devops team. They did the entire deployment. 

The first installations were tricky. There were some bugs and workarounds, but it was never hard.

Newer versions were smoother and the problems no longer exist.

Linux in general is a different flavor. Nothing out of the unexpected. Though, as in all things, there is room for improvement. One solid BIN would be nice.

In the installation of ORIGIN, using the playbook and Ansible install in the Docker, there are fixed points which would make the install easier.

The installation is better now than early on and can be complicated to set up if you are not familiar with Red Hat Linux and Docker.

This was my first installation. It was not straightforward due to internal limitations, not the product.

The initial setup was straightforward; not complex.

The initial setup is straightforward, it took around three to four days. We used the support and four or five of our engineering personnel for deployment.