git clone https://github.com/RackHD/RackHD.git
cd RackHD/docker


# for example, if you are installing RackHD latest release:
sudo TAG=latest docker-compose pull               # Download pre-built docker images.
sudo TAG=latest docker-compose up                 # Create containers and Run RackHD.

# or just use `TAG=2.53.0` for 2.53.0 release instead

git clone https://github.com/RackHD/RackHD.git
cd RackHD/docker
sudo TAG=nightly docker-compose pull               # Download pre-built docker images.
sudo TAG=nightly docker-compose up                 # Create containers and Run RackHD.

# 1. Remove the original nightly build debian source(main) in /etc/apt/sources.list if any (using ```sed``` to replace that line with blank line)
sudo sed -i  's#deb https://dl.bintray.com/rackhd/debian trusty main##' /etc/apt/sources.list
# 2. add release debian source(release) in /etc/apt/sources.list 
echo deb https://dl.bintray.com/rackhd/debian trusty release | sudo tee -a /etc/apt/sources.list

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
sudo apt-get update

sudo apt-get install rackhd

If the nightly build debian source exists in /etc/apt/sources.list (```deb https://dl.bintray.com/rackhd/debian trusty main```)

the RC(release candidate) build will be treated newer than offical released version, say, "apt-get" will think of 1.0.0-20170116UTC is newer than 1.0.0.

and you will never install release version using ```apt-get install rackhd```.

 echo deb https://dl.bintray.com/rackhd/debian trusty main | sudo tee -a /etc/apt/sources.list
 sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
 sudo apt-get update

sudo apt-cache policy rackhd

sudo apt-get install aptitude
sudo aptitude install rackhd=${version}

wget https://raw.githubusercontent.com/panpan0000/RackHD/805d9958818f4d1283d8bd17baa83ba59ccc09d7/example/install_src.sh
sudo ./install_src.sh  release/1.1.0

git fetch --all --tags
git checkout 1.1.0        # or 1.1.0-rc , depends on which tag you want to checkout
npm install --production

cd $repo/node_modules
rm on-core -rf
rm on-tasks -rf
ln -s ../../on-core      on-core
ln -s ../../on-tasks     on-tasks

apps:
  - script: index.js
     name: on-taskgraph
     cwd: on-taskgraph
  - script: index.js
     name: on-http
     cwd: on-http
  - script: index.js
     name: on-dhcp-proxy
     cwd: on-dhcp-proxy
  - script: index.js
     name: on-syslog
     cwd: on-syslog
  - script: index.js
     name: on-tftp
     cwd: on-tftp

If you are looking to run RackHD in  vagrant/virtualbox image, please email to rackhd@emc.com or contact us in Slack Channel.

vagrant init rackhd/rackhd --force --box-version 1.1.0  # rackhd/rackhd is the Atlas repository of rackhd, this cmd will generate a simple Vagrantfile
vagrant up                                              # start the rackhd vagrant box according to Vagrantfile
vagrant ssh                                             # enter the box

vagrant init rackhd/rackhd --force --box-version 0.01.13

If you are looking to run the RackHD OVA image, please email to rackhd@emc.com .  You are also welcome to create your own OVA leveraging this script: https://github.com/RackHD/RackHD/blob/master/packer/build_ova.sh

RackHD OVA deployment out of the CI/CD pipeline will be discontinued as of 10/27/17.  Script capabiltiies will continue to be supported and validated allowing users to generate their own RackHD OVA. 

for OVA before RackHD 2.2.0, you can't directly deploy the OVA to a vSphere.

please follow below as a workaround..

------------------------------------

So far, vSphere(ESX server) is NOT supported with customized property (OVF 2.0 format ?). only vCenter can support this OVA (because there's a customized prosperity feature to config IP during deployment.)

reference: https://blogs.vmware.com/vapp/2009/07/commandline-ovf-deployments-.html

Error message will be like below:

Error: OVF Package is not supported by target:
- Line 155: Unsupported element 'Property'

if you want to deploy to vSphere/ESXi, follow below steps:

$# 1. Demote  the OVA file name is rackhd-ubuntu-14.04 , example
FNAME=rackhd-ubuntu-14.04

$# 2. covert OVA to OVF and VMDK
ovftool   ${FNAME}.ova        ${FNAME}.ovf    
#  or using 7zip :  -->     7z x ${FNAME}.ova   
# then there will be 3 files: ${FNAME}-disk1.vmdk             ${FNAME}.mf                   ${FNAME}.ovf

$# 3. replace the Property XML fields from the .ovf file
sed  -i  "/<Property/,/<\/Property>/c\ "  ${FNAME}.ovf

$# 4. then deploy with the updated ${FNAME}.ovf file via ESXi vSphere GUI or ovftool command line
      #below is an example of ovftool usage, please replace the ${xx} to your real values.
 ovftool  --skipManifestCheck  --name=${GivenNameOfTheVM} --datastore=${TargetDatastore} --net:"ADMIN"="${AdminBridge}"      ${FNAME}.ovf           vi://user:pwd@${ESXi_IP}

If you deploy using VSphere GUI under Windows, please delete the *.mf file before deployment, because the *.ovf file has been updated, and the sha256 checksum in the *.mf file has changed. the vSphere GUI will report "sha256 checksum mismatched".