Fedora 20 で Vagrant を試してみる

2016年1月27日

この 2 年とてもじゃないけど色々試す余裕が心身共になかった。何度会社を辞めようかと思ったことか判らない。

この歳になってすり減らされるのはキツイ。
最近、やっと少しだけ余裕が見えてきた。周りでは当たり前のように使われている
vagrant と puppet を触ってみたいと思っている。

まず必要なのは VirtualBox と Vagrant。 インストールは yum からでも、下記公式サイト
どちらからダウンロードしてインストールしてもいいと思うけど、yum でインストール
できるのが若干古いので、公式サイトからダウンロードした。

1. VirtualBox と Vagrant のインストール

ORACLE VirtualBox のサイトよりダウンロードしてインストールした。

2. Vagrant で仮想マシンを作る

Vagrant は仮想環境の自動構築、自動破棄ができると後輩たちから聞いている。
これは楽ちんだなー 全員の環境同じにとか簡単にできそうだ。
ちょっと触った感じだとこんな感じの特徴があるのかな?

  • ディレクトリごとに使い分ける
  • OSイメージを box と呼ぶらしい
  • 一度 box
    をダウンロードしたらキャッシュして、何度もダウンロードしない
    \~/.vagrant.d/ にキャッシュされる
  • クライアントが Windows でも OK

後で Puppet を試したいので、Puppet Labs が配布している Ubuntu 13.10
Server を使ってみることにした。

http://puppet-vagrant-boxes.puppetlabs.com/ まず、vagrant init で
Vagrantfile というファイルを作るようだ。

$ vagrant init ub1310-puppet http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-1310-x64-virtualbox-puppet.box
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.

これでできた Vagrantfile がこちら

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "ub1310-puppet"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  config.vm.box_url = "http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-1310-x64-virtualbox-puppet.box"

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # If true, then any SSH connections made will enable agent forwarding.
  # Default value: false
  # config.ssh.forward_agent = true

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
  # end
  #
  # View the documentation for the provider you're using for more
  # information on available options.

  # Enable provisioning with CFEngine. CFEngine Community packages are
  # automatically installed. For example, configure the host as a
  # policy server and optionally a policy file to run:
  #
  # config.vm.provision "cfengine" do |cf|
  #   cf.am_policy_hub = true
  #   # cf.run_file = "motd.cf"
  # end
  #
  # You can also configure and bootstrap a client to an existing
  # policy server:
  #
  # config.vm.provision "cfengine" do |cf|
  #   cf.policy_server_address = "10.0.2.15"
  # end

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file default.pp in the manifests_path directory.
  #
  # config.vm.provision "puppet" do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "site.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding
  # some recipes and/or roles.
  #
  # config.vm.provision "chef_solo" do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { mysql_password: "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision "chef_client" do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # If you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
end  

使用する box の指定を vagrant init で行ったら、次に box
のダウンロードと仮想マシン作成と起動を行うのが vagrant up。

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ub1310-puppet' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Adding box 'ub1310-puppet' (v0) for provider: virtualbox
    default: Downloading: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-1310-x64-virtualbox-puppet.box
==> default: Successfully added box 'ub1310-puppet' (v0) for 'virtualbox'!
==> default: Importing base box 'ub1310-puppet'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: ub1310-puppet_default_1401608862255_31673
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => /home/miyamiya/vagrant/ub1310-puppet

3. Vagrant で作った仮想マシンに接続する

作成した仮想マシンに接続するには vagrant ssh と叩く。

$ vagrant ssh
Welcome to Ubuntu 13.10 (GNU/Linux 3.11.0-12-generic x86_64)

 * Documentation:  https://help.ubuntu.com/
Last login: Thu Jan 16 16:49:46 2014 from 10.0.2.2
vagrant@ubuntu1310:~$

実はなぜか一回目起動しきれなかったので、停止削除をして作りなおした。

$ vagrant halt      # 仮想マシンの停止
$ vagrant destroy   # 仮想マシンの破棄
$ vagrant up        # 仮想マシンの作成と起動

とりあえずこんなとこかな。