| 2015-04-13 10:16:44 |
Alexander Kislitsky |
bug |
|
|
added bug |
| 2015-04-14 15:20:02 |
Alexander Kislitsky |
tags |
feature feature-stats non-release |
feature feature-nailgun feature-stats |
|
| 2015-04-14 15:26:25 |
OpenStack Infra |
fuel: status |
Triaged |
In Progress |
|
| 2015-04-21 16:13:03 |
Dmitry Pyzhov |
tags |
feature feature-nailgun feature-stats |
feature feature-stats |
|
| 2015-04-27 13:29:47 |
Dmitry Pyzhov |
tags |
feature feature-stats |
feature feature-stats non-release |
|
| 2015-04-30 12:51:48 |
Dmitry Pyzhov |
fuel: milestone |
6.1 |
7.0 |
|
| 2015-05-20 08:56:38 |
Alexander Kislitsky |
description |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be accepted by collector.
Filtering rules is dict with release numbers as keys. Value of dict by key is list of dicts with keys: build_id, from_dt. from_dt is optional value. If from_dt is not present, then stats from build_id is accepted. If from_date is present, then stats from build_id is accetpted only after from_dt. Format of from_dt is ISO 8601.
If release is not listed in filtering rules, data shouldn't be accepted.
If build_is is not listed for release in filtering rules, data shouldn't be accepted.
Filtering rules example:
{'6.1': [
{'build_id': '2015-04-13_234_13-12-31', 'from_dt': '2015-04-30T23:00:18'},
{'build_id': '2015-04-13_06-18-10'},
]}
If release and build_id is not specified in data, it will be saved. This is required for support 6.0 installations.
Work items:
- Add release_id, build_id into fuel-stats protocol on the nailgun side
- Handle filtriation on the fuel-collector side. |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules is dict with release numbers as keys. Value of dict by key is list of dicts with keys: build_id, from_dt. from_dt is optional value. If from_dt is not present, then stats from build_id is accepted. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
Filtering rules example:
{'6.1': [
{'build_id': '2015-04-13_234_13-12-31', 'from_dt': '2015-04-30T23:00:18'},
{'build_id': '2015-04-13_06-18-10'},
]}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter. |
|
| 2015-05-20 09:34:03 |
Alexander Kislitsky |
description |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules is dict with release numbers as keys. Value of dict by key is list of dicts with keys: build_id, from_dt. from_dt is optional value. If from_dt is not present, then stats from build_id is accepted. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
Filtering rules example:
{'6.1': [
{'build_id': '2015-04-13_234_13-12-31', 'from_dt': '2015-04-30T23:00:18'},
{'build_id': '2015-04-13_06-18-10'},
]}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter. |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules structure: {release_id: {build_id: from_dt}}. If from_dt is not present, then stats from build_id is not marked as filtered. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
All other data will be marked as filtered.
Filtering rules example:
{'6.1':
{'2015-04-13_234_13-12-31': '2015-04-30T23:00:18', # 6.1 build 2015-04-13_234_13-12-31 not filtered after 2015-04-30T23:00:18 UTC
'2015-04-13_06-18-10': None # 6.1 build 2015-04-13_06-18-10 not filtered
},
'6.1.1': {}, # All builds of 6.1.1 not filtered
'7.0': None # All builds of 7.0 not filtered
}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter. |
|
| 2015-05-20 12:44:38 |
Alexander Kislitsky |
description |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules structure: {release_id: {build_id: from_dt}}. If from_dt is not present, then stats from build_id is not marked as filtered. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
All other data will be marked as filtered.
Filtering rules example:
{'6.1':
{'2015-04-13_234_13-12-31': '2015-04-30T23:00:18', # 6.1 build 2015-04-13_234_13-12-31 not filtered after 2015-04-30T23:00:18 UTC
'2015-04-13_06-18-10': None # 6.1 build 2015-04-13_06-18-10 not filtered
},
'6.1.1': {}, # All builds of 6.1.1 not filtered
'7.0': None # All builds of 7.0 not filtered
}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter. |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules structure: {release_id: {build_id: from_dt}}. If from_dt is not present, then stats from build_id is not marked as filtered. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
All other data will be marked as filtered.
Filtering rules example:
{'6.1':
{
# 6.1 build 2015-04-13_234_13-12-31 became not filtered only
# after 2015-04-30T23:00:18 UTC
'2015-04-13_234_13-12-31': '2015-04-30T23:00:18',
# 6.1 build 2015-04-13_06-18-10 not filtered
'2015-04-13_06-18-10': None
},
'6.1.1': {}, # All builds of 6.1.1 filtered
'7.0': None # All builds of 7.0 not filtered
}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter. |
|
| 2015-06-29 07:28:30 |
Alexander Kislitsky |
description |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules structure: {release_id: {build_id: from_dt}}. If from_dt is not present, then stats from build_id is not marked as filtered. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
All other data will be marked as filtered.
Filtering rules example:
{'6.1':
{
# 6.1 build 2015-04-13_234_13-12-31 became not filtered only
# after 2015-04-30T23:00:18 UTC
'2015-04-13_234_13-12-31': '2015-04-30T23:00:18',
# 6.1 build 2015-04-13_06-18-10 not filtered
'2015-04-13_06-18-10': None
},
'6.1.1': {}, # All builds of 6.1.1 filtered
'7.0': None # All builds of 7.0 not filtered
}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter. |
We should filter data on the collector side. Additional configuration of rules for filtration sould be able to load from external config. If filtration rules are not provided, then all data will be marked as not filtered by collector.
Filtering rules structure: {release_id: {build_id: from_dt}}. If from_dt is not present, then stats from build_id is not marked as filtered. If from_date is present, then stats from build_id is marked as non filtered only after datetime greater than from_dt. Format of from_dt is ISO 8601.
from_dt timezone is UTC.
If filtering rules are present and release is not listed in filtering rules, data should be marked as filtered.
If build_id is not listed for release in filtering rules, data should be marked as filtered.
All other data will be marked as filtered.
Filtering rules example:
{'6.1':
{
# 6.1 build 2015-04-13_234_13-12-31 became not filtered only
# after 2015-04-30T23:00:18 UTC
'2015-04-13_234_13-12-31': '2015-04-30T23:00:18',
# 6.1 build 2015-04-13_06-18-10 not filtered
'2015-04-13_06-18-10': None
},
'6.1.1': {}, # All builds of 6.1.1 filtered
'7.0': None # All builds of 7.0 not filtered
}
Work items:
- Handle filtration on the fuel-collector side,
- Handle filtering status in the CSV exporter.
- Handle filtering status in the fuel-stats web UI. |
|
| 2015-06-30 17:02:01 |
OpenStack Infra |
fuel: status |
In Progress |
Fix Committed |
|
| 2015-09-25 10:02:45 |
Andrey Sledzinskiy |
fuel: status |
Fix Committed |
Fix Released |
|
