|
|
(75 intermediate revisions by 12 users not shown) |
Line 1: |
Line 1: |
− | = Installing StarlingX with containers: All in One Duplex configuration = | + | {{Warning|header='''Warning - Deprecated'''|body='''This wiki page is out of date and now deprecated. For the current and upcoming versions, see [https://docs.starlingx.io/deploy_install_guides/index.html StarlingX Installation and Deployment guides]'''}} |
| | | |
− | == History == | + | = Documentation Contribution = |
| | | |
− | '''January 24, 2019:''' Initial draft
| + | You might consider contributing to StarlingX documentation if you find a bug or have a suggestions for improvement. |
| + | To get started: |
| | | |
− | == Introduction == | + | * Please use "[https://docs.starlingx.io/contributor/index.html Contribute]" guides. |
| + | * Launch a bug in [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs StarlingX Launchpad] with the tag ''stx.docs''. |
| | | |
− | These instructions are for an All-in-one duplex system in VirtualBox.
| + | = History = |
− | Other configurations are in development.
| |
− | Installing on bare metal is also possible, however the the process would have to be adapted for the specific hardware configuration.
| |
| | | |
− | '''Note''': These instructions are valid for a load built on '''January 24, 2019''' or later.
| + | Go to [https://wiki.openstack.org/w/index.php?title=StarlingX/Containers/InstallationOnAIODX&action=history Page > History] link if you want to: |
| | | |
− | == Building the Software ==
| + | * See the old content of this page |
− | | + | * Compare revisions |
− | Follow the standard build process in the [https://docs.starlingx.io/developer_guide/index.html StarlingX Developer Guide].
| |
− | | |
− | Alternatively a prebuilt iso can be used, all required packages are provided by the [http://mirror.starlingx.cengn.ca/mirror/starlingx/ StarlingX CENGN mirror]
| |
− | | |
− | == Setup the VirtualBox VM ==
| |
− | | |
− | Refer to these instructions on the AIO SX page [[StarlingX/Containers/Installation#Setup_the_VirtualBox_VM| Setup_the_VirtualBox_VM]]
| |
− | | |
− | Remember to setup TWO VMs.
| |
− | | |
− | == VirtualBox Nat Networking ==
| |
− | | |
− | Refer to these instructions on the AIO SX page [[StarlingX/Containers/Installation#VirtualBox_Nat_Networking| VirtualBox_Nat_Networking]]
| |
− | | |
− | == Install StarlingX ==
| |
− | | |
− | Boot the VM from the ISO media. Select the following options for installation:
| |
− | *All-in-one Controller | |
− | *Graphical Console
| |
− | *Standard Security Profile
| |
− | | |
− | Once booted, log into Controller-0 as user wrsroot, with password wrsroot. The first time you log in as wrsroot, you are required to change your password. Enter the current password (wrsroot):
| |
− | | |
− | <pre>
| |
− | Changing password for wrsroot.
| |
− | (current) UNIX Password: wrsroot
| |
− | </pre>
| |
− | | |
− | Enter a new password for the wrsroot account and confirm it.
| |
− | | |
− | == Initial Configuration ==
| |
− | | |
− | Run config_controller
| |
− | | |
− | <code>sudo config_controller --kubernetes</code>
| |
− | | |
− | Use default settings during config_controller, except for the following
| |
− | System mode: '''duplex'''
| |
− | | |
− | If you do not have direct access to the public docker registry (https://hub.docker.com/u/starlingx) and instead use a proxy for internet access, you will need to add proxy information
| |
− | when prompted.
| |
− | | |
− | If you do not have direct access to the google DNS nameserver 8.8.8.8 , you will need to configure that when prompted.
| |
− | | |
− | The system configuration should look like this:
| |
− | <pre>
| |
− | TO DO
| |
− | </pre>
| |
− | | |
− | == Provisioning the platform ==
| |
− | | |
− | TO DO
| |
− | | |
− | == Boot the second AIO controller ==
| |
− | | |
− | Boot the second VM (without an ISO media mounted)
| |
− | Hit F12 immediately when the VM starts to select a different boot option - select the "lan" option to force a network boot.
| |
− | | |
− | At the controller-1 console, you will see a message instructing you to configure the personality of the node. Do this from a shell on controller-0 as follows:
| |
− | | |
− | <pre>
| |
− | source /etc/platform/openrc
| |
− | system host-list
| |
− | +----+--------------+-------------+----------------+-------------+--------------+
| |
− | | id | hostname | personality | administrative | operational | availability |
| |
− | +----+--------------+-------------+----------------+-------------+--------------+
| |
− | | 1 | controller-0 | controller | unlocked | enabled | available |
| |
− | | 2 | None | None | locked | disabled | offline |
| |
− | +----+--------------+-------------+----------------+-------------+--------------+
| |
− | [wrsroot@controller-0 ~(keystone_admin)]# system host-update 2 personality=controller
| |
− | </pre>
| |
− | | |
− | The packages will install and the controller will reboot.
| |
− | | |
− | TO DO: add output from host-update step
| |
− | | |
− | == Provisioning the second AIO controller ==
| |
− | | |
− | TO DO
| |
− | | |
− | == Prepare the host for running the containerized services ==
| |
− | | |
− | TO DO
| |
− | | |
− | == Using sysinv to bring up/down the containerized services ==
| |
− | | |
− | Refer to these instructions on the AIO SX page [[StarlingX/Containers/Installation#Using_sysinv_to_bring_up.2Fdown_the_containerized_services| here ]]
| |
− | | |
− | == Verify the cluster endpoints ==
| |
− | | |
− | Refer to these instructions on the AIO SX page [[StarlingX/Containers/Installation#Verify_the_cluster_endpoints| here ]]
| |
− | | |
− | == Provider/tenant networking setup ==
| |
− | | |
− | Refer to these instructions on the AIO SX page [[StarlingX/Containers/Installation#Provider.2Ftenant_networking_setup| here ]]
| |
− | | |
− | == Horizon access ==
| |
− | | |
− | Refer to these instructions on the AIO SX page [[StarlingX/Containers/Installation#Horizon_access| here ]]
| |
− | | |
− | == Known Issues and Troubleshooting ==
| |
− | | |
− | None
| |
You might consider contributing to StarlingX documentation if you find a bug or have a suggestions for improvement.
To get started: