HashiCorp Vagrant vs. VMware Cloud Director

I would recommend this tool to a colleague looking to create a repeatably deployable local dev environment based on their staging and production environments. I would recommend this mostly for individuals or teams requiring environments with server-side software such as php, et al. There are likely less processor-heavy and smaller tools for simpler projects.

Incentivized

If you have a lot of customers that all need to have a separate place to work in, without the possibility of getting in each other way, and you want to safe yourself a lot of work. Than I strongly recommend you Cloud director. Ofcourse, only if you have a VMware environment as your working environment. If you just have a small group of customers and you can easily handle the work that's coming from it, then it is overkill to add cloud director to your environment. In a later station, you can always introduce cloud director (so tis never to late if you still want to use it)

Incentivized

• Vagrant is decentralized so anyone can make a container package to get a project started. you aren't limited to wordpress, or even one style of wordpress install (you can make a sage.io wordpress environment).
• Vagrant easily lets you set ports and URLs for local development.
• I have yet to have a problem with Vagrant, as opposed to MAMP and DesktopServer, which both gave me SQL or other issues.

Incentivized

• Building virtual racks
• Managing the customers' network and security
• Simplicity but the completeness of IaaS solution
• Integration with major software providers

Incentivized

• Because Vagrant is a low-level tool with many ways to configure it, there is a steep learning curve. You don't just have to learn (or install) Vagrant, but also Virtualbox, Ansible and possibly some Vagrant plugins to keep boxes up to date.
• Support on Windows doesn't seem great. I'm a Mac guy, so it's been very difficult getting things to work as expected when a developer wants to work on Windows.
• Perhaps I didn't configure it correctly, but the default shared folders are not the best for performance. There are also frequently weird issues regarding file permissions.

Incentivized

• The add-on/extension required on the internet browser sometimes are difficult to get working at first. We've experience instances where the add-on/extension latest versions will not work and have to downgrade to an older version.
• The server console lacks features and tools. For example it would be useful to have a copy and paste tool or a file upload tool.
• The vCloud Director management site uses Adobe Flash, which makes it impossible to use on a mobile device.

Incentivized

Vagrant is fast, versatile and does exactly what we need it to do: spin up virtual servers for local development fast and without trouble.

Incentivized

A GUI would be nice for entry level users.

Incentivized

I liked lando better because lando seemed extremely easy to setup compared to other VM's and it seemed faster though that project was simpler. Virtualbox I ran on windows and it has a gui and has often been slow. The vagrant boxes I used did well but had slightly more problems than lando.

Incentivized

vCloud Director is definitely my favorite as far as cloud managers. The only thing that compares is Cisco UCS Director, but it has slightly different functionality and purpose. I understand why a lot of clients still go with vCloud Director even though VMware intends to sunset it

Incentivized

• Vagrant is free - It requires a bit of extra technical knowledge in terms of setup, but since it costs nothing it's an excellent resource
• It can be time consuming to learn, but once you get a good handle on it you're in good shape.

Incentivized

• Saves a lot of time, and time is money
• Stable, so little to non downtime
• With P1 , good support

Incentivized