Activity log for bug #1432401

Date Who What changed Old value New value Message
2015-03-15 17:40:01 Travis Tripp bug added bug
2015-03-15 17:40:11 Travis Tripp horizon: status New In Progress
2015-03-15 17:40:16 Travis Tripp horizon: assignee Travis Tripp (travis-tripp)
2015-03-16 02:08:56 OpenStack Infra horizon: assignee Travis Tripp (travis-tripp) Shaoquan Chen (sean-chen2)
2015-03-16 06:05:48 OpenStack Infra horizon: assignee Shaoquan Chen (sean-chen2) Brian Tully (brian-tully)
2015-03-16 06:08:48 Brian Tully horizon: assignee Brian Tully (brian-tully)
2015-03-16 06:10:31 Brian Tully horizon: assignee Brian Tully (brian-tully)
2015-03-16 06:10:37 OpenStack Infra horizon: assignee Brian Tully (brian-tully) Shaoquan Chen (sean-chen2)
2015-03-16 06:28:42 OpenStack Infra horizon: assignee Shaoquan Chen (sean-chen2) Brian Tully (brian-tully)
2015-03-16 17:42:29 Shaoquan Chen horizon: assignee Brian Tully (brian-tully) Shaoquan Chen (sean-chen2)
2015-03-18 23:34:07 Travis Tripp summary New Launch instance wizard should not display networks when neutron is not enabled. [Launch Instance Fix] Should not display networks when neutron is not enabled
2015-03-18 23:35:23 OpenStack Infra horizon: assignee Shaoquan Chen (sean-chen2) Travis Tripp (travis-tripp)
2015-03-22 03:29:04 OpenStack Infra horizon: assignee Travis Tripp (travis-tripp) Shaoquan Chen (sean-chen2)
2015-03-26 00:20:23 OpenStack Infra horizon: assignee Shaoquan Chen (sean-chen2) Travis Tripp (travis-tripp)
2015-03-27 04:35:26 OpenStack Infra horizon: assignee Travis Tripp (travis-tripp) Richard Jones (r1chardj0n3s)
2015-03-27 05:00:26 OpenStack Infra horizon: assignee Richard Jones (r1chardj0n3s) Travis Tripp (travis-tripp)
2015-03-27 23:50:09 Travis Tripp description New Launch instance wizard should not display networks when neutron is not enabled. See: https://review.openstack.org/#/c/164359/ New Launch instance wizard should not display networks when neutron is not enabled. See: https://review.openstack.org/#/c/164359/ To test this in a single environment, ensure that you have neutron setup properly. Then setup a two region environment. In Horizon openstack_dashboard/local/local_setting.py Uncomment / add the following (assumes keystone running locally) AVAILABLE_REGIONS = [ ('http://127.0.0.1:5000/v2.0', 'RegionOne'), ('http://localhost:5000/v2.0', 'RegionTwo'), ] Use the keystone command line client to get the service list. You'll need the IDs later. source <devstack-location>/openrc admin admin keystone service-list Then create endpoint entries in the keystone service catalog for the second region. In that region do not add an endpoint for neutron. The following shell script will accomplish this. Just replace the id's appropriately from the service list above. Then in horizon, login with RegionOne. Open Launch Instance. Observe networks step loads properly (assuming you actually have neutron) Use the project / region select on top toolbar to switch to RegionTwo. - Do no use the far right one Launch instance. Observe that network step is no longer available. ----------- Shell script below for creating endpoints --------- #!/bin/bash region_name=RegionTwo compute_svc=<replace with service id> computev2_1_svc=<replace with service id> network_svc=<replace with service id> image_svc=<replace with service id> volume_svc=<replace with service id> volumev2_svc=<replace with service id> # keystone endpoint-get --service compute keystone endpoint-create --region $region_name --service $compute_svc --publicurl 'http://localhost:8774/v2/$(tenant_id)s' --adminurl 'http://localhost:8774/v2/$(tenant_id)s' --internalurl 'http://localhost:8774/v2/$(tenant_id)s' # compute v2.1 keystone endpoint-create --region $region_name --service $computev2_1_svc --publicurl 'http://localhost:8774/v2.1/$(tenant_id)s' --adminurl 'http://localhost:8774/v2.1/$(tenant_id)s' --internalurl 'http://localhost:8774/v2.1/$(tenant_id)s' # image keystone endpoint-create --region $region_name --service $image_svc --publicurl 'http://127.0.0.1:9292' --adminurl 'http://127.0.0.1:9292' --internalurl 'http://127.0.0.1:9292' # volume keystone endpoint-create --region $region_name --service $volume_svc --publicurl 'http://localhost:8776/v1/$(tenant_id)s' --adminurl 'http://localhost:8776/v1/$(tenant_id)s' --internalurl 'http://localhost:8776/v1/$(tenant_id)s' # volume v2 keystone endpoint-create --region $region_name --service $volumev2_svc --publicurl 'http://localhost:8776/v2/$(tenant_id)s' --adminurl 'http://localhost:8776/v2/$(tenant_id)s' --internalurl 'http://localhost:8776/v2/$(tenant_id)s' #network Uncomment following to also create network endpoint #keystone endpoint-create --region $region_name --service $network_svc --publicurl 'http://localhost:9696' --adminurl 'http://localhost:9696' --internalurl 'http://localhost:9696'
2015-03-27 23:56:32 Travis Tripp summary [Launch Instance Fix] Should not display networks when neutron is not enabled [Launch Instance Fix] - MultiRegion Support / Networks
2015-03-27 23:57:01 Travis Tripp description New Launch instance wizard should not display networks when neutron is not enabled. See: https://review.openstack.org/#/c/164359/ To test this in a single environment, ensure that you have neutron setup properly. Then setup a two region environment. In Horizon openstack_dashboard/local/local_setting.py Uncomment / add the following (assumes keystone running locally) AVAILABLE_REGIONS = [ ('http://127.0.0.1:5000/v2.0', 'RegionOne'), ('http://localhost:5000/v2.0', 'RegionTwo'), ] Use the keystone command line client to get the service list. You'll need the IDs later. source <devstack-location>/openrc admin admin keystone service-list Then create endpoint entries in the keystone service catalog for the second region. In that region do not add an endpoint for neutron. The following shell script will accomplish this. Just replace the id's appropriately from the service list above. Then in horizon, login with RegionOne. Open Launch Instance. Observe networks step loads properly (assuming you actually have neutron) Use the project / region select on top toolbar to switch to RegionTwo. - Do no use the far right one Launch instance. Observe that network step is no longer available. ----------- Shell script below for creating endpoints --------- #!/bin/bash region_name=RegionTwo compute_svc=<replace with service id> computev2_1_svc=<replace with service id> network_svc=<replace with service id> image_svc=<replace with service id> volume_svc=<replace with service id> volumev2_svc=<replace with service id> # keystone endpoint-get --service compute keystone endpoint-create --region $region_name --service $compute_svc --publicurl 'http://localhost:8774/v2/$(tenant_id)s' --adminurl 'http://localhost:8774/v2/$(tenant_id)s' --internalurl 'http://localhost:8774/v2/$(tenant_id)s' # compute v2.1 keystone endpoint-create --region $region_name --service $computev2_1_svc --publicurl 'http://localhost:8774/v2.1/$(tenant_id)s' --adminurl 'http://localhost:8774/v2.1/$(tenant_id)s' --internalurl 'http://localhost:8774/v2.1/$(tenant_id)s' # image keystone endpoint-create --region $region_name --service $image_svc --publicurl 'http://127.0.0.1:9292' --adminurl 'http://127.0.0.1:9292' --internalurl 'http://127.0.0.1:9292' # volume keystone endpoint-create --region $region_name --service $volume_svc --publicurl 'http://localhost:8776/v1/$(tenant_id)s' --adminurl 'http://localhost:8776/v1/$(tenant_id)s' --internalurl 'http://localhost:8776/v1/$(tenant_id)s' # volume v2 keystone endpoint-create --region $region_name --service $volumev2_svc --publicurl 'http://localhost:8776/v2/$(tenant_id)s' --adminurl 'http://localhost:8776/v2/$(tenant_id)s' --internalurl 'http://localhost:8776/v2/$(tenant_id)s' #network Uncomment following to also create network endpoint #keystone endpoint-create --region $region_name --service $network_svc --publicurl 'http://localhost:9696' --adminurl 'http://localhost:9696' --internalurl 'http://localhost:9696' New Launch instance wizard should not display networks when neutron is not enabled. It needs to account for multi-region differences and the user's currently selected region. See: https://review.openstack.org/#/c/164359/ To test this in a single environment, ensure that you have neutron setup properly. Then setup a two region environment. In Horizon openstack_dashboard/local/local_setting.py Uncomment / add the following (assumes keystone running locally) AVAILABLE_REGIONS = [     ('http://127.0.0.1:5000/v2.0', 'RegionOne'),     ('http://localhost:5000/v2.0', 'RegionTwo'), ] Use the keystone command line client to get the service list. You'll need the IDs later. source <devstack-location>/openrc admin admin keystone service-list Then create endpoint entries in the keystone service catalog for the second region. In that region do not add an endpoint for neutron. The following shell script will accomplish this. Just replace the id's appropriately from the service list above. Then in horizon, login with RegionOne. Open Launch Instance. Observe networks step loads properly (assuming you actually have neutron) Use the project / region select on top toolbar to switch to RegionTwo.  - Do no use the far right one Launch instance. Observe that network step is no longer available. ----------- Shell script below for creating endpoints --------- #!/bin/bash region_name=RegionTwo compute_svc=<replace with service id> computev2_1_svc=<replace with service id> network_svc=<replace with service id> image_svc=<replace with service id> volume_svc=<replace with service id> volumev2_svc=<replace with service id> # keystone endpoint-get --service compute keystone endpoint-create --region $region_name --service $compute_svc --publicurl 'http://localhost:8774/v2/$(tenant_id)s' --adminurl 'http://localhost:8774/v2/$(tenant_id)s' --internalurl 'http://localhost:8774/v2/$(tenant_id)s' # compute v2.1 keystone endpoint-create --region $region_name --service $computev2_1_svc --publicurl 'http://localhost:8774/v2.1/$(tenant_id)s' --adminurl 'http://localhost:8774/v2.1/$(tenant_id)s' --internalurl 'http://localhost:8774/v2.1/$(tenant_id)s' # image keystone endpoint-create --region $region_name --service $image_svc --publicurl 'http://127.0.0.1:9292' --adminurl 'http://127.0.0.1:9292' --internalurl 'http://127.0.0.1:9292' # volume keystone endpoint-create --region $region_name --service $volume_svc --publicurl 'http://localhost:8776/v1/$(tenant_id)s' --adminurl 'http://localhost:8776/v1/$(tenant_id)s' --internalurl 'http://localhost:8776/v1/$(tenant_id)s' # volume v2 keystone endpoint-create --region $region_name --service $volumev2_svc --publicurl 'http://localhost:8776/v2/$(tenant_id)s' --adminurl 'http://localhost:8776/v2/$(tenant_id)s' --internalurl 'http://localhost:8776/v2/$(tenant_id)s' #network Uncomment following to also create network endpoint #keystone endpoint-create --region $region_name --service $network_svc --publicurl 'http://localhost:9696' --adminurl 'http://localhost:9696' --internalurl 'http://localhost:9696'
2015-03-28 00:10:54 Travis Tripp description New Launch instance wizard should not display networks when neutron is not enabled. It needs to account for multi-region differences and the user's currently selected region. See: https://review.openstack.org/#/c/164359/ To test this in a single environment, ensure that you have neutron setup properly. Then setup a two region environment. In Horizon openstack_dashboard/local/local_setting.py Uncomment / add the following (assumes keystone running locally) AVAILABLE_REGIONS = [     ('http://127.0.0.1:5000/v2.0', 'RegionOne'),     ('http://localhost:5000/v2.0', 'RegionTwo'), ] Use the keystone command line client to get the service list. You'll need the IDs later. source <devstack-location>/openrc admin admin keystone service-list Then create endpoint entries in the keystone service catalog for the second region. In that region do not add an endpoint for neutron. The following shell script will accomplish this. Just replace the id's appropriately from the service list above. Then in horizon, login with RegionOne. Open Launch Instance. Observe networks step loads properly (assuming you actually have neutron) Use the project / region select on top toolbar to switch to RegionTwo.  - Do no use the far right one Launch instance. Observe that network step is no longer available. ----------- Shell script below for creating endpoints --------- #!/bin/bash region_name=RegionTwo compute_svc=<replace with service id> computev2_1_svc=<replace with service id> network_svc=<replace with service id> image_svc=<replace with service id> volume_svc=<replace with service id> volumev2_svc=<replace with service id> # keystone endpoint-get --service compute keystone endpoint-create --region $region_name --service $compute_svc --publicurl 'http://localhost:8774/v2/$(tenant_id)s' --adminurl 'http://localhost:8774/v2/$(tenant_id)s' --internalurl 'http://localhost:8774/v2/$(tenant_id)s' # compute v2.1 keystone endpoint-create --region $region_name --service $computev2_1_svc --publicurl 'http://localhost:8774/v2.1/$(tenant_id)s' --adminurl 'http://localhost:8774/v2.1/$(tenant_id)s' --internalurl 'http://localhost:8774/v2.1/$(tenant_id)s' # image keystone endpoint-create --region $region_name --service $image_svc --publicurl 'http://127.0.0.1:9292' --adminurl 'http://127.0.0.1:9292' --internalurl 'http://127.0.0.1:9292' # volume keystone endpoint-create --region $region_name --service $volume_svc --publicurl 'http://localhost:8776/v1/$(tenant_id)s' --adminurl 'http://localhost:8776/v1/$(tenant_id)s' --internalurl 'http://localhost:8776/v1/$(tenant_id)s' # volume v2 keystone endpoint-create --region $region_name --service $volumev2_svc --publicurl 'http://localhost:8776/v2/$(tenant_id)s' --adminurl 'http://localhost:8776/v2/$(tenant_id)s' --internalurl 'http://localhost:8776/v2/$(tenant_id)s' #network Uncomment following to also create network endpoint #keystone endpoint-create --region $region_name --service $network_svc --publicurl 'http://localhost:9696' --adminurl 'http://localhost:9696' --internalurl 'http://localhost:9696' New Launch instance wizard should not display networks when neutron is not enabled. It needs to account for multi-region differences and the user's currently selected region. See: https://review.openstack.org/#/c/164359/ To test this in a single environment, ensure that you have neutron setup properly. Then setup a two region environment. In Horizon openstack_dashboard/local/local_setting.py Uncomment / add the following (assumes keystone running locally) AVAILABLE_REGIONS = [     ('http://127.0.0.1:5000/v2.0', 'RegionOne'),     ('http://localhost:5000/v2.0', 'RegionTwo'), ] Use the keystone command line client to get the service list. You'll need the IDs later. source <devstack-location>/openrc admin admin keystone service-list Then create endpoint entries in the keystone service catalog for the second region. In that region do not add an endpoint for neutron. The following shell script will accomplish this. Just replace the id's appropriately from the service list above. Then in horizon, login with RegionOne. Open Launch Instance. Observe networks step loads properly (assuming you actually have neutron) Use the project / region select on top toolbar to switch to RegionTwo.  - Do no use the far right one Launch instance. Observe that network step is no longer available. PLEASE NOTE, it will fail to actually launch in region two unless you actually setup a real nova region with nova networking enabled. In other words, this is just to emulate two regions. ----------- Shell script below for creating endpoints --------- #!/bin/bash region_name=RegionTwo compute_svc=<replace with service id> computev2_1_svc=<replace with service id> network_svc=<replace with service id> image_svc=<replace with service id> volume_svc=<replace with service id> volumev2_svc=<replace with service id> # keystone endpoint-get --service compute keystone endpoint-create --region $region_name --service $compute_svc --publicurl 'http://localhost:8774/v2/$(tenant_id)s' --adminurl 'http://localhost:8774/v2/$(tenant_id)s' --internalurl 'http://localhost:8774/v2/$(tenant_id)s' # compute v2.1 keystone endpoint-create --region $region_name --service $computev2_1_svc --publicurl 'http://localhost:8774/v2.1/$(tenant_id)s' --adminurl 'http://localhost:8774/v2.1/$(tenant_id)s' --internalurl 'http://localhost:8774/v2.1/$(tenant_id)s' # image keystone endpoint-create --region $region_name --service $image_svc --publicurl 'http://127.0.0.1:9292' --adminurl 'http://127.0.0.1:9292' --internalurl 'http://127.0.0.1:9292' # volume keystone endpoint-create --region $region_name --service $volume_svc --publicurl 'http://localhost:8776/v1/$(tenant_id)s' --adminurl 'http://localhost:8776/v1/$(tenant_id)s' --internalurl 'http://localhost:8776/v1/$(tenant_id)s' # volume v2 keystone endpoint-create --region $region_name --service $volumev2_svc --publicurl 'http://localhost:8776/v2/$(tenant_id)s' --adminurl 'http://localhost:8776/v2/$(tenant_id)s' --internalurl 'http://localhost:8776/v2/$(tenant_id)s' #network Uncomment following to also create network endpoint #keystone endpoint-create --region $region_name --service $network_svc --publicurl 'http://localhost:9696' --adminurl 'http://localhost:9696' --internalurl 'http://localhost:9696'
2015-03-30 15:14:20 OpenStack Infra horizon: assignee Travis Tripp (travis-tripp) Brian Tully (brian-tully)
2015-03-30 21:21:34 OpenStack Infra horizon: assignee Brian Tully (brian-tully) Travis Tripp (travis-tripp)
2015-03-30 22:57:12 OpenStack Infra horizon: assignee Travis Tripp (travis-tripp) Shaoquan Chen (sean-chen2)
2015-03-31 20:05:45 OpenStack Infra horizon: assignee Shaoquan Chen (sean-chen2) Travis Tripp (travis-tripp)
2015-04-01 08:08:51 OpenStack Infra horizon: assignee Travis Tripp (travis-tripp) Shaoquan Chen (sean-chen2)
2015-04-01 23:55:54 OpenStack Infra horizon: status In Progress Fix Committed
2015-04-09 09:55:20 Akihiro Motoki horizon: milestone kilo-rc1
2015-04-14 16:05:16 David Lyle horizon: importance Undecided High
2015-04-14 16:43:07 Thierry Carrez horizon: status Fix Committed Fix Released
2015-04-30 08:37:11 Thierry Carrez horizon: milestone kilo-rc1 2015.1.0