| 2017-11-23 17:11:19 |
Bogdan Dobrelya |
bug |
|
|
added bug |
| 2017-11-23 17:11:26 |
Bogdan Dobrelya |
tripleo: importance |
Undecided |
Medium |
|
| 2017-11-23 17:11:28 |
Bogdan Dobrelya |
tripleo: milestone |
|
queens-2 |
|
| 2017-11-23 17:11:32 |
Bogdan Dobrelya |
tripleo: status |
New |
Triaged |
|
| 2017-11-23 17:12:18 |
Bogdan Dobrelya |
tags |
|
quickstart |
|
| 2017-11-23 17:12:39 |
Bogdan Dobrelya |
summary |
Adapt config downloads for deployed servers |
Adapt config downloads in quickstart for deployed servers |
|
| 2017-11-23 17:14:03 |
Bogdan Dobrelya |
description |
In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap:
controller0-ctlplane:
fixed_ips:
- ip_address:
into configurable:
DeployedServerPortMap:
<host-cloud-nova-server-hostname>-ctlplane:
fixed_ips:
- ip_address: <host-cloud-ctlplane-subnet-IP> |
In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 , and a flag deploy_steps_ansible_workflow, that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap:
controller0-ctlplane:
fixed_ips:
- ip_address:
into configurable:
DeployedServerPortMap:
<host-cloud-nova-server-hostname>-ctlplane:
fixed_ips:
- ip_address: <host-cloud-ctlplane-subnet-IP> |
|
| 2017-11-23 17:18:06 |
Bogdan Dobrelya |
description |
In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 , and a flag deploy_steps_ansible_workflow, that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap:
controller0-ctlplane:
fixed_ips:
- ip_address:
into configurable:
DeployedServerPortMap:
<host-cloud-nova-server-hostname>-ctlplane:
fixed_ips:
- ip_address: <host-cloud-ctlplane-subnet-IP> |
In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 , and a flag deploy_steps_ansible_workflow, that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap:
controller0-ctlplane:
fixed_ips:
- ip_address:
into configurable:
DeployedServerPortMap:
<host-cloud-nova-server-hostname>-ctlplane:
fixed_ips:
- ip_address: <host-cloud-ctlplane-subnet-IP>
Note that, 'tripleo-ansible-inventory --list' command shows overcloud group only when there is an undercloud stack called "overcloud" exists.
If it's called something different, you have to export TRIPLEO_PLAN_NAME=foo. The issue is that the quickstart's config-download.yaml template expects the overcloud stack to already present, while it's being created later, when overcloud deploy commands executes.
This chicken and egg problem for deployed servers should be resolved as well. |
|
| 2017-11-23 17:20:12 |
Bogdan Dobrelya |
tags |
quickstart |
quickstart ux |
|
| 2017-11-23 17:25:54 |
Bogdan Dobrelya |
bug |
|
|
added subscriber Jiří Stránský |
| 2017-11-23 17:26:01 |
Bogdan Dobrelya |
bug |
|
|
added subscriber James Slagle |
| 2017-11-23 17:26:07 |
Bogdan Dobrelya |
bug |
|
|
added subscriber Steven Hardy |
| 2017-11-23 17:28:50 |
Bogdan Dobrelya |
description |
In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 , and a flag deploy_steps_ansible_workflow, that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap:
controller0-ctlplane:
fixed_ips:
- ip_address:
into configurable:
DeployedServerPortMap:
<host-cloud-nova-server-hostname>-ctlplane:
fixed_ips:
- ip_address: <host-cloud-ctlplane-subnet-IP>
Note that, 'tripleo-ansible-inventory --list' command shows overcloud group only when there is an undercloud stack called "overcloud" exists.
If it's called something different, you have to export TRIPLEO_PLAN_NAME=foo. The issue is that the quickstart's config-download.yaml template expects the overcloud stack to already present, while it's being created later, when overcloud deploy commands executes.
This chicken and egg problem for deployed servers should be resolved as well. |
In quickstart, there is a template https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/overcloud-deploy/templates/config-download.yaml.j2 , and a flag deploy_steps_ansible_workflow, that configures port mappings for deployed servers, yet does this too opinionated and consumable with only CI multinode cases.
The flexible approach should follow the deployed server docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deployed_server.html#network-configuration and allow users, say RDOcloud to meet their case, which is to transform :
DeployedServerPortMap:
controller0-ctlplane:
fixed_ips:
- ip_address:
into configurable:
DeployedServerPortMap:
<host-cloud-nova-server-hostname>-ctlplane:
fixed_ips:
- ip_address: <host-cloud-ctlplane-subnet-IP>
Note that, 'tripleo-ansible-inventory --list' command shows overcloud group only when there is an undercloud stack called "overcloud" exists.
If it's called something different, you have to export TRIPLEO_PLAN_NAME=foo. The issue is that the quickstart's config-download.yaml template expects the overcloud stack to already present, while it's being created later, when overcloud deploy commands executes.
For config download to work the deploy of the heat stack must already be complete, that's not that quickstart's deploy_steps_ansible_workflow follows yet.
This chicken and egg problem for deployed servers should be resolved as well. |
|
| 2017-12-05 00:08:23 |
Alex Schultz |
tripleo: milestone |
queens-2 |
queens-3 |
|
| 2018-01-26 00:57:43 |
Emilien Macchi |
tripleo: milestone |
queens-3 |
queens-rc1 |
|
| 2018-02-20 22:27:28 |
Alex Schultz |
tripleo: milestone |
queens-rc1 |
rocky-1 |
|
| 2018-04-20 17:10:03 |
Alex Schultz |
tripleo: milestone |
rocky-1 |
rocky-2 |
|
| 2018-06-05 19:14:39 |
Emilien Macchi |
tripleo: milestone |
rocky-2 |
rocky-3 |
|
| 2018-07-26 13:50:45 |
Emilien Macchi |
tripleo: milestone |
rocky-3 |
rocky-rc1 |
|
| 2018-07-26 15:28:39 |
Emilien Macchi |
tripleo: milestone |
rocky-rc1 |
stein-1 |
|
| 2018-10-30 16:20:35 |
Juan Antonio Osorio Robles |
tripleo: milestone |
stein-1 |
stein-2 |
|
| 2019-01-13 22:41:24 |
Emilien Macchi |
tripleo: milestone |
stein-2 |
stein-3 |
|
| 2019-03-13 23:20:43 |
Alex Schultz |
tripleo: milestone |
stein-3 |
train-1 |
|
| 2019-06-07 20:11:18 |
Alex Schultz |
tripleo: milestone |
train-1 |
train-2 |
|
| 2019-07-29 14:36:57 |
Alex Schultz |
tripleo: milestone |
train-2 |
train-3 |
|
| 2019-09-12 13:33:04 |
Alex Schultz |
tripleo: milestone |
train-3 |
ussuri-1 |
|
| 2019-12-19 15:10:47 |
Emilien Macchi |
tripleo: milestone |
ussuri-1 |
ussuri-2 |
|
| 2020-02-10 21:31:22 |
wes hayutin |
tripleo: milestone |
ussuri-2 |
ussuri-3 |
|
| 2020-04-13 18:16:02 |
wes hayutin |
tripleo: milestone |
ussuri-3 |
ussuri-rc3 |
|
| 2020-05-11 20:19:27 |
wes hayutin |
tripleo: status |
Triaged |
Incomplete |
|
| 2020-05-26 20:55:32 |
wes hayutin |
tripleo: milestone |
ussuri-rc3 |
victoria-1 |
|
| 2020-07-28 12:33:57 |
Emilien Macchi |
tripleo: milestone |
victoria-1 |
victoria-3 |
|
