prehistoric-systems/scottslowe-learning-tools
1
0
Fork 0
mirror of https://codeberg.org/scottslowe/learning-tools.git synced 2026-03-11 09:04:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
scottslowe-learning-tools/lxd-ansible
History
Scott S. Lowe ba4d123faf Shift to nested YAML data files 
Edit YAML data files to use nested data structures. Edit Vagrantfile to reference YAML data accordingly.

Signed-off-by: Scott S. Lowe <scott.lowe@scottlowe.org>
2016-11-09 23:24:47 -07:00
..
ansible.cfg Restore shell-based LXD environment 2016-01-17 15:57:22 -07:00
machines.yml Shift to nested YAML data files 2016-11-09 23:24:47 -07:00
provision.yml Update Ansible playbook 2016-02-03 17:03:50 -07:00
README.md Restore shell-based LXD environment 2016-01-17 15:57:22 -07:00
Vagrantfile Shift to nested YAML data files 2016-11-09 23:24:47 -07:00

README.md

Running LXC-Based OS Containers with LXD

These files were created to allow users to use Vagrant (http://www.vagrantup.com) and Ansible (http://www.ansible.com) to relatively easily experiment with LXD (pronounced "lex-dee"), a new daemon and CLI client for working with LXC-based OS containers. The configuration was tested using Vagrant 1.8.1, VMware Fusion 8.1.0, the Vagrant VMware plugin, and Ansible 1.9.1. Other versions are likely to work, but haven't been tested.

Contents

  • ansible.cfg: This Ansible configuration file instructs Ansible to use an inventory file named hosts in the current directory, and to use the default vagrant user (vagrant) and default insecure Vagrant SSH private key.

  • hosts: This file is created automatically when you run vagrant status or vagrant up (anytime Vagrant processes Vagrantfile). This file relies on the presence of a "ip_addr" value in machines.yml. Do not edit this file directly---instead edit machines.yml to change the values that will be automatically written into this file.

  • machines.yml: This YAML file contains a list of VM definitions and associated configuration data. It is referenced by Vagrantfile when Vagrant instantiates the VMs. Only minimal changes may be needed to this file; see the "Instructions" section below.

  • provision.yml: This YAML file is an Ansible playbook that configures the VMs created by Vagrant when they are first provisioned. Ansible is called automatically by Vagrant; you do not need to invoke Ansible separately. No changes are needed to this file.

  • README.md: The file you're currently reading.

  • Vagrantfile: This file is used by Vagrant to spin up the virtual machines. This file is fairly extensively commented to help explain what's happening. You should be able to use this file unchanged; all the VM configuration options are stored outside this file.

Instructions

These instructions assume you've already installed VMware Fusion, Vagrant, the Vagrant VMware plugin, and Ansible. Please refer to the documentation for those products for more information on installation or configuration.

  1. Use vagrant box add to install an Ubuntu 14.04 x64 box for the "vmware_fusion" provider. I have a base box you can use for this purpose; to use my Ubuntu 14.04 x64 base box, add the box with vagrant box add slowe/ubuntu-trusty-x64. (In theory you should be able to use this Vagrant environment with VMware Workstation as well, but only VMware Fusion was tested.)

  2. Place the files from the lxd directory of this GitHub repository (the "lowescott/learning-tools" repository) into a directory on your system. You can clone the entire "learning-tools" repository (using git clone), or just download the specific files from the lxd directory.

  3. Edit machines.yml to ensure that the box specified in that file matches the Ubuntu 14.04 x64 base box you just installed and will be using. I recommend that you do not change any other values in this file unless you know it is necessary. If you use my base box as described in step #1, no changes are needed to machines.yml.

  4. From a terminal window, change into the directory where the files from this directory are stored and run vagrant up to bring up the VMs specified in machines.yml and Vagrantfile. (By default, it will create and power on only a single VM.)

  5. Once Vagrant has finished creating, booting, and provisioning the VM (note you'll need Internet access for this step), log into the VM (named "lxd-01" by default) using vagrant ssh.

  6. Add the public LinuxContainers.org image repository by running lxc remote add lxc-org images.linuxcontainers.org.

  7. Copy the 32-bit Ubuntu 14.04 container image to your system with the command lxc image copy lxc-org:/ubuntu/trusty/i386 local: --alias=trusty32.

  8. Launch a container based on this image with the command lxc launch trusty32 lxd-test-01. This will start a container named "lxd-test-01" based on the "trusty32" image (which is an alias for the image you copied in step 7).

  9. Run file /bin/ls and note the output. (You'll use the output for comparison in just a moment.)

  10. Open a shell in the 32-bit container you launched in step 8 with the command lxc exec lxd-test-01 /bin/bash.

  11. Inside the container, run file /bin/ls and compare the output to the output of the same command you ran outside the container. You'll see that inside the container the file is reported as a 32-bit ELF executable; outside the container the same file is listed as a 64-bit ELF executable.

  12. Press Ctrl-D to exit the shell in the container.

  13. The container is still running, so stop the container with lxc stop lxd-test-01.

There you have it---a way to quickly and easily experiment with LXD. Enjoy!