Instead of doing a lot of instructions to setup
a deployment machine, we just ask the user to pull
and use a container already setup with all the needed
tools.
Signed-off-by: Simental Magana, Marcos <marcos.simental.magana@intel.com>
Start by specify supported hardware and provide help to determinate
if user's system is available to run clearlinux in a later
paragraph.
Signed-off-by: Simental Magana, Marcos <marcos.simental.magana@intel.com>
The `os-common` bundle doesn't exists (should be `openstack-common`
instead) and we can use the `c-basic` instead of `os-core-dev`
as it's smaller.
Signed-off-by: Simental Magana, Marcos <marcos.simental.magana@intel.com>
Appended /icis/ to bulk_provisioning URLs
Two of the URLs in source/bulk_provisioning.rst pointed to the wrong
URL on the PXE / ICIS server. They now point to the icis subdirectory
where the uwsgi app is running.
Signed-off-by: John Andersen <john.s.andersen@intel.com>
See merge request !103
Two of the URLs in source/bulk_provisioning.rst pointed to the wrong
URL on the PXE / ICIS server. They now point to the icis subdirectory
where the uwsgi app is running.
Signed-off-by: John Andersen <john.s.andersen@intel.com>
Instructions for NATing cluster on network boot
The description of how to construct your network was missing from the
network_boot documentation. This adds instructions on how to
configure the cluster so that the PXE / DHCP server allows traffic
to flow from internal to external networks and vice versa. Without
this the documentation is incomplete as it assumes the user knows how
to set up some kind of networking. By providing this information the
user is able to get a fully functioning cluster up an running biased
solely on this document.
Signed-off-by: John Andersen <john.s.andersen@intel.com>
See merge request !102
The description of how to construct your network was missing from the
network_boot documentation. This adds instructions on how to
configure the cluster so that the PXE / DHCP server allows traffic
to flow from internal to external networks and vice versa. Without
this the documentation is incomplete as it assumes the user knows how
to set up some kind of networking. By providing this information the
user is able to get a fully functioning cluster up an running biased
solely on this document.
Signed-off-by: John Andersen <john.s.andersen@intel.com>
The playbook creates some files when its executed.
The files are:
./certificates directory which contains the certificates used in the cluster
./images directory which contains the os images used in the cluster
./openrc file which contains environment variables to authenticate openstack cli
./ciaorc file which contains environment variables to authenticate ciao cli
Signed-off-by: Alberto Murillo <alberto.murillo.silva@intel.com>
The bundles table has updated with current
status of Active / WIP / Deprecated bundles
as of release 10320.
Signed-off-by: Leona <leonax.cook@intel.com>
- The Prerequisite section no longer explains how to
create an ssh-key. Remove a reference to it.
- Specify defaults/main.yml file on each role contains
a full list of available variables that can be used.
- "Start" the deployment rather than "fire" it
- Specify the location of ciaorc file
Signed-off-by: Alberto Murillo <alberto.murillo.silva@intel.com>
Miguel Bernal Marin