From 92c808fd97e3bd7430d504127037e63ee5c1e0c1 Mon Sep 17 00:00:00 2001 From: David Roberts Date: Tue, 17 Jan 2017 14:46:11 +0000 Subject: [PATCH] Remove C++ code It now lives in the machine-learning-cpp repository Original commit: elastic/x-pack-elasticsearch@11ac8212d71652c14af1999cb957b51fdea0ddac --- vagrant/.gitignore | 1 - vagrant/README.md | 108 -------------------------------------------- vagrant/Vagrantfile | 37 --------------- 3 files changed, 146 deletions(-) delete mode 100644 vagrant/.gitignore delete mode 100644 vagrant/README.md delete mode 100644 vagrant/Vagrantfile diff --git a/vagrant/.gitignore b/vagrant/.gitignore deleted file mode 100644 index 8000dd9db47..00000000000 --- a/vagrant/.gitignore +++ /dev/null @@ -1 +0,0 @@ -.vagrant diff --git a/vagrant/README.md b/vagrant/README.md deleted file mode 100644 index f3dbfa6eb6e..00000000000 --- a/vagrant/README.md +++ /dev/null @@ -1,108 +0,0 @@ -## Vagrant build environment - -This provides a vagrant box for building the C++ side of Ml (and the Java side, -although that is easily accomplished outside vagrant). - -Provisioning the box will take a fair amount of time, since it needs to download -and compile a number of dependencies. - - -### Details -- Ubuntu Trusty64 (14.04.5 LTS) -- 25% of host's memory -- 100% host's cores -- Maps ml source repository to `/home/vagrant/ml/src` - - Directory is shared with the host, so you can point your IDE to the ml repo - and build inside vagrant -- Maps ml build directory to `/home/vagrant/ml/build` -- Changes into `/home/vagrant/ml/src` on login - -### Pre-baked box -Don't feel like compiling the entire box? No fear, there's a pre-baked box available -on S3. It is ~1.1gb to download: - -```bash -# Change into some random directory to download the box. -# Doesn't matter where this goes, but *cannot* go into prelert-legacy/vagrant -$ cd ~/some_directory - -# Export the path to your prelert-legacy repo. This is so the box knows where -# to sync the folders -$ export ML_SRC_HOME=/path/to/prelert-legacy - -# Download the box from S3 -$ s3cmd get s3://ml-elastic-dump/ml_env.box - # ... - # Downloading... - # ... - -$ vagrant box add ml ml_env.box -$ vagrant init ml -$ vagrant up -$ vagrant ssh - - Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-96-generic x86_64) - ... - ... - Last login: Tue Oct 4 16:06:32 2016 from 10.0.2.2 - -vagrant@vagrant-ubuntu-trusty-64:~/ml/src$ -``` - -Once you've logged into the box, you'll be in the ml source directory. You -can build immediately via: - -```bash -vagrant@vagrant-ubuntu-trusty-64:~/ml/src$ gradle cppmake -``` -The pre-baked box has already compiled ml once, so subsequent compilations -should happen considerably faster. - -### Compiling from Scratch - -If you feel like compiling everything from scratch instead of downloading the pre-baked -box, simply `vagrant up` and let the provisioners run: - -```bash -$ cd prelert-legacy/vagrant -$ vagrant up - # ... - # wait while vagrant provisions - # ... -$ vagrant ssh - - Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-96-generic x86_64) - ... - ... - Last login: Tue Oct 4 16:06:32 2016 from 10.0.2.2 - -vagrant@vagrant-ubuntu-trusty-64:~/ml/src$ -``` - -Once you've logged into the box, you'll be in the ml source directory. You -can build immediately via: - -```bash -vagrant@vagrant-ubuntu-trusty-64:~/ml/src$ gradle cppmake - # ... - # much building - # ... -``` - -### Suspending your box -Once you've provisioned a box, you can use `vagrant suspend` to "sleep" the box. -This has the advantage of rebooting quickly when you `vagrant up`, and returns you -to exactly what you were doing. On the downside, it eats more disk space since it -needs to sleep the entire image. - -You can alternatively use `vagrant halt`, which gracefully powers down the machine. -Rebooting via `vagrant up` takes longer since you are rebooting the entire OS, -but it saves more disk space. - -### Fixing a broken box -If you accidentally kill the provisioning process before it completes, you can -attempt to reprovision it with `vagrant reload --provision`. That will run -the provisioners that did not complete previously. - -If your box is still horribly broken, you can destroy it with `vagrant destroy` -and try again with `vagrant up` diff --git a/vagrant/Vagrantfile b/vagrant/Vagrantfile deleted file mode 100644 index 5c4661674b2..00000000000 --- a/vagrant/Vagrantfile +++ /dev/null @@ -1,37 +0,0 @@ -Vagrant.configure(2) do |config| - config.vm.box = "ubuntu/trusty64" - config.vm.provider "virtualbox" do |v| - host = RbConfig::CONFIG['host_os'] - - # Give VM 1/4 system memory - linux = RUBY_PLATFORM =~ /linux/ - osx = RUBY_PLATFORM =~ /darwin/ - windows = (/cygwin|mswin|mingw|bccwin|wince|emx/ =~ RUBY_PLATFORM) != nil - if osx - cpus = `sysctl -n hw.ncpu`.to_i - mem = `sysctl -n hw.memsize`.to_i / 1024 / 1024 - end - if linux - cpus = `nproc`.to_i - mem = `sed -n -e '/^MemTotal/s/^[^0-9]*//p' /proc/meminfo`.to_i / 1024 - end - if windows - cpus = `wmic computersystem get numberofprocessors`.split("\n")[2].to_i - mem = `wmic OS get TotalVisibleMemorySize`.split("\n")[2].to_i / 1024 - end - - mem = mem / 4 - v.customize ["modifyvm", :id, "--memory", mem] - v.customize ["modifyvm", :id, "--cpus", cpus] - end - - if File.expand_path(File.dirname(__FILE__)).include? "prelert-legacy/vagrant" - puts "Syncing host's source directory [" + File.expand_path("../") + "] to [/home/vagrant/ml/src]" - config.vm.synced_folder "../", "/home/vagrant/ml/src", mount_options: ["dmode=777,fmode=777"] - else - puts "Syncing host's source directory [" + File.expand_path(ENV['ML_SRC_HOME']) + "] to [/home/vagrant/ml/src] (via $ML_SRC_HOME)" - config.vm.synced_folder ENV['ML_SRC_HOME'], "/home/vagrant/ml/src", mount_options: ["dmode=777,fmode=777"] - end - - config.vm.provision :shell, path: "provision.sh" -end