[colug-432] 2015-10-21 Vagrant Scribbles

[Joseph Beard]

Thanks for these notes! You had a question in your notes that I
realize now that I forgot to address.

> vagrant destroy -f (to force it for misbehaving ?)

The `-f` flag does nothing more than skip the prompt asking if I am
sure that I want to destroy the VM. A small time saver for when I
really am sure; nothing more.

Thanks everyone for coming! The slides are available at
https://dl.dropboxusercontent.com/u/18693508/2015-10-21-COLUG-Skip_the_Excuse.pdf


Joe
--
Joseph Beard
joseph at josephbeard.net


On Thu, Oct 22, 2015 at 03:39:27PM -0400, jep200404 at columbus.rr.com wrote:
> LOPSA is having DevOpsDays Ohio 2015
> 2015-11-18 and 2015-11-19
> The Bluestone 583 E Broad St
> 8 formal presentations?
> more open spaces
> 
> 2015-10-21 COLUG at Covermymeds
> 
> Joseph Beard presented about Vagrant
> He uses VMware
> 
> Vagrant creates, manages, distributes
>     portable development environments (in VMs)
> linux guests (and newly Windows guests)
> vagrant init hashicortp/precise64
>     creates vagrant file, which is config file for VM
> 
> vagrant up
>     reads config file, does complete setup of VM, ending with running VM
>     takes time
> defaults to same common key for all vagrant instances (NOT SECURE)
> can generate unique keys if needed
> 
> vagrant ssh (ssh: into a running instance)
> has full root access by default (NOT SECURE)
> 
> /vagrant is separate mount with persistence even after destroying VM
> /vagrant/Vagrantfile is visible to machine using it
> 
> vagrant rdp (for into Windows with a remote desktop)
> 
> vagrant halt
>     graceful shutdown (does not destroy)
> (next) vagrant up
>     just boots previously made VM
> 
> vagrant provision to redo provisioning
> provisioning is the customization of a stock image
> vagrant status
> vagrant destroy (shuts down and delete VM)
> vagrant destroy -f (to force it for misbehaving ?)
> vagrant share
>     allows others to acces the VM
>     (handy for testers)
> 
> vagrant can be used in continuous ingregration
> 
> to deploy, use provisioning scripts same as vagrant used
> 
> vagrant eases dealing with multiple projects with conflicting dependencies
> 
> makes it easier to bring on a new developer
> 
> packer 
>     makes tarball of VM
>     can generate images for production for various hypervisors
>         how relevant are those images for production
>         considering vagrant's absence of security?
> 
> pgrep
> 
> vagrantcloud.com has many VM images
>     seems to have been subsumed by atlas.hashicorp.com
> 
> As discussed recently on mailing list
> Vagrant Up and Running
>     is out of date
>     ideas are good
>     syntax is old version
> 
> also as discussed on mailing list
>     hashicorp only documents current version
>     dox are not available for previous versions
> 
> VMware plugin $80?
> VMware $300?
> 
> vagrant repo
> vagrant can be used with docker containers
> he demonstrated such. it was fast
> 
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> 
> writing script to go through directories,
> find all the man pages and convert them to all the popular ebook formats
> 
> wp: prefix means Wikipedia
> To get good answers, consider following the advice in the links below.
> http://catb.org/~esr/faqs/smart-questions.html
> http://web.archive.org/web/20090627155454/www.greenend.org.uk/rjk/2000/06/14/quoting.html
> 
> wp:Silent Circle (software)
> Silent Text
> 
> wp:4chan
> wp:8chan
> _______________________________________________
> colug-432 mailing list
> colug-432 at colug.net
> http://lists.colug.net/mailman/listinfo/colug-432

-- 
Joseph Beard
joseph at josephbeard.net
@jbeard6