...
Code Block |
---|
language | bash |
---|
theme | DJangoEmacs |
---|
title | Get docker images |
---|
|
git clone https://github.com/RackHD/RackHD.git
cd RackHD/docker
# for example, if you are installing RackHD 2.53.0latest release:
sudo TAG=2.53.0latest docker-compose pull # Download pre-built docker images.
sudo TAG=2.53.0latest docker-compose up # Create containers and Run RackHD.
# or just use `TAG=latest`2.53.0` for latest2.53.0 release instead |
Latest nightly build
Code Block |
---|
language | bash |
---|
theme | DJangoEmacs |
---|
title | Get latest nightly build |
---|
|
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. |
...
Sprint release
- Install latest sprint release:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
for service in $(echo "on-dhcp-proxy on-http on-tftp on-syslog on-taskgraph");
do
npm install $service;
done |
Below code use 1.1.0 as an example:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
for service in $(echo "on-dhcp-proxy on-http on-tftp on-syslog on-taskgraph");
do
npm install $service@1.1.0;
done |
2.1. Create a pm2.yml like below, the ```cwd``` field should locate the where the on-xxx package lives.
2.2. Run $sudo pm2 start pm2.yml
Code Block |
---|
language | text |
---|
theme | Midnight |
---|
|
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 |
Latest nightly build
- Install NodeJS 4.0 and dependencies
- Install latest nightly build:
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
for service in $(echo "on-dhcp-proxy on-http on-tftp on-syslog on-taskgraph");
do
npm install $service@ci-release;
done |
- Start Services
Start services with the same steps as sprint release.
...
Info |
---|
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. |
Warning |
---|
|
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: Code Block |
---|
| Error: OVF Package is not supported by target:
- Line 155: Unsupported element 'Property'
|
if you want to deploy to vSphere/ESXi, follow below steps: Code Block |
---|
| $# 1. Demote the OVA file name is rackhd-ubuntu-14.04 , example
FNAME=rackhd-ubuntu-14.04
|
Code Block |
---|
| $# 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
|
Code Block |
---|
| $# 3. replace the Property XML fields from the .ovf file
sed -i "/<Property/,/<\/Property>/c\ " ${FNAME}.ovf
|
Code Block |
---|
| $# 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". |
...