Step-by-step guide

Add the steps involved:

1. Add a new internal network connected via a router to an additional external network

2. Create a new entry for the new interface and bring it up
   
   

   # cat /etc/sysconfig/network-scripts/ifcfg-eth1 BOOTPROTO=dhcp DEVICE=eth1 HWADDR=fa:16:3e:5c:29:91 ONBOOT=yes TYPE=Ethernet USERCTL=no # ifup eth1

   
   

3. List the current floating ip pools
   
   

   # nova floating-ip-pool-list +------------------+ | name | +------------------+ | services-vlan600 | | nova | | lab1-vlan541 | | aws-vlan542 | +------------------+

   
   

4. Create a new floating ip from the desired pool
   
   

   # nova floating-ip-create aws-vlan542 +--------------------------------------+-------------+-----------+----------+-------------+ | Id | IP | Server Id | Fixed IP | Pool | +--------------------------------------+-------------+-----------+----------+-------------+ | 0acbdab4-5138-47d2-ab95-6a743214fd71 | 172.16.85.1 | - | - | aws-vlan542 | +--------------------------------------+-------------+-----------+----------+-------------+

   
   

5. List the project instances
   
   

   # nova list +--------------------------------------+--------------+--------+------------+-------------+-------------------------------------------------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+--------------+--------+------------+-------------+-------------------------------------------------------------------------+ | 40b45fa5-715b-426b-a23f-f8be95a87edb | Confluence-1 | ACTIVE | - | Running | Access=10.1.0.14, 192.168.68.58; Management=10.3.0.10; Backend=10.2.0.5 | | 1f69f96b-e843-4e90-8fd7-dd41c873182f | Xwiki | ACTIVE | - | Running | Access=10.1.0.20, 192.168.68.98 | | d003fdfa-a616-41bd-8c7d-9cbdb1dc7ada | cert | ACTIVE | - | Running | Access=10.1.0.6, 192.168.68.82 | | a26658db-d97b-4724-82dd-d55d14795abd | gitlab | ACTIVE | - | Running | Access=10.1.0.26, 192.168.68.91; aws-internal=10.16.80.6 | | cc0cb7b8-46c1-4664-a18a-d47fbbfa716f | jira | ACTIVE | - | Running | Access=10.1.0.25, 192.168.68.104 | | 1309f59d-c938-4233-b209-b8e824f699f7 | oscm-1 | ACTIVE | - | Running | Access=10.1.0.5, 192.168.68.61; Management=10.3.0.11; Backend=10.2.0.6 | | b25efd8b-ce2e-4877-83a9-686ee5873338 | prometheus | ACTIVE | - | Running | Access=10.1.0.13, 192.168.68.68 | +--------------------------------------+--------------+--------+------------+-------------+-------------------------------------------------------------------------+

   
   

6. Associate the new floating ip
   
   

   # nova floating-ip-associate --fixed-address 10.16.80.6 gitlab 172.16.85.1

   
   

7. Check the new assignment
   
   

   # nova list +--------------------------------------+--------------+--------+------------+-------------+-------------------------------------------------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+--------------+--------+------------+-------------+-------------------------------------------------------------------------+ | 40b45fa5-715b-426b-a23f-f8be95a87edb | Confluence-1 | ACTIVE | - | Running | Access=10.1.0.14, 192.168.68.58; Management=10.3.0.10; Backend=10.2.0.5 | | 1f69f96b-e843-4e90-8fd7-dd41c873182f | Xwiki | ACTIVE | - | Running | Access=10.1.0.20, 192.168.68.98 | | d003fdfa-a616-41bd-8c7d-9cbdb1dc7ada | cert | ACTIVE | - | Running | Access=10.1.0.6, 192.168.68.82 | | a26658db-d97b-4724-82dd-d55d14795abd | gitlab | ACTIVE | - | Running | Access=10.1.0.26, 192.168.68.91; aws-internal=10.16.80.6, 172.16.85.1 | | cc0cb7b8-46c1-4664-a18a-d47fbbfa716f | jira | ACTIVE | - | Running | Access=10.1.0.25, 192.168.68.104 | | 1309f59d-c938-4233-b209-b8e824f699f7 | oscm-1 | ACTIVE | - | Running | Access=10.1.0.5, 192.168.68.61; Management=10.3.0.11; Backend=10.2.0.6 | | b25efd8b-ce2e-4877-83a9-686ee5873338 | prometheus | ACTIVE | - | Running | Access=10.1.0.13, 192.168.68.68 | +--------------------------------------+--------------+--------+------------+-------------+-------------------------------------------------------------------------+

   
   

8. On the Gitlab instance add the AWS network route via the AWS router
   
   

   # route add -net 172.16.80.0/20 gw 10.16.80.1

   
   

1. You can also copy and paste or drag and drop images into your instructions.

Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.