SBs Public IP Modification (#216)

* SB01 Public IP Modify * SB02 Public IP Modify * SB04 Public IP Modify * SB05 Public IP Modify * SB06 Public IP Modify * SB07 Public IP Modify * Fix Spaceing * SB08 Public IP Modify * SB09 Public IP Modify * SB10 Public IP Modify * SB11 Public IP Modify * SB12 Update Docs * SB13 Public IP Modify * Fix Spaceing * SB14 Public IP Modify * SB15 Public IP Modify * SB03 Public IP Modify
netrisai · Apr 23, 2024 · 2a0ebbd · 2a0ebbd
1 parent 6a552ea
commit 2a0ebbd
Show file tree

Hide file tree

Showing 61 changed files with 439 additions and 406 deletions.
diff --git a/sandbox/Sandbox1/configurations.rst b/sandbox/Sandbox1/configurations.rst
@@ -70,7 +70,7 @@ You may also observe the functioning NAT rule in action by pinging any public IP
 
 * In a terminal window:
 
-  1. SSH to server **srv04-nyc**: ``ssh demo@166.88.17.24 -p 30064``.
+  1. SSH to server **srv04-nyc**: ``ssh demo@216.172.128.201 -p 30064``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session: ``ping4 1.1.1.1``
 

diff --git a/sandbox/Sandbox1/creating-services.rst b/sandbox/Sandbox1/creating-services.rst
@@ -17,7 +17,7 @@ Let's create a V-Net service to give server **srv05-nyc** the ability to reach i
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.24 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.201 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Type ``ip route ls`` and we can see **192.168.46.1** is configured as the default gateway, indicated by the "**default via 192.168.46.1 dev eth1 proto kernel onlink**" line in the output.
   4. Start a ping session towards the default gateway: ``ping 192.168.46.1``
@@ -90,7 +90,7 @@ Now that we have both internal and external facing services, we can aim for our
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.24 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.201 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session towards any public IP address (e.g. ``ping 1.1.1.1``).
   4. Keep the ping running as an indicator for when the service starts to work.
@@ -176,7 +176,7 @@ Now that **srv05-nyc** can communicate with both internal and external hosts, le
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.24 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.201 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session: ``ping 1.1.1.1``.
   4. If the previous steps were followed, you should see successful ping replies in the form of "**64 bytes from 1.1.1.1: icmp_seq=55 ttl=62 time=1.23 ms**".

diff --git a/sandbox/Sandbox1/index.rst b/sandbox/Sandbox1/index.rst
@@ -7,7 +7,7 @@
   ------------------------------------------------------------------------------------------------ 
   Sandbox1                   # Sandbox name Uppercase(case sensitive)
   sandbox1                   # Sandbox name Lowercase
-  166.88.17.24               # Hypervisor PUBLIC IP
+  216.172.128.201            # Hypervisor PUBLIC IP
   10.254.45.0/24             # *STATIC NO NEED TO REPLACE* MANAGEMENT Allocation/Subnet
   10.254.46.0/24             # *STATIC NO NEED TO REPLACE* LOOPBACK Allocation/Subnet
   192.168.44.0/24            # *STATIC NO NEED TO REPLACE* ROH Allocation/Subnet

diff --git a/sandbox/Sandbox1/sandbox-info.rst b/sandbox/Sandbox1/sandbox-info.rst
@@ -49,11 +49,11 @@ Example pre-configured Netris services:
 
 .. code-block:: shell-session
 
-  srv01-nyc: ssh demo@166.88.17.24 -p 30061
-  srv02-nyc: ssh demo@166.88.17.24 -p 30062
-  srv03-nyc: ssh demo@166.88.17.24 -p 30063
-  srv04-nyc: ssh demo@166.88.17.24 -p 30064
-  srv05-nyc: ssh demo@166.88.17.24 -p 30065
+  srv01-nyc: ssh demo@216.172.128.201 -p 30061
+  srv02-nyc: ssh demo@216.172.128.201 -p 30062
+  srv03-nyc: ssh demo@216.172.128.201 -p 30063
+  srv04-nyc: ssh demo@216.172.128.201 -p 30064
+  srv05-nyc: ssh demo@216.172.128.201 -p 30065
 
 
 Kubernetes cluster

diff --git a/sandbox/Sandbox10/configurations.rst b/sandbox/Sandbox10/configurations.rst
@@ -62,7 +62,7 @@ You may also observe the functioning NAT rule in action by pinging any public IP
 
 * In a terminal window:                                                                                   
 
-  1. SSH to server **srv04-nyc**: ``ssh demo@166.88.17.19 -p 30064``.
+  1. SSH to server **srv04-nyc**: ``ssh demo@216.172.128.210 -p 30064``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session: ``ping4 1.1.1.1``
 

diff --git a/sandbox/Sandbox10/creating-services.rst b/sandbox/Sandbox10/creating-services.rst
@@ -14,7 +14,7 @@ Let's create a V-Net service to give server **srv05-nyc** the ability to reach i
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.19 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.210 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Type ``ip route ls`` and we can see **192.168.46.1** is configured as the default gateway, indicated by the "**default via 192.168.46.1 dev eth1 proto kernel onlink**" line in the output.
   4. Start a ping session towards the default gateway: ``ping 192.168.46.1`` 
@@ -86,7 +86,7 @@ Now that we have both internal and external facing services, we can aim for our
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.19 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.210 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session towards any public IP address (e.g. ``ping 1.1.1.1``).
   4. Keep the ping running as an indicator for when the service starts to work.
@@ -168,7 +168,7 @@ Now that **srv05-nyc** can communicate with both internal and external hosts, le
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.19 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.210 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session: ``ping 1.1.1.1``.
   4. If the previous steps were followed, you should see successful ping replies in the form of "**64 bytes from 1.1.1.1: icmp_seq=55 ttl=62 time=1.23 ms**".

diff --git a/sandbox/Sandbox10/index.rst b/sandbox/Sandbox10/index.rst
@@ -7,7 +7,7 @@
   ------------------------------------------------------------------------------------------------ 
   Sandbox10                  # Sandbox name Uppercase(case sensitive)
   sandbox10                  # Sandbox name Lowercase
-  166.88.17.19               # Hypervisor PUBLIC IP
+  216.172.128.210            # Hypervisor PUBLIC IP
   10.254.45.0/24             # *STATIC NO NEED TO REPLACE* MANAGEMENT Allocation/Subnet
   10.254.46.0/24             # *STATIC NO NEED TO REPLACE* LOOPBACK Allocation/Subnet
   192.168.44.0/24            # *STATIC NO NEED TO REPLACE* ROH Allocation/Subnet

diff --git a/sandbox/Sandbox10/sandbox-info.rst b/sandbox/Sandbox10/sandbox-info.rst
@@ -46,11 +46,11 @@ Example pre-configured Netris services:
 
 .. code-block:: shell-session  
   
-  srv01-nyc: ssh demo@166.88.17.19 -p 30061
-  srv02-nyc: ssh demo@166.88.17.19 -p 30062
-  srv03-nyc: ssh demo@166.88.17.19 -p 30063
-  srv04-nyc: ssh demo@166.88.17.19 -p 30064
-  srv05-nyc: ssh demo@166.88.17.19 -p 30065
+  srv01-nyc: ssh demo@216.172.128.210 -p 30061
+  srv02-nyc: ssh demo@216.172.128.210 -p 30062
+  srv03-nyc: ssh demo@216.172.128.210 -p 30063
+  srv04-nyc: ssh demo@216.172.128.210 -p 30064
+  srv05-nyc: ssh demo@216.172.128.210 -p 30065
   
 
 Kubernetes cluster

diff --git a/sandbox/Sandbox11/configurations.rst b/sandbox/Sandbox11/configurations.rst
@@ -70,7 +70,7 @@ You may also observe the functioning NAT rule in action by pinging any public IP
 
 * In a terminal window:
 
-  1. SSH to server **srv04-nyc**: ``ssh demo@50.117.27.82 -p 30064``.
+  1. SSH to server **srv04-nyc**: ``ssh demo@216.172.128.211 -p 30064``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session: ``ping4 1.1.1.1``
 

diff --git a/sandbox/Sandbox11/creating-services.rst b/sandbox/Sandbox11/creating-services.rst
@@ -17,7 +17,7 @@ Let's create a V-Net service to give server **srv05-nyc** the ability to reach i
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@50.117.27.82 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.211 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Type ``ip route ls`` and we can see **192.168.46.1** is configured as the default gateway, indicated by the "**default via 192.168.46.1 dev eth1 proto kernel onlink**" line in the output.
   4. Start a ping session towards the default gateway: ``ping 192.168.46.1``
@@ -90,7 +90,7 @@ Now that we have both internal and external facing services, we can aim for our
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@50.117.27.82 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.211 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session towards any public IP address (e.g. ``ping 1.1.1.1``).
   4. Keep the ping running as an indicator for when the service starts to work.
@@ -176,7 +176,7 @@ Now that **srv05-nyc** can communicate with both internal and external hosts, le
 
 * In a terminal window:
 
-  1. SSH to server **srv05-nyc**: ``ssh demo@50.117.27.82 -p 30065``.
+  1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.211 -p 30065``.
   2. Enter the password provided in the introductory e-mail.
   3. Start a ping session: ``ping 1.1.1.1``.
   4. If the previous steps were followed, you should see successful ping replies in the form of "**64 bytes from 1.1.1.1: icmp_seq=55 ttl=62 time=1.23 ms**".

diff --git a/sandbox/Sandbox11/index.rst b/sandbox/Sandbox11/index.rst
@@ -7,7 +7,7 @@
   ------------------------------------------------------------------------------------------------ 
   Sandbox11                  # Sandbox name Uppercase(case sensitive)
   sandbox11                  # Sandbox name Lowercase
-  50.117.27.82               # Hypervisor PUBLIC IP
+  216.172.128.211            # Hypervisor PUBLIC IP
   10.254.45.0/24             # *STATIC NO NEED TO REPLACE* MANAGEMENT Allocation/Subnet
   10.254.46.0/24             # *STATIC NO NEED TO REPLACE* LOOPBACK Allocation/Subnet
   192.168.44.0/24            # *STATIC NO NEED TO REPLACE* ROH Allocation/Subnet

diff --git a/sandbox/Sandbox11/sandbox-info.rst b/sandbox/Sandbox11/sandbox-info.rst
@@ -49,11 +49,11 @@ Example pre-configured Netris services:
 
 .. code-block:: shell-session
 
-  srv01-nyc: ssh demo@50.117.27.82 -p 30061
-  srv02-nyc: ssh demo@50.117.27.82 -p 30062
-  srv03-nyc: ssh demo@50.117.27.82 -p 30063
-  srv04-nyc: ssh demo@50.117.27.82 -p 30064
-  srv05-nyc: ssh demo@50.117.27.82 -p 30065
+  srv01-nyc: ssh demo@216.172.128.211 -p 30061
+  srv02-nyc: ssh demo@216.172.128.211 -p 30062
+  srv03-nyc: ssh demo@216.172.128.211 -p 30063
+  srv04-nyc: ssh demo@216.172.128.211 -p 30064
+  srv05-nyc: ssh demo@216.172.128.211 -p 30065
 
 
 Kubernetes cluster