Public bug reported:
Problem Description
===
A routing metric is a quantitative value that is used to evaluate the path cost.
But neutron can't specify a different metric with the same destination address.
It is useful to realize FRR(Fast Reroute) in Telecoms and NFV scenario.
Public bug reported:
According to http://specs.openstack.org/openstack/neutron-
specs/specs/pike/extend-quota-api-to-send-usage-stats.html
A new optional argument will be added to the openstack client, for example: $
openstack quota show {tenant_id/project_id} –detail
This adds following
Public bug reported:
The old link is invalid, we can't access any more.
so fix it
** Affects: neutron
Importance: Undecided
Assignee: zhangyanxian (zhang-yanxian)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => zhangyanxian (zhang-yanxian)
--
Public bug reported:
Similar with bug https://bugs.launchpad.net/neutron/+bug/1716558,
According to
http://specs.openstack.org/openstack/neutron-specs/specs/pike/qos-detailed-reporting-of-available-rules.html,
we should get details of every available rule type with different drivers in
pike
Public bug reported:
I have installed the pike version by devstack.
According to
https://docs.openstack.org/releasenotes/neutron/pike.html,Implements a new
extension, quota_details which extends existing quota API to show detailed
information for a specified tenant. The new API shows details
Public bug reported:
Use the new OpenStack envirement created by devstack:
(1)Create a vm by horizon dashboard;
(2)step 1 failed and report spawning state for a long time
(3)delete the vm
(4)step 3 still failed and report deleting state for a long time(over 30
minutes)
Now the information as
6 matches
Mail list logo
