Skip to content
Snippets Groups Projects
Verified Commit 495ebd31 authored by Boris Parak's avatar Boris Parak :8ball:
Browse files

Minor tweaks in GUI docs

parent e4934249
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 12 additions and 26 deletions
1-gui/README.md
+ 12
− 26
View file @ 495ebd31
# Using OpenStack's Web Interface
This introduction is intended for users that want to start a few virtual machine instances in the cloud or they want to adjust their project more carefully to their needs through the Graphical Interface of OpenStack.
This introduction is intended for users that want to start a larger number of virtual machine instances in the cloud or use advanced features through the Graphical User Interface of OpenStack.
The process is practically very similar to creating a virtual machine instance in [Quickstart](https://cloud.gitlab-pages.ics.muni.cz/documentation/0-quickstart/), you need to
* sign in via the MetaCentrum cloud web interface,
The process is similar to creating a virtual machine instance in [Quickstart](/documentation/0-quickstart/), you need to
* sign in via the MetaCentrum Cloud web interface,
* create an *ssh* key pair or use an existing key pair,
* create virtual machine instances,
* create virtual private network,
* create virtual router,
* join virtual private network to internet through router interfaces,
......@@ -54,9 +53,7 @@ All virtual machine instances running in the cloud have to be accessed remotely.
![](/0-quickstart/CreateKeyPair3.png)
{% endreveal %}
## Network
## Create Network
1. In **Project > Network > Network Topology** you can see the actual status of your networks. In the beginning there are only public networks visible, because you haven't created yet your network. You can do it by clicking on the button "Create Network". This network will serve as connection of your instances.
{% reveal text="Show Screenshot" %}
......@@ -85,7 +82,7 @@ All virtual machine instances running in the cloud have to be accessed remotely.
Now you can continue by creating router.
## Create router
## Create Router
1. In **Project > Network > Network Topology** or in **Project > Network > Routers** push the button "Create Router". This router will serve as connection between your subnet and public network.
{% reveal text="Show Screenshot" %}
......@@ -117,7 +114,7 @@ All virtual machine instances running in the cloud have to be accessed remotely.
![](/1-gui/router6.png)
{% endreveal %}
## Create virtual machine instances
## Create Virtual Machine Instance(s)
The creation of virtual machine instances is very straight-forward:
1. In **Compute > Instances** push the button "Launch Instance"
......@@ -125,23 +122,17 @@ The creation of virtual machine instances is very straight-forward:
![](/1-gui/instance0.png)
{% endreveal %}
2. Choose Instance Name, (optionally) Description, Availability Zone and Count of instances, how many VMs you want to create. If you are creating more instances, the number in format '-X' will be added automatically to the Instance Name for each instance.
2. Choose Instance Name, (optionally) Description, Availability Zone and Count of instances, how many VMs you want to create. If you are creating more instances, the number in format '-X' will be added automatically to the Instance Name for each instance.
{% reveal text="Show Screenshot" %}
![](/1-gui/instance1.png)
{% endreveal %}
Then click on Next.
3. Choose the source of booting (you can boot your Instances from Image or a snapshot), Volume Size and from Available choose the desired image to boot from.
According to the purpose of your project you can change these default settings Create New Volume and Delete Volume on Instance Delete (default "No"), if you want to use created volume and if you want to have not persistant volume.
3. Choose the source of booting (you can boot your Instances from Image or a snapshot), Volume Size and from Available choose the desired image to boot from. According to the purpose of your project you can change these default settings Create New Volume and Delete Volume on Instance Delete (default "No"), if you want to use created volume and if you want to have not persistant volume.
{% reveal text="Show Screenshot" %}
![](/1-gui/instance2.png)
{% endreveal %}
4. Pick the flavour - size of Instances created: VCPUs, RAM, Total Disk (Root). There are a few possibilities to choose from. You can add [additional disk]() later.
{% reveal text="Show Screenshot" %}
![](/1-gui/instance3.png)
{% endreveal %}
......@@ -151,8 +142,6 @@ Then click on Next.
![](/1-gui/instance4.png)
{% endreveal %}
You can jumped through Network Ports and Security Groups to Key Pair.
6. (optional) Security Groups tab you can see to what security group instances will be added. Usually you would like to stick with default option. Click on "Next".
{% reveal text="Show Screenshot" %}
![](/1-gui/instance5.png)
......@@ -163,8 +152,6 @@ You can jumped through Network Ports and Security Groups to Key Pair.
![](/1-gui/instance6.png)
{% endreveal %}
If you haven't created key pair yet, you can do it now or you can import existing public key from file on your computer.
8. (optional) You can now go to Metadata (the left bottom tab) and choose the packages of software, which you want to have installed on your instances.
{% reveal text="Show Screenshot" %}
![](/1-gui/instance7.png)
......@@ -175,9 +162,9 @@ If you haven't created key pair yet, you can do it now or you can import existin
![](/1-gui/instance8.png)
{% endreveal %}
## Allocate and associate floating IP (optional)
## Allocate and Associate a Floating IP (optional)
Sometimes we want to have an instance accessible from public network. In OpenStack project you can do it easilly from the menu for each instance in **Project > Compute > Instances** or you can manage them more conscious way with at first allocating and then associating of IP address with instance. (You can of course later disassociate IP address from instance or disallocate IP address from your pool, when you don't need it, or associate with another instance and so on.)
Sometimes we want to have an instance accessible from public network. In OpenStack project you can do it easily from the menu for each instance in **Project > Compute > Instances** or you can manage them more conscious way with at first allocating and then associating of IP address with instance. (You can of course later disassociate IP address from instance or disallocate IP address from your pool, when you don't need it, or associate with another instance and so on.)
1. Go to **Project > Network > Floating IPs** and click on "Allocate IP to Project"
{% reveal text="Show Screenshot" %}
......@@ -189,7 +176,7 @@ Sometimes we want to have an instance accessible from public network. In OpenSta
![](/1-gui/allocate_IP1.png)
{% endreveal %}
3. Now you should have IP address to your disposal.
3. Now you should have IP address to your disposal.
{% reveal text="Show Screenshot" %}
![](/1-gui/allocate_IP2.png)
{% endreveal %}
......@@ -209,6 +196,5 @@ Sometimes we want to have an instance accessible from public network. In OpenSta
![](/1-gui/allocate_IP4.png)
{% endreveal %}
##
## Volume
## Create Volume
> TODO
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment