#2946: Update custom trusty64 box in 'Vagrantfile'

[jeff1evesque]

Resolves #2946.

[coveralls]

Coverage remained the same at 48.928% when pulling d7cf97c on feature-2946 into 34ca4a6 on master.

[jeff1evesque]

The purposed commits build successfully:

$ vagrant up main
...
==> main: Notice: /Stage[main]/Nginx::Config/File[/etc/nginx/conf.stream.d]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/etc/nginx/conf.mail.d]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/var/nginx]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/var/log/nginx]/group: group changed 'adm' to 'root'
==> main: Notice: /Stage[main]/Nginx::Config/File[/var/nginx/client_body_temp]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/var/nginx/proxy_temp]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/etc/nginx/streams-enabled]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/etc/nginx/streams-available]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Config/File[/etc/nginx/nginx.conf]/content: content changed '{md5}a85dcbc5367783f3d42d0b7eab22ea50' to '{md5}de983fff1c3d7515a8100b89ed6ab532'
==> main: Notice: /Stage[main]/Webserver::Service/Nginx::Resource::Vhost[machine-learning.com]/Concat[/etc/nginx/sites-available/machine-learning.com.conf]/File[/etc/nginx/sites-available/machine-learning.com.conf]/ensure: defined content as '{md5}5937732bcc4cee3f211f266c2e3ccbb1'
==> main: Notice: /Stage[main]/Webserver::Service/Nginx::Resource::Vhost[machine-learning.com]/File[machine-learning.com.conf symlink]/ensure: created
==> main: Notice: /Stage[main]/Nginx::Service/Service[nginx]: Triggered 'refresh' from 1 events
==> main: Notice: /Stage[main]/Webserver::Start/Service[start_gunicorn]/ensure: ensure changed 'stopped' to 'running'
==> main: Notice: Applied catalog in 593.34 seconds

Additionally, we were able to /register a new account, /login, and successfully generate a prediction:

[jeff1evesque]

It seems even though our virtualbox vm had reasonable partitions:

the equivalent vagrant up vm has partitions similar to that before this issue:

vagrant@ubuntu-14:/vagrant$ df -h
Filesystem                                                     Size  Used Avail Use% Mounted on
udev                                                           487M  4.0K  487M   1% /dev
tmpfs                                                          100M  456K   99M   1% /run
/dev/sda1                                                      2.4G  2.2G  113M  96% /
none                                                           4.0K     0  4.0K   0% /sys/fs/cgroup
none                                                           5.0M     0  5.0M   0% /run/lock
none                                                           497M     0  497M   0% /run/shm
none                                                           100M     0  100M   0% /run/user
/dev/sda6                                                      5.1G   11M  4.8G   1% /home
vagrant                                                        466G  129G  337G  28% /vagrant
tmp_vagrant-puppet_environments                                466G  129G  337G  28% /tmp/vagrant-puppet/environments
tmp_vagrant-puppet_modules-3c00084ae9953309c24252b2dd2bf5cd    466G  129G  337G  28% /tmp/vagrant-puppet/modules-3c00084ae9953309c24252b2dd2bf5cd
tmp_vagrant-puppet_modules-044f8ea6fe024da4abbd7bbb8407a17e    466G  129G  337G  28% /tmp/vagrant-puppet/modules-044f8ea6fe024da4abbd7bbb8407a17e
tmp_vagrant-puppet_manifests-3def0df79d1c452de6a52de4d163c7cc  466G  129G  337G  28% /tmp/vagrant-puppet/manifests-3def0df79d1c452de6a52de4d163c7cc

[jeff1evesque]

We are going to close this issue, to prevent accidental merge, until a proper solution can be determined.

[jeff1evesque]

This pull request was prematurely closed, because we hadn't removed our older local instance of our vagrant box, before vagrant up xxx. In order to test our updated trusty64 1.1.0 box from atlas repository, we had to remove the local instance of our custom vagrant base box:

$ vagrant box list
centos/6              (virtualbox, 1611.01)
jeff1evesque/centos7x (virtualbox, 1.0.0)
jeff1evesque/centos7x (virtualbox, 1.0.2)
jeff1evesque/trusty64 (virtualbox, 0)
$ vagrant box remove jeff1evesque/trusty64
Box 'jeff1evesque/trusty64' (v0) with provider 'virtualbox' appears
to still be in use by at least one Vagrant environment. Removing
the box could corrupt the environment. We recommend destroying
these environments first:

aristotle (ID: de268ebd34f34d94ba1de2e37b40d1cf)
socrates (ID: 35a07918022549d59a292375ef35dae6)
plato (ID: db6951cc5aee426a90c62d380a3e2b4c)
confucious (ID: dd91f5fce59d4d93a0870208e6d34211)
laotzu (ID: fd0916a197974e3c81dd921cf8b7c99c)
siddhartha (ID: 764a498ddef943b8b912aabd06547946)
galileo (ID: bdfc75b5455445a392f57d6c4269e47e)
copernicus (ID: edc958bf511c416a8f46214c8aebf8db)
main (ID: 836d945f2cf04f69ae3394fbd9e9cfdc)
kepler (ID: 6a111d3b0d904aa286cfb6ca2d5bea5b)

Are you sure you want to remove this box? [y/N] y
Removing box 'jeff1evesque/trusty64' (v0) with provider 'virtualbox'...
$ vagrant box list
centos/6              (virtualbox, 1611.01)
jeff1evesque/centos7x (virtualbox, 1.0.0)
jeff1evesque/centos7x (virtualbox, 1.0.2)

Then, we were able to download our updated 1.1.0 custom trusty64 box, as a part of the vagrant up main command. After the vagrant up main command succeeded as a whole, we noticed the corresponding partitions were increased noticeably for our main instance of our application:

vagrant@trusty64:~$ hostname
trusty64
vagrant@trusty64:~$ df -h
Filesystem                                                     Size  Used Avail Use% Mounted on
udev                                                           486M  4.0K  486M   1% /dev
tmpfs                                                          100M  516K   99M   1% /run
/dev/sda1                                                      7.8G  2.2G  5.2G  30% /
none                                                           4.0K     0  4.0K   0% /sys/fs/cgroup
none                                                           5.0M     0  5.0M   0% /run/lock
none                                                           497M     0  497M   0% /run/shm
none                                                           100M     0  100M   0% /run/user
vagrant                                                        466G  139G  327G  30% /vagrant
tmp_vagrant-puppet_environments                                466G  139G  327G  30% /tmp/vagrant-puppet/environments
tmp_vagrant-puppet_modules-3c00084ae9953309c24252b2dd2bf5cd    466G  139G  327G  30% /tmp/vagrant-puppet/modules-3c00084ae9953309c24252b2dd2bf5cd
tmp_vagrant-puppet_modules-044f8ea6fe024da4abbd7bbb8407a17e    466G  139G  327G  30% /tmp/vagrant-puppet/modules-044f8ea6fe024da4abbd7bbb8407a17e
tmp_vagrant-puppet_manifests-3def0df79d1c452de6a52de4d163c7cc  466G  139G  327G  30% /tmp/vagrant-puppet/manifests-3def0df79d1c452de6a52de4d163c7cc

Note: for the time being, we will perform our unit tests within the main instance of our application.

---

Additionally, corresponding mongodb nodes, yield a similar vagrant up xxx result:

vagrant@trusty64:~$ hostname
kepler
vagrant@kepler:~$ df -h
Filesystem                                                     Size  Used Avail Use% Mounted on
udev                                                           108M  4.0K  108M   1% /dev
tmpfs                                                           24M  516K   24M   3% /run
/dev/sda1                                                      7.8G  4.7G  2.7G  65% /
none                                                           4.0K     0  4.0K   0% /sys/fs/cgroup
none                                                           5.0M     0  5.0M   0% /run/lock
none                                                           119M     0  119M   0% /run/shm
none                                                           100M     0  100M   0% /run/user
vagrant                                                        466G  139G  327G  30% /vagrant
tmp_vagrant-puppet_environments                                466G  139G  327G  30% /tmp/vagrant-puppet/environments
tmp_vagrant-puppet_modules-f07217ab419cc50c879fbe11d04e38c8    466G  139G  327G  30% /tmp/vagrant-puppet/modules-f07217ab419cc50c879fbe11d04e38c8
tmp_vagrant-puppet_modules-68f1d46533c7b79be8c41ff7869052d7    466G  139G  327G  30% /tmp/vagrant-puppet/modules-68f1d46533c7b79be8c41ff7869052d7
tmp_vagrant-puppet_manifests-ac62d95a83a122596be3eb429665cace  466G  139G  327G  30% /tmp/vagrant-puppet/manifests-ac62d95a83a122596be3eb429665cace

[coveralls]

Coverage remained the same at 48.928% when pulling 1b21dd6 on feature-2946 into 34ca4a6 on master.