Skip to content
Snippets Groups Projects
Verified Commit 3af55ddf authored by Jiří Brázdil's avatar Jiří Brázdil
Browse files

Merge branch 'feature/issue186_quick_start_part2'

parents 33260979 e6ac9d91
Branches
No related tags found
1 merge request!38Quick Start section - moved network info
Hide whitespace changes
Inline Side-by-side
network/README.md
+ 53
− 4
View file @ 3af55ddf
......@@ -35,6 +35,24 @@ Inside the interactive dialog:
3. For the last tab **Subnet Details** just check that a DNS is present and DHCP box is checked, alternatively you can create the allocation pool or specify static routes in here (for advanced users).
![](/network/images/5.png)
#### Setup Router gateway (Required for Group projects)
Completing [Create Virtual Machine Instance](/quick-start/#create-virtual-machine-instance) created instance connected
to software defined network represented by internal network, subnet and router. Router has by default gateway address
from External Network chosen by cloud administrators. You can change it to any External Network with [GROUP](/register/#group-project) suffix, that
is visible to you (e.g. **public-muni-147-251-124-GROUP** or **public-cesnet-78-128-251-GROUP**). Usage of External Networks
with suffix PERSONAL (e.g. **public-cesnet-78-128-250-PERSONAL**) is discouraged. IP addresses from
PERSONAL segments will be automatically released from Group projects.
For changing gateway IP address follow these steps:
1. In **Network > Routers**, click the **Set Gateway** button next to router.
If router exists with another settings, then use button Clear Gateway, confirm Clear Gateway.
If router isn't set then use button Create router and choose network.
2. From list of External Network choose **public-cesnet-78-128-251-GROUP**, **public-muni-147-251-124-GROUP** or any other [GROUP](/register/#group-project) network you see.
![](/network/images/network_routers-group.png)
Router is setup with persistent gateway.
#### Router creation
......@@ -50,11 +68,42 @@ Now you need to attach your internal network to the router.
3. Select a previously created subnet and submit.
![](/network/images/r3.png)
#### FIP allocation
Navigate yourself towards **Network > Floating IPs** in the left menu and click on the **Allocate IP To Project** on the right side of the window.
Select the same public network with `-GROUP` suffix as you did with the router. This is cruicial in order to network connection function correctly.
![](/network/images/f1.png)
#### 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 > Network > Floating IPs**, select **Allocate IP to Project**. Pick an IP pool from which to allocate
the address. Click on **Allocate IP**.
<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/>
In case of group projects when picking an IP pool from which to allocate a floating IP address, please, keep in mind that you have to allocate
an address in the pool connected to your virtual router.
</div>
<div style="border-width:0;border-left:5px solid #ff0000;background-color:rgba(255, 0, 0, 0.2);margin:20px 0;padding:10px 20px;font-size:15px;">
<strong>Warning:</strong><br/>
Group projects can persistently allocate IPs only from External Network with GROUP suffix (e.g. public-muni-147-251-124-GROUP or public-cesnet-78-128-251-GROUP).
IPs from External Networks with suffix PERSONAL (e.g. public-cesnet-78-128-250-PERSONAL) will be released automatically.
</div>
<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 explicitly 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>
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 and click on **Associate**.
![](/quick-start/images/network_floating_ip.png)
## Change external network in GUI
......
quick-start/README.md
+ 16
− 45
View file @ 3af55ddf
......@@ -184,58 +184,29 @@ ssh -A -X -i ~/.ssh/id_rsa debian@192.168.18.15
For details, refer to [the official documentation](https://docs.openstack.org/horizon/rocky/user/launch-instances.html).
## Setup Router gateway (Required for Group projects)
Completing [Create Virtual Machine Instance](/quick-start/#create-virtual-machine-instance) created instance connected
to software defined network represented by internal network, subnet and router. Router has by default gateway address
from External Network chosen by cloud administrators. You can change it to any External Network with [GROUP](/register/#group-project) suffix, that
is visible to you (e.g. **public-muni-147-251-124-GROUP** or **public-cesnet-78-128-251-GROUP**). Usage of External Networks
with suffix PERSONAL (e.g. **public-cesnet-78-128-250-PERSONAL**) is discouraged. IP addresses from
PERSONAL segments will be automatically released from Group projects.
For changing gateway IP address follow these steps:
1. In **Network &gt; Routers**, click the **Set Gateway** button next to router.
If router exists with another settings, then use button Clear Gateway, confirm Clear Gateway.
If router isn't set then use button Create router and choose network.
<div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(255,0,0,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
<strong>WARNING:</strong><br/><br/>
If you have <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#group-project">GROUP</a> project, you need to configure
Router gateway for your network. <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/network/#setup-router-gateway">Here</a> you can find the manual.
</div>
2. From list of External Network choose **public-cesnet-78-128-251-GROUP**, **public-muni-147-251-124-GROUP** or any other [GROUP](/register/#group-project) network you see.
## Setup Router gateway (Required for Group projects)
![](/quick-start/images/network_routers-group.png)
<div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(255,0,0,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
<strong>WARNING:</strong><br/><br/>
If you have <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#group-project">GROUP</a> project, you need to configure
Router gateway for your network. <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/network/#setup-router-gateway">Here</a> you can find the manual.
</div>
Router is setup with persistent gateway.
## 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; Network &gt; Floating IPs**, select **Allocate IP to Project**. Pick an IP pool from which to allocate
the address. Click on **Allocate IP**.
<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/>
In case of group projects when picking an IP pool from which to allocate a floating IP address, please, keep in mind that you have to allocate
an address in the pool connected to your virtual router.
</div>
<div style="border-width:0;border-left:5px solid #ff0000;background-color:rgba(255, 0, 0, 0.2);margin:20px 0;padding:10px 20px;font-size:15px;">
<strong>Warning:</strong><br/>
Group projects can persistently allocate IPs only from External Network with GROUP suffix (e.g. public-muni-147-251-124-GROUP or public-cesnet-78-128-251-GROUP).
IPs from External Networks with suffix PERSONAL (e.g. public-cesnet-78-128-250-PERSONAL) will be released automatically.
</div>
<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 explicitly 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>
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 and click on **Associate**.
![](/quick-start/images/network_floating_ip.png)
<div style="border-width:0;border-left:5px solid #b8d6f4;background-color:rgba(255,0,0,0.3);margin:20px 0;padding:10px 20px;font-size:15px;">
<strong>WARNING:</strong><br/><br/>
To make an instance accessible from external networks (e.g., The Internet), a so-called Floating IP Address has to be
associated with it. <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/network/#associate-floating-ip">Here</a> you can find the manual.
</div>
## Create Volume
......
register/README.md
+ 1
− 0
View file @ 3af55ddf
......@@ -5,6 +5,7 @@ one of the following identity federations
* __EINFRA CESNET__,
* __EGI Check-in__`*`,
* __ELIXIR AAI__`*`.
* __DEEP AAI__`*`.
Users from the Czech academic community should always use the `EINFRA CESNET`
identity provider, unless instructed otherwise by user support.
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment