- apply image
- generate defaults
- confirm / edit config
Apply the Image
NOTE: if you need details on how to apply the image to your USB or optical disk, see media prep.
once booted to the live image, select the automated install and 'ENTER'.
click User Creation at the next screen complete the required fields to set up a non-root admin user. If this step is not completed now do not fear, you will be prompted to create this account after first login.
click Finish Installation and wait for reboot
accept licensing agreement:
update Centos to current by running:
sudo yum update -y && reboot
One of the primary tasks complete during install is the creation of the file
/etc/rocknsm/config.yml. This file contains key variables like network interface setup, cpu cores used, what components are enabled, and more.
TIP: take care with these options as this file will be read during the next step, deployment.
For example: if you wish to run an offline install (the ISO sets you up for this already) edit
/etc/rocknsm/config.yml and change the following (line 30):
If this value is set to
True, Ansible will configure your system for the yum repositories listed and pull packages and git repos directly from the URLs given. You could easily point this to local mirrors, if needed.
If this value is set to
False, Ansible will look for the cached files in
/srv/rocknsm. There is another script called
offline-snapshot.sh that will create the necessary repository and file structure. Run this from a system that is Internet connected and copy it to your sensors for offline deployment.
While you're in there, you can change the auto-detected defaults, such as which interfaces to use, hostname, fqdn, resources to use, etc. You can also disable features altogether at the bottom by simply changing the feature value to
False as shown below. Don't do this unless you know what you're doing.
This disables nginx from installing or being configured. Note that it will not remove it if it is already present.
Once your config file is tuned to your situation, it's time to deploy! This is done by running the deployment script:
If everything is well, this should set up all the components you selected and give you a success banner similar to the example below:
NOTE: If you find the deployment is failing, the script can be run with very verbose output. This example will write the output to a file for review:
DEBUG=1 ./deploy_rock.sh | tee /tmp/deploy_rock.log
Continue to the Usage Guide.
NOTE: for a detailed guide on how to set up a virtual machine to throw packets at see the VM Build Guide wiki/dev section.