Wow - I'm excited about the provider interface, especially for AWS and the other cloud services.
Question - could Vagrant work with LXC?
Vagrant 1.1, VMware Fusion
11–20 of 25 posts
Re: Vagrant 1.1, VMware Fusion
#12Wow - I'm excited about the provider interface, especially for AWS and the other cloud services. Question - could Vagrant work with LXC?
> Question - could Vagrant work with LXC?
Easily.
Re: Vagrant 1.1, VMware Fusion
#13In general a cool release, mostly because it finally adds providers. However, given the price point of 79 USD per seat, I can hold my breath a little longer, especially since VMWare adds another 50-70 Euros on top of that. That's somewhere in the ballpark of 140 USD to replace something that's basically working fine.
I don't think you need to use VMWare. I understood from the article that you can upgrade to 1.1 and continue to use VirtualBox as the provider with basically no hiccups.
Re: Vagrant 1.1, VMware Fusion
#14Whew. This was/is a big one. Vagrant 1.1 is the first release in Vagrant's history that is provider-agnostic. I'm shipping a Fusion provider and open source AWS and RackSpace provider, but the interface itself is completely open source and documented, meaning anyone can add their own providers: http://docs.vagrantup.com/v2/plugins/providers.html And the provider API was introduced while retaining full compatibility f…
Can you comment on compatibility.
For example, if I decide to buy VMware Fusion for a team of 6 developers today (Professional costs 45 EUR*6 = 270 EUR).
Will I have to spend the same amount each year again or are you going to support each version (and potential changes to the APIs) down the road? I have no idea how drastic changes are going to be from Fusion 5 to 6 and beyond.
From reading your announcement, it seems like your plugin is a one time fee. I've seen other companies try this business model for software only to replace it with a yearly license down the road. Any thoughts on this?
Does the email support include a response time, etc.?
Re: Vagrant 1.1, VMware Fusion
#15Whew. This was/is a big one. Vagrant 1.1 is the first release in Vagrant's history that is provider-agnostic. I'm shipping a Fusion provider and open source AWS and RackSpace provider, but the interface itself is completely open source and documented, meaning anyone can add their own providers: http://docs.vagrantup.com/v2/plugins/providers.html And the provider API was introduced while retaining full compatibility f…
Can you comment on compatibility. For example, if I decide to buy VMware Fusion for a team of 6 developers today (Professional costs 45 EUR*6 = 270 EUR). Will I have to spend the same amount each year again or are you going to support each version (and potential changes to the APIs) down the road? I have no idea how drastic changes are going to be from Fusion 5 to 6 and beyond. From reading your announcement, it seem…
And I forgot another — any thoughts on volume licenses? E.g. a pack of 10.
Re: Vagrant 1.1, VMware Fusion
#16Wow - I'm excited about the provider interface, especially for AWS and the other cloud services. Question - could Vagrant work with LXC?
I'm on it https://github.com/fgrehm/vagrant-lxc ;)
I need to make it work as a real Vagrant plugin since I started it before 1.1 was actually released
Re: Vagrant 1.1, VMware Fusion
#17Whew. This was/is a big one. Vagrant 1.1 is the first release in Vagrant's history that is provider-agnostic. I'm shipping a Fusion provider and open source AWS and RackSpace provider, but the interface itself is completely open source and documented, meaning anyone can add their own providers: http://docs.vagrantup.com/v2/plugins/providers.html And the provider API was introduced while retaining full compatibility f…
Congratulations! Vagrant is awesome. The blog post says that future releases in the 1.x series will not necessarily be backwards compatible. Does this mean you are not adhering to SemVer? If so, why not?
This is a great question as well. I'm a little concerned by this choice because I'm not looking forward to constantly enforcing updates all across the board.
Re: Vagrant 1.1, VMware Fusion
#18In general a cool release, mostly because it finally adds providers. However, given the price point of 79 USD per seat, I can hold my breath a little longer, especially since VMWare adds another 50-70 Euros on top of that. That's somewhere in the ballpark of 140 USD to replace something that's basically working fine.
I don't think you need to use VMWare. I understood from the article that you can upgrade to 1.1 and continue to use VirtualBox as the provider with basically no hiccups.
Yeah, I must admit I was confused by this as well. Do we need Fusion + a license for the Vagrant VMWare provider, or is the Vagrant VMWare provider stand-alone?
Re: Vagrant 1.1, VMware Fusion
#19Whew. This was/is a big one. Vagrant 1.1 is the first release in Vagrant's history that is provider-agnostic. I'm shipping a Fusion provider and open source AWS and RackSpace provider, but the interface itself is completely open source and documented, meaning anyone can add their own providers: http://docs.vagrantup.com/v2/plugins/providers.html And the provider API was introduced while retaining full compatibility f…
Can you comment on compatibility. For example, if I decide to buy VMware Fusion for a team of 6 developers today (Professional costs 45 EUR*6 = 270 EUR). Will I have to spend the same amount each year again or are you going to support each version (and potential changes to the APIs) down the road? I have no idea how drastic changes are going to be from Fusion 5 to 6 and beyond. From reading your announcement, it seem…
There may be an upgrade fee associated with new versions. I haven't decided yet. Even if there is, it won't be the full cost of the license.
I won't ever charge an annual license fee is because the long term business model of HashiCorp is _not_ licenses. This is just a way to keep going and have folks support Vagrant.
Email includes a 48 hour response time.
Contact me at mitchell@hashicorp.com and I'd love to talk to you about this in more detail.
Re: Vagrant 1.1, VMware Fusion
#20Whew. This was/is a big one. Vagrant 1.1 is the first release in Vagrant's history that is provider-agnostic. I'm shipping a Fusion provider and open source AWS and RackSpace provider, but the interface itself is completely open source and documented, meaning anyone can add their own providers: http://docs.vagrantup.com/v2/plugins/providers.html And the provider API was introduced while retaining full compatibility f…
Congratulations! Vagrant is awesome. The blog post says that future releases in the 1.x series will not necessarily be backwards compatible. Does this mean you are not adhering to SemVer? If so, why not?
Yes, I don't adhere to SemVer. I am sorry. If it helps, you can think of it as SemVer if you make the SECOND number the major version (according to semver terminology, it is the X, in X.Y.Z).
I always say this warning to disclaim myself from future backwards incompatibilities, but if I follow 1.x like 0.x at all, then they'll be minimal.
Vagrant 2.0, of course, will introduce long term stability, like Vagrant 1.0. But that is far off. :)