[Yahoo-eng-team] [Bug 1582087] [NEW] The default value of neutron.qos.notification_drivers should be a list
Public bug reported: Now the default value of neutron.qos.notification_drivers is a string [1]. This will not have functional error because the oslo can consume string and turn to list. But for the sample.conf file, it will generate something like this: # # From neutron.qos # # Drivers list to use to send the update notification (list value) #notification_drivers = m,e,s,s,a,g,e,_,q,u,e,u,e which is not user-friendly. Change the default value to a list can eliminate this issue. ** Affects: neutron Importance: Undecided Assignee: Hong Hui Xiao (xiaohhui) Status: New ** Tags: qos ** Changed in: neutron Assignee: (unassigned) => Hong Hui Xiao (xiaohhui) ** Tags added: qos -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1582087 Title: The default value of neutron.qos.notification_drivers should be a list Status in neutron: New Bug description: Now the default value of neutron.qos.notification_drivers is a string [1]. This will not have functional error because the oslo can consume string and turn to list. But for the sample.conf file, it will generate something like this: # # From neutron.qos # # Drivers list to use to send the update notification (list value) #notification_drivers = m,e,s,s,a,g,e,_,q,u,e,u,e which is not user-friendly. Change the default value to a list can eliminate this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1582087/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582086] [NEW] Add negative API tests that try to remove the resources in use.
Public bug reported: The tests that remove resources in use are not covered enough in api tests. E.g.: The test that try to delete the router in which interface has been added, without running router_remove_interface API. These tests are necessary for it avoid that the user can delete resources in use by mistake. ** Affects: neutron Importance: Undecided Assignee: Maho Koshiya (koshiya-maho) Status: In Progress ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Maho Koshiya (koshiya-maho) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1582086 Title: Add negative API tests that try to remove the resources in use. Status in neutron: In Progress Bug description: The tests that remove resources in use are not covered enough in api tests. E.g.: The test that try to delete the router in which interface has been added, without running router_remove_interface API. These tests are necessary for it avoid that the user can delete resources in use by mistake. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1582086/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582081] [NEW] Should hide the flavor that flavor disk is smaller the old one
Public bug reported: When we resize a vm, and select a flavor which flavor disk smaller than old one, The nova-compute will raise a error: ERROR oslo_messaging.rpc.dispatcher ResizeError: Resize error: Unable to resize disk down. So we should hide the flavor which disk is smaller the old one ** Affects: horizon Importance: Undecided Assignee: zhurong (zhu-rong) Status: New ** Changed in: horizon Assignee: (unassigned) => zhurong (zhu-rong) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1582081 Title: Should hide the flavor that flavor disk is smaller the old one Status in OpenStack Dashboard (Horizon): New Bug description: When we resize a vm, and select a flavor which flavor disk smaller than old one, The nova-compute will raise a error: ERROR oslo_messaging.rpc.dispatcher ResizeError: Resize error: Unable to resize disk down. So we should hide the flavor which disk is smaller the old one To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1582081/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1548151] Re: Created two host-routes on one subnet by running two commands update host-route parameter in case of neutron server active-active
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1548151 Title: Created two host-routes on one subnet by running two commands update host-route parameter in case of neutron server active-active Status in neutron: Expired Bug description: I had three controllers, I found a bug. I can create two host-route on one subnet by I run two commands update host-route parameter AT THE SAME TIME How to reproduce: Topology: http://codepad.org/ff0debPB Step 1: Create subnet with host-route is 172.16.69.0/26 and nexthop is 172.16.69.10 $ neutron subnet-create --name sub-int-net --host-route destination=172.16.69.0/26,nexthop=172.16.69.10 test-net 172.16.69.0/24 Step 2: Update host-route parameter Please running two commands AT THE SAME TIME - On Controller1 $ neutron subnet-update --host-route destination=172.16.69.64/26,nexthop=172.16.69.10 sub-int-net - On Controller2 $ neutron subnet-update --host-route destination=172.16.69.128/26,nexthop=172.16.69.20 sub-int-net The result: After create subnet: - This is result: http://codepad.org/eyX15Mnu After update subnet: - Show information subnet This is result: http://codepad.org/36C25S0f - Show information in "subnetroutes" tables: This is result: http://codepad.org/zrUh1CK8 In originally, When we update host-route parameter, the system will remove the existing host-route and write a new host-route, which have value in command update . That mean: after update this subnet has only one host-route. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1548151/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1470337] Re: Some aspects of subnets not validated when using subnet pools
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470337 Title: Some aspects of subnets not validated when using subnet pools Status in neutron: Expired Bug description: It looks like _validate_subnet is not called when allocating from a subnet pool. See here [1] for a discussion about it. [1] https://review.openstack.org/#/c/153236/89/neutron/db/db_base_plugin_v2.py To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1470337/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation
I am able to reproduce this same issue on a multinode devstack running libvirt. On the source host, the last call to nova/network/base_api.py::update_instance_cache_with_nw_info for a specific instance before the source host crashes has the nw_info passed in as a VIF object with the "active" attribute set to False. This is because the VM has just been deployed and the network was just created. In other words, the last time the instance's InstanceInfoCache's network_info attribute was updated before the source host went down, the VIF was considered not active. In some environments, especially when doing concurrent deploys, it may take a while for the InstanceInfoCache to update the network_info to show as active. What this boils down to is that Nova's InstanceInfoCache can potentially have a stale network_info active state. This causes the rebuild flow (which is the same as the spawn flow) to potentially end up waiting for the network-vif-plugged event, which will never come because it was sent to the source host instead of the destination. This results in the rebuild to fail because the VIF plugging times out. Steps: 1) Deploy VM(s) to host A 2) Take host A down (e.g., kill it's nova api and nova compute processes) once VM(s) from (1) are finished deploying 3) Try to evacuate VM(s) from host A to host B 4) Evacuation will potentially time out based on explanation above. It is much easier to reproduce if you do step (2) as soon as possible after the VM(s) finish deploying stack@controller:~$ glance image-list +--+-+ | ID | Name| +--+-+ | f91197db-16b5-44b2-beb4-72a9e57041c2 | cirros-0.3.4-x86_64-uec | | 1348de9b-501d-426c-8cb5-e65381208085 | cirros-0.3.4-x86_64-uec-kernel | | 790ebadb-bc5b-48be-b1f0-95a9214a11ae | cirros-0.3.4-x86_64-uec-ramdisk | +--+-+ stack@controller:~$ stack@controller:~$ neutron net-list +--+-+--+ | id | name| subnets | +--+-+--+ | 4ba74a3e-e7a8-4ca4-9de5-8a1d9e1042b8 | public | c9210289-4895-481b-946a-b406ba5889b4 2001:db8::/64 | | | | 9a044095-ab4d-4767-817e-02d81cbe90ef 172.24.4.0/24 | | d7faf346-1a26-41a0-bb62-b08808f6ba13 | private | f45ab890-a0d6-48c1-906e-9c8f81659d65 fdfd:f0f5:a83a::/64 | | | | 0e85f797-0270-49e9-9600-6f21b9cf47d0 10.254.1.0/24 | +--+-+--+ stack@controller:~$ stack@controller:~$ nova boot tdp-test-vm --flavor 1 --availability-zone nova:hostA --block-device id=f91197db-16b5-44b2-beb4-72a9e57041c2,source=image,dest=volume,size=1,bootindex=0 --nic net-id=4ba74a3e-e7a8-4ca4-9de5-8a1d9e1042b8 --min-count 5 --poll +--+-+ | Property | Value | +--+-+ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | - | | OS-EXT-SRV-ATTR:hostname | tdp-test-vm-1 | | OS-EXT-SRV-ATTR:hypervisor_hostname | - | | OS-EXT-SRV-ATTR:instance_name| instance-0021 | | OS-EXT-SRV-ATTR:kernel_id| 1348de9b-501d-426c-8cb5-e65381208085 | | OS-EXT-SRV-ATTR:launch_index | 0 | | OS-EXT-SRV-ATTR:ramdisk_id | 790ebadb-bc5b-48be-b1f0-95a9214a11ae | | OS-EXT-SRV-ATTR:reservation_id | r-erf2jgt0 | | OS-EXT-SRV-ATTR:root_device_name | - | | OS-EXT-SRV-ATTR:user_data| - | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state| scheduling | | OS-EXT-STS:vm_state | building | | OS-SRV-USG:launched_at | -
[Yahoo-eng-team] [Bug 1535918] [NEW] instance.host not updated on evacuation
You have been subscribed to a public bug: I'm working on the nova-powervm driver for Mitaka and trying to add support for evacuation. The problem I'm hitting is that instance.host is not updated when the compute driver is called to spawn the instance on the destination host. It is still set to the source host. It's not until after the spawn completes that the compute manager updates instance.host to reflect the destination host. The nova-powervm driver uses instance events callback mechanism during plug VIF to determine when Neutron has finished provisioning the network. The instance events code sends the event to instance.host and hence is sending the event to the source host (which is down). This causes the spawn to fail and also causes weirdness when the source host gets the events when it's powered back up. To temporarily work around the problem, I hacked in setting instance.host = CONF.host; instance.save() in the compute driver but that's not a good solution. ** Affects: nova Importance: Undecided Assignee: Drew Thorstensen (thorst) Status: Fix Released ** Tags: compute libvirt -- instance.host not updated on evacuation https://bugs.launchpad.net/bugs/1535918 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582058] [NEW] when a vm with serial port live-migrate to a host with disabled serial_port , live-migrate fails and vm_state is error
Public bug reported: I think let the VM is in error state unreasonable, and should be able to fall back to the normal state. log of nova-compute: ERROR nova.virt.libvirt.driver [req-5c6f9f3e-2b8d-4971-95bf-a248ce8fde1d d87519daaeaf49658f59ed55c7870be7 269fb3d6f1794558a602fabd1865c2d1 - - -] [instance: edfc2354-fc10-4d43-bc3f-f1d1b9776e9d] Live Migration failure: internal error: process exited while connecting to monitor: 2016-01-31T11:29:03.541912Z qemu-system-x86_64: -chardev socket,id=charserial0,host=10.43.239.165,port=20001,telnet,server,nowait: Failed to bind socket: Cannot assign requested address ** Affects: nova Importance: Undecided Assignee: wangyicheng (wang-yicheng) Status: New ** Changed in: nova Assignee: (unassigned) => wangyicheng (wang-yicheng) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1582058 Title: when a vm with serial port live-migrate to a host with disabled serial_port , live-migrate fails and vm_state is error Status in OpenStack Compute (nova): New Bug description: I think let the VM is in error state unreasonable, and should be able to fall back to the normal state. log of nova-compute: ERROR nova.virt.libvirt.driver [req-5c6f9f3e-2b8d-4971-95bf-a248ce8fde1d d87519daaeaf49658f59ed55c7870be7 269fb3d6f1794558a602fabd1865c2d1 - - -] [instance: edfc2354-fc10-4d43-bc3f-f1d1b9776e9d] Live Migration failure: internal error: process exited while connecting to monitor: 2016-01-31T11:29:03.541912Z qemu-system-x86_64: -chardev socket,id=charserial0,host=10.43.239.165,port=20001,telnet,server,nowait: Failed to bind socket: Cannot assign requested address To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1582058/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582052] [NEW] glance v1 and v2 image-show api are not compatible
Public bug reported:
The V1 image-show interface returns the following format：
The V2 image-show interface returns the following format：
{u'status': u'active', u'tags': [], u'container_format': None, u'min_ram': 0,
u'updated_at': u'2016-05-10T11:17:10Z', u'visibility': u'private',
u'image_name': u'test_cirros', u'image_id':
u'498cc673-7c95-4883-9df7-6850deb8168f', u'file':
u'/v2/images/c6b906d0-a22e-4d8f-83e6-b54e887d3335/file', u'owner':
u'55bbe36a87af48c0af04c9204a49a854', u'virtual_size': None, u'id':
u'c6b906d0-a22e-4d8f-83e6-b54e887d3335', u'size': 0, u'min_disk': 0, u'name':
u'test_snapshot_zy', u'checksum': None, u'created_at': u'2016-05-10T11:17:10Z',
u'block_device_mapping': u'[{"guest_format": null, "boot_index": 0,
"no_device": null, "snapshot_id": "55581528-cb88-4e5a-bee4-d3bb267a93cc",
"delete_on_termination": null, "disk_bus": "virtio", "image_id": null,
"source_type": "snapshot", "device_type": "disk", "volume_id": null,
"destination_type": "volume", "volume_size": null}, {"guest_format": null,
"boot_index": null, "no_device": null, "snapshot_id":
"9fcbc64c-1ebc-43d7-b899-6c7a42093697", "delete_on_termination": null,
"disk_bus": null, "image_id": null, "source_type": "snapshot", "device_type":
null, "volume_id": null, "destination_type": "volume", "volume_size": null}]',
u'disk_format': None, u'bdm_v2': u'True', u'protected': False,
u'root_device_name': u'/dev/vda', u'schema': u'/v2/schemas/image'}
In V1, 'block_device_mapping' as a key of 'properties'. But There is no
'properties' in V2.
So, the cinder and the nova don't Parse 'block_device_mapping'the attribute.
** Affects: glance
Importance: Undecided
Assignee: YaoZheng_ZTE (zheng-yao1)
Status: New
** Changed in: glance
Assignee: (unassigned) => YaoZheng_ZTE (zheng-yao1)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1582052
Title:
glance v1 and v2 image-show api are not compatible
Status in Glance:
New
Bug description:
The V1 image-show interface returns the following format：
The V2 image-show interface returns the following format：
{u'status': u'active', u'tags': [], u'container_format': None, u'min_ram': 0,
u'updated_at': u'2016-05-10T11:17:10Z', u'visibility': u'private',
u'image_name': u'test_cirros', u'image_id':
u'498cc673-7c95-4883-9df7-6850deb8168f', u'file':
u'/v2/images/c6b906d0-a22e-4d8f-83e6-b54e887d3335/file', u'owner':
u'55bbe36a87af48c0af04c9204a49a854', u'virtual_size': None, u'id':
u'c6b906d0-a22e-4d8f-83e6-b54e887d3335', u'size': 0, u'min_disk': 0, u'name':
u'test_snapshot_zy', u'checksum': None, u'created_at': u'2016-05-10T11:17:10Z',
u'block_device_mapping': u'[{"guest_format": null, "boot_index": 0,
"no_device": null, "snapshot_id": "55581528-cb88-4e5a-bee4-d3bb267a93cc",
"delete_on_termination": null, "disk_bus": "virtio", "image_id": null,
"source_type": "snapshot", "device_type": "disk", "volume_id": null,
"destination_type": "volume", "volume_size": null}, {"guest_format": null,
"boot_index": null, "no_device": null, "snapshot_id":
"9fcbc64c-1ebc-43d7-b899-6c7a42093697", "delete_on_termination": null,
"disk_bus": null, "image_id": null, "source_type": "snapshot", "device_type":
null, "volume_id": null, "destination_type": "volume", "volume_size": null}]',
u'disk_format': None, u'bdm_v2': u'True', u'protected': False,
u'root_device_name': u'/dev/vda', u'schema': u'/v2/schemas/image'}
In V1, 'block_device_mapping' as a key of 'properties'. But There is no
'properties' in V2.
So, the cinder and the nova don't Parse 'block_device_mapping'the attribute.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1582052/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582045] [NEW] Nova doesn't support v3 when connecting to Ironic
Public bug reported: nova-ironic communication only supports v2, deprecated auth parameters, e.g [1]. this will cause a fatal error during a v3-only devstack setup, as ironic keeps waiting for nova to provide resources and a timeout occurs (logs will show a lot of 401s) failing the setup. currently an ironic-enabled, v3-only devstack setup will fail because ironic itself doesn't support v3, but we already have a filled bug [2] and a patch on the way [3]. to reproduce this issue: setup a v3-only devstack with patched [3] ironic enabled. it should fail waiting for nova-hypervisor to provide VMs. [1] https://github.com/openstack/nova/blob/master/nova/virt/ironic/client_wrapper.py#L72-L78 [2] https://bugs.launchpad.net/ironic/+bug/1494776 [3] https://review.openstack.org/#/c/236982/ ** Affects: nova Importance: Undecided Assignee: Clenimar Filemon (clenimar-filemon) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Clenimar Filemon (clenimar-filemon) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1582045 Title: Nova doesn't support v3 when connecting to Ironic Status in OpenStack Compute (nova): In Progress Bug description: nova-ironic communication only supports v2, deprecated auth parameters, e.g [1]. this will cause a fatal error during a v3-only devstack setup, as ironic keeps waiting for nova to provide resources and a timeout occurs (logs will show a lot of 401s) failing the setup. currently an ironic-enabled, v3-only devstack setup will fail because ironic itself doesn't support v3, but we already have a filled bug [2] and a patch on the way [3]. to reproduce this issue: setup a v3-only devstack with patched [3] ironic enabled. it should fail waiting for nova-hypervisor to provide VMs. [1] https://github.com/openstack/nova/blob/master/nova/virt/ironic/client_wrapper.py#L72-L78 [2] https://bugs.launchpad.net/ironic/+bug/1494776 [3] https://review.openstack.org/#/c/236982/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1582045/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1580294] Re: Impossible to create another iSCSI volume after encrypted one was created
I ran that test twice in a row on a simple devstack setup with the default cinder storage backend (lvm) and didn't have any issues, so maybe it's a problem with the Nexenta driver in Cinder? ** Also affects: cinder Importance: Undecided Status: New ** Changed in: nova Status: New => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1580294 Title: Impossible to create another iSCSI volume after encrypted one was created Status in Cinder: New Status in OpenStack Compute (nova): Incomplete Bug description: Description === Tempest test for Cinder drivers which uses encrypted volumes fails. I figured out that test uses nova.volume.encryptors.cryptsetup.CryptsetupEncryptor. On setup it executes: cryptsetup create --key-file=- dev_name dev_path ln --symbolic --force /dev/mapper/dev_name symlink_path On remove: cryptsetup remove dev_name and it doesn't restore the link. When a driver deletes a volume and creates anoter one with the same name as previous, that link becomes broken and volume is not able to be working. When I manually replace the link with original one, it works fine. Steps to reproduce == cd /opt/stack/tempest tox -eall -- --concurrency=1 test_encrypted_cinder_volumes_cryptsetup run the test twice Expected result === the test passes every time Actual result = the test passes only the first time Environment === I used devstack from master branch and Nexenta iSCSI driver. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1580294/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1486127] Re: Support RBAC neutron-client changes.
** Project changed: openstack-api-site => neutron ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1486127 Title: Support RBAC neutron-client changes. Status in neutron: Confirmed Bug description: https://review.openstack.org/205482 commit 22c84927d133158c9de429ba1b9dbcd1d077d773 Author: Ramanjaneya Date: Fri Jul 24 15:51:53 2015 +0530 Support RBAC neutron-client changes. This patch adds the command line support for RBAC work. DocImpact APIImpact Partially-Implements: blueprint rbac-networks Co-Authored-By: dongfeng Change-Id: I00c6b84b3f7d810f137ce05c0cd936dc194d9708 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1486127/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1481600] Re: Remove Catalog Index Service
** Project changed: openstack-api-site => glance ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1481600 Title: Remove Catalog Index Service Status in Glance: Triaged Bug description: https://review.openstack.org/197043 commit feb927c8a11813c2cd4fbb73b2561a73e281f1aa Author: Louis Taylor Date: Tue Jun 30 12:19:34 2015 + Remove Catalog Index Service The Catalog Index Service added in the kilo cycle has been split into a new project named searchlight. This code now lives in a seperate repository: https://git.openstack.org/openstack/searchlight For more information about the split, see the governance change: I8b44aac03585c651ef8d5e94624f64a0ed2d10b2 DocImpact UpgradeImpact APIImpact Change-Id: I239ac9e32857f6a728f40c169e773ee977cca3ca To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1481600/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1408112] Re: Update documentation for port does not show how to remove dhcp_extra_opt
** Tags added: api-ref
** Project changed: openstack-api-site => neutron
** Changed in: neutron
Milestone: mitaka => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1408112
Title:
Update documentation for port does not show how to remove
dhcp_extra_opt
Status in neutron:
Confirmed
Bug description:
The manual shows how to add dhcp_extra_opts but not have to unset them
Need to add an example
{
"port":
{
"extra_dhcp_opts": [{"opt_value": null, "opt_name": "33"}]
}
}
---
Built: 2014-08-11T21:06:30 00:00
git SHA: 3302e05316e88d42067e3c1555df34371043999d
URL:
http://docs.openstack.org/api/openstack-network/2.0/content/extra-dhc-opt-ext-update.html
source File:
file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-extra-dhcp-options.xml
xml:id: extra-dhc-opt-ext-update
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1408112/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1505776] Re: Validate src_ip_adress, dest_ip_address and ip_version
** Project changed: openstack-api-site => neutron ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1505776 Title: Validate src_ip_adress, dest_ip_address and ip_version Status in neutron: Confirmed Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/215768 commit 29c51879683087e8ea486aaa9866bbce1f47a15c Author: Sean M. Collins Date: Mon Aug 10 15:24:52 2015 -0400 Validate src_ip_adress, dest_ip_address and ip_version The FwaaS API should not allow the creation of firewall rules where the ip_version is set to 4, but the source or destination IPs are IPv6 addresses APIImpact DocImpact Closes-Bug: #1487599 Change-Id: Iad680996a47adcf27f9dc7e0bc0fea924fff4f9f To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1505776/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1551368] Re: L7 capability extension implementation for lbaas v2
The API-Ref is changed from doc to each project (neutron) ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1551368 Title: L7 capability extension implementation for lbaas v2 Status in neutron: Confirmed Status in openstack-api-site: Invalid Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/148232 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 254190b3051453f823dbdf1826f1a6b984c57164 Author: Evgeny Fedoruk Date: Mon Jan 19 03:47:39 2015 -0800 L7 capability extension implementation for lbaas v2 Including extension modifications Including db model modifications Including alembic migration Including new driver managers for l7 rules and policies Inclufing logging_noop driver implementation Including unit testing Including Octavia driver updates DocImpact APIImpact Change-Id: I8f9535ebf28155adf43ebe046d2dbdfa86c4d81b Implements: blueprint lbaas-l7-rules Co-Authored-By: Evgeny Fedoruk Co-Authored-By: Stephen Balukoff To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1551368/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1481600] [NEW] Remove Catalog Index Service
You have been subscribed to a public bug: https://review.openstack.org/197043 commit feb927c8a11813c2cd4fbb73b2561a73e281f1aa Author: Louis Taylor Date: Tue Jun 30 12:19:34 2015 + Remove Catalog Index Service The Catalog Index Service added in the kilo cycle has been split into a new project named searchlight. This code now lives in a seperate repository: https://git.openstack.org/openstack/searchlight For more information about the split, see the governance change: I8b44aac03585c651ef8d5e94624f64a0ed2d10b2 DocImpact UpgradeImpact APIImpact Change-Id: I239ac9e32857f6a728f40c169e773ee977cca3ca ** Affects: glance Importance: Undecided Status: Triaged ** Tags: glance -- Remove Catalog Index Service https://bugs.launchpad.net/bugs/1481600 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1408112] [NEW] Update documentation for port does not show how to remove dhcp_extra_opt
You have been subscribed to a public bug:
The manual shows how to add dhcp_extra_opts but not have to unset them
Need to add an example
{
"port":
{
"extra_dhcp_opts": [{"opt_value": null, "opt_name": "33"}]
}
}
---
Built: 2014-08-11T21:06:30 00:00
git SHA: 3302e05316e88d42067e3c1555df34371043999d
URL:
http://docs.openstack.org/api/openstack-network/2.0/content/extra-dhc-opt-ext-update.html
source File:
file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-extra-dhcp-options.xml
xml:id: extra-dhc-opt-ext-update
** Affects: neutron
Importance: Low
Assignee: Sana Khan (sana.khan)
Status: Confirmed
** Tags: api-ref
--
Update documentation for port does not show how to remove dhcp_extra_opt
https://bugs.launchpad.net/bugs/1408112
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1486127] [NEW] Support RBAC neutron-client changes.
You have been subscribed to a public bug: https://review.openstack.org/205482 commit 22c84927d133158c9de429ba1b9dbcd1d077d773 Author: Ramanjaneya Date: Fri Jul 24 15:51:53 2015 +0530 Support RBAC neutron-client changes. This patch adds the command line support for RBAC work. DocImpact APIImpact Partially-Implements: blueprint rbac-networks Co-Authored-By: dongfeng Change-Id: I00c6b84b3f7d810f137ce05c0cd936dc194d9708 ** Affects: neutron Importance: Medium Status: Confirmed ** Tags: python-neutronclient -- Support RBAC neutron-client changes. https://bugs.launchpad.net/bugs/1486127 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1548511] Re: Shared pools support
The API-Ref is changed from doc to each project (neutron) ** Changed in: openstack-api-site Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1548511 Title: Shared pools support Status in neutron: Confirmed Status in openstack-api-site: Invalid Bug description: https://review.openstack.org/218560 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 4f3cf154829fcd69ecf3fa7f4e49f82d0104a4f0 Author: Stephen Balukoff Date: Sat Aug 29 02:51:09 2015 -0700 Shared pools support In preparation for L7 switching functionality, we need to reduce the rigidity of our model somewhat and allow pools to exist independent of listeners and be shared by 0 or more listeners. With this patch, pools are now associated with loadbalancers directly, and there is now a N:M relationship between listeners and pools. This patch does alter the Neutron LBaaS v2 API slightly, but all these changes are backward compatible. Nevertheless, since Neutron core dev team has asked that any API changes take place in an extension, that is what is being done in this patch. This patch also updates the reference namespace driver to render haproxy config templates correctly given the pool sharing functionality added with the patch. Finally, the nature of shared pools means that the usual workflow for tenants can be (but doesn't have to be) altered such that pools can be created before listeners independently, and assigned to listeners as a later step. DocImpact APIImpact Partially-Implements: blueprint lbaas-l7-rules Change-Id: Ia0974b01f1f02771dda545c4cfb5ff428a9327b4 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1548511/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550559] Re: Qos policy RBAC DB setup and migration
The API-Ref is changed from doc to each project (neutron) ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1550559 Title: Qos policy RBAC DB setup and migration Status in neutron: Confirmed Status in openstack-api-site: Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/250081 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit aeaf77a5295080a3010a2e9c32e24f47c8cc73cc Author: Haim Daniel Date: Wed Nov 25 18:49:45 2015 -0500 Qos policy RBAC DB setup and migration This patch implements a new database model required for the qos-policy RBAC support. In addition it migrates the current qos-policy 'shared' attribute to leverage the new 'qospolicyrbacs' table. 'shared' is no longer a property of the QosPolicy DB model. Its status is based on the tenant ID of the API caller. From an API perspective the logic remains the same - tenants will see qos-policies as 'shared=True' in case the qos-policy is shared with them). However, internal callers (e.g. plugins, drivers, services) must not check for the 'shared' attribute on qos-policy db objects any more. DocImpact APIImpact Blueprint: rbac-qos Related-bug: #1512587 Change-Id: I1c59073daa181005a3e878bc2fe033a0709fbf31 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1550559/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1565631] Re: [Shared images] is missing and wrong parameter
** Project changed: openstack-api-site => glance ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1565631 Title: [Shared images] is missing and wrong parameter Status in Glance: Confirmed Bug description: Response parameters in List shared images [1] miss "shared_images" parameter. And type of "image_id" parameter is "xsd:string", this value is wrong. It should be change "csapi:UUID". [1] http://developer.openstack.org/api-ref- image-v1.html#listSharedImages-v1 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1565631/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1505776] [NEW] Validate src_ip_adress, dest_ip_address and ip_version
You have been subscribed to a public bug: https://review.openstack.org/215768 commit 29c51879683087e8ea486aaa9866bbce1f47a15c Author: Sean M. Collins Date: Mon Aug 10 15:24:52 2015 -0400 Validate src_ip_adress, dest_ip_address and ip_version The FwaaS API should not allow the creation of firewall rules where the ip_version is set to 4, but the source or destination IPs are IPv6 addresses APIImpact DocImpact Closes-Bug: #1487599 Change-Id: Iad680996a47adcf27f9dc7e0bc0fea924fff4f9f ** Affects: neutron Importance: Undecided Status: Confirmed ** Affects: openstack-manuals Importance: Medium Assignee: KATO Tomoyuki (kato-tomoyuki) Status: Fix Released ** Tags: neutron-fwaas -- Validate src_ip_adress, dest_ip_address and ip_version https://bugs.launchpad.net/bugs/1505776 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1537121] Re: Add functionality to define requests without body
** Project changed: openstack-api-site => glance ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1537121 Title: Add functionality to define requests without body Status in Glance: Confirmed Bug description: https://review.openstack.org/207150 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 9b430f99518e10ae263bedec3062408af332068c Author: Niall Bunting Date: Tue Jul 28 15:05:10 2015 + Add functionality to define requests without body This allows functions that do not accept bodies to define this in the router file. As currently many requests will cause a 500 if a body is supplied when the API request does not expect it. This currently only affects the core parts of the v2 api, that is, calls to v2/images and v2/schemas. It does not cover the "tasks" API or the metadefs api as I was keeping this patch concise. As this does not affect the behaviour if not included this makes no change to the metadefs api behaviour. DocImpact Partial-Bug: 1475647 Change-Id: Ieb510e5516128078d40d39fd9b4f339ce64e10e7 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1537121/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1565631] [NEW] [Shared images] is missing and wrong parameter
You have been subscribed to a public bug: Response parameters in List shared images [1] miss "shared_images" parameter. And type of "image_id" parameter is "xsd:string", this value is wrong. It should be change "csapi:UUID". [1] http://developer.openstack.org/api-ref- image-v1.html#listSharedImages-v1 ** Affects: glance Importance: Undecided Assignee: Nam (namnh) Status: Confirmed ** Tags: glance -- [Shared images] is missing and wrong parameter https://bugs.launchpad.net/bugs/1565631 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1532220] Re: OS-EP-FILTER extension missing
** Project changed: openstack-api-site => keystone ** Tags added: api-ref ** Summary changed: - OS-EP-FILTER extension missing + [api-ref]OS-EP-FILTER extension missing -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1532220 Title: [api-ref]OS-EP-FILTER extension missing Status in OpenStack Identity (keystone): Confirmed Bug description: Missing OS-EP-FILTER extension for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-ep-filter-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1532220/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1532222] Re: OS-FEDERATION extension missing
** Project changed: openstack-api-site => keystone ** Tags added: api-ref ** Summary changed: - OS-FEDERATION extension missing + [api-ref]OS-FEDERATION extension missing -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/153 Title: [api-ref]OS-FEDERATION extension missing Status in OpenStack Identity (keystone): Confirmed Bug description: The OS-FEDERATION extension is missing for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-federation-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/153/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1537121] [NEW] Add functionality to define requests without body
You have been subscribed to a public bug: https://review.openstack.org/207150 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 9b430f99518e10ae263bedec3062408af332068c Author: Niall Bunting Date: Tue Jul 28 15:05:10 2015 + Add functionality to define requests without body This allows functions that do not accept bodies to define this in the router file. As currently many requests will cause a 500 if a body is supplied when the API request does not expect it. This currently only affects the core parts of the v2 api, that is, calls to v2/images and v2/schemas. It does not cover the "tasks" API or the metadefs api as I was keeping this patch concise. As this does not affect the behaviour if not included this makes no change to the metadefs api behaviour. DocImpact Partial-Bug: 1475647 Change-Id: Ieb510e5516128078d40d39fd9b4f339ce64e10e7 ** Affects: glance Importance: Undecided Status: Confirmed ** Tags: glance -- Add functionality to define requests without body https://bugs.launchpad.net/bugs/1537121 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1506149] Re: Bodies that are not dicts or lists return 400
The API-REF is canged from doc to each project (glance) ** Project changed: openstack-api-site => glance ** Changed in: glance Milestone: mitaka => None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1506149 Title: Bodies that are not dicts or lists return 400 Status in Glance: Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/204138 commit d8ca5c20c51a205624b3e815726e5c103a30b632 Author: Niall Bunting Date: Tue Jul 21 15:22:06 2015 + Bodies that are not dicts or lists return 400 Type errors that are encountered due to unexpected types being passed in now get a 400 'Body format is invalid'. This hardens the glance api from other types. ApiImpact DocImpact Closes-Bug: 1476695 Closes-Bug: 1476253 Change-Id: Ieee0662f67c800b2b3c07c6a8b7877939cf9e1fe To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1506149/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1471032] Re: Support Basic Address Scope CRUD as extensions
** Project changed: openstack-api-site => neutron ** Tags added: api-ref ** Summary changed: - Support Basic Address Scope CRUD as extensions + [api-ref]Support Basic Address Scope CRUD as extensions -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1471032 Title: [api-ref]Support Basic Address Scope CRUD as extensions Status in neutron: Confirmed Bug description: https://review.openstack.org/189741 commit cbd95318ad6c44e72a3aa163f7a399353c8b4458 Author: vikram.choudhary Date: Tue Jun 9 19:55:59 2015 +0530 Support Basic Address Scope CRUD as extensions This patch adds the support for basic address scope CRUD. Subsequent patches will be added to use this address scope on subnet pools. DocImpact APIImpact Co-Authored-By: Ryan Tidwell Co-Authored-By: Numan Siddique Change-Id: Icabdd22577cfda0e1fbf6042e4b05b8080e54fdb Partially-implements: blueprint address-scopes To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1471032/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1552015] Re: Support cleanup of tenant resources with a single API call
The API-Ref is changed from doc to each project (neutron). ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1552015 Title: Support cleanup of tenant resources with a single API call Status in neutron: Confirmed Status in openstack-manuals: Fix Released Status in python-neutronclient: Invalid Bug description: https://review.openstack.org/276541 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/python-neutronclient" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 88fbd3870cf3872fb0c9b4269503c62458664b3b Author: John Davidge Date: Mon Feb 15 10:02:54 2016 -0800 Support cleanup of tenant resources with a single API call The addition of the 'neutron purge' command allows cloud admins to conveniently delete multiple neutron resources associated with a given tenant. The command will delete all supported resources provided that they can be deleted (not in use, etc) and feedback the amount of each resource deleted to the user. A completion percentage is also given to keep the user informed of progress. Currently supports deletion of: Networks Subnets (implicitly) Routers Ports (including router interfaces) Floating IPs Security Groups This feature can be easily extended to support more resource types in the future. DocImpact: Update API documentation to describe neutron-purge usage Change-Id: I5a366d3537191045eb53f9cccd8cd0f7ce54a63b Closes-Bug: 1511574 Partially-Implements: blueprint tenant-delete To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1552015/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1532222] [NEW] OS-FEDERATION extension missing
You have been subscribed to a public bug: The OS-FEDERATION extension is missing for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-federation-ext.html ** Affects: keystone Importance: Low Assignee: Diane Fleming (diane-fleming) Status: Confirmed ** Tags: keystone -- OS-FEDERATION extension missing https://bugs.launchpad.net/bugs/153 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1532220] [NEW] OS-EP-FILTER extension missing
You have been subscribed to a public bug: Missing OS-EP-FILTER extension for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-ep-filter-ext.html ** Affects: keystone Importance: Low Assignee: Diane Fleming (diane-fleming) Status: Confirmed ** Tags: keystone -- OS-EP-FILTER extension missing https://bugs.launchpad.net/bugs/1532220 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1552015] [NEW] Support cleanup of tenant resources with a single API call
You have been subscribed to a public bug: https://review.openstack.org/276541 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/python-neutronclient" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 88fbd3870cf3872fb0c9b4269503c62458664b3b Author: John Davidge Date: Mon Feb 15 10:02:54 2016 -0800 Support cleanup of tenant resources with a single API call The addition of the 'neutron purge' command allows cloud admins to conveniently delete multiple neutron resources associated with a given tenant. The command will delete all supported resources provided that they can be deleted (not in use, etc) and feedback the amount of each resource deleted to the user. A completion percentage is also given to keep the user informed of progress. Currently supports deletion of: Networks Subnets (implicitly) Routers Ports (including router interfaces) Floating IPs Security Groups This feature can be easily extended to support more resource types in the future. DocImpact: Update API documentation to describe neutron-purge usage Change-Id: I5a366d3537191045eb53f9cccd8cd0f7ce54a63b Closes-Bug: 1511574 Partially-Implements: blueprint tenant-delete ** Affects: neutron Importance: Medium Status: Confirmed ** Affects: openstack-manuals Importance: Undecided Assignee: John Davidge (john-davidge) Status: Fix Released ** Affects: python-neutronclient Importance: Medium Assignee: John Davidge (john-davidge) Status: Invalid ** Tags: doc python-neutronclient -- Support cleanup of tenant resources with a single API call https://bugs.launchpad.net/bugs/1552015 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1547271] Re: Preserve subnet_create behavior in presence of subnet pools
The API-Ref is moved from doc to each project (neutron) ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1547271 Title: Preserve subnet_create behavior in presence of subnet pools Status in neutron: Confirmed Status in openstack-api-site: Invalid Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/279378 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit d38aeade9db7169955b4524a5fc8d814067dec15 Author: Armando Migliaccio Date: Thu Feb 11 20:56:20 2016 -0800 Preserve subnet_create behavior in presence of subnet pools The development of the auto_allocate extension, which relies on subnet pools, revealed some discrepancies in the behavior of the subnet_create API: if a user specifies a cidr on subnet_create like he/she is used to, the API outcome changes in presence of default subnetpools. For instance the command 'neutron subnet-create network ' returns a subnet associated to a pool, if a default pool exists, but it does not otherwise. At the same time, attempting to create a subnet without passing any detail but the ip version also behaves unexpectedly depending on the state of the system. Whilst this could be considered convenient in some circumstances, it is problematic for a couple of reasons: a) it breaks a well defined contract (backward compat of the subnet-create command), and b) it leads to ambiguity of the API. This patch restores the semantic of the subnet_create API where it is mandatory to specify CIDR/IP version regardless of the conditions under which the request is issued. On the other hand, associating subnets to subnet pools will have to be more prescriptive, and require the user to explicitly state his/her intentions when creating the subnet: if a user does want a subnet (CIDR) to belong to a subnet pool, he/she will have to state so, either by specifying a subnetpool name/uuid, or by asking for a default one. This will be tackled as a follow-up, especially in order to address the needs of prefix delegation which currently rely on the ambiguous behavior that this patch is fixing. Closes-bug: 1545199 DocImpact: subnetpools can be used to simplify IPAM, and can be specified during subnet creation. Change-Id: Idf516ed9db24d779742cdff0584b48182a8502d6 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1547271/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1506149] [NEW] Bodies that are not dicts or lists return 400
You have been subscribed to a public bug: https://review.openstack.org/204138 commit d8ca5c20c51a205624b3e815726e5c103a30b632 Author: Niall Bunting Date: Tue Jul 21 15:22:06 2015 + Bodies that are not dicts or lists return 400 Type errors that are encountered due to unexpected types being passed in now get a 400 'Body format is invalid'. This hardens the glance api from other types. ApiImpact DocImpact Closes-Bug: 1476695 Closes-Bug: 1476253 Change-Id: Ieee0662f67c800b2b3c07c6a8b7877939cf9e1fe ** Affects: glance Importance: Medium Assignee: Atsushi SAKAI (sakaia) Status: Confirmed ** Affects: openstack-manuals Importance: Medium Assignee: Sana Khan (sana.khan) Status: Confirmed ** Tags: glance -- Bodies that are not dicts or lists return 400 https://bugs.launchpad.net/bugs/1506149 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1471032] [NEW] Support Basic Address Scope CRUD as extensions
You have been subscribed to a public bug: https://review.openstack.org/189741 commit cbd95318ad6c44e72a3aa163f7a399353c8b4458 Author: vikram.choudhary Date: Tue Jun 9 19:55:59 2015 +0530 Support Basic Address Scope CRUD as extensions This patch adds the support for basic address scope CRUD. Subsequent patches will be added to use this address scope on subnet pools. DocImpact APIImpact Co-Authored-By: Ryan Tidwell Co-Authored-By: Numan Siddique Change-Id: Icabdd22577cfda0e1fbf6042e4b05b8080e54fdb Partially-implements: blueprint address-scopes ** Affects: neutron Importance: Medium Status: Confirmed ** Tags: neutron -- Support Basic Address Scope CRUD as extensions https://bugs.launchpad.net/bugs/1471032 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1564887] Re: Neutron v2 Layer-3 extension - `routes` attribute not helpful
** Project changed: openstack-api-site => neutron ** Tags added: api-ref ** Summary changed: - Neutron v2 Layer-3 extension - `routes` attribute not helpful + [api-ref]Neutron v2 Layer-3 extension - `routes` attribute not helpful -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1564887 Title: [api-ref]Neutron v2 Layer-3 extension - `routes` attribute not helpful Status in neutron: In Progress Bug description: In all the router responses, you see a `routes` attribute. This is the explanation for it: routes plain xsd:listThe extra routes configuration for L3 router. 1. What exactly is the structure of this value? "xsd:list" means nothing to me. Are there nested objects, nested strings? 2. The description doesn't explain how a route functions. Also, how do routes get set on routers? It's not included as an input param for POST or PUT operations. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1564887/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1564887] [NEW] Neutron v2 Layer-3 extension - `routes` attribute not helpful
You have been subscribed to a public bug: In all the router responses, you see a `routes` attribute. This is the explanation for it: routes plain xsd:listThe extra routes configuration for L3 router. 1. What exactly is the structure of this value? "xsd:list" means nothing to me. Are there nested objects, nested strings? 2. The description doesn't explain how a route functions. Also, how do routes get set on routers? It's not included as an input param for POST or PUT operations. ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: In Progress ** Tags: neutron -- Neutron v2 Layer-3 extension - `routes` attribute not helpful https://bugs.launchpad.net/bugs/1564887 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1516073] Re: Replace subnetpool config options with admin-only API
** Project changed: openstack-api-site => neutron ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1516073 Title: Replace subnetpool config options with admin-only API Status in neutron: Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/230983 commit 6ee91e56c84ea6e930369f8649f1d2b50096cb80 Author: John Davidge Date: Thu Oct 1 20:37:34 2015 +0100 Replace subnetpool config options with admin-only API This patch adds a new boolean 'is_default' property to subnetpools. This allows the admin to set the default v4/v6 subnetpools via the API rather than the existing neutron.conf options - which are deprecated by this patch. Only one subnetpool per IP family can be set to default. DocImpact ApiImpact Co-Authored-By: Carl Baldwin Change-Id: I5daba2347cfb91fac0b155b2c1b459ee7d9e4505 Closes-Bug: 1501328 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516073/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1516073] [NEW] Replace subnetpool config options with admin-only API
You have been subscribed to a public bug: https://review.openstack.org/230983 commit 6ee91e56c84ea6e930369f8649f1d2b50096cb80 Author: John Davidge Date: Thu Oct 1 20:37:34 2015 +0100 Replace subnetpool config options with admin-only API This patch adds a new boolean 'is_default' property to subnetpools. This allows the admin to set the default v4/v6 subnetpools via the API rather than the existing neutron.conf options - which are deprecated by this patch. Only one subnetpool per IP family can be set to default. DocImpact ApiImpact Co-Authored-By: Carl Baldwin Change-Id: I5daba2347cfb91fac0b155b2c1b459ee7d9e4505 Closes-Bug: 1501328 ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: Confirmed ** Affects: openstack-manuals Importance: High Assignee: John Davidge (john-davidge) Status: Confirmed ** Tags: neutron -- Replace subnetpool config options with admin-only API https://bugs.launchpad.net/bugs/1516073 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1364221] Re: IPSec site connections in OpenStack Networking API v2.0 (neutron) Reference - API v2.0 (neutron) and extensions
The API-ref issue is moved from doc to each project (neutron). ** Project changed: openstack-api-site => neutron ** Changed in: neutron Milestone: liberty => None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1364221 Title: IPSec site connections in OpenStack Networking API v2.0 (neutron) Reference - API v2.0 (neutron) and extensions Status in neutron: Confirmed Status in python-neutronclient: Won't Fix Bug description: peer_id attribute can be IPv4/IPv6 address as per design now ,but in notes mentioned as it can be IPv4/IPv6 address, e-mail address, key id, or FQDN. --- Built: 2014-08-11T21:06:27 00:00 git SHA: 3302e05316e88d42067e3c1555df34371043999d URL: http://docs.openstack.org/api/openstack-network/2.0/content/vpnaas_ext_ops_ipsec_site_connection.html source File: file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-vpnaas.xml xml:id: vpnaas_ext_ops_ipsec_site_connection To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1364221/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1570892] Re: Openswan/Libreswan: support sha256 for auth algorithm
** Project changed: openstack-api-site => neutron ** Summary changed: - Openswan/Libreswan: support sha256 for auth algorithm + [api-ref]Openswan/Libreswan: support sha256 for auth algorithm ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1570892 Title: [api-ref]Openswan/Libreswan: support sha256 for auth algorithm Status in neutron: Confirmed Bug description: https://review.openstack.org/303684 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit b73e1002555cfa70ccfea8ffe685672c0b679212 Author: nick.zhuyj Date: Fri Apr 8 23:48:33 2016 -0500 Openswan/Libreswan: support sha256 for auth algorithm Add support for sha256 as it is requirement from customer. Currently, there is no ike/esp fields in strongswan ipsec.conf template, so by default. sha256 is used. But for openswan auth algorithm is get from configuration, so only sha1 is supported. This patch enable Openswan/Libreswan to support sha256. Note: this change is DocImpact and APIImpact Change-Id: I02c80ec3494eb0edef2fdaa5d21ca0c3bbcacac2 Closes-Bug: #1567846 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1570892/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1572168] Re: Missing response parameter tables identity admin API
** Project changed: openstack-api-site => keystone ** Summary changed: - Missing response parameter tables identity admin API + [api-ref]Missing response parameter tables identity admin API ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1572168 Title: [api-ref]Missing response parameter tables identity admin API Status in OpenStack Identity (keystone): In Progress Bug description: http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-listTenants http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-showTenantByName http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-showTenantById http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-listRolesForUserOnTenant The above APIs do not have response parameter table. They must be documented. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1572168/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1364221] [NEW] IPSec site connections in OpenStack Networking API v2.0 (neutron) Reference - API v2.0 (neutron) and extensions
You have been subscribed to a public bug: peer_id attribute can be IPv4/IPv6 address as per design now ,but in notes mentioned as it can be IPv4/IPv6 address, e-mail address, key id, or FQDN. --- Built: 2014-08-11T21:06:27 00:00 git SHA: 3302e05316e88d42067e3c1555df34371043999d URL: http://docs.openstack.org/api/openstack-network/2.0/content/vpnaas_ext_ops_ipsec_site_connection.html source File: file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-vpnaas.xml xml:id: vpnaas_ext_ops_ipsec_site_connection ** Affects: neutron Importance: Low Status: Confirmed ** Affects: python-neutronclient Importance: Undecided Status: Won't Fix -- IPSec site connections in OpenStack Networking API v2.0 (neutron) Reference - API v2.0 (neutron) and extensions https://bugs.launchpad.net/bugs/1364221 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1572168] [NEW] Missing response parameter tables identity admin API
You have been subscribed to a public bug: http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-listTenants http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-showTenantByName http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-showTenantById http://developer.openstack.org/api-ref-identity-admin-v2.html#admin-listRolesForUserOnTenant The above APIs do not have response parameter table. They must be documented. ** Affects: keystone Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: In Progress ** Tags: keystone -- Missing response parameter tables identity admin API https://bugs.launchpad.net/bugs/1572168 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1570892] [NEW] Openswan/Libreswan: support sha256 for auth algorithm
You have been subscribed to a public bug: https://review.openstack.org/303684 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit b73e1002555cfa70ccfea8ffe685672c0b679212 Author: nick.zhuyj Date: Fri Apr 8 23:48:33 2016 -0500 Openswan/Libreswan: support sha256 for auth algorithm Add support for sha256 as it is requirement from customer. Currently, there is no ike/esp fields in strongswan ipsec.conf template, so by default. sha256 is used. But for openswan auth algorithm is get from configuration, so only sha1 is supported. This patch enable Openswan/Libreswan to support sha256. Note: this change is DocImpact and APIImpact Change-Id: I02c80ec3494eb0edef2fdaa5d21ca0c3bbcacac2 Closes-Bug: #1567846 ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: Confirmed ** Tags: doc neutron-vpnaas -- Openswan/Libreswan: support sha256 for auth algorithm https://bugs.launchpad.net/bugs/1570892 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1566607] Re: [Show user details] miss request parameter
** Project changed: openstack-api-site => keystone ** Summary changed: - [Show user details] miss request parameter + [api-ref][Show user details] miss request parameter ** Tags added: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1566607 Title: [api-ref][Show user details] miss request parameter Status in OpenStack Identity (keystone): Confirmed Bug description: Show user details [1] miss parameters: name, enabled, email, id, user and username [1]http://developer.openstack.org/api-ref-identity-admin-v2.html #admin-showUser To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1566607/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1566607] [NEW] [Show user details] miss request parameter
You have been subscribed to a public bug: Show user details [1] miss parameters: name, enabled, email, id, user and username [1]http://developer.openstack.org/api-ref-identity-admin-v2.html#admin- showUser ** Affects: keystone Importance: Undecided Assignee: Nam (namnh) Status: Confirmed ** Tags: keystone -- [Show user details] miss request parameter https://bugs.launchpad.net/bugs/1566607 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1418635] Re: Neutron API reference is inconsistent and differs from implementation
** Project changed: openstack-api-site => neutron
** Summary changed:
- Neutron API reference is inconsistent and differs from implementation
+ [api-ref]Neutron API reference is inconsistent and differs from implementation
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1418635
Title:
[api-ref]Neutron API reference is inconsistent and differs from
implementation
Status in neutron:
Confirmed
Bug description:
I'm implementing modules for SaltStack (not yet on GitHub) to create entities
in OpenStack Neutron and came across quite a few problems
with the API documentation:
* Link "Filtering and Column Selection" to
http://docs.openstack.org/api/openstack-network/2.0/content/filtering.html
404s
* Section http://developer.openstack.org/api-ref-
networking-v2.html#subnets
* "POST /v2.0/subnets" aka "Create subnet"
- 'id' is listed to be an optional parameter but the Neutron-API in
Icehouse refuses to set a user-selected ID
- parameters 'dns_nameservers' and 'host_routes' missing from
documentation (undocumented extensions?)
* "GET /v2.0/subnets" aka "List subnets"
- can't filter by "allocation_pools" or "enable_dhcp"
* "PUT /v2.0/subnets/{subnet_id}" aka "Update subnet"
- parameters "allocation_pools", "network_id", "tenant_id", "id" listed
as optional request parameters but Neutron-API in Icehouse returns
"Cannot update read-only attribute $PARAMETER"
* Section http://developer.openstack.org/api-ref-
networking-v2.html#networks
* "GET /v2.0/networks" aka "List networks"
- parameter "shared" is ignored as a filter
* Section http://developer.openstack.org/api-ref-
networking-v2.html#layer3
* "POST /v2.0/routers" aka "Create router"
- Description states "router:external" and "external_gateway_info" are
valid request parameters but they're not listed in the table of
request parameters
- What's the parameter router described as "A router object." supposed
to be? A router object in JSON/XML notation inside a router object in
JSON/XML notation?
I'll probably add more when implementing functions for managing
routers in Neutron.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1418635/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1552077] Re: Use network RBAC feature for external access
The API-Ref is changed from api-site to project (neutron) ** Changed in: openstack-api-site Status: Confirmed => Invalid ** Changed in: neutron Status: Invalid => Confirmed ** Summary changed: - Use network RBAC feature for external access + [api-ref]Use network RBAC feature for external access -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1552077 Title: [api-ref]Use network RBAC feature for external access Status in neutron: Confirmed Status in openstack-api-site: Invalid Bug description: https://review.openstack.org/282295 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 49b4dd3478d782aee4260033825aa6b47eaf644a Author: Kevin Benton Date: Fri Feb 19 03:34:27 2016 -0800 Use network RBAC feature for external access This allows access to external networks to be controlled via the RBAC framework added during Liberty with a new 'access_as_external' action. A migration adds all current external networks to the RBAC policies table with a wildcard indicating that all tenants can access the network as RBAC. Unlike the conversion of shared networks to RBAC, the external table is left in the DB to avoid invasive changes throughout the codebase to calculate the flag relative to the caller. So the current 'external' flag is used throughout the code base as it previously was for wiring up floating IPs, router gateway ports, etc. Then the RBAC entries are only referenced when determining what networks to show the tenants. API Behavior: * Marking a network as 'external' will automatically create a wildcard entry that allows that network to be accessed by all tenants. * An external network may have all of its RBAC entries deleted and then only an admin will be able to attach to it. * An RBAC 'access_as_external' entry cannot be deleted if it is required for a tenant that currently has a router attached to that network. * Creating an 'access_as_external' RBAC entry will automatically convert the network into an external network. (This is to enable a workflow where a private external network is never visible to everyone.) * The default policy.json will prevent a non-admin from creating wildcard 'access_as_external' RBAC entries to align with the current default policy we have on setting the 'external' field on the network to prevent poluting everyone else's network lists. * The default policy.json will allow a tenant to create an 'access_as_external' RBAC entry to allow specific tenants (including itself) the ability to use its network as an external network. Closes-Bug: #1547985 DocImpact: External networks can now have access restricted to small subsets of tenants APIImpact: 'access_as_external' will be allowed as an action in the RBAC API for networks Change-Id: I4d8ee78a9763c58884e4fd3d7b40133da659cd61 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1552077/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1382268] Re: Add notification for server group operations
** Project changed: openstack-api-site => nova ** Summary changed: - Add notification for server group operations + [api-ref]Add notification for server group operations -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1382268 Title: [api-ref]Add notification for server group operations Status in OpenStack Compute (nova): Confirmed Bug description: https://review.openstack.org/107954 commit daf278c0c8b6cc917b84f514fec65758adf17028 Author: Jay Lau Date: Thu Oct 16 15:08:32 2014 -0400 Add notification for server group operations Currently, there is no notification when create/update/delete server groups, this caused some 3rd party client cannot know when those operations are finished. The fix was adding notifications for those operations. DocImpact The wiki page https://wiki.openstack.org/wiki/SystemUsageData needs to be updated once this patch was merged. Change-Id: Ia1f4a6752668ddb73ebb8faf525b58a28d183754 Closes-Bug: #1343200 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1382268/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1418635] [NEW] Neutron API reference is inconsistent and differs from implementation
You have been subscribed to a public bug:
I'm implementing modules for SaltStack (not yet on GitHub) to create entities
in OpenStack Neutron and came across quite a few problems
with the API documentation:
* Link "Filtering and Column Selection" to
http://docs.openstack.org/api/openstack-network/2.0/content/filtering.html
404s
* Section http://developer.openstack.org/api-ref-
networking-v2.html#subnets
* "POST /v2.0/subnets" aka "Create subnet"
- 'id' is listed to be an optional parameter but the Neutron-API in
Icehouse refuses to set a user-selected ID
- parameters 'dns_nameservers' and 'host_routes' missing from
documentation (undocumented extensions?)
* "GET /v2.0/subnets" aka "List subnets"
- can't filter by "allocation_pools" or "enable_dhcp"
* "PUT /v2.0/subnets/{subnet_id}" aka "Update subnet"
- parameters "allocation_pools", "network_id", "tenant_id", "id" listed
as optional request parameters but Neutron-API in Icehouse returns
"Cannot update read-only attribute $PARAMETER"
* Section http://developer.openstack.org/api-ref-
networking-v2.html#networks
* "GET /v2.0/networks" aka "List networks"
- parameter "shared" is ignored as a filter
* Section http://developer.openstack.org/api-ref-
networking-v2.html#layer3
* "POST /v2.0/routers" aka "Create router"
- Description states "router:external" and "external_gateway_info" are
valid request parameters but they're not listed in the table of
request parameters
- What's the parameter router described as "A router object." supposed
to be? A router object in JSON/XML notation inside a router object in
JSON/XML notation?
I'll probably add more when implementing functions for managing routers
in Neutron.
** Affects: neutron
Importance: Medium
Assignee: Edgar Magana (emagana)
Status: Confirmed
** Tags: api documentation in-stable-icehouse neutron
--
Neutron API reference is inconsistent and differs from implementation
https://bugs.launchpad.net/bugs/1418635
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1382268] [NEW] Add notification for server group operations
You have been subscribed to a public bug: https://review.openstack.org/107954 commit daf278c0c8b6cc917b84f514fec65758adf17028 Author: Jay Lau Date: Thu Oct 16 15:08:32 2014 -0400 Add notification for server group operations Currently, there is no notification when create/update/delete server groups, this caused some 3rd party client cannot know when those operations are finished. The fix was adding notifications for those operations. DocImpact The wiki page https://wiki.openstack.org/wiki/SystemUsageData needs to be updated once this patch was merged. Change-Id: Ia1f4a6752668ddb73ebb8faf525b58a28d183754 Closes-Bug: #1343200 ** Affects: nova Importance: Medium Status: Confirmed ** Tags: nova -- Add notification for server group operations https://bugs.launchpad.net/bugs/1382268 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1553332] Re: API documentation missing for neutron rbac-policies
** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1553332 Title: API documentation missing for neutron rbac-policies Status in neutron: In Progress Bug description: https://specs.openstack.org/openstack/neutron-specs/specs/liberty /rbac-networks.html#rest-api-impact doesn't appear to be reflected in the neutron API documentation, despite the fact that the spec was implemented (see neutron/extensions/rbac.py). I believe this should be included on http://developer.openstack.org/api-ref- networking-v2-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1553332/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1553653] Re: Add a description field to all standard resources
API-Ref is moved from doc to each project (neutron). ** Changed in: neutron Status: Invalid => Confirmed ** Changed in: openstack-api-site Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1553653 Title: Add a description field to all standard resources Status in neutron: Confirmed Status in openstack-api-site: Invalid Bug description: https://review.openstack.org/269887 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 5dacbba701037200f9b0ae40c34981ecd941b41c Author: Kevin Benton Date: Wed Feb 10 17:00:21 2016 -0800 Add a description field to all standard resources In order to give users and operators more flexibility in annotating the purpose of various Neutron resources, this patch adds a description field limited to 255 chars to all of the Neutron resources that reference the standard attribute table. The resource that reference the table are the following: security_group_rules, security_groups, ports, subnets, networks, routers, floatingips, subnetpools This patch adds a description table related to standard attributes and migrates over the existing security group description to the new table as well. Co-Authored-By: James Dempsey APIImpact DocImpact: Adds a description field to all resources outline in commit message. Closes-Bug: #1483480 Change-Id: I6e1ef53d7aae7d04a5485810cc1db0a8eb125953 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1553653/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1487745] Re: Neutron RBAC API and network support
** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1487745 Title: Neutron RBAC API and network support Status in neutron: Confirmed Status in openstack-manuals: Won't Fix Bug description: https://review.openstack.org/192555 commit 4595899f7f2b3774dc2dac2f8dd1a085b1e7973d Author: Kevin Benton Date: Tue Jun 16 23:43:59 2015 -0700 Neutron RBAC API and network support This adds the new API endpoint to create, update, and delete role-based access control entries. These entries enable tenants to grant access to other tenants to perform an action on an object they do not own. This was previously done using a single 'shared' flag; however, this was too coarse because an object would either be private to a tenant or it would be shared with every tenant. In addition to introducing the API, this patch also adds support to for the new entries in Neutron networks. This means tenants can now share their networks with specific tenants as long as they know the tenant ID. This feature is backwards-compatible with the previous 'shared' attribute in the API. So if a deployer doesn't want this new feature enabled, all of the RBAC operations can be blocked in policy.json and networks can still be globally shared in the legacy manner. Even though this feature is referred to as role-based access control, this first version only supports sharing networks with specific tenant IDs because Neutron currently doesn't have integration with Keystone to handle changes in a tenant's roles/groups/etc. DocImpact APIImpact Change-Id: Ib90e2a931df068f417faf26e9c3780dc3c468867 Partially-Implements: blueprint rbac-networks To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1487745/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1532223] Re: [api-ref]OS-REVOKE extension missing for Identity v3
** Summary changed: - OS-REVOKE extension missing for Identity v3 + [api-ref]OS-REVOKE extension missing for Identity v3 ** Project changed: openstack-api-site => keystone -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1532223 Title: [api-ref]OS-REVOKE extension missing for Identity v3 Status in OpenStack Identity (keystone): Confirmed Bug description: OS-REVOKE extension is missing for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-revoke-ext.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1532223/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1553332] [NEW] API documentation missing for neutron rbac-policies
You have been subscribed to a public bug: https://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac- networks.html#rest-api-impact doesn't appear to be reflected in the neutron API documentation, despite the fact that the spec was implemented (see neutron/extensions/rbac.py). I believe this should be included on http://developer.openstack.org/api-ref- networking-v2-ext.html ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: In Progress -- API documentation missing for neutron rbac-policies https://bugs.launchpad.net/bugs/1553332 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1517705] Re: Move federation extension into keystone core
The api-ref is changed from api-site to keystone. ** Project changed: openstack-api-site => keystone -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1517705 Title: Move federation extension into keystone core Status in OpenStack Identity (keystone): Confirmed Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/214775 commit cbefe7c7b83b5f940f817adf60a4be35bd324775 Author: Steve Martinelli Date: Sun Oct 11 03:01:05 2015 -0400 Move federation extension into keystone core Remove federation as an extension and move it to a core resource. For now we leave the database migrations in the extension directory until we have a general policy for merging these into core. Some instances of federation constants were removed because they were causing a circular dependency, these can be refactored in a later patch. DocImpact: You should no longer run the migrations for this extension Implements: bp move-extensions Co-Authored-By: Nithya Renganathan Change-Id: If5857a6ee4c7c527929069b25beab40f4c5d87e2 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1517705/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581977] [NEW] Invalid input for dns_name when spawning instance with .number at the end
Public bug reported: When attempting to deploy an instance with a name which ends in dot (e.g. .123, as in an all-numeric TLD) or simply a name that, after conversion to dns_name, ends as ., nova conductor fails with the following error: 2016-05-15 13:15:04.824 ERROR nova.scheduler.utils [req-4ce865cd-e75b- 4de8-889a-ed7fc7fece18 admin demo] [instance: c4333432-f0f8-4413-82e8-7f12cdf3b5c8] Error from last host: silpixa00394065 (node silpixa00394065): [u'Traceback (most recent call last):\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 1926, in _do_build_and_run_instance\nfilter_properties)\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 2116, in _build_and_run_instance\ninstance_uuid=instance.uuid, reason=six.text_type(e))\n', u"RescheduledException: Build of instance c4333432-f0f8-4413-82e8-7f12cdf3b5c8 was re-scheduled: Invalid input for dns_name. Reason: 'networking-ovn-ubuntu-16.04' not a valid PQDN or FQDN. Reason: TLD '04' must not be all numeric.\nNeutron server returns request_ids: ['req-7317c3e3-2875-4073-8076-40e944845b69']\n"] This throws one instance of the infamous Horizon message: Error: No valid host was found. There are not enough hosts available. This issue was observed using stable/mitaka via DevStack (nova commit fb3f1706c68ea5b58f05ea810c6339f2449959de). In the above example, the instance name is "networking-ovn (Ubuntu 16.04)", which resulted in an attempted dns_name="networking-ovn- ubuntu-16.04", where the 04 was interpreted as a TLD and, consequently, an invalid TLD. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1581977 Title: Invalid input for dns_name when spawning instance with .number at the end Status in OpenStack Compute (nova): New Bug description: When attempting to deploy an instance with a name which ends in dot (e.g. .123, as in an all-numeric TLD) or simply a name that, after conversion to dns_name, ends as ., nova conductor fails with the following error: 2016-05-15 13:15:04.824 ERROR nova.scheduler.utils [req-4ce865cd-e75b- 4de8-889a-ed7fc7fece18 admin demo] [instance: c4333432-f0f8-4413-82e8-7f12cdf3b5c8] Error from last host: silpixa00394065 (node silpixa00394065): [u'Traceback (most recent call last):\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 1926, in _do_build_and_run_instance\nfilter_properties)\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 2116, in _build_and_run_instance\ninstance_uuid=instance.uuid, reason=six.text_type(e))\n', u"RescheduledException: Build of instance c4333432-f0f8-4413-82e8-7f12cdf3b5c8 was re-scheduled: Invalid input for dns_name. Reason: 'networking-ovn-ubuntu-16.04' not a valid PQDN or FQDN. Reason: TLD '04' must not be all numeric.\nNeutron server returns request_ids: ['req-7317c3e3-2875-4073-8076-40e944845b69']\n"] This throws one instance of the infamous Horizon message: Error: No valid host was found. There are not enough hosts available. This issue was observed using stable/mitaka via DevStack (nova commit fb3f1706c68ea5b58f05ea810c6339f2449959de). In the above example, the instance name is "networking-ovn (Ubuntu 16.04)", which resulted in an attempted dns_name="networking-ovn- ubuntu-16.04", where the 04 was interpreted as a TLD and, consequently, an invalid TLD. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1581977/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1487745] [NEW] Neutron RBAC API and network support
You have been subscribed to a public bug: https://review.openstack.org/192555 commit 4595899f7f2b3774dc2dac2f8dd1a085b1e7973d Author: Kevin Benton Date: Tue Jun 16 23:43:59 2015 -0700 Neutron RBAC API and network support This adds the new API endpoint to create, update, and delete role-based access control entries. These entries enable tenants to grant access to other tenants to perform an action on an object they do not own. This was previously done using a single 'shared' flag; however, this was too coarse because an object would either be private to a tenant or it would be shared with every tenant. In addition to introducing the API, this patch also adds support to for the new entries in Neutron networks. This means tenants can now share their networks with specific tenants as long as they know the tenant ID. This feature is backwards-compatible with the previous 'shared' attribute in the API. So if a deployer doesn't want this new feature enabled, all of the RBAC operations can be blocked in policy.json and networks can still be globally shared in the legacy manner. Even though this feature is referred to as role-based access control, this first version only supports sharing networks with specific tenant IDs because Neutron currently doesn't have integration with Keystone to handle changes in a tenant's roles/groups/etc. DocImpact APIImpact Change-Id: Ib90e2a931df068f417faf26e9c3780dc3c468867 Partially-Implements: blueprint rbac-networks ** Affects: neutron Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: Confirmed ** Affects: openstack-manuals Importance: Undecided Status: Won't Fix ** Tags: neutron -- Neutron RBAC API and network support https://bugs.launchpad.net/bugs/1487745 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1532223] [NEW] [api-ref]OS-REVOKE extension missing for Identity v3
You have been subscribed to a public bug: OS-REVOKE extension is missing for Identity v3: http://specs.openstack.org/openstack/keystone-specs/api/v3/identity- api-v3-os-revoke-ext.html ** Affects: keystone Importance: Low Assignee: Diane Fleming (diane-fleming) Status: Confirmed ** Tags: keystone -- [api-ref]OS-REVOKE extension missing for Identity v3 https://bugs.launchpad.net/bugs/1532223 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1517705] [NEW] Move federation extension into keystone core
You have been subscribed to a public bug: https://review.openstack.org/214775 commit cbefe7c7b83b5f940f817adf60a4be35bd324775 Author: Steve Martinelli Date: Sun Oct 11 03:01:05 2015 -0400 Move federation extension into keystone core Remove federation as an extension and move it to a core resource. For now we leave the database migrations in the extension directory until we have a general policy for merging these into core. Some instances of federation constants were removed because they were causing a circular dependency, these can be refactored in a later patch. DocImpact: You should no longer run the migrations for this extension Implements: bp move-extensions Co-Authored-By: Nithya Renganathan Change-Id: If5857a6ee4c7c527929069b25beab40f4c5d87e2 ** Affects: keystone Importance: Undecided Status: Confirmed ** Affects: openstack-manuals Importance: Medium Status: Confirmed ** Tags: config-reference keystone -- Move federation extension into keystone core https://bugs.launchpad.net/bugs/1517705 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1253672] Re: update Images v2 API to include info about multilevel restricted JSON pointers
** Project changed: openstack-api-site => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1253672 Title: update Images v2 API to include info about multilevel restricted JSON pointers Status in Glance: Triaged Bug description: The Havana release of Glance introduces a "multiple image locations" option. In order to allow the http PATCH (image-update) request to operate on multiple locations, the "restricted JSON pointers" used by the application/openstack-images-v2.1-json-patch media type has been expanded to allow multilevel references. (1) The documentation in the OpenStack Image Service API v2 Reference needs to be updated to reflect this. (2) Need to supply at least one example, either in Appendix B or in the image update section, illustrating how to use the multilevel pointer to update an image location. (3) Judgement call: update the image detail section to show what an image response looks like with multiple image locations turned on. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1253672/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1524153] Re: Need to write "update user of OS-KSCRUD extension" on identity v2 API
** Project changed: openstack-api-site => keystone ** Summary changed: - Need to write "update user of OS-KSCRUD extension" on identity v2 API + [api-ref]Need to write "update user of OS-KSCRUD extension" on identity v2 API -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1524153 Title: [api-ref]Need to write "update user of OS-KSCRUD extension" on identity v2 API Status in OpenStack Identity (keystone): Confirmed Bug description: Now keystone supports "update user of OS-KSCRUD extension" on identity v2 API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. The URL is "OS-KSCRUD/users/" and the method is PATCH on identity v2 API. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1524153/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526212] Re: [api-ref]Need to write "add dhcp agent to network" on Networking API
** Summary changed: - Need to write "add dhcp agent to network" on Networking API + [api-ref]Need to write "add dhcp agent to network" on Networking API ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526212 Title: [api-ref]Need to write "add dhcp agent to network" on Networking API Status in neutron: Confirmed Bug description: Neutron supports "add dhcp agent to network" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526212/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526670] Re: [api-ref]Need to write "add router to l3 agent" on Networking API
** Summary changed: - Need to write "add router to l3 agent" on Networking API + [api-ref]Need to write "add router to l3 agent" on Networking API ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526670 Title: [api-ref]Need to write "add router to l3 agent" on Networking API Status in neutron: Confirmed Bug description: Neutron supports "add router to l3 agent" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526670/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1253672] [NEW] update Images v2 API to include info about multilevel restricted JSON pointers
You have been subscribed to a public bug: The Havana release of Glance introduces a "multiple image locations" option. In order to allow the http PATCH (image-update) request to operate on multiple locations, the "restricted JSON pointers" used by the application/openstack-images-v2.1-json-patch media type has been expanded to allow multilevel references. (1) The documentation in the OpenStack Image Service API v2 Reference needs to be updated to reflect this. (2) Need to supply at least one example, either in Appendix B or in the image update section, illustrating how to use the multilevel pointer to update an image location. (3) Judgement call: update the image detail section to show what an image response looks like with multiple image locations turned on. ** Affects: glance Importance: Medium Assignee: Atsushi SAKAI (sakaia) Status: Triaged ** Tags: havana image-api -- update Images v2 API to include info about multilevel restricted JSON pointers https://bugs.launchpad.net/bugs/1253672 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526673] Re: Need to write "update agent" on Networking API
** Project changed: openstack-api-site => neutron ** Summary changed: - Need to write "update agent" on Networking API + [api-ref]Need to write "update agent" on Networking API -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526673 Title: [api-ref]Need to write "update agent" on Networking API Status in neutron: In Progress Bug description: Neutron supports "update agent" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526673/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526670] [NEW] [api-ref]Need to write "add router to l3 agent" on Networking API
You have been subscribed to a public bug: Neutron supports "add router to l3 agent" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. ** Affects: neutron Importance: Undecided Assignee: Sangeetha Srikanth (ssrikant) Status: Confirmed ** Tags: neutron -- [api-ref]Need to write "add router to l3 agent" on Networking API https://bugs.launchpad.net/bugs/1526670 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526212] [NEW] [api-ref]Need to write "add dhcp agent to network" on Networking API
You have been subscribed to a public bug: Neutron supports "add dhcp agent to network" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. ** Affects: neutron Importance: Undecided Status: Confirmed ** Tags: neutron -- [api-ref]Need to write "add dhcp agent to network" on Networking API https://bugs.launchpad.net/bugs/1526212 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1524153] [NEW] Need to write "update user of OS-KSCRUD extension" on identity v2 API
You have been subscribed to a public bug: Now keystone supports "update user of OS-KSCRUD extension" on identity v2 API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. The URL is "OS-KSCRUD/users/" and the method is PATCH on identity v2 API. ** Affects: keystone Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: Confirmed ** Tags: keystone -- Need to write "update user of OS-KSCRUD extension" on identity v2 API https://bugs.launchpad.net/bugs/1524153 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526673] [NEW] Need to write "update agent" on Networking API
You have been subscribed to a public bug: Neutron supports "update agent" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: In Progress ** Tags: neutron -- Need to write "update agent" on Networking API https://bugs.launchpad.net/bugs/1526673 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1361791] Re: Allow attaching external networks based on configurable policy
** Project changed: openstack-api-site => nova ** Summary changed: - Allow attaching external networks based on configurable policy + [api-ref]Allow attaching external networks based on configurable policy -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1361791 Title: [api-ref]Allow attaching external networks based on configurable policy Status in OpenStack Compute (nova): Confirmed Bug description: https://review.openstack.org/112750 commit 674954f731bf4b66356fadaa5baaeb58279c5832 Author: Chris Yeoh Date: Fri Aug 8 11:48:17 2014 +0930 Allow attaching external networks based on configurable policy Commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 restricted attaching external networks to admin clients. This patch changes it to a policy based check instead with the default setting being admin only. This allows operators to more precisely configure who they wish to allow to attach external networks without having to give them admin access Change-Id: I59e71f117f889f2abffddc36c1870ef1e0fe3711 DocImpact: Adds network:attach_external_network policy Closes-Bug: #1352102 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1361791/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1361791] [NEW] Allow attaching external networks based on configurable policy
You have been subscribed to a public bug: https://review.openstack.org/112750 commit 674954f731bf4b66356fadaa5baaeb58279c5832 Author: Chris Yeoh Date: Fri Aug 8 11:48:17 2014 +0930 Allow attaching external networks based on configurable policy Commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 restricted attaching external networks to admin clients. This patch changes it to a policy based check instead with the default setting being admin only. This allows operators to more precisely configure who they wish to allow to attach external networks without having to give them admin access Change-Id: I59e71f117f889f2abffddc36c1870ef1e0fe3711 DocImpact: Adds network:attach_external_network policy Closes-Bug: #1352102 ** Affects: nova Importance: Medium Status: Confirmed ** Tags: nova -- Allow attaching external networks based on configurable policy https://bugs.launchpad.net/bugs/1361791 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1523012] Re: set `is_admin` on tokens for admin project
** Project changed: openstack-api-site => keystone -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1523012 Title: set `is_admin` on tokens for admin project Status in OpenStack Identity (keystone): In Progress Status in openstack-manuals: Confirmed Bug description: https://review.openstack.org/240719 commit e7023697a884759716d0a01605825a3af90d4db6 Author: Adam Young Date: Sun Oct 11 23:15:52 2015 -0400 set `is_admin` on tokens for admin project Adds two new configuration value: admin_project_name admin_project_domain_name If both values are set, and tokens requested for projects (only, not domains) that match both will have an additional value in them; `is_admin_project=true` DocImpact -- Configuration changes need documentation APIImpact -- Adds optional return values in token validation calls SecurityImpact -- Should be helpful in making access control decisions Implements: blueprint is-admin-project Partial-Bug: #968696 Change-Id: Ic9cf9862739381a30130b4be87075f726736ff88 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1523012/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1539467] Re: [Image service API v2] Incorrect description for List API
** Tags added: api-ref ** Project changed: openstack-api-site => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1539467 Title: [Image service API v2] Incorrect description for List API Status in Glance: In Progress Bug description: I 've tested this API: http://developer.openstack.org/api-ref-image-v2.html#listVersions-image-v2 The description for the response of the API says: "This operation does not accept a request body and does not return a response body." But the API does return a response. The description should be: "This operation does not accept a request body." To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1539467/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1523012] [NEW] set `is_admin` on tokens for admin project
You have been subscribed to a public bug: https://review.openstack.org/240719 commit e7023697a884759716d0a01605825a3af90d4db6 Author: Adam Young Date: Sun Oct 11 23:15:52 2015 -0400 set `is_admin` on tokens for admin project Adds two new configuration value: admin_project_name admin_project_domain_name If both values are set, and tokens requested for projects (only, not domains) that match both will have an additional value in them; `is_admin_project=true` DocImpact -- Configuration changes need documentation APIImpact -- Adds optional return values in token validation calls SecurityImpact -- Should be helpful in making access control decisions Implements: blueprint is-admin-project Partial-Bug: #968696 Change-Id: Ic9cf9862739381a30130b4be87075f726736ff88 ** Affects: keystone Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: In Progress ** Affects: openstack-manuals Importance: Undecided Status: Confirmed ** Tags: autogenerate-config-docs keystone -- set `is_admin` on tokens for admin project https://bugs.launchpad.net/bugs/1523012 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1539467] [NEW] [Image service API v2] Incorrect description for List API
You have been subscribed to a public bug: I 've tested this API: http://developer.openstack.org/api-ref-image-v2.html#listVersions-image-v2 The description for the response of the API says: "This operation does not accept a request body and does not return a response body." But the API does return a response. The description should be: "This operation does not accept a request body." ** Affects: glance Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: In Progress ** Tags: api-ref glance -- [Image service API v2] Incorrect description for List API https://bugs.launchpad.net/bugs/1539467 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1480400] Re: Documentation error for properties
The api-ref is maintained by each module (for this case glance).
So I close for api-site ticket.
** Changed in: openstack-api-site
Status: In Progress => Opinion
** Changed in: openstack-api-site
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1480400
Title:
Documentation error for properties
Status in Glance:
In Progress
Status in openstack-api-site:
Invalid
Bug description:
Document: http://developer.openstack.org/api-ref-image-v2.html
Under the image create drop down there is the following line:
properties (Optional) plain | xsd:dict | Properties, if any, that are
associated with the image.
This suggests that the properties are a dict and would look like this:
-d '{"name": "thename", "properties": {"myprop", "mydata"}}'
this is not the case, as if you want
to define custom properties in a curl command you do it by defining it like
any other property eg.
-d '{"name": "thename", "myprop": "mydata"}'
The documentation is not clear about this distinction.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1480400/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581666] Re: [api-ref]Broken link to filtering section in list floating IP detail operation
** Summary changed: - Broken link to filtering section in list floating IP detail operation + [api-ref]Broken link to filtering section in list floating IP detail operation ** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581666 Title: [api-ref]Broken link to filtering section in list floating IP detail operation Status in neutron: New Bug description: In repo: https://github.com/openstack/api-site/blob/master/api-ref/source/networking/v2-ext/layer3-ext.inc In operation "Show floating IP details" here http://developer.openstack.org/api-ref-networking-v2-ext.html#showFloatingIp It offers a link to filtering section which is broken. Link should point to : https://wiki.openstack.org/wiki/Neutron/APIv2-specification#Filtering_and_Column_Selection The “List floating IP” operation links correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581666/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581666] [NEW] [api-ref]Broken link to filtering section in list floating IP detail operation
You have been subscribed to a public bug: In repo: https://github.com/openstack/api-site/blob/master/api-ref/source/networking/v2-ext/layer3-ext.inc In operation "Show floating IP details" here http://developer.openstack.org/api-ref-networking-v2-ext.html#showFloatingIp It offers a link to filtering section which is broken. Link should point to : https://wiki.openstack.org/wiki/Neutron/APIv2-specification#Filtering_and_Column_Selection The “List floating IP” operation links correctly. ** Affects: neutron Importance: Undecided Status: New ** Tags: api-ref -- [api-ref]Broken link to filtering section in list floating IP detail operation https://bugs.launchpad.net/bugs/1581666 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581962] [NEW] when creating external network for specific tenant, all tenants can see the network (RBAC)
Public bug reported: We created external network with admin user for tenantA. $ neutron net-create admin-ext --provider:network_type=vxlan --router:external --tenant_id=TENANTA_ID The rbac policy was created with "*" in target_tenant attribute. When creatin an external network for specific tenant the rbac policy "target_tenant" value should be the same as "--tenant_id" value . ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581962 Title: when creating external network for specific tenant, all tenants can see the network (RBAC) Status in neutron: New Bug description: We created external network with admin user for tenantA. $ neutron net-create admin-ext --provider:network_type=vxlan --router:external --tenant_id=TENANTA_ID The rbac policy was created with "*" in target_tenant attribute. When creatin an external network for specific tenant the rbac policy "target_tenant" value should be the same as "--tenant_id" value . To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581962/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581935] [NEW] update "--router:external" attribute to true should be blocked when network has ports in use
Public bug reported: Network update "--router:external" attribute should be blocked if the network has ports in use ( not including qdhcp port) When a network with a port attached to a VM turnes to be external, it can make an opening to issues of qdhcp NS for this network, The VMs on this network. If the network was attached as internal interface on a router and becomes external , there is a contrast between the network role ( external) to network usage ( attached as internal ) BR Alex ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581935 Title: update "--router:external" attribute to true should be blocked when network has ports in use Status in neutron: New Bug description: Network update "--router:external" attribute should be blocked if the network has ports in use ( not including qdhcp port) When a network with a port attached to a VM turnes to be external, it can make an opening to issues of qdhcp NS for this network, The VMs on this network. If the network was attached as internal interface on a router and becomes external , there is a contrast between the network role ( external) to network usage ( attached as internal ) BR Alex To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581935/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581933] [NEW] RBAC "access_as_external" policy on in-use internal netwok
Public bug reported: When the internal network have ports in use, a rbac "access_as_external" policy should not be allowed. We should have an error message explaining that. When we execute such an action, the "router:external" for the internal network becomes "true" neutron net-show 10567136-eda7-4b34-bd70-a7854f6d09ed +-+--+ | Field | Value| +-+--+ | admin_state_up | True | | availability_zone_hints | | | availability_zones | | | created_at | 2016-05-11T08:09:20 | | description | | | id | 10567136-eda7-4b34-bd70-a7854f6d09ed | | ipv4_address_scope | | | ipv6_address_scope | | | is_default | False| | mtu | 1450 | | name| net-toni | | router:external | True | | shared | False| | status | ACTIVE | | subnets | | | tags| | | tenant_id | 25a1c11e26354d7dbb5b204eb1310f33 | | updated_at | 2016-05-11T08:09:20 | +-+--+ But the network has ports assigned to internal purposes like VM or internal router interface and it opens many spots for errors . MITAKA ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581933 Title: RBAC "access_as_external" policy on in-use internal netwok Status in neutron: New Bug description: When the internal network have ports in use, a rbac "access_as_external" policy should not be allowed. We should have an error message explaining that. When we execute such an action, the "router:external" for the internal network becomes "true" neutron net-show 10567136-eda7-4b34-bd70-a7854f6d09ed +-+--+ | Field | Value| +-+--+ | admin_state_up | True | | availability_zone_hints | | | availability_zones | | | created_at | 2016-05-11T08:09:20 | | description | | | id | 10567136-eda7-4b34-bd70-a7854f6d09ed | | ipv4_address_scope | | | ipv6_address_scope | | | is_default | False| | mtu | 1450 | | name| net-toni | | router:external | True | | shared | False| | status | ACTIVE | | subnets | | | tags| | | tenant_id | 25a1c11e26354d7dbb5b204eb1310f33 | | updated_at | 2016-05-11T08:09:20 | +-+--+ But the network has ports assigned to internal purposes like VM or internal router interface and it opens many spots for errors . MITAKA To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581933/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581931] [NEW] RBAC -access_as_external - exclude tenant
Public bug reported: If we have 50 tenants and we will want to expose the external network to 49 of them, we will have to create 49 rbac rules. IMHO it can be not so comfortable. I believe we should make an option to exclude specific tenant/tenants from being targeted by the rbac rule. May be we can add attribute "exclude_tenants" to the RBAC policy in order to make it happen. MITAKA ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581931 Title: RBAC -access_as_external - exclude tenant Status in neutron: New Bug description: If we have 50 tenants and we will want to expose the external network to 49 of them, we will have to create 49 rbac rules. IMHO it can be not so comfortable. I believe we should make an option to exclude specific tenant/tenants from being targeted by the rbac rule. May be we can add attribute "exclude_tenants" to the RBAC policy in order to make it happen. MITAKA To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581931/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581929] [NEW] RBAC -access_as_external lack of flexibility
Public bug reported: If we have an external network, with default rbac policy, and even 1 tenant is using this network, we can not delete the default rbac policy in order to decide to which tenants this network will be exposed. In this situation the network will be exposed to all tenants unless the admin first disconnects the using tenant and then makes the needed changes. In a situation with many tenants this will be non user friendly. MITAKA. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581929 Title: RBAC -access_as_external lack of flexibility Status in neutron: New Bug description: If we have an external network, with default rbac policy, and even 1 tenant is using this network, we can not delete the default rbac policy in order to decide to which tenants this network will be exposed. In this situation the network will be exposed to all tenants unless the admin first disconnects the using tenant and then makes the needed changes. In a situation with many tenants this will be non user friendly. MITAKA. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581929/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1581928] [NEW] RBAC "access_as_external" policy for internal network
Public bug reported: External network has no qdhcp namespace, when internal network does. So, After creating "access_as_external" rbac policy for tenant internal network ( convertes the network to external), the network qdhcp namespace is not removed. IMHO it should be removed. Mitaka ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1581928 Title: RBAC "access_as_external" policy for internal network Status in neutron: New Bug description: External network has no qdhcp namespace, when internal network does. So, After creating "access_as_external" rbac policy for tenant internal network ( convertes the network to external), the network qdhcp namespace is not removed. IMHO it should be removed. Mitaka To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1581928/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
Reviewed: https://review.openstack.org/315397 Committed: https://git.openstack.org/cgit/openstack/vitrage/commit/?id=a3aeb31a63092569c4b2e465009fd99db8755ac4 Submitter: Jenkins Branch:master commit a3aeb31a63092569c4b2e465009fd99db8755ac4 Author: sharat.sharma Date: Thu May 12 13:37:17 2016 +0530 Changed assertTrue(isinstance) to assertIsInstance() Change-Id: I87fb09fb56ed886cb7d2a398e5c719b7f381ce80 Closes-Bug: #1268480 ** Changed in: vitrage Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Invalid Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Invalid Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Fix Committed Status in OpenStack SDK: Fix Released Status in python-rackclient: Fix Committed Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: Fix Released Status in zaqar: In Progress Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
