Back to bug 1042187
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHOS Integration | 2013-12-12 21:18:48 UTC | Keywords | FutureFeature | |
| Whiteboard | upstream_milestone_icehouse-2 upstream_status_started | |||
| Red Hat Bugzilla | 2013-12-12 21:18:48 UTC | Doc Type | Bug Fix | Enhancement |
| RHOS Integration | 2013-12-17 00:44:56 UTC | Whiteboard | upstream_milestone_icehouse-2 upstream_status_started | upstream_milestone_icehouse-2 upstream_status_blocked |
| RHOS Integration | 2013-12-26 23:04:21 UTC | Target Release | 5.0 | --- |
| Whiteboard | upstream_milestone_icehouse-2 upstream_status_blocked | upstream_milestone_icehouse-2 upstream_status_needs-code-review | ||
| RHEL Program Management | 2013-12-26 23:33:47 UTC | Target Release | --- | 5.0 |
| John Skeoch | 2014-01-13 01:15:53 UTC | CC | hateya | |
| RHOS Integration | 2014-01-22 05:05:41 UTC | Target Release | 5.0 | --- |
| Whiteboard | upstream_milestone_icehouse-2 upstream_status_needs-code-review | upstream_milestone_icehouse-2 upstream_status_implemented | ||
| RHEL Program Management | 2014-01-22 05:21:19 UTC | Target Release | --- | 5.0 |
| Stephen Gordon | 2014-01-23 20:50:39 UTC | Status | NEW | POST |
| RHOS Integration | 2014-02-19 22:27:49 UTC | Target Release | 5.0 | --- |
| Whiteboard | upstream_milestone_icehouse-2 upstream_status_implemented | upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved | ||
| RHEL Program Management | 2014-02-19 22:56:41 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-20 16:03:40 UTC | Target Release | 5.0 | --- |
| RHEL Program Management | 2014-02-20 17:19:52 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-20 17:54:46 UTC | Target Release | 5.0 | --- |
| RHEL Program Management | 2014-02-20 18:22:16 UTC | Target Release | --- | 5.0 |
| RHOS Integration | 2014-02-20 21:49:52 UTC | Target Release | 5.0 | --- |
| RHEL Program Management | 2014-02-20 22:16:33 UTC | Target Release | --- | 5.0 |
| Scott Lewis | 2014-03-26 18:41:40 UTC | CC | sbaker, sdake, shardy | |
| Component | RFEs | openstack-heat | ||
| Steven Dake | 2014-04-08 17:13:53 UTC | Priority | unspecified | low |
| Doc Text | Feature: Implement neutron metering resources. Reason: Not sure how these are useful. Result (if any): |
|||
| Steven Dake | 2014-04-08 17:14:18 UTC | Flags | needinfo?(sbaker) | |
| Scott Lewis | 2014-07-07 13:42:07 UTC | Target Milestone | Upstream M2 | rc |
| Scott Lewis | 2014-07-07 13:53:33 UTC | Target Milestone | rc | ga |
| Scott Lewis | 2014-07-22 19:08:58 UTC | Status | POST | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-07-22 15:08:58 UTC | |||
| Steve Baker | 2014-07-27 21:19:17 UTC | Doc Text | Feature: Implement neutron metering resources. Reason: Not sure how these are useful. Result (if any): | Feature: Implement neutron metering resources. Reason: To allow template authors to configure IP ranges and to assign a label to them. An example setting two labels; one for the internal traffic, and the other one for the external traffic. Each label will measure the traffic for a specific set of ip range. Then, bandwidth measurement will be send for each label to the Oslo notification system and could be collected by Ceilometer. Result (if any): The ability to define neutron metering labels and rules in a heat template. |
| Flags | needinfo?(sbaker) | |||
| Bruce Reeler | 2014-08-19 02:41:56 UTC | CC | breeler | |
| Doc Text | Feature: Implement neutron metering resources. Reason: To allow template authors to configure IP ranges and to assign a label to them. An example setting two labels; one for the internal traffic, and the other one for the external traffic. Each label will measure the traffic for a specific set of ip range. Then, bandwidth measurement will be send for each label to the Oslo notification system and could be collected by Ceilometer. Result (if any): The ability to define neutron metering labels and rules in a heat template. | A new feature has been added which implements OpenStack Networking metering resources. This allows template authors to configure IP ranges and to assign a label to them. For example, setting two labels: one for the internal traffic, and the other one for the external traffic. Each label will measure the traffic for a specific IP range. Then, bandwidth measurement will be sent for each label to the Oslo notification system and could be collected by the Telemetry service. This enhancement gives users the ability to define OpenStack Networking metering labels and rules in an Orchestration template. |
Back to bug 1042187