blob: 24c55aad8d7bded61c9aadad6a4955b28eeabb24 [file] [log] [blame]
Mohammed Nasera5467342024-04-30 00:34:16 -04001###########
2Quick Start
3###########
4
5There are several ways that you can quickly get started with Atmosphere to explore
6it's capabilities.
7
8**********
9Deployment
10**********
11
12This section covers all of the different ways you can deploy a quick start
13environment for Atmosphere.
14
15.. admonition:: Testing & Development Only
16 :class: info
17
18 The quick start installation is not for production use, it's perfect
19 for testing and development.
20
21All-in-one
22==========
23
24The easiest way to get started with Atmosphere is to deploy the all-in-one
25installation. This will install an entire stack of Atmosphere, with Ceph
26and all the OpenStack services inside a single machine.
27
28.. admonition:: Non-reversible Changes
29 :class: warning
30
31 The all-in-one will fully take-over the machine by making system-level
32 changes. It's recommended to run it inside a virtual machine or a
33 physical machine that can be dedicated to this purpose.
34
35In order to get started, you'll need a **Ubuntu 22.04** system with the
36following minimum system requirements:
37
38- Cores: 8 threads (or vCPUs)
39- Memory: 32GB
40
41If you're looking to run Kubernetes clusters, you'll need more memory
42for the workloads, it following minimum is recommended (but more memory
43is always better!):
44
45- Cores: 16 threads (or vCPUs)
46- Memory: 64GB
47
48.. admonition:: Nested Virtualization
49 :class: warning
50
51 If you're running this inside a virtual machine, it is **extremely**
52 important that the virtual machines supported nested virtualization,
53 otherwise the performance of the VMs will be un-usable.
54
vexxhost-botda9062e2024-08-13 22:00:58 -040055You'll need to start by installing all of the necessary dependencies first,
56**you also need to make sure you run all of these commands as ``root``**:
Mohammed Nasera5467342024-04-30 00:34:16 -040057
58.. code-block:: bash
59
vexxhost-botda9062e2024-08-13 22:00:58 -040060 $ sudo -i
61 $ apt-get update
62 $ apt-get install git tox
Mohammed Nasera5467342024-04-30 00:34:16 -040063
64Once done, you can clone the repository locally and switch to the
65``atmosphere`` directory:
66
67.. code-block:: bash
68
69 $ git clone https://github.com/vexxhost/atmosphere.git
70 $ cd atmosphere
71
72Once you're in the directory, you can deploy the all-in-one environment
vexxhost-botda9062e2024-08-13 22:00:58 -040073by running the following command as ``root``:
Mohammed Nasera5467342024-04-30 00:34:16 -040074
75.. code-block:: bash
76
vexxhost-botda9062e2024-08-13 22:00:58 -040077 $ tox -e molecule-aio-ovn
Mohammed Naserf3152222024-07-19 00:40:24 -040078
79If you want to use the ML2/Open vSwitch plugin, you can run the following
80command:
81
82.. code-block:: bash
83
vexxhost-botda9062e2024-08-13 22:00:58 -040084 $ tox -e molecule-aio-openvswitch
Mohammed Nasera5467342024-04-30 00:34:16 -040085
86Once the deployment is done, it will have a full deployment of all services
87inside the same host, so you can use the cloud from the same machine by
88referencing the usage section.
89
90Multi-node
91==========
92
93The multi-node intends to provide the most near-production experience possible,
94as it is architected purely towards production-only environments. In order to
95get a quick production-ready experience of Atmosphere, this will deploy a full
96stack of Atmosphere, with Ceph and all the OpenStack services across multiple
97machines in a lab environment.
98
99OpenStack
100---------
101
102You can deploy Atmosphere on top of an existing OpenStack environment where many
103virtual machines will be deployed in the same way that you'd have multiple
104physical machines in a datacenter for a production environment.
105
106The quick start is powered by Molecule and it is used in continuous integration
107running against the VEXXHOST public cloud so that would be an easy target to
108use to try it out.
109
110ou will need the following quotas set up in your cloud account:
111
112* 8 instances
113* 32 cores
114* 128GB RAM
115* 360GB storage
116
117These resources will be used to create a total of 8 instances broken up as
118follows:
119
120* 3 Controller nodes
121* 3 Ceph OSD nodes
122* 2 Compute nodes
123
124First of all, you'll have to make sure you clone the repository locally to your
125system with `git` by running the following command:
126
127.. code-block:: console
128
129 $ git clone https://github.com/vexxhost/atmosphere
130
Mohammed Naserf3152222024-07-19 00:40:24 -0400131You will need ``tox`` installed on your operating system. You will need to make
Mohammed Nasera5467342024-04-30 00:34:16 -0400132sure that you have the appropriate OpenStack environment variables set (such
133as ``OS_CLOUD`` or ``OS_AUTH_URL``, etc.). You can also use the following
134environment variables to tweak the behaviour of the Heat stack that is created:
135
136* ``ATMOSPHERE_STACK_NAME``: The name of the Heat stack to be created (defaults to
137 `atmosphere`).
138* ``ATMOSPHERE_PUBLIC_NETWORK``: The name of the public network to attach floating
139 IPs from (defaults to ``public``).
140* ``ATMOSPHERE_IMAGE``: The name or UUID of the image to be used for deploying the
141 instances (defaults to ``Ubuntu 20.04.3 LTS (x86_64) [2021-10-04]``).
142* ``ATMOSPHERE_INSTANCE_TYPE``(Deprecated): The instance type used to deploy all of the
143 different instances.(It doesn't have its own default value.)
144 This has been deprecated from v1.4.0. You can configure the instance type per a
145 machine role using ``ATMOSPHERE_CONTROLLER_INSTANCE_TYPE``,
146 ``ATMOSPHERE_COMPUTE_INSTANCE_TYPE``, and ``ATMOSPHERE_STORAGE_INSTANCE_TYPE``
147 variables. For backwards compatibility, if variables specific to the machine roles
148 are not set and ``ATMOSPHERE_INSTANCE_TYPE`` is set, ``ATMOSPHERE_INSTANCE_TYPE`` value
149 is used.
150* ``ATMOSPHERE_CONTROLLER_INSTANCE_TYPE``: The instance type used to deploy controller
151 instances (defaults to ``v3-standard-16``).
152* ``ATMOSPHERE_COMPUTE_INSTANCE_TYPE``: The instance type used to deploy compute
153 instances (defaults to ``v3-standard-4``).
154* ``ATMOSPHERE_STORAGE_INSTANCE_TYPE``: The instance type used to deploy storage
155 instances (defaults to ``v3-standard-4``).
156* ``ATMOSPHERE_NAMESERVERS``: A comma-separated list of nameservers to be used for
157 the instances (defaults to ``1.1.1.1``).
158* ``ATMOSPHERE_USERNAME``: The username what is used to login into the instances (
159 defaults to ``ubuntu``).
160* ``ATMOSPHERE_DNS_SUFFIX_NAME``: The DNS domainname that is used for the API and
161 Horizon. (defaults to ``nip.io``).
162* ``ATMOSPHERE_ACME_SERVER``: The ACME server, currenly this is from LetsEncrypt,
163 with StepCA from SmallStep it is possible to run a internal ACME server.
164 The CA of that ACME server should be present in the instance image.
165* ``ATMOSPHERE_ANSIBLE_VARS_PATH``: The path for ansible group_vars and host_vars.
166 This to build a multinode development cluster with own configs, that are not
167 generated by molecule. This way you can test your configs before you bring
168 them to production.
169
Mohammed Naserf3152222024-07-19 00:40:24 -0400170Once you're ready to get started, you can run the following command to build
171the Heat stack:
Mohammed Nasera5467342024-04-30 00:34:16 -0400172
173.. code-block:: console
174
Mohammed Naserf3152222024-07-19 00:40:24 -0400175 $ tox -e molecule-venv -- converge
Mohammed Nasera5467342024-04-30 00:34:16 -0400176
177This will create a Heat stack with the name `atmosphere` and start deploying
178the cloud. Once it's complete, you can login to any of the systems by using
179the `login` sub-command. For exampel, to login to the first controller node,
180you can run the following:
181
182.. code-block:: console
183
Mohammed Naserf3152222024-07-19 00:40:24 -0400184 $ tox -e molecule-venv -- login -h ctl1
Mohammed Nasera5467342024-04-30 00:34:16 -0400185
186At this point, you can proceed to the usage section to see how to interact
187with the cloud.
188
189Once you're done with your environment and you need to tear it down, you can
190use the `destroy` sub-command:
191
192.. code-block:: console
193
Mohammed Naserf3152222024-07-19 00:40:24 -0400194 $ tox -e molecule-venv -- destroy
Mohammed Nasera5467342024-04-30 00:34:16 -0400195
196For more information about the different commands used by Molecule, you can
197refer to the Molecule documentation.
198
199*****
200Usage
201*****
202
203Once the deployment is done, you can either use the CLI to interact with
204the OpenStack environment, or you can access the Horizon dashboard.
205
206For the CLI, you can ``source /root/openrc`` and then use the ``openstack``
207CLI. For example, if you want to list the networks, you can run the
208following command:
209
210.. code-block:: console
211
212 $ source /root/openrc
213 $ openstack network list
214
215For the Horizon dashboard, you can find the URL to access it by running
216the following command:
217
218.. code-block:: console
219
220 $ kubectl -n openstack get ingress/dashboard -ojsonpath='{.spec.rules[0].host}'
221
222You can find the credentials to login to the dashboard reading the
223`/root/openrc` file. You can use the following variables to match
224the credentials:
225
226- Username: ``OS_USERNAME``
227- Password: ``OS_PASSWORD``
228- Domain: ``OS_USER_DOMAIN_NAME``