HashiCorp Packer vs. HashiCorp Vagrant vs. IBM DevOps Code ClearCase

We use packer to generate new machine images for multiple platforms on every change to our Configuration Management tools like Chef/Puppet/Ansible It's act single tool for Image building for Multi-provider like AWS/Azure/GCP Helps to achieve Dev/Prod Parity Packer itself doesn't have a state like Terraform. You can't do packer output AMI ID. If you have a scenario where you want to maintain the state for images it would be tough to manage via Packer.

Incentivized

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

IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control

Incentivized

• Multi-provider portability
• Greater testability
• Super fast infrastructure deployment

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

• Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
• Rational ClearCase handles parallel development of many dependent applications really well.
• The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.

Incentivized

• Manageability
• Manageability
• Manageability

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

• Extremely buggy.
• Sometimes the repository gets locked for no reason.
• Slow.

Incentivized

We are happy with the use of Packer in our organization. Apart from manageability, I don't find any other drawback with Packer.

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

It's best for building Image with many features and benefits.

Incentivized

A GUI would be nice for entry level users.

Incentivized

I only once required support and it was very smooth.

Incentivized

I haven't found any issue in Implementation that itself describes how well this tool is built.

Incentivized

There are lot of tools in market which does the job for Image creation but all of them are not complete Machine/Image as a code. All other alternatives can create Image partially. Main reason for selecting Packer are Packer is lightweight, portable, and command-line driven Packer helps keep development, staging, and production as similar as possible. Packer automates the creation of any type of machine image Multi-provider portability is the feature to die for

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

If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.

Incentivized

• Super fast infrastructure deployment
• Quick turnaround of infrastructure in multiple cloud using single tool.
• Increase productivity by reducing time in infrastructure building.

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

• Managed code versioning for many years.
• Only one person can edit code at a time - slows processing down.
• IBM is an expensive product to support.

Incentivized