Ask Your Question

Revision history [back]

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-
Availability VMs from undercloud Outbound connectivity for those VMs

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

VMs

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

Log into Controller && source file overcloudrc ( pick it up under /home/stack)

1. Delete old external && old private && old neutron router
2. create new as advised external shared
3. Create new tenant and user1 ( say user1 and ostenant , make user1 admin for ostenant)
4. Create keystoner_user1 having overcloud as sample
5. Source keystone_user1
6. Create new router && private network
and so on as usual

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

Log into Controller && source file overcloudrc ( pick it up under /home/stack)

1. Delete old external && old private && old neutron router
2. create new as advised external shared
3. Create new tenant and user1 ( say user1 and ostenant , make user1 admin for ostenant)
4. Create keystoner_user1 having overcloud as sample
5. Source keystone_user1
6. Create new router && private network
and so on as usual

Would like GUI setup FoxyProxy per https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-one-hosted-server/

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

Log into Controller && source file overcloudrc ( pick it up under /home/stack)

1. Delete old external && old private && old neutron router
2. create new as advised external shared
3. Create new tenant and user1 ( say user1 and ostenant , make user1 admin for ostenant)
4. Create keystoner_user1 having overcloud as sample
5. Source keystone_user1
6. Create new router && private network
and so on as usual

Would you like Dashboard GUI setup FoxyProxy per https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-one-hosted-server/

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

Log into Controller && source file overcloudrc ( pick it up under /home/stack)

1. Delete old external && old private && old neutron router
2. create new as advised external shared
3. Create new tenant and user1 ( say user1 and ostenant , make user1 admin for ostenant)
4. Create keystoner_user1 having overcloud as sample
5. Source keystone_user1
6. Create new router && private network
and so on as usual

Would you like Dashboard GUI setup FoxyProxy per https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-one-hosted-server/
Neutron reports on undercloud TripleO QuickStart

[stack@undercloud ~]$ neutron net-list
+--------------------------------------+----------+---------------------------------------------------+
| id                                   | name     | subnets                                           |
+--------------------------------------+----------+---------------------------------------------------+
| 31ad0819-160f-49d5-a8e6-828ccc58c1b0 | ctlplane | 51b2a558-6cd0-48c8-8d89-0959d4fb659c 192.0.2.0/24 |
+--------------------------------------+----------+---------------------------------------------------+
[stack@undercloud ~]$ neutron subnet-list
+--------------------------------------+------+--------------+----------------------------------------+
| id                                   | name | cidr         | allocation_pools                       |
+--------------------------------------+------+--------------+----------------------------------------+
| 51b2a558-6cd0-48c8-8d89-0959d4fb659c |      | 192.0.2.0/24 | {"start": "192.0.2.5", "end":          |
|                                      |      |              | "192.0.2.30"}                          |
+--------------------------------------+------+--------------+----------------------------------------+
[stack@undercloud ~]$ neutron port-list
+------------------------------+--------------------+-------------------+-------------------------------+
| id                           | name               | mac_address       | fixed_ips                     |
+------------------------------+--------------------+-------------------+-------------------------------+
| 439fa4d1-3d3c-48f6-abaa-     | control_virtual_ip | fa:16:3e:31:83:07 | {"subnet_id": "51b2a558-6cd0- |
| 37f10e279cef                 |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.6"}    |
| 4eeb846d-007a-458f-          |                    | 00:8f:77:64:a5:6c | {"subnet_id": "51b2a558-6cd0- |
| 9a42-ed485c6dfc2e            |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.12"}   |
| 504c0a34-51a9-4a77-a0b4-20c6 |                    | 00:8f:77:64:a5:78 | {"subnet_id": "51b2a558-6cd0- |
| 065142ba                     |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.10"}   |
| 702bd7be-784c-               |                    | 00:8f:77:64:a5:7c | {"subnet_id": "51b2a558-6cd0- |
| 45c3-ac11-e701fcfe8658       |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.8"}    |
| 805d0833-96c5-4fb2-85da-     |                    | 00:8f:77:64:a5:70 | {"subnet_id": "51b2a558-6cd0- |
| 430a0eabfc94                 |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.9"}    |
| 81c91950-043b-4117-9989-c84d |                    | fa:16:3e:37:b3:53 | {"subnet_id": "51b2a558-6cd0- |
| 7fcd4d75                     |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.5"}    |
| d0a49996-9029-481a-81bf-     |                    | 00:8f:77:64:a5:74 | {"subnet_id": "51b2a558-6cd0- |
| d9e421db8537                 |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.11"}   |
| ffa9aab0-6d23-4b37-8258-4dbb | redis_virtual_ip   | fa:16:3e:16:45:00 | {"subnet_id": "51b2a558-6cd0- |
| d5fcf249                     |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.7"}    |
+------------------------------+--------------------+-------------------+-------------------------------+

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

Log into Controller && source file overcloudrc ( pick it up under /home/stack)

1. Delete old external && old private && old neutron router
2. create new as advised external shared
3. Create new tenant and user1 ( say user1 and ostenant , make user1 admin for ostenant)
4. Create keystoner_user1 having overcloud as sample
5. Source keystone_user1
6. Create new router && private network
and so on as usual

Would you like Dashboard GUI setup FoxyProxy per https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-one-hosted-server/
Neutron reports on undercloud TripleO QuickStartPer http://docs.openstack.org/developer/tripleo-docs/environments/environments.html

image description

[stack@undercloud ~]$ neutron net-list
+--------------------------------------+----------+---------------------------------------------------+
| id                                   | name     | subnets                                           |
+--------------------------------------+----------+---------------------------------------------------+
| 31ad0819-160f-49d5-a8e6-828ccc58c1b0 | ctlplane | 51b2a558-6cd0-48c8-8d89-0959d4fb659c 192.0.2.0/24 |
+--------------------------------------+----------+---------------------------------------------------+
[stack@undercloud ~]$ neutron subnet-list
+--------------------------------------+------+--------------+----------------------------------------+
| id                                   | name | cidr         | allocation_pools                       |
+--------------------------------------+------+--------------+----------------------------------------+
| 51b2a558-6cd0-48c8-8d89-0959d4fb659c |      | 192.0.2.0/24 | {"start": "192.0.2.5", "end":          |
|                                      |      |              | "192.0.2.30"}                          |
+--------------------------------------+------+--------------+----------------------------------------+
[stack@undercloud ~]$ neutron port-list
+------------------------------+--------------------+-------------------+-------------------------------+
| id                           | name               | mac_address       | fixed_ips                     |
+------------------------------+--------------------+-------------------+-------------------------------+
| 439fa4d1-3d3c-48f6-abaa-     | control_virtual_ip | fa:16:3e:31:83:07 | {"subnet_id": "51b2a558-6cd0- |
| 37f10e279cef                 |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.6"}    |
| 4eeb846d-007a-458f-          |                    | 00:8f:77:64:a5:6c | {"subnet_id": "51b2a558-6cd0- |
| 9a42-ed485c6dfc2e            |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.12"}   |
| 504c0a34-51a9-4a77-a0b4-20c6 |                    | 00:8f:77:64:a5:78 | {"subnet_id": "51b2a558-6cd0- |
| 065142ba                     |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.10"}   |
| 702bd7be-784c-               |                    | 00:8f:77:64:a5:7c | {"subnet_id": "51b2a558-6cd0- |
| 45c3-ac11-e701fcfe8658       |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.8"}    |
| 805d0833-96c5-4fb2-85da-     |                    | 00:8f:77:64:a5:70 | {"subnet_id": "51b2a558-6cd0- |
| 430a0eabfc94                 |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.9"}    |
| 81c91950-043b-4117-9989-c84d |                    | fa:16:3e:37:b3:53 | {"subnet_id": "51b2a558-6cd0- |
| 7fcd4d75                     |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.5"}    |
| d0a49996-9029-481a-81bf-     |                    | 00:8f:77:64:a5:74 | {"subnet_id": "51b2a558-6cd0- |
| d9e421db8537                 |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.11"}   |
| ffa9aab0-6d23-4b37-8258-4dbb | redis_virtual_ip   | fa:16:3e:16:45:00 | {"subnet_id": "51b2a558-6cd0- |
| d5fcf249                     |                    |                   | 48c8-8d89-0959d4fb659c",      |
|                              |                    |                   | "ip_address": "192.0.2.7"}    |
+------------------------------+--------------------+-------------------+-------------------------------+
  On Snapshot above every overcolud node has 2 interfaces. The first one you have it's in Virtual Environment. It's colour is "Green". Consider colour "Yellow", Color "Yellow"  at least in Triple0 QuickStart is present only on UNDERCLOUD and nowhere else. Reports posted as UPDATEs to your answer are quite the same as TripleO QuickStart CURRENTLY does. Due to in meantime "TripleO  QuickStart" per my very personal opinion based
     on recent discussion @RDO Mailing list is a work in progress.

Per reports provided :-
1. Create external virtual network 192.0.2.0/24 with gateway 192.0.2.1
2. When created overcloud VMs will obtain FIPs on 192.0.2.0/24 . It will result :-

Availability VMs  from  undercloud 
Outbound connectivity for those VMs

Log into Controller && source file overcloudrc ( pick it up under /home/stack)

1. Delete old external && old private && old neutron router
2. create new as advised external shared
3. Create new tenant and user1 ( say user1 and ostenant , make user1 admin for ostenant)
4. Create keystoner_user1 having overcloud as sample
5. Source keystone_user1
6. Create new router && private network
and so on as usual

Would you like Dashboard GUI setup FoxyProxy per https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-one-hosted-server/
Per http://docs.openstack.org/developer/tripleo-docs/environments/environments.html

image description

  On Snapshot above every overcolud node has 2 interfaces. The first one you have it's in Virtual Environment. It's colour is "Green". Consider colour "Yellow", Color "Yellow"  at least in Triple0 QuickStart is present only on UNDERCLOUD and nowhere else. Reports posted as UPDATEs to your answer are quite the same as TripleO QuickStart CURRENTLY does. Due to in meantime "TripleO  QuickStart" per my very personal opinion based
     on recent discussion @RDO Mailing list is a work in progress.

As of now I am using approach suggested in https://www.linux.com/blog/set-vm-connect-tripleo-quickstart-overcloud-virt-manager-gui using several VMs like RemoteConsole ( slang from posting ) for several users. Having corresponding ssh-keypairs copied each one to particular RemoteConsole(X) accessible by particular users