Objetivos 2017

Acabo de leer el post de David Bonilla con sus objetivos de 2017, y me ha servido para darme cuenta que este año no he blogueado nada (al menos aquí).

Sirva de excusa que este año he empezado a postear en el blog de Wearepeople, pero sobre todo que dediqué mucha de mi energía (junto a la de otros pocos valientes como Alejandra, Rocío, Berto y Laura) a hacer que la Conferencia Rails 2016 sucediese.

Así que sin más preámbulos, vamos a copiar al Gran Maestre Tarugo:

¿Cómo ha ido 2016?

Tener tiempo con la familia: Este es uno agridulce, he pasado un montón de tiempo con mi hija viéndola crecer y aprender, pero a cambio he sufrido los turnos de tarde de mi compañera de viaje haciéndome llevar vida un poco "monoparental", veredicto: Necesita Mejorar

Hacer más deporte: Aquí siento una nota de orgullo, este año convertí mi experimento con las BiciMad en un nuevo hábito, adquiriendo una bici propia y usándola para más o menos la mitad de los desplazamientos al trabajo. Además, en la segunda mitad del año logré volver a hacer un hueco para mi pasión por las artes marciales encontrando una que podía practicar con mis lesiones y cerca de casa. Soy un novato felíz en la Escuela Fong Nang de Ving Tsun bajo la tutela del genial Sifu Jesús Carballo. veredicto: Exitazo 😊

Comer más sano: Éste ha sido uno de los peores apartados, al compartir menos tiempo con mi luna y mis estrellas, he priorizado otras tareas por encima de la compra y la cocina sana y este año ha sido un poco fritanguero. veredicto: Vergüenza sobre mi vaca 🐮

Resucitar Conferencia Rails: este año, el enorme esfuerzo de un pequeño grupo de locas y locos hizo posible, contra todo sentido común, la resurrección del evento que hace diez años cambió el rumbo de mi vida: La Conferencia Rails. Por supuesto, hicimos casi todo mal, pero aún así funcionó.veredicto: ALUCINANTE

Así es como se consigue que Kerri Miller y Aaron Patterson te firmen la misma orden de alejamiento :-)
Bonus: este año, después de 13 años amortizando el pequeño utilitario coreano que me regalaran mis padres cuando me saqué el carné, al fin he cambiado de coche, con tan buena fortuna que ahora lo poco que conduzco es con un híbrido, algo más respetuoso con el planeta en general y el aire que respeiran mis convecinos madrileños en particular. Como icing on the cake, mi padre, que tenía el coche desde el mismo año, ha cambiado también a un híbrido casi igual.

Despedida: mucho se ha hablado de la gente que este 2016 se ha llevado por delante, como Prince, David Bowie, Carrie Fisher, Debbie Reynolds... sin embargo, la partida que me ha tocado más de cerca este año ha sido la de Bosco.
 

Pocas personas han expresado lo que pasa entre los humanos y nuestros perros como Oatmeal.

¿Qué esperar ahora de 2017?

• Más tiempo con la familia
• Más pedales
• Más kung fu
• Comer más sano/tener un peso de dos cifras
• Traer a Sandi Metz a la Conferencia Rails 2017
• Que el mundo se de cuenta de que Wearepeople es la mejor empresa de la Vía Lactea y hagamos un absurdillón de euros Molar al menos la mitad que Xavi Noria.

the happy developer environment strikes back

Fresh from the developer wiki, I bring you the last installment of my preferred development sandbox setup, for you to try and enjoy:

 

(Optional/Mac-OSX)

Install boot2docker

Docker runs in a VirtualBox VM through an image called boot2docker. The reason we have to use boot2docker and VirtualBox is because the Mac OSX filesystem is not compatible with the type of filesystem required to support Docker. Hence, we must run our Docker containers within yet another virtual machine.
Download and install VirtualBox.
Now install boot2docker and Docker Compose.

   $ brew install boot2docker docker-compose

Initialize and start up boot2docker

   $ boot2docker init
   $ boot2docker start

Configure your Docker host to point to your boot2docker image.

   $ $(boot2docker shellinit)

You’ll need to run this for every terminal session that invokes the docker or docker-compose command – better export this line into your .zshrc or .bashrc.

 

Install docker from the web

Install docker

 

Install docker-compose from docker web

Install docker-compose

 

Create Dockerfile

Create on project root with following content

 # ./Dockerfile
 FROM ruby:2.2
 MAINTAINER name@wearepeople.io
 
 ENV APP_PATH /app
 
 # This will be a host folder mounted to cache installed gems
 ENV BUNDLE_PATH /bundle
 
 # Install apt based dependencies required to run Rails as
 # well as RubyGems. As the Ruby image itself is based on a
 # Debian image, we use apt-get to install those.
 RUN apt-get update -qq && apt-get install -y build-essential libpq-dev
 
 RUN mkdir -p $APP_PATH
 
 # Expose port 3000 to the Docker host, so we can access it
 # from the outside.
 EXPOSE 3000
 
 # Configure the main working directory. This is the base
 # directory used in any further RUN, COPY, and ENTRYPOINT
 # commands. 
 WORKDIR $APP_PATH
 
 # Copy the main application.  
 COPY . $APP_PATH
 
 # The main command to run when the container starts. Also
 CMD ./start

 

Create .dockerignore

Create .dockerignore file with following contents:

 .git*
 log/*
 tmp/*
 Dockerfile
 README.rdoc

 

Create de comopse config

Create docker-compose.yml file with following contents:

 # docker-compose.yml
 app:
   build: .
   command: "./start"
   volumes:
     - .:/app
     - .bundle:/bundle  # gem cache folder
   ports:
     - "3000:3000"
   links:
     - db
     - mail
     - redis
   environment:
     BUNDLE_JOBS: 4
 db:
   image: postgres
   ports:
     - "5432"
 redis:
   image; redis
   ports:
     - "6379"
 mail:
   image: schickling/mailcatcher
   ports:
     - "1080:1080"

 

Adapt application configurations accordingly:

• config/database.yml

 development: &default
   adapter: postgresql
   encoding: unicode
   database: appname_development
   pool: 5
   username: postgres
   password:
   host: db
 
 test:
   <<: *default
   database: appname_test

• ./start

 #!/usr/bin/env bash
 
 echo "Removing old server pid's if any..."
 rm -f tmp/pids/server.pid
 
 echo "Checking bundle dependencies..."
 bundle check || bundle install
 
 echo "Booting up..."
 bundle exec rails s -p 3000 -b 0.0.0

• config/initializers/session_store.rb

 redis_server = ENV['REDIS_PORT_6379_TCP_ADDR'] || 'localhost' # docker sets ENV, production uses localhost for now
 redis_port   = ENV['REDIS_PORT_6379_TCP_PORT'] || '6379'
 
 Coaching::Application.config.session_store :redis_store,
   servers: "https://#{redis_server}:#{redis_port}/session"

 

Build containers

 docker-compose build

 

Initialize Gems & Database

 docker-compose run app bash -c 'bundle install && rake db:setup'
 

 

Run app

This will start app container (and dependencies) as a daemon, thus leaving the terminal free

 docker-compose up -d

And this allows us to follow the process output/log as 'tail -f' or 'foreman start' would do

 docker-compose logs

There are other useful commands listed here: docker-compose commandline reference

Developer experience, and "you don't have to be big too be cool"

Today I want to talk about something written by @david_bonilla author of a well known weekly mail-list where he publicly meditates on the Spanish software industry, the start-up ecosystem and whatnot.

In his last issue he speaks about how some companies alienate visitors, even business relevant and required visitors in lieu of a poor understanding of security or negotiation or both.

But what first caught my attention was the example he set.

«To a computer techie, your laptop is like the katana for a Samurai. It is not a simple tool of the trade, but an item of such complicity and familiarity, that it is perceived as an extension of one's self. Therefore, when a security guard stamps some sticker on it , it bothers me as much as if was being stick to my forehead or you were to tuck a finger in my nose and revolve counter-clockwise.»

image by solvash

This, besides of showing David's humorous narrative skill's addresses something that has been silently bothering me since I started to thrive as a developer until recently.

At every company I worked for before, I have been provided with a set of tools mostly to the company (usually naive) understanding of my needs. Some were outright crappy, like a 14'' CRT 10 year old clone with no internet.

Some others were a mark or hierarchy/privilege, so when someone new entered the company, new equipment was bought and assigned to the bossiest person, who would pass remains along to ne next and so on, so the new person had the scrapings nobody else wanted.

My last employer did a very good effort to provide powerful and competitive equipment, but they struggled with customizabillity (like fixed provider, fixed OS, fixed -old- OS version...)

At my current company, the smallest I have worked for so far, has been the first to say: «this is your tool, so we pay for it but you must choose what it is to be like». I know it to be a great deal for a company of this size to do this. I came up with a very effective setup free of any extravaganzas. And also was offered to choose chair, laptop stand, screen...

I took me the best of nine years to find someone in Spain understanding what Joel Spolsky was saying back in 2006, and it was not some cool SF start-up, it was a coder-born entrepreneur.

This is an open advise to all that companies throwing sacks of euros/dollars to recruiters, and languishing to find good talent. If you want good and great developers to come to you, and stay with you, stop patronizing, just treat them well, like professionals that know what they are doing, and let everybody know how you roll.

A happy developer environment: revisited

Some time ago I wrote A happy developer's environment aiming to share my sanbox creation scripts.

I promised a "part 2" that never was. Sorry, I am busy and/or lazy.

Now that my magic-auto-sandbox thing has evolved, it's time to revisit it.

Get virtualbox

In my case, adding repositories as instructed in https://www.virtualbox.org/wiki/Linux_Downloads.

 

Get vagrant

It is a virtualization automation tool that was a ruby gem in its origins.
Nowadays, the recommended (linux) install procedure is downloading packages for your favourite distro from: https://www.vagrantup.com/downloads.html

 

Create config files

Three files, read and adapt to your particular needs:

 

./Vagrantfile

It is vagrant's config file, it tells vagrant what machine to start if it already exists or how to create it, if it hasn't been yet.

Vagrant.configure("2") do |vagrant|
  vagrant.vm.define "project_name" do |config|

    # Inject code from outer FS (edit outside, run inside)
    # required by type: "nfs"
    config.vm.network "private_network", ip: '192.168.50.10'
    config.vm.synced_folder "./code", "/home/vagrant/code", type: "nfs"

    # Access app with outer browser
    # otherwise use rails s -b 0.0.0.0 and private ip
    config.vm.network "forwarded_port", guest: 3000, host: 3000

    config.vm.network "public_network", bridge: 'wlan0'

    # http://rvm.io/integration/vagrant
    config.vm.provision :shell, path: 'provision/bootstrap.sh', keep_color: true

    config.vm.provider "virtualbox" do |vb, override|
      # http://www.vagrantbox.es/
      # Prepare with: wget -O ../trusty-vbox.box http://goo.gl/8wqNnb
      override.vm.box_url = "../trusty-vbox.box"
      override.vm.box = "trusty-vbox"
      vb.name = 'project_name'
      vb.memory = ENV['VM_MEM'] || 1024
      vb.cpus = ENV['VM_CPU'] || 2
      vb.customize ['modifyvm', :id, "--natdnshostresolver1", "on"]
    end
  end
end 

./provision/bootstrap.sh

If you happen to be a systems person (or have one near) here is where they will suggest puppet or chef or whatever "configuration automation" tool.
A simple shell script is enough for Xavi Noria, and is enough for me.

#!/usr/bin/env bash
## Ruby on Rails Development Environment Provision Script ##
# Inspired by @fxn's https://github.com/rails/rails-dev-box

# Configuration variables with custom values
RUBY_VERSION="2.2.1"
APP="project_name"
HOSTNAME='project_name.dev'

echo -e "\n== «$APP» on _$RUBY_VERSION_ ==\n"

# Load auxiliary functions:
source /vagrant/provision/functions.sh

# General System layout
install 'development tools' build-essential
set_timezone 'Etc/UTC'
setup_locale 'LANG="en_US.UTF-8"\nLANGUAGE="en_US:en LC_ALL=en_US.UTF-8"\n'
hostname $HOSTNAME
install Git git

# Ruby & Rails:
install_rvm
install_postgres
install 'Nokogiri dependencies' libxml2 libxml2-dev libxslt1-dev
install_node

# Developer happiness stuff:
install 'ACK-Grep' ack-grep
install 'Log colorizer' ccze
install 'Vim' vim

# App specific stuff
install_bower

echo -e "\033[1;32m All set, rock on! thanks to the awesome @fxn!\033[0m"

./provision/functions.sh

These are the parts that change less from project to project, so I have extracted them for easier reuse.

#!/usr/bin/env bash

echo -e "\033[1;32m Loading auxiliary functions for provision...\033[0m"

# The ouput of all these installation steps is noisy. With this utility
# the progress report is nice and concise.
function install {
    echo installing $1 ...
    shift
    debian_frontend=noninteractive apt-get -y install "$@" >/dev/null 2>&1
    echo -e "\033[1;32m [OK] \033[0m"
}

# Executes a command as the vagrant user
# Example:
#   run 'Description' 'command'
function vagrant_run {
    echo -e "\n$1:"
    eval "su -l vagrant -c '$2'"
}

# Installs ruby environment through RVM
function install_rvm {
  if [ ! -x /home/vagrant/.rvm/scripts/rvm ]; then
      vagrant_run "Getting RVM keyring" \
        'gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3'
      echo -e "\nInstalling RVM:"
      su -l vagrant -c 'curl -sSL https://get.rvm.io | bash -s -- stable'
      echo -e "\nLoading RVM to continue:"
      su -l vagrant -c 'source $HOME/.rvm/scripts/rvm'
      echo -e "\nInstalling Ruby ($RUBY_VERSION)"
      su -l vagrant -c "rvm use $RUBY_VERSION --default --install"
      echo -e "\nInstalling Bundler:"
      su -l vagrant -c 'gem install bundler'
      su -l vagrant -c 'echo "gem: --no-rdoc --no-ri" >> /home/vagrant/.gemrc'
  fi
}

# Installs PostgreSQL database
function install_postgres {
  echo -e "\nInstalling Postgres DB and config..."
  if [ ! -x /usr/bin/psql ]; then
      install PostgreSQL postgresql postgresql-contrib libpq-dev
      sudo -u postgres createuser --superuser vagrant
      sudo -u postgres createdb -O vagrant ${APP}_development
      sudo -u postgres createdb -O vagrant ${APP}_test

      # enable pg_admin access from host machine:
      PG_CONF='/etc/postgresql/9.3/main'
      PUBLIC_IP=$(ip -o -4 addr show eth1 | cut -d ' ' -f 7)
      echo "listen_addresses = '*'" >> $PG_CONF/postgresql.conf
      echo "host all all $PUBLIC_IP trust" >> $PG_CONF/pg_hba.conf
      service postgresql restart
  fi
}

# Set VM timezone to have consistent test results
function set_timezone {
    # http://manpages.ubuntu.com/manpages/precise/man7/debconf.7.html
    echo "Setting timezone to: '$1'"
    export DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_FRONTEND=noninteractive
    echo "$1" > /etc/timezone
    dpkg-reconfigure tzdata
}

function setup_locale {
  # Needed for docs generation.
  echo -e "$1" > /etc/default/locale
}

function install_node {
    install 'ExecJS runtime (for coffee)' nodejs
    install 'Npm' npm
    su -l vagrant -c 'if [ ! -f $HOME/.npmrc ]; then
        echo prefix = $HOME/.node >> $HOME/.npmrc
        echo "export PATH=\"\$PATH:\$HOME/.node/bin\"" >> $HOME/.bashrc
        source $HOME/.bashrc
      fi'

    if [ ! -f /usr/bin/node ]; then
      ln -s /usr/bin/nodejs /usr/bin/node
    fi
}

function install_bower {
  echo -e "\nInstalling Bower and vendored assets..."
  BOWER_FILE='/home/vagrant/code/.bowerrc'
  if [ ! -f $BOWER_FILE ]; then
    echo -e "{\n\t"directory": "vendor/assets/components"\n}" >> $BOWER_FILE
  fi

  if [ ! -x /home/vagrant/.node/bin/bower ]; then
      vagrant_run "Installing bower" "npm install -g bower --silent"

      # Installing bower dependencies
      vagrant_run "Installing bower assets" \
        'cd /home/vagrant/code; /home/vagrant/.node/bin/bower install'
  fi
}

Get the base machine

As it is instructed in the comments on Vagrantfile:

wget -O ../trusty-vbox.box http://goo.gl/8wqNnb

You will only have to do this once for all the projects you may share the base machine with. (All of them in my case)

Create the machine

You use the command:

vagrant up 

and it will create (and provision) the machine the first time is called and all following occasions it will just boot it up.

To connect to your machine you use:

vagrant ssh

To stop it:

vagrant halt

To destroy (in case you are debugging your creation/provision process):

vagrant destroy

There are improvements to the experience if you set up sudo and ~/.ssh/config on the host machine so they never ask you for passwords, but I will let you decide if you want to go that path while you ponder the security implications.

Surviving zombie apocalypses for fun an profit

Another Codemotion came and went. All in all it wasn't bad, considering its dimension and organizational challenges.

As a former international event volunteer organizer, I find myself in deep empathy with the enormous achievement of making this happen. Near 2000 people, 8 tracks, 2 days...

On the other hand, as a conference attendee, I have suffered the price of some of those numbers.

The size

It's too big, corridors and talk-rooms get unevenly crowded, and you loose interesting talks because they get full.

The food you can offer to 2K people does not leave much place for excellence, and there was even some twitter trolling related to this, I will just say it was dull and felt cheap.

It is impossible for any crew to reasonably choose technically relevant talks of such diverse branches, so they delegate in the local communities with mixed results, there is not an uniform quality level in the contents, nor in the delivery.

The venue

I have no opinion on San Pablo CEU as an educational institution, I just don't appreciate religious indoctrination mixed with my tech talks, they every right to mix it into education as long as it is a private educational institution, and students or parents choose freely to attend it.

I do no appreciate either having to take the car to go a place wrongly mapped by popular GPS software that non one in the crew tried before recommending.

I find id a bad choice, horribly far from down-town for locals, and even worse for attendees coming from other provinces that had to search for accommodation in Madrid and suffer a weirdest commute to get there.

Rooms where crowded on the most popular tracks, which is very difficult to avoid when you go for 8-tracks, which is one of the reasons you shouldn't.

The talks

I was quite lucky and saw a good deal of decent talks. But I lost two I wanted to go because of full rooms, even after seeing people sitting in the ground during several talks from the first day.

Special mentions to @serabe, @arctarus @carlossanchezp, @alvaro_sanchez, @olmaygti, @jorgeleria, @vianasw, @chemaalonso, @david_bonilla whose talks I liked specialy.

David Bonilla's talk and call to action deserves a post on their own, but there will be many and probably better than the one I would do, so I will try to transform that energy on deeds instead of more words.

Thanks to my really nice employer wearepeople.io for my free day :-)

If you want to see the slides of any of them, just help yourself: https://twitter.com/search?q=%23codemotion_es%20slides

Adventure Time

Last month I jumped onto a new challenge. I have entered the ranks of We Are People Engineering. It is a (for now) small code-shop in Madrid which values and views I have find myself significantly aligned with.

A year ago I did another jump in the void when I embarked Avature, leaving behind among other things ruby and backend development, which had been my specialities for the last lustrum and more.

This new course change obeys not to regret on that decision but to a deeper understanding of what I like and find important in the craft.

I value every day I have spent outside of my comfort zone, every challenge to my beliefs, every proof that my old ways where not the only ones... It has been enlightening as only living abroad and learning a different language can be. But one can get homesick abroad.

Many Spanish companies that I know of have a lot to learn form Avature about how they treat people. Their approach to onboarding and team building is more human and peer-like than anything I saw before. That, much more than the very decent salary, is the reason I pursued this journey to strangeland so far. That and the very good company from the Madrid team (kudos to you all, pals).

This are not easy things to leave behind, and thus I did not so lightly. My current affair is one of meaningful comprehension of a shared core of values. I walk away from a lot of good things because I think my contributions will be more meaningful to WeArePeople, and I hope to the community.

Change is what life is made of, may you all live interesting times.

A happy developer's environment: part 1

I have been working lately with my development stack held inside a linux container (LXC), and it has been my best sandboxing experience so far, so I decided to share the process with everyone.

In this first part I will cover the vagrant and lxc installation and the box creation, later in part 2 I will cover provision and backup of the box.

Install lxc

sudo apt-get install lxc

Install Vagrant

Go to http://www.vagrantup.com/downloads and download and install the appropiate one for you

Install Vagrant-LXC plugin

vagrant plgin install  vagrant-lxc

Clone Vagrant-LXC-boxes repo

git clone https://github.com/fgrehm/vagrant-lxc-base-boxes.git
cd vagrant-lxc-base-boxes 

Build a base box with your provisioner of choice

CHEF=1 make precise
==> [ubuntu-precise] Building box to 'output/2014-09-26/vagrant-lxc-precise-amd64.box'...
    [ubuntu-precise] Creating container...
    [ubuntu-precise] Container created!
    [ubuntu-precise] Adding ipv6 allhosts entry to container's /etc/hosts
    [ubuntu-precise] Running [/usr/sbin/locale-gen es_ES.UTF-8] inside 'vagrant-base-precise-amd64' container...
    [ubuntu-precise] Running [update-locale LANG=es_ES.UTF-8] inside 'vagrant-base-precise-amd64' container...
==> [ubuntu-precise] Installing extra packages and upgrading
    [ubuntu-precise] Sleeping for 5 seconds...
    [ubuntu-precise] Running [apt-get update] inside 'vagrant-base-precise-amd64' container...
    [ubuntu-precise] Running [apt-get install vim software-properties-common nfs-common curl wget man-db bash-completion python-software-properties ca-certificates sudo -y --force-yes] inside 'vagrant-base-precise-amd64' container...
    [ubuntu-precise] Running [apt-get upgrade -y --force-yes] inside 'vagrant-base-precise-amd64' container...
    [ubuntu-precise] Installing Chef
    [ubuntu-precise] Running [/tmp/install-chef.sh] inside 'vagrant-base-precise-amd64' container...
    [ubuntu-precise] Skipping Puppet installation
    [ubuntu-precise] Skipping Salt installation
    [ubuntu-precise] Skipping Babushka installation
==> [ubuntu-precise] Preparing vagrant user...
    [ubuntu-precise] Renamed ubuntu user to vagrant and changed password.
    [ubuntu-precise] SSH credentials configured for the vagrant user.
    [ubuntu-precise] Sudoers file created.
==> [ubuntu-precise] Cleaning up 'vagrant-base-precise-amd64'...
    [ubuntu-precise] Removing temporary files...
    [ubuntu-precise] cleaning up dhcp leases
    [ubuntu-precise] Removing downloaded packages...
    [ubuntu-precise] Running [apt-get clean] inside 'vagrant-base-precise-amd64' container...
==> [ubuntu-precise] Packaging 'vagrant-base-precise-amd64' to 'output/2014-09-26/vagrant-lxc-precise-amd64.box'...
    [ubuntu-precise] Removing previous rootfs tarball
    [ubuntu-precise] Compressing container's rootfs
    [ubuntu-precise] Preparing box package contents
    [ubuntu-precise] Packaging box
==> [ubuntu-precise] Finished building 'output/2014-09-26/vagrant-lxc-precise-amd64.box'!
    [ubuntu-precise] Run `sudo lxc-destroy -n vagrant-base-precise-amd64` or `make clean` to remove the container that was created along the way

Move/rename box

mv output/2014-09-26/vagrant-lxc-precise-amd64.box ../precise64.box

Remove build artifacts

make clean
cd ..

Create a Vagrantfile

ENV["VAGRANT_DEFAULT_PROVIDER"]='lxc'

Vagrant.configure("2") do |config|
  config.vm.box = "precise64"
  config.vm.box_url = "./precise64.box"
  config.vm.provider :lxc do |lxc|
    # Same effect as 'customize ["modifyvm", :id, "--memory", "1024"]' for VirtualBox
    # lxc.customize 'cgroup.memory.limit_in_bytes', '1024M'
  end
end

Set up NFS folder sync (if you want)

On the server:

Add to the Vagrantfile:

config.vm.synced_folder './code', '/home/vagrant/code', nfs: true

As root add in /etc/apparmor.d/lxc/lxc-default:

profile lxc-container-default flags=(attach_disconnected,mediate_deleted) {
  ...
    mount options=(rw, bind),
  ...

Reload apparmor:

sudo /etc/init.d/apparmor reload

Launch Vagrant (it will import the .box the first time)

vagrant up
Bringing machine 'default' up with 'lxc' provider...
==> default: Setting up mount entries for shared folders...
    default: /vagrant => /tmp/lxc
==> default: Starting container...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 10.0.3.105:22
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
nfsd running
==> default: Mounting NFS shared folders...
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.

If you get tired of writing your password:

vagrant lxc sudoers

Access the machine

vagrant ssh
Welcome to Ubuntu 12.04.5 LTS (GNU/Linux 3.13.0-35-generic x86_64)

 * Documentation:  https://help.ubuntu.com/
vagrant@vagrant-base-precise-amd64:~$

And that's all, you are in, if you just wanted to have an isolated environment to make experiments without paying for servers or loosing performance like virtual machines, then you are good to go.

Otherwise, if you are still interested in the provisioning thing keep tuned for the second part.