Metering - metering-label-rule doesn't need 'tenant_id'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Low
|
Ukesh | ||
python-neutronclient |
Invalid
|
Undecided
|
Ukesh |
Bug Description
In current metering-
However, even if we specify 'tenant_id' by using CLI or REST-API, 'tenant_id'
isn't stored on DB[2] and we cannot see the result. Therefore, I think
following fixes are necessary:
1. 'tenant_id' definition should be removed at extensions/
2. Remove 'tenant_id' option from CLI(meter-
[CLI]
(neutron) meter-label-
Created a new metering_
+------
| Field | Value |
+------
| direction | ingress |
| excluded | False |
| id | 4ef89142-
| metering_label_id | 543ce87e-
| remote_ip_prefix | 192.168.2.0/24 |
+------
[REST-API]
$ source devstack/openrc admin admin
$ export TOKEN=`openstack token issue | grep ' id ' | get_field 2`
$ curl -s -X POST -H "accept:
{
"metering_
"remote_
"direction": "ingress",
"metering_
"id": "d300512f-
"excluded": false
}
}
[1] https:/
[2] https:/
Changed in neutron: | |
assignee: | nobody → Ukesh (ukeshkumar) |
Changed in python-neutronclient: | |
assignee: | nobody → Ukesh (ukeshkumar) |
Changed in python-neutronclient: | |
status: | New → Invalid |
The only fields that are applicable to Metering Label Rule are: direction, remote_ip_prefix, excluded and metering_label_id.