From b82ff7b341abb15cd36fb31092e1f48d96ee697f Mon Sep 17 00:00:00 2001
From: Adam Merka <405417@muni.cz>
Date: Fri, 7 Dec 2018 14:24:41 +0100
Subject: [PATCH] Creates 9-Privacy, GDPR and stuff/README.md
Auto commit by GitBook Editor
---
0-quickstart/README.md | 29 ++++++++++----------
2-networking/README.md | 42 ++++++++++++++++++++++++++---
9-Privacy, GDPR and stuff/README.md | 0
GLOSSARY.md | 13 ++++++++-
SUMMARY.md | 2 ++
5 files changed, 67 insertions(+), 19 deletions(-)
create mode 100644 9-Privacy, GDPR and stuff/README.md
diff --git a/0-quickstart/README.md b/0-quickstart/README.md
index 8e151a1..c69332b 100644
--- a/0-quickstart/README.md
+++ b/0-quickstart/README.md
@@ -12,37 +12,38 @@ To create and gain acces to virtual machine you need to:
1. One of the access options is the web interface that is available at [https://cloud.muni.cz](https://cloud.muni.cz). We recommend using the English version of the interface. The Czech translation of individual terms is not yet sufficiently experienced and their use may complicate communication with technical support. Use the following credentials to log in:
-* **Domain** **-** UCN
-* **User Name - **UÄŚO[^1]@ucn.muni.cz
-* **Password - **your secondary password.
-
-> Please note that you need to access OpenStack from within the internal university network. You can either use the two available networks - [eduroam and MUNI](https://it.muni.cz/en/services/wireless-wi-fi-connection "How to connect to Masaryk University network") or setup a [VPN access](https://it.muni.cz/en/services/vpn "How to setup a VPN access.").
-
+2. **Domain** **-** UCN
+3. **User Name - **UÄŚO[^1]@ucn.muni.cz
+4. **Password - **your secondary password.
+> Please note that you need to access OpenStack from within the internal university network. You can either use the two available networks - [eduroam and MUNI](https://it.muni.cz/en/services/wireless-wi-fi-connection "How to connect to Masaryk University network") or setup a [VPN access](https://it.muni.cz/en/services/vpn "How to setup a VPN access.").
+>
> **TODO** add login info and screenshots
## 2. Import/create SSH keys
To create a first instance accessible from the network you typically need to go through a few one-time steps that are not required later on. The first step is to create/import SSH keys.
-1. To create a new SSH key, go to **Project > Compute > Key Pairs **and clock the button "Create Key Pair"
+1. To create a new SSH key, go to **Project > Compute > Key Pairs **and clock the button "Create Key Pair"
2. Name your new key and hit "Create Key Pair" again. Try to avoid special characters if possible. 
-3. You can see your newly created key pair and its fingerprint. Your browser will automatically save your key pair in your designated download location. We recommend you save it in a safe location and back it up andin case you accidentally delete it. 
+
+3. You can see your newly created key pair and its fingerprint. Your browser will automatically save your key pair in your designated download location. We recommend you save it in a safe location and back it up andin case you accidentally delete it.
+ 
## 3. Set-up Security Groups
All network traffic is blocked in OpenStack by default. You need to explicitly grant access to individual services by utilising Security Groups. This is similar to setting up firewall rules on your router or server. If setup correctly, you can access your virtual machine via SSH connection from your terminal.[^2]
-1. Go to **Project > Networks > Security Groups **You can see a default security group. You can either create a new one or edit the default by hitting "Manage Rules"
+1. Go to **Project > Networks > Security Groups **You can see a default security group. You can either create a new one or edit the default by hitting "Manage Rules"
-2. Next you need to add two new rules to be able to connect to your new instance. Hit the button "Add rule", give it a name and choose "ALL ICMP". Leave the rest of the fields unchanged.
+2. Next you need to add two new rules to be able to connect to your new instance. Hit the button "Add rule", give it a name and choose "ALL ICMP". Leave the rest of the fields unchanged.
-3. Add another rule. This time choose "SSH" and leave the remaining fields unchanged.
+3. Add another rule. This time choose "SSH" and leave the remaining fields unchanged.
## 4. Start a virtual machine
@@ -54,13 +55,11 @@ All network traffic is blocked in OpenStack by default. You need to explicitly g
5. Add a virtual network for your instance.
6. You can leave the rest of the fields unchanged.
-
-
## 5. Assign a public IP address
-To access your machine from the internet, you need to allocate a new public IP address to your project. Once the IP is allocated, you canthen assign it to a specific instance.
+To access your machine from the internet, you need to allocate a new public IP address to your project. Once the IP is allocated, you canthen assign it to a specific instance.
-1. In the left menu, navigate to **Project** > **Network > Floating IPs** and hit the button "**Allocate IP To Project**".
+1. In the left menu, navigate to **Project** > **Network > Floating IPs** and hit the button "**Allocate IP To Project**".
2. Select "public-float-21" and hit the button "**Allocate IP**".
3. The last step is to assign the IP to your selected instance. Find the instance you want and hit the "Associate Floating IP" in the last section of the row titled "**Actions**".
4. Finally simply select the allocated IP and you're done.
diff --git a/2-networking/README.md b/2-networking/README.md
index f0e431b..0151ef0 100644
--- a/2-networking/README.md
+++ b/2-networking/README.md
@@ -1,5 +1,41 @@
-# Networking
+# Network settings
-## Floating IP
+Instances in OpenStack make use of user-defined internal networks, through which they can communicate. To access your instances from an external network, you need to connect the internal and the external network via a virtual router and allocate a public \(floating\) IP address to your virtual machine.
+
+By logging in, you are automatically provided with a default internal network **"internal-net"** and a default virtual router that connects to the public network **"public-float-21" **with a subnet of **192.168.0.0/24. **In order to make your instance publicly accessible, you only need to assign a public IP to it.
+
+## 1. Internal network creation {#vytvoreni_interni_site}
+
+1V levĂ© lište se dostaneme do správy sĂtĂ pĹ™es: **1.Project**→**2.Network**→**3.Networks** a klikneme na **4. Create network**:
+
+2Zde si pojmenujeme sĂĹĄ:
+
+3NastavĂme podsĂĹĄ \(jmĂ©no i sĂĹĄová adresa je libovolná\):
+
+4V detailech ješte přidáme adresy DNS serverů a to konkrétně:
+147.251.4.33
+147.251.6.10
+
+## 2. Security groups
+
+All network traffic is blocked in OpenStack by default. You need to explicitly grant access to individual services by utilising Security Groups. This is similar to setting up firewall rules on your router or server. If setup correctly, you can access your virtual machine via SSH connection from your terminal.
+
+1.
+## 3. Floating IP {#nastaveni_routeru}
+
+## 4. Router settings {#nastaveni_site}
+
+
+
+NynĂ vytvoĹ™Ăme virtuálnĂ router, kterĂ˝m spojĂme vytvoĹ™enou internĂ sĂĹĄ s veĹ™ejnou sĂtĂ. V sekci: **1.Project** → **2.Network** → **3.Routers** klikneme na **4. Create router**.
+
+6Zde pojmenujeme router a zvolĂme veĹ™ejnou sĂĹĄ public-float-21, kterou mu pĹ™iĹ™adĂme:
+
+NynĂ musĂme spojit prostĹ™ednictvĂm námi vytvoĹ™enĂ©ho routeru naši internĂ sĂĹĄ s veĹ™ejnou sĂtĂ \(public-float-21\).
+To uděláme následovně.
+7V nastavenà routerů klikneme na náš router:
+
+8Otevře se nám nastavenà rozhranà routeru, klikneme na_Add Interface_:
+
+9NynĂ uĹľ staÄŤĂ jen vybrat sĂĹĄ, kterou chceme propojit s veĹ™ejnou sĂtĂ:
-## Security groups
diff --git a/9-Privacy, GDPR and stuff/README.md b/9-Privacy, GDPR and stuff/README.md
new file mode 100644
index 0000000..e69de29
diff --git a/GLOSSARY.md b/GLOSSARY.md
index bac57a6..91665f6 100644
--- a/GLOSSARY.md
+++ b/GLOSSARY.md
@@ -1,3 +1,14 @@
# Glossary
-TODO
+## Instance
+
+OpenStack virtual machines are called instances, mostly because they are instances of an image that is created upon request and that is configured when launched. ... In the persistent model, the instance is launched from a persistent volume on a compute node, or from a block storage volume, and not from the Image service.
+
+## Security Group
+
+## Project
+
+
+
+
+
diff --git a/SUMMARY.md b/SUMMARY.md
index de52158..2fb7bb3 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -10,3 +10,5 @@
* [CLI](6-cli/README.md)
* [Orchestration](7-heat/README.md)
* [FAQ](8-faq/README.md)
+* [Privacy, GDPR and stuff](privacy-gdpr-and-stuff.md)
+
--
GitLab