.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:
+  - apt-get update && apt-get -y install calibre # needed for conversion to PDF
+  - 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
+    - gitbook pdf . public/mcc-user-guide.pdf # add PDF version
+  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
+
+__Overview__:
+* 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,
+* associate a floating IP address,
+* access the running instance using *ssh*,
+* __(optional)__ add extra volume for data.
+
+## Sign In
+
+The Graphical User Interface is available at [https://dashboard.cloud.muni.cz](https://dashboard.cloud.muni.cz).
+
+To sign in,
+* Select `EINFRA CESNET`.
+
+  <div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(228,240,251,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
+    <strong>Notice:</strong><br/>
+    Users of the Czech national e-infrastructure should always select <strong>EINFRA CESNET</strong>.
+    International users may choose <strong>EGI Check-in</strong> or <strong>ELIXIR AAI</strong>, depending on
+    their membership.
+  </div>
+
+* Click on **Sign In**.
+
+  ![](/0-gui/images/sign_in1.png)
+
+* Select your institution from the drop-down list. Youy can 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.
+
+<div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(228,240,251,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
+  <strong>Notice:</strong><br/>
+  If your attempts repeatedly result in an error message about projects, make sure you have an active MetaCentrum account
+  and you are selecting the correct institution when attempting to log in. If the problem persists, please, contact user
+  support.
+</div>
+
+## 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. In **Project &gt; Compute &gt; Key Pairs**, click the **Create Key Pair** button.
+
+  ![](/0-gui/images/CreateKeyPair1.png)
+
+2. Name your key. 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)
+
+## Update Security Group
+
+In OpenStack, all incoming traffic from external networks to virtual machine instances is blocked by default.
+You need to explicitly allow access to virtual machine instances and services via a security group.
+
+You need to add two new rules to be able to connect to your new instance (or any instance using the given security group).
+This is similar to setting up firewall rules on your router or server. If set up correctly, you will be able to access
+your virtual machine via *ssh* from your local terminal.
+
+1. Go to **Project &gt;  Network &gt; Security Groups**. Click on **Manage Rules**, for the **default** security group.
+
+  ![](/0-gui/images/SecurityGroups1.png)
+
+2. Click on **Add rule**, choose **SSH** and leave the remaining fields unchanged.
+   This will allow you to access your instance.
+
+  ![](/0-gui/images/SecurityGroups2.png)
+
+3. Click on **Add rule**, choose **ALL ICMP** and leave the remaining fields unchanged.
+   This will allow you to `ping` your instance.
+
+  ![](/0-gui/images/SecurityGroups3.png)
+
+## Create Virtual Machine Instance
+
+1. In **Compute &gt; Instances**, click the **Launch Instance** button.
+
+  ![](/0-gui/images/instance0.png)
+
+2. Choose name, description, and the number of instances.
+   If you are creating more instances, '-%i' will be automatically added to the name of each instance.
+
+  ![](/0-gui/images/instance1.png)
+
+3. You can boot your instances from Image or Volume. Instances booted from Image are not
+   persistent, Volume will remain even if the instance is destroyed (unless otherwise specified).
+
+  ![](/0-gui/images/instance2.png)
+
+4. Choose the size of your instance by selecting a flavor. Additional volumes for data can be attached later on.
+
+  ![](/0-gui/images/instance3.png)
+
+5. __(optional)__ On the Configuration tab, you can use `user_data` to customize your instance at boot.
+   See [cloud-init](https://cloud-init.io/) for details.
+
+## Associate Floating IP
+
+To make an instance accessible from external networks (e.g., The Internet), a so-called Floating IP Address has to be
+associated with it.
+
+1. In **Project &gt; Compute &gt; Instances**, select **Associate Floating IP** from the Actions drop-down menu for the
+   given instance.
+
+2. Select IP address (or click on `+` to allocate one) and click on **Associate**.
+
+  ![](/0-gui/images/allocate_IP3.png)
+
+<div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(228,240,251,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
+  <strong>Notice:</strong><br/>
+  Please, keep an eye on the number of allocated IPs in <strong>Project &gt; Network &gt; Floating IPs</strong>. IPs
+  remain allocated to you until you explicity release them in this tab. Detaching an IP from an instance is not sufficient
+  and the IP in question will remain allocated to you and consume your Floating IP Quota.
+</div>
+
+## Create Volume
+> TODO
+
+## Create Network
+
+1. Go to **Project &gt; Network &gt; Networks**, click in the "Create Network" button.
+
+2. Choose a name. Click **Next**.
+
+3. In the subnet tab, choose a subnet name. In **Network Address Source**, select **Allocate Network Addres from a pool**.
+   In **Address pool** select any of the available pools. Click **Next**.
+
+4. Click **Create**. Do not change any other options.
+
+5. Go to **Project &gt; Network &gt; Network Topology**, review your newly created network topology.
+
+  ![](/0-gui/images/network5.png)
+
+## Create Router
+
+1. Go to **Project &gt; Network &gt; Routers**, click on the **Create Router** button.
+
+2. Choose a name. Select **External Network** and click **Create Router**.
+
+  <div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(228,240,251,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
+    <strong>Notice:</strong><br/>
+    Please, remember that your will have to allocate floating IP addresses in this exact External Network for all instances
+    using this router as a gateway.
+  </div>
+
+3. Go to **Project &gt; Network &gt; Network Topology**, the newly create router should be now present.
+
+  ![](/0-gui/images/router3.png)
+
+4. Click on the router icon, select **Add Interface**.
+
+  ![](/0-gui/images/router4.png)
+
+5. Choose the previously created network/subnet from the drop-down menu. Click **Submit**.
+
+  ![](/0-gui/images/router5.png)
+
+6. The router is now attached to an external network.
+
+  ![](/0-gui/images/router6.png)
+
+
+<div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(228,240,251,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
+  <strong>Notice:</strong><br/>
+  Routers can also be used to route traffic between internal networks. This is an advanced topic not covered in this guide.
+</div>