Merge branch 'fix/FIP' into 'master'

Fix FIP and Group FIP in networking.md

See merge request !54

topics/compute/openstack/docs/technical-reference/brno-g1-site/networking.md

@@ -11,7 +11,7 @@ search:
 
 ### IPv4 Personal Floating IPs
 
-It is currently limited to the common internal networks. You can start your machine in the `147-251-115-pers-proj-net` or `78-128-250-pers-proj-net` networks and allocate floating IP address from the `public-muni-147-251-115-PERSONAL` or `public-cesnet-78-128-250-PERSONAL` pools respectively. All VMs need to be connected to the same network. You cannot use virtual routers with personal projects. We encourage users to also use IPv6 addresses for long term use. Unassigned allocated addresses are released daily.
+It is currently limited to the common internal networks. You can start your machine in the `147-251-115-pers-proj-net` network and allocate floating IP address from the `public-muni-147-251-115-PERSONAL` pool. You can also try `78-128-250-pers-proj-net` network and allocate IP adress from `public-cesnet-78-128-250-PERSONAL`, but this network is not recommended as in we often see no available addresses there. Keep in mind that you should use matching network and public FIP pool (recommended: `147-251-115-pers-proj-net` + `public-muni-147-251-115-PERSONAL`) as OpenStack does not allow you to associate FIP address from mismatching pool with message `External network <ID> is not reachable from subnet <ID>. Therefore, cannot associate Port <ID> with a Floating IP...`. All VMs need to be connected to the same network. You cannot use virtual routers with personal projects. We encourage users to also use IPv6 addresses for long term use. Unassigned allocated addresses are released daily.
 
 ### IPv4 Group Floating IPs
 
@@ -21,7 +21,6 @@ The situation is rather different for group projects. You cannot use the same ap
  - `public-cesnet-195-113-167-GROUP`
  - `public-muni-147-251-21-GROUP`
  - `public-muni-147-251-124-GROUP`
- - `public-muni-147-251-255-GROUP`
 
 !!! warning