A "demo" project is needed for the rest of the demostration commands shown.
Something/somebody was pre-creating this automagically in our dev
environment internally, but it needs done manually normally and that needs
documented.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
Given my prior observation of outdated ciao-cli invocations, I did a read
through of ciao-cli related bits and found a number of additional areas
needing updated.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
Quite some time back the command line was modified without reverse
compatibility, and the docu here has bit rotted.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
ClearLinux has simplified their mechanism for CA trust. This nicely
trims a lot of complexity from our ciao documentation.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
The unique thing here versus the upstream documentation is we're describing
a cluster setup where the image, once created, needs to land in a very
specific location.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
An upstream page has the maintained/preferred workflow for setting up a
CNCI. Rather than trying to maintain a duplicate of this, lets minimally
describe what's needed and refer to the upstream documentation point.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
Fix vm virtualbox
On external IRC (freenode) some people are asking to use VirtualBox on ClearLinux.
This PR updates VirtualBox documentation to ensure a proper usage.
This is a P1 issue that afects ClearLinux.
See merge request !83
Ciao certs
We've got a snippet of stale information around adding certificates to a system, and could use some actionable info here to help users get their certs fully configured.
See merge request !82
We removed a section on adding certificates to your browser, yet we do need
info on adding a certificate to the system CA trust. But this varies with
each linux distribution. It's complicated and authoritative information on
the topic is out there in web, so give minimal information to help a
reasonable system administrator on their way.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
Ciao deploy update
Update *ciao-deploy.rst* documentation with current examples in https://github.com/clearlinux/clear-config-management/tree/master/examples/ciao
Changes:
* updated the group_vars/all file with newest example
* deployment added a compute node
* Added the `--private-key=<ssh_key>` instruction when running the playbooks
Please merge once @onmunoz , @albertom , @lmaciasm , @eocardon and @carlosag comment it's all OK with the changes
See merge request !81
This commit removes the --network option that was specified on the various
ciao-launcher example command lines in the previous version of this
document. --network is no longer needed as the role of a given launcher
instance is now determined from its SSNTP certificate.
The instructions for resetting compute and network nodes have been updated.
The --hard-reset option for launcher makes the other steps unnecessary.
Signed-off-by: Mark Ryan <mark.d.ryan@intel.com>
A new image is rsyncing to https://download.clearlinux.org/demos/ciao/
and the documentation needs to reference it. To prevent the need for
these changes repeatedly in the future, we'll soon have things set up
to consume automagically whatever is the latest image.
Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
Tim Pepper