yahoo-eng-team team mailing list archive

[xiewj <36429515@xxxxxx>]

Public bug reported:

‘ACL’ appears in the spec document of 'rbac-qos-policies',actually
should be RBAC

In the spec document of 'rbac-qos-policies' of Mitaka release, shown as follows:
https://github.com/openstack/neutron-specs/blob/master/specs/mitaka/rbac-qos-policies.rst

In the QosPolicyRBAC Table structure of 'Data Model Impact' section,appears 'ACL',actually should be RBAC
1)Attribute 'id' is described as 'id of ACL entry',I think it should be 'id of RBAC entry'.
2)Attribute 'tenant_id'is described as 'owner of ACL entry',I think it should be 'owner of RBAC entry'.
3)Attribute 'object_id' is described as 'object affected by ACL',I think it should be 'the id of the RBAC object'.
4)The table doesn't contain attribute 'type'

In the API Tests section,it is the same,ACL should be replaced by RBAC
Excercise basic CRUD of ACL entries.
Make sure qos policies are revealed and hidden as ACL entries are changed

** Affects: neutron
     Importance: Undecided
     Assignee: xiewj (36429515-3)
         Status: New

** Summary changed:

- ‘ACL related’ appears in the spec document of 'rbac-qos-policies',actually should be RBAC
+ ‘ACL ’ appears in the spec document of 'rbac-qos-policies',actually should be RBAC

** Description changed:

- ‘ACL related’ appears in the spec document of 'rbac-qos-
- policies',actually should be RBAC
+ ‘ACL’ appears in the spec document of 'rbac-qos-policies',actually
+ should be RBAC
  
  In the spec document of 'rbac-qos-policies' of Mitaka release, shown as follows:
  https://github.com/openstack/neutron-specs/blob/master/specs/mitaka/rbac-qos-policies.rst
  
  In the QosPolicyRBAC Table structure of 'Data Model Impact' section,appears 'ACL',actually should be RBAC
  1)Attribute 'id' is described as 'id of ACL entry',I think it should be 'id of RBAC entry'.
  2)Attribute 'tenant_id'is described as 'owner of ACL entry',I think it should be 'owner of RBAC entry'.
  3)Attribute 'object_id' is described as 'object affected by ACL',I think it should be 'the id of the RBAC object'.
  4)The table doesn't contain attribute 'type'
  
  In the API Tests section,it is the same,ACL should be replaced by RBAC
  Excercise basic CRUD of ACL entries.
  Make sure qos policies are revealed and hidden as ACL entries are changed

** Changed in: neutron
     Assignee: (unassigned) => xiewj (36429515-3)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1596445

Title:
  ‘ACL ’ appears in the spec document of 'rbac-qos-policies',actually
  should be RBAC

Status in neutron:
  New

Bug description:
  ‘ACL’ appears in the spec document of 'rbac-qos-policies',actually
  should be RBAC

  In the spec document of 'rbac-qos-policies' of Mitaka release, shown as follows:
  https://github.com/openstack/neutron-specs/blob/master/specs/mitaka/rbac-qos-policies.rst

  In the QosPolicyRBAC Table structure of 'Data Model Impact' section,appears 'ACL',actually should be RBAC
  1)Attribute 'id' is described as 'id of ACL entry',I think it should be 'id of RBAC entry'.
  2)Attribute 'tenant_id'is described as 'owner of ACL entry',I think it should be 'owner of RBAC entry'.
  3)Attribute 'object_id' is described as 'object affected by ACL',I think it should be 'the id of the RBAC object'.
  4)The table doesn't contain attribute 'type'

  In the API Tests section,it is the same,ACL should be replaced by RBAC
  Excercise basic CRUD of ACL entries.
  Make sure qos policies are revealed and hidden as ACL entries are changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1596445/+subscriptions