I've been doing this for so long. We've been doing VMware since 2.X. It was all done on-premise. We had support back in the day if there was an implementation problem. We had support on the phone with us until it was resolved. We had more problems back when it was still called VMTurbo. When I called support, I would get a senior engineer who actually wrote code for VMTurbo instead of a support desk. 

We just worked with Turbonomic. Cisco was our reseller, but they actually provide Turbonomic resources.

We have only two people involved with setup and maintenance. I have one main person with a backup person for him. That is how easy it is to set up and maintain. Our future plans are to migrate to the cloud offering probably later this year. Once we do that, that will free up one person.

The main guy is a Windows Server admin who supports the Turbonomic platform, but this isn't his only job. It is something that just takes up a fraction of his time. Once we go to the cloud offering, then the management of the tool goes back to Turbonomic and we will just be a consumer of the data.

We did it ourselves with the help of Turbonomic engineers. It probably took us two months because of the processes that we had to follow.

It required people from all areas. We needed people from security, on-prem data center management, and storage teams, but they were not required for the entire two months. On average, three to four people were required on a need basis.

We did the implementation ourselves. It took one guy to deploy it.

My group built a couple of the VMs that we needed and installed it. It took a couple of days. As far as gathering information, you don't have to put agents on any servers or anything like that. You give a user an ID for vCenter, and we have multiple vCenters.

The product was purchased from reseller CDI and I recommend them.

We deployed it ourselves but received assistance directly from Turbonomic.

With respect to product maintenance, it's a fairly hands-off tool. 

We're trying to hand off some of the routine maintenance windows. A lot of the predefined actions are in there but it's a case of setting the window based on our approved maintenance times for reclamation of resources.

If it's a change that involves policy and configuration then the change will be by a senior engineer or someone a little bit higher, because the change can be disruptive if it's not configured correctly. Otherwise, it's fairly hands-off.

The team even considers it an employee at certain times. For storage migrations, as an example, tasks that we had an administrator dedicated to, such as moving workload after workload, have now been assumed by Turbonomic.

We used Turbonomic for everything to do with the setup. On our side, it required about five FTEs, who were engineering and operations personnel. There were folks who were creating the design and where it would be rolled out. That design was passed down to the operations folks who were actually implementing everything. So, it was done in phases.

We only have two engineers doing maintenance, a primary and a backup, and this is like their extracurricular activity.

IBM Turbonomic helped us with the implementation. They were a great partner.

Resources from Turbonomic assisted us with the deployment. They were very knowledgeable and were able to help our staff, who had never used the product before, understand it very quickly.

Our internal resources worked with the Turbonomic team. After that, I turned over the application to the team that is going to be supporting the applications, because I have no insight into applications. That's not my role. Turbonomic is meant to be in their hands, not mine.

There were three to four people involved initially. Once you get it installed, you start bringing in your DevOps engineers to have them understand it, and they'll work with the application support people. 

The team grows as large as it has to, depending on how many application teams and DevOps engineers you have. People can manage their applications or they can manage multiple applications. You can divide it up, so the teams vary in size. But it's always going to land as close to the application as it can, to get the right people to make the right decisions. If you're a very large organization, you don't centralize the product. It doesn't work well that way.

Working with Turbonomic consultants, the deployment was probably a couple of days. That was more to familiarize ourselves with the environment, what the commands were, etc. It was not a function of the complexity of the tool.

We don't have many people working on the product. We have about three people going through the testing and PoC environment right now and setting it up for deployment in our dev stage, and then finally in our production environment. There are about three individuals working on that. 

Because the product is self-managing in many ways and runs the way that it does, i.e., it runs as an application inside of OpenShift, I would probably dedicate half a resource from the OpenShift side to managing Turbonomic over the long-term.

Maintenance is necessary, and one person is sufficient for the task.

We did this all in-house with the help of VMTurbo.

I did the deployment of the appliance by myself while the configuration of the group policies and rules was done with Turbonomic's assistance. There were two of us from my company who were focused on the deployment and we had two or three individuals on it from Turbonomic.

In-house.

In-house.

No, we did it ourselves with relatively minimal support from VMTurbo.

In-house.

In-house team, with some recommendations from Turbonomic engineers.

We did the implementation in-house.

In-house.

We implemented it with the help of VMTurbo team.

Deployed was completed in-house.

Since we were an early adopter, the deployment was performed with in-house staff on a WebEx with Turbonomiocs, although it is simple enough that you do not really need assistance with it.

Vendor team. They were knowledgeable and the deployment was pretty smooth.

implemented in-house.

We installed the appliance.

We implemented in-house

The implementation was done in-house.

In-house.

There are only a couple of us who actually handle the updates. It is mostly used by my network administrators. There are about ten of us who actually use the tool to make adjustments in our VMware environment. It's pretty much just my VMware administrators who utilize the tool.

In-house, as it was very straightforward.

It was very easy because it's a virtual appliance. We were able to download it into our network, connect it to vSphere, and within a few minutes of scanning our environment, it was able to plug in and connect to all of our VMs, and manage them for us.

I was still having to babysit a lot of the VMotion requirements for my environment. I was having to move things around manually. VMTurbo has promised, and the promise they delivered on was no more manual VMotions for eight months. That's been a huge time saver for me, and I can trust it to take care of my environment.

Our initial build was done in-house and was followed up with a training session. The trainer was knowledgeable, but we have received a higher level tech advice, as we moved forward, from other resources at Turbonomic.

In house.

We did the intial deployment in house - we've had Turbonomic onsite to help us tune the product to our specifications.

In house.

In-house

In-house. I had contacted support on an as-need basis.

We implemented with an in-house team after a week of onsite training at Turbonomic's office.

Our in-house team implemented the solution in an afternoon.

We implemented in-house but had a vendor team in for group training to show us how to better use the tools.

In-house.

In-house.

I implemented the solution myself, I did receive help from my sales contact via WebExs for some things I wasn't sure about.

In house.

Our implementation was done through an in-house team. No problems were experienced, and the install was well documented and straightforward.

A vendor team who was excellent.

Implemented on my own.

In-house.

The vendor has been very helpful in getting the software installed and configured. They are extremely knowledgeable and professional.

The implementation was in-house.

In-house.

Turbonomic performed the implementation. The initial setup was done fairly quickly by a very competent tech.

In-house with the help of their Technical Support team.

In-house deployment.

VMturbo support/presales team installed via remote desktop.

We deployed in-house.

Was able to do it myself with very little vendor help. Startup package is include with purchase.

In-house team with help from the Turbonomic technical team

I implemented it myself.

In-house, with assistance from Turbonomic.

Implementation was done by an in-house team.

In-house, implemented it myself.

Vendor team, good level of expertise.

After registering for an extended trial license, the implementation was done by our in-house team under continuous support from Turbonomic consulting.

In-house team.

We were assisted by a vendor team; very knowledgeable.

An in-house team implemented it.

Implemented with Turbonomic.

We implemented directly with Turbonomic and it was one of the easiest implementation we have had.

In-house, with the help of support for configuration.

We implemented in-house.

It was just in-house combined with support from sales/tech support.

We worked with the vendor's staff. They helped with training and setup. They are really top notch.

We implemented this ourselves.

In-house

We implemented in-house with no issues.

Not in initial implementation, but for upgrades we use Turbonomic support to help us and have great results.

In-house.

In house/directly with VMTurbo.

I implemented the appliance myself with the help of VMTurbo

In House.

We purchased direct, and implementation was done via a WebEx.

In-house.

We used a vendor as well as Turbonomic support to get going initially.

We went through in-house. Their knowledge was very good.

In-house with input from application vendor.

Through a vendor. They took the time to explain everything and show us how to get the ball rolling.

In-house.

In-house.

In-house.

In-house implementation.

It was implemented in-house by myself.

We tried both ways.

In-house, with Turbonomic's assistance

All implementation was done in-house with no initial input from Turbonomic.

In-house

In-house.

We implemented ourselves with remote support from Turbonomic.

Over the phone assistance with internal staff. It was great. There were no problems.

In-house team only.

Vendor

The implementation was done in-house with assistance from Turbonomic's engineers.

Implementation was performed through an in-house team with Turbonomic staff available for WebEx for assistance.

In-house.

In-house.

In-house

This was installed in-house.

In-house implementation.

In-house.

In-house.

I implemented this myself.

Direct from Turbonomic.

Me, myself, and I.

We set it up with Tubonomic's help.

In-house.

In-house.

We implemented this solution in-house.

Implementation was done in-house.

For final tuning and automation features we got help from technical support.

Installation took place a little before my time. But as far as what I can gather, it was a hybrid of in-house and vendor. The installation was performed via a RD session.

This was in-house.

In-House!

We implemented through an in-house team.

In-house.

In-house deployment was our method.

The team of me, myself and I.

In-house.

we Didn't implement with a vendor. We did alone only with Turbonomic support. It was very easy this deploy

The setup was done in-house.

We worked directly with Turbonomic - although it was called VMTurbo at the time. Obviously, their expertise was second to none.

Through our Business Partners. They learnt as they went but did a good job overall

In-house.

Deployed through in house team.

I did it by myself

We implemented in-house.

In-house.

In-house, directly through Turbonomic.

We implemented ourselves with minimal VMTurbo support.

In-house.

We implemented in-house with the use of Turbonimics legendary support.

In-house team.

In-house team was easily able to install.

In-house with assistance from Turbonmic support team. Smooth process.

In house. The solution did not seem intimidating enough to require engagement of an outside resource. That being said, we have not implemented all of the features of Turbonomic either. Perhaps with a Vendor would would have had a greater feature set in place.

I don't recall it was a while ago.

The vendor team assisted with the implementation and we didn't encounter any issues, so they knew what they were doing.

We implemented it in-house.

In-house team.

In-house team.

In house team.

We implemented ourselves, with VMTurbo support.

In-house.

Through an in-house team.

Vendor team, easy implementation.