1. 27 Mar, 2018 1 commit
    • chef: merge refresh_metric and process_new_measures · 51ac20f0
      This simplifies the code base by just allowing to process new measures sack per
      sack with the existing process_new_measures_for_sack() or to use the new
      refresh_metrics() who takes a list of metrics. Since the list of metric must be
      known, there's no need to use list_metric_with_measures_to_process() anymore,
      so it can be removed.
      
      Since some of the tests (test_rest) need to process all sacks now, reduce the
      number of sack to a small number in order for each test not to take 10s.
      Julien Danjou committed
  2. 23 Mar, 2018 1 commit
  3. 22 Mar, 2018 2 commits
  4. 21 Mar, 2018 2 commits
  5. 20 Mar, 2018 3 commits
  6. 19 Mar, 2018 2 commits
  7. 16 Mar, 2018 2 commits
    • chef: lock sack when using process_new_measures_for_sack · 5778cfb1
      This makes it safer to call it without taking care of the lock externally.
      Julien Danjou committed
    • incoming: introduce process_measures_for_sack · ea9531da
      This adds a new method process_measures_for_sack to incoming storage driver. It
      allows to read an entire sack for new measure rather than individual metrics.
      This avoids doing 2 listing to process new metrics and only does one to load
      the measures.
      
      The process_new_measures(metrics) is kept for the refresh_metric() use case for
      now. Some refactoring might be possible after this patch.
      
      The S3 storage driver is a bit modified to store the incoming measures in
      <sack>/<metric>/ rather than <sack><metric>/ so it's easier to list incoming
      sacks and metrics.
      Julien Danjou committed
  8. 14 Mar, 2018 1 commit
  9. 13 Mar, 2018 1 commit
  10. 10 Mar, 2018 2 commits
  11. 09 Mar, 2018 3 commits
  12. 08 Mar, 2018 2 commits
  13. 07 Mar, 2018 3 commits
  14. 06 Mar, 2018 3 commits
    • Move out from pbr · 3f8a22a5
      All pbr interesting features (the seutp.cfg) have been implemented in
      setuptools since version 30.3.0 (8 Dec 2016).
      Also pbr will break us soon and force us to found a new solution
      to generate things during setup.py steps.
      https://github.com/gnocchixyz/gnocchi/issues/755
      
      When you use pbr you cannot override most of the cmdclass. So we cannot
      make our hooks working anymore.
      
      Generation of ChangeLog and AUTHORS are done during egg_info.
      gnocchi-api script is created on the fly with the right python header
      
      Package file listing and package version is done by the pypa maintained
      setuptools_scm.
      
      This may impact downstream packaging as setuptools versions are a bit
      old:
      * xenial: 20.7
      * zesty: 33.1.1
      * centos7/rhel7: 0.9.8 ... really ?
      * rdo queen: 22.0
      * rdo rocky plan to 38.6
      
      Closes-bug: #755
      Mehdi Abaakouk committed
    • storage: remove metric existence check when retrieving splits · d8fd8e6a
      Splits are either retrieve for reading from:
      
      - the REST API, where the splits are actually listed before being retrieved, we
        don't care about the metric existence or not, None is enough.
      
      - on rewriting the split (WRITE_FULL) and in that case we know the metric
        exists
      Julien Danjou committed
    • storage: fix corruption scenario · 60e75855
      If data corruption occurs, the _get_splits_and_unserialize() method might not
      return the same number of arguments that it received. It's not a big deal when
      concatenating the splits to retrieve the data for reading. However, when
      requesting a bunch of splits for rewrite, that's a problem because the list is
      zipped with other data on iteration, possibly corrupting the results.
      Julien Danjou committed
  15. 05 Mar, 2018 5 commits
  16. 02 Mar, 2018 3 commits
  17. 01 Mar, 2018 4 commits