- Taschenbuch: 155 Seiten
- Verlag: O'Reilly and Associates; Auflage: 1 (11. Juni 2013)
- Sprache: Englisch
- ISBN-10: 1449335837
- ISBN-13: 978-1449335830
- Größe und/oder Gewicht: 17,8 x 1 x 23,3 cm
- Durchschnittliche Kundenbewertung: 2 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 65.599 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Vagrant: Up and Running (Englisch) Taschenbuch – 11. Juni 2013
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
Mitchell Hashimoto is a passionate engineer, professional speaker, and entrepreneur. Mitchell has been creating and contributing to open source software for almost a decade. He has spoken at dozens of conferences about his work, such as VelocityConf, OSCON, FOSDEM, and more. Mitchell is the founder of HashiCorp, a company whose goal is to make the best DevOps tools in the world, including Vagrant. Prior to HashiCorp, Mitchell spent five years as a web developer and another four as an operations engineer.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Das Buch ist ausgesprochen verständlich geschrieben, folgt einem logischen und sinnvollen roten Faden und steigt nach und nach in die Konzepte und Ideen von Vagrant ein: Beginnt man zunächst mit dem Aufsetzen einer neuen virtuellen Maschine, geht es danach um deren Fernsteuerung, deren Konfiguration und zu guter letzt um die Erweiterbarkeit von Vagrant.
Besonders gut hat mir gefallen, dass das Buch kompakt ist und seinen Inhalt auf den Punkt bringt: Kein unnötiges Blabla, sondern eine gute Einführung mit einem Blick über den Tellerrand, die nicht künstlich aufgeblasen wurde, nur damit man ein Buch mit mehr als 130 Seiten verkaufen kann. Weniger ist mehr :-).
Insofern kann ich das Buch nur jedem ans Herz legen, der sich mit Vagrant beschäftigen möchte. Großes Lob und Kompliment an Autor und Verlag für eine wirklich ausgezeichnete Leistung!
Wer sich einen ersten Einblick in Vagrant verschaffen möchte ist mit diesem Buch bestens bedient. Es eignet sich aber nicht nur für Anfänger, den es werden alle Kernfunktionen von Vagrant beschrieben.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
The last chapter covers Vagrant plugins and should be very helpful for plugin developers. Mitchell does a good job of explaining how to create command, configuration and provisioner plugins, and he steps through several complete examples in this section of the book. In my opinion, this chapter is the best existing documentation on Vagrant plugin development.
However, I'm only giving this book three stars because as good as it is I think it still leaves a lot to be desired. There are numerous spelling and grammar errors in the book. The quality of writing isn't particularly good; for example, there is an awful lot of repetitive writing that is tiresome to read and just feels like filler, and the way v1 vs v2 configuration is described and handled in the book felt awkward.
But the biggest problem with the book is the plugin chapter (which, interestingly, is also probably the most valuable part of the book!). In particular, there are two problematic aspects.
First, by Mitchell's own admission this chapter's coverage of plugin development is incomplete. He explains this is because the API and architecture of host, guest and provider plugins aren't that common and are also about to undergo major changes. Personally, I think if these plugin types are so uncommon then it is actually more important to cover them here, because there will be fewer examples in the wild that other developers can study. Also, I wonder why he and O'Reilly didn't just hold publication until after the API changes. In my opinion it would be better to wait longer for the book to come out if that means its coverage will be more comprehensive, rather than ending the most valuable chapter in the book with "there's this other stuff I didn't want to talk about, but if you're curious you can always read the source."
Second, the difference between the v1 and v2 configurations is confusing. Mitchell explains this is because the v1.1 series introduced some non-backwards compatible changes (and then he repeats this several more times throughout the rest of the chapter), but it still just feels... half-baked. I applaud Vagrant's commitment to backwards compatibility, and I understand the technical reasons as he explains them. But the way it is handled just feels awkward. I wonder if it wouldn't have been better just to focus exclusively on the v1 configuration and never mention the existence of the v2 configuration. Since the v1.0 series is the current stable release and v2.0 is still a ways off, I think it would be fine to only cover the stable configuration and leave the newer stuff to a future edition of the book. Alternatively, as I mentioned before, I think he and O'Reilly should have delayed publication until Vagrant 2.0. It just feels muddled that there are these different configuration versions, and he goes to such pains to explain them and the reason why they exist and what Vagrant's version numbers mean, but then he skips discussing a few different plugin types because they're about to change.
In about 4 hours, I was able to work through the first six of seven chapters of the book, including time to experiment with creating and destroying Vagrant environments. The last little exercise was creating a two-node cluster, one of which installed and ran MySQL, the other installed and ran Apache. And then confirming that networking was running properly between them, and the host. Along the way, I won't say I gained a complete education on the ins and outs of Vagrant, but I learned much, and now feel confident that I can go to Vagrant's online documentation and find any further information I need. This book did a great job of explaining the why as well as the how of Vagrant.
Considering I got this as a Kindle book for about half the print price, it was really a great bargain. If you're looking to bootstrap your knowledge of Vagrant, I recommend this book.
(One little sidenote: If you try the hostonly example, and the 192.168.33.* subnet doesn't work for you, try 192.168.133.*.)
It's short, clear and sufficient to get "up and running" - I read most of it over a (busy) weekend and by the end of it I had two boxes up and running with Apache Mesos (master/agent) happily talking to each other.
My main gripe with the book is that it's now more than two years old and it only talks about the v1 syntax - this is now so outdated that you can't even find the reference documentation on the website (at least, not easily): this is not made clear enough in the book's page and it should be, instead, IMO a big red WARN flag.
Ideally, I'd love it if the author were to update it to use the v2 sintax of Vagrant - were that the case, this book would easily get 5 stars.
It is a good overview -- more complete than the web site, but some of the examples and commands are out-dated. I am having to go through both the web site and the book, making notes about the "correct" commands. This was not a complete waste of money, but it certainly was not the "valuable resource" I was hoping for.
I contribute to the open source projects I use and like. I guess this was my contribution to Vagrant.
Don't get me wrong about Vagrant. I still am quite happy with what it is doing for me! I just wish the book was up-to-date.