Skip to content
Snippets Groups Projects
Unverified Commit b418a985 authored by Jaromír Hradil's avatar Jaromír Hradil
Browse files

Network section update part 2

parent a7139dc0
No related branches found
No related tags found
1 merge request!46Network section update part 2
...@@ -8,7 +8,8 @@ For the networking in Cloud2 metacentrum we need to distinguish following scenar ...@@ -8,7 +8,8 @@ For the networking in Cloud2 metacentrum we need to distinguish following scenar
<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;display: -webkit-inline-box;"> <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;display: -webkit-inline-box;">
<strong>WARNING:</strong><br/><br/> <strong>WARNING:</strong><br/><br/>
Please read the following rules: Please read the following rules:
1. If you are using a <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#personal-project">PERSONAL</a> project you have to use the `78-128-250-pers-proj-net` network to make your instance accesible from external network (e.g. Internet). Use `public-cesnet-78-128-250-PERSONAL` for FIP allocation, FIPs from this pool will be periodically released.
1. If you are using a <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#personal-project">PERSONAL</a> project you have to use the `78-128-250-pers-proj-net` network to make your instance accesible from external network (e.g. Internet). Use `public-cesnet-78-128-250-PERSONAL` for FIP allocation, FIPs from this pool will be periodically released.
2. If you are using a <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#group-project">GROUP</a> project you may choose from the `public-cesnet-78-128-251-GROUP`, `public-muni-147-251-124-GROUP` or any other <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#group-project">GROUP</a> network for FIP allocation to make your instance accesible from external network (e.g. Internet). 2. If you are using a <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#group-project">GROUP</a> project you may choose from the `public-cesnet-78-128-251-GROUP`, `public-muni-147-251-124-GROUP` or any other <a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/register/#group-project">GROUP</a> network for FIP allocation to make your instance accesible from external network (e.g. Internet).
3. Violation of the network usage may lead into resource removal and reducing of the quotas assigned. 3. Violation of the network usage may lead into resource removal and reducing of the quotas assigned.
</div> </div>
...@@ -24,6 +25,13 @@ Is currently limited to the common internal network. The network in which you sh ...@@ -24,6 +25,13 @@ Is currently limited to the common internal network. The network in which you sh
In group project situation is rather different. You cannot use the same approach as personal project (resources allocated in previously mentioned networks will be periodically released). For FIP you need to allocate from pools with `-GROUP` suffix (namely `public-cesnet-78-128-251-GROUP`, `public-muni-147-251-21-GROUP` or `public-muni-147-251-124-GROUP`). In group project situation is rather different. You cannot use the same approach as personal project (resources allocated in previously mentioned networks will be periodically released). For FIP you need to allocate from pools with `-GROUP` suffix (namely `public-cesnet-78-128-251-GROUP`, `public-muni-147-251-21-GROUP` or `public-muni-147-251-124-GROUP`).
<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 you use MUNI account, you can use private-muni-10-16-116 and log into the network via MUNI VPN or you can set up Proxy networking, which is described
<a href="https://cloud.gitlab-pages.ics.muni.cz/documentation/network/#proxy-networking">here</a>
</div>
#### Network creation #### Network creation
For group project you need to create internal network first, you may use autoallocated pool for subnet autocreation. For group project you need to create internal network first, you may use autoallocated pool for subnet autocreation.
...@@ -146,6 +154,12 @@ Now, you should navigate yourself to the **Project &gt; Network &gt; Routers**. ...@@ -146,6 +154,12 @@ Now, you should navigate yourself to the **Project &gt; Network &gt; Routers**.
### Allocate new Floating IP(s) ### Allocate new Floating IP(s)
<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>Warning:</strong><br/>
New floating IP address for router must be from same network pool which was selected as new gateway.
</div>
1. Go to **Project &gt; Network &gt; Floating IPs** and click on the **Allocate IP to Project** button. Select **Pool** with the same value as the network you chose in the previous step and confirm it by clicking **Allocate IP** 1. Go to **Project &gt; Network &gt; Floating IPs** and click on the **Allocate IP to Project** button. Select **Pool** with the same value as the network you chose in the previous step and confirm it by clicking **Allocate IP**
![](/network/images/allocate-fip.png) ![](/network/images/allocate-fip.png)
...@@ -279,5 +293,3 @@ $ openstack floating ip create public-cesnet-78-128-251 ...@@ -279,5 +293,3 @@ $ openstack floating ip create public-cesnet-78-128-251
``` ```
$ openstack server add floating ip net-test1 78.128.251.27 $ openstack server add floating ip net-test1 78.128.251.27
``` ```
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment