.gitignore

+# Compiled book
+/_book/
+
+# Build deps
+/node_modules/

.gitlab-ci.yml

+# requiring the environment of NodeJS 10
+image: node:10
+
+# add 'node_modules' to cache for speeding up builds
+cache:
+  paths:
+    - node_modules/ # Node modules and dependencies
+
+before_script:
+  - npm install gitbook-cli -g # install gitbook
+  - gitbook fetch 3.2.3 # fetch final stable version
+  - gitbook install # add any requested plugins in book.json
+    
+# the 'pages' job will deploy and build your site to the 'public' path
+pages:
+  stage: deploy
+  script:
+    - gitbook build . public # build to public path
+  artifacts:
+    paths:
+      - public
+    expire_in: 1 week
+  only:
+    - master # this job will affect only the 'master' branch

0-gui/README.md

+# Using OpenStack's Graphical User Interface
+
+This introduction is intended for users wanting to start a virtual machine instance
+through the Graphical User Interface of OpenStack.
+
+Overview of necessary steps:
+* sign in via OpenStack's Graphical User Interface - Horizon Dashboard,
+* create an *ssh* key pair or use an existing key pair,
+* set up or update a security group,
+* start a virtual machine instance,
+* allocate floating IP address (add or remove IP address to/from virtual machine instance)
+* log in to the running instance using *ssh* (secure shell),
+* (optional) create new volume (add/remove volume to/from virtual machine instance).
+
+## Sign In
+
+The Graphical User Interface is available at [https://dashboard.cloud.muni.cz](https://dashboard.cloud.muni.cz).
+
+To sign in,
+* select `ENIFRA CESNET`,
+* click on `Sign In`,
+
+  ![](/0-gui/images/sign_in1.png)
+
+* select your institution from the drop-down list (use the search box at the top as a filter),
+
+  ![](/0-gui/images/sign_in2.png)
+
+* provide your institution-specific sign-in credentials,
+
+  ![](/0-gui/images/sign_in3.png)
+
+* wait to be redirected back to our Graphical User Interface.
+
+## Create Key Pair
+
+All virtual machine instances running in the cloud have to be accessed remotely. The most common way of accessing
+a virtual machine instance remotely is *ssh*. Using *ssh* requires a pair of keys - a public key and a private key.
+
+1. To create a new *ssh* key pair, go to **Project > Compute > Key Pairs** and click the button "Create Key Pair"
+
+  ![](/0-gui/images/CreateKeyPair1.png)
+
+2. Name your new key and click on "Create Key Pair" again. Avoid using special characters, if possible.
+
+  ![](/0-gui/images/CreateKeyPair2.png)
+
+3. You can see your newly created key pair and its fingerprint. We recommend you store the key in a safe location and back it up in case you accidentally delete it.
+
+  ![](/0-gui/images/CreateKeyPair3.png)
+
+## 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.
+
+  ![](/0-gui/images/network1.png)
+
+2. Name the network, which will join your instances, and click "Next".
+
+  ![](/0-gui/images/network2.png)
+
+3. In Subnet tab name your subnet and choose a range of valid IP addresses (e.g. 10.1.1.0/24 or whatever you wanti) in CIDR format. The gateway will be automatically added as default (in our example it would be 10.1.1.1). Click "Next".
+
+  ![](/0-gui/images/network3.png)
+
+4. In Subnet Details tab in Allocation Pools you can choose what ranges will be served by DHCP server (what ranges will be automatically assigned if a machine will use DHCP server for joining a subnet). Use format in description (e.g. for range between 10.1.1.220 and 10.1.1.249 write: 10.1.1.220,10.1.1.249 - so limits separated by comma). You can leave default DNS servers. Click "Create".
+
+  ![](/0-gui/images/network4.png)
+
+5. Now in **Project > Network > Network Topology** you should see the new network created by you.
+
+  ![](/0-gui/images/network5.png)
+
+   Now you can continue by creating 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.
+
+  ![](/0-gui/images/router1.png)
+
+2. Add router name, select External Network (public network, through which you will be connected to internet) and click "Create Router". The router should be created and joined to public network.
+
+  ![](/0-gui/images/router2.png)
+
+3. In **Project > Network > Network Topology** the router should be now visible.
+
+  ![](/0-gui/images/router3.png)
+
+4. Now you can go to **Project > Network > Network Topology** and create interface for connection to your subnet. Pointing over the router icon you will get to information window, where is a button "Add Interface". Click on it.
+
+  ![](/0-gui/images/router4.png)
+
+5. In opened pop-up window choose the available subnet. Click "Submit".
+
+  ![](/0-gui/images/router5.png)
+
+6. In **Project > Network > Network Topology** you can now see your network joined to public network.
+
+  ![](/0-gui/images/router6.png)
+
+## Create Virtual Machine Instance(s)
+
+The creation of virtual machine instances is very straight-forward:
+1. In **Compute > Instances** push the button "Launch Instance"
+
+  ![](/0-gui/images/instance0.png)
+
+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.
+
+  ![](/0-gui/images/instance1.png)
+
+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.
+
+  ![](/0-gui/images/instance2.png)
+
+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.
+
+  ![](/0-gui/images/instance3.png)
+
+5. Next you check if your Instances were added to network created earlier
+
+  ![](/0-gui/images/instance4.png)
+
+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".
+
+  ![](/0-gui/images/instance5.png)
+
+7. In Key Pair you need to add your earlier created public key. It will be added to authorized keys on instances and will allow you to ssh access to them from terminal/Putty or whatever you are using as ssh tool for connecting.
+
+  ![](/0-gui/images/instance6.png)
+
+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.
+
+  ![](/0-gui/images/instance7.png)
+
+9. Then you can click on Launch Instance. After a few minutes they will be ready for using.
+
+  ![](/0-gui/images/instance8.png)
+
+## 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 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"
+
+  ![](/0-gui/images/allocate_IP0.png)
+
+2. In pop-up window choose from which public network (Pool) do you want to allocate IP address for your instance eventually what will be the name of IP address. You have to choose the public network, to which your network is connected to, otherwise it won't work. Click on "Allocate".
+
+  ![](/0-gui/images/allocate_IP1.png)
+
+3. Now you should have IP address to your disposal.
+
+  ![](/0-gui/images/allocate_IP2.png)
+
+4. The next step is associate the free IP address to an instance. Click on "Associate".
+
+  ![](/0-gui/images/allocate_IP2a.png)
+
+5. Select IP address and Port to be associated and click on "Associate".
+
+  ![](/0-gui/images/allocate_IP3.png)
+
+6. In **Project > Compute > Instances** you should be able to see instance with the associated public IP address.
+
+  ![](/0-gui/images/allocate_IP4.png)
+
+## Create Volume
+> TODO