The initial setup of Pivotal Cloud Foundry is straightforward.

Regarding the setup phase, every step is a hurdle. With Pivotal Cloud Foundry, I won't get any proper resources for that. Even if I Google it, there is no proper solution for Pivotal Cloud Foundry. However, if we go for Azure or some other cloud, we can get a lot of information. I believe there is not much information for Pivotal Cloud Foundry since it may be some license issue. If you go for Azure, the migration process is straightforward.

Since we have been given 10 GB of space in the public cloud, we are utilizing it in our company. So, we are trying to deploy our application on the cloud, and for us, it is like a trial process for now. From our total application rate, I can say that only two to three percent is on Pivotal Cloud Foundry. Currently, half of the code is in the shell script, which is causing issues. Also, most people in my organization have worked on Java-related code. For most of the applications, they are using the same, that is, shell script and AUTOsist, and so we haven't migrated yet. So that is the reason that we are planning to opt for a hybrid model so that we don't have to migrate completely to Pivotal Cloud Foundry.

I won't be able to comment on the setup process since I am not a member of the infrastructure team. In our organization, we have deployed Pivotal Cloud Foundry on a private cloud.

For the initial setup, we have to follow certain processes, so it's not just the Pivotal issue. The actual cloud's computer probably takes five minutes to maybe ten minutes. But we need to do lots of checks and stuff, so deployment will probably take around four hours.

Typically, the deployment takes less than 30 minutes, especially for the Pivotal platform foundation, as the setup of the platform is quite complex. It is done by the central platform team, who are experts. If there are any issues, they can also quickly resolve them.

The Pivotal Cloud Foundry's initial setup has a learning curve for my team, but it was easy to use.

Pivotal Cloud Foundry is easy to install. It is relatively easy to install in a data center. We use a BOSH software, which allows us to install the Pivotal Cloud Foundry on multiple systems and virtual machines.

The initial setup isn't too bad. I'd rate the product seven out of ten. 

We found difficulties migrating from PCF1 to PCF2. However, the initial enhancement should be seamless, and it is easy to move the code seamlessly without much effort.

The deployment takes some time. It took three to six months to move everything to a new server.

The initial setup was not that challenging. It is a console-based interface where you can push the apps to deploy and see everything. However, when there is a migration, there is a challenge to move from one version to the upgraded version.

We had a big team involved as it was an effort to keep the data centers up and install the solution. 

There would be maintenance involved since you need to upgrade the latest JDK along with the containers. You do that when the earlier JDK becomes vulnerable to the dependencies. We have an infra team that takes care of maintenance. 

The initial setup of Pivotal Cloud Foundry is complicated. However, we made it easy by automating it. It took us approximately one week to complete.

The initial setup was not easy, it was a bit complex.

The initial setup was straightforward. 

The setup is not straightforward in PCF, there's a lot of configuration. It takes a lot of time to connect to third-party applications and it is a complex process.

The initial setup is a little complex compared to other products.

Many of our deployments are hybrid because our clients do not want to lose their existing infrastructure. On average, it takes one and a half to two hours to deploy, depending on how much troubleshooting we have to do.

The initial setup was very easy. Deployment takes maybe half a day.

The initial setup is straightforward, and it provided a good integration with Venafi. I rate it eight out of ten.