The contents of this repository are still available in the Git source
code management system. To see the contents of this repository before it
reached its end of life, please check out the previous commit with
"git checkout HEAD^1".
For any further questions, please email
openstack-discuss@lists.openstack.org or join #openstack-telemetry on OFTC.
Change-Id: Ic8a7001e708d8da7cf8951eefd0a96762ea5fa46
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
Remove docs requirements from test-requirement, it's enough to have them
in doc/requirements.txt.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I8d4234212ecceb639e40eae423af72d2d08b010d
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: I92f240b2b2fbb8a0a7ac188ff9bed8b0d11209b3
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I3760aae7bb78fdffc34a492f150bc7df8a4a9bf2
* Intree panko tempest plugin does not contains any tempest tests
and has just dummy tempest plugin skeletion, so it is better to
remove from the project. If in future new panko tempest tests
will be written, will go to a new repo where all the telemetry
tests will resides.
Change-Id: I4f56bdac3ddd7b55ae791c9e6aafb78bc5f6e14b
Project documents are being reprocessed due to document migration[1].
Update the docs theme to openstackdocstheme instead of oslosphinx.
[1] https://review.openstack.org/#/c/472275/
Change-Id: I9353ba579b093d0ab91e2f60612b8cbc8ffbb733
Co-Authored-By: chenxing <chen.xing@99cloud.net>
This change leverages the Gnocchi Batch API by using it
in the Ceilometer dispatcher for measurements.
It introduces a small behavior change in the dispatcher.
The resource metadata update is now decorrelated from measures posting.
So, even if posting measurements fail, the resource metadata will
be updated.
Change-Id: I140e7301a31bbee50c2c8bc3ff2d78925680a573
This removes these tests because they:
1. Depends on httplib2 which is being deprecated
2. Test running of `ceilometer-api' which is anyhow tested in the
devstack functional testing.
Closes-Bug: #1556985
Change-Id: Ic5fd445c651e28a37ee3ec72fbb0894486af6be6
os-win is a library containing Windows / Hyper-V related code.
It contains utils modules that are used by nova, cinder,
networking_hyperv, os-brick. It also contains Hyper-V metrics
related utils, which can be used in ceilometer.
Adds os-win to requirements.txt.
Replaces the current usage of *Utils classes in the
Hyper-V Inspector with the equivalent *Utils classes
from os-win.
Adds decorators to the HyperVInspector methods that prevent
os-win specific exceptions to leak outside the inspector.
Depends-On: Ia937399c999d7293799a864a322323e3d2efc123
Depends-On: I1256b632be7aa90561338b595b9406c30f406c7c
Change-Id: Ic637e2a9c929cac88b1cb99f5b55dd70c4f84c47
This patches leverage overtest to setup the database environment needed.
Change-Id: I8198041b4a87bf187d8f6499f0c7c1a43d4dcac2
Depends-On: I29e480611e743ddc645fd067ca2c63b51b11b518
What this does is store a key value pair in oslo_cache where the key
is the resource id and the value is a hash of the frozenset of
the attributes of the resource less the defined metrics[1]. When it
is time to create or update a resource we ask the cache:
Are the resource attributes I'm about to store the same as the
last ones stored for this id?
If the answer is yes we don't need to store the resource. That's all
it does and that is all it needs to do because if the cache fails
to have the correct information that's the same as the cache not
existing in the first place.
To get this to work in the face of eventlet's eager beavering we
need to lock around create_resource and update_resource so that
we have a chance to write the cache before another *_resource is
called in this process. Superficial investigation shows that this
works out pretty well because when, for example, you start a new
instance the collector will all of sudden try several
_create_resources, only one of which actually needs to happen.
The lock makes sure only that one happens when there is just
one collector. Where there are several collectors that won't be
the case but _some_ of them will be stopped. And that's the point
here: better not perfect.
The cache is implemented using oslo_cache which can be configured
via oslo_config with an entry such as:
[cache]
backend = dogpile.cache.redis
backend_argument = url:redis://localhost:6379
backend_argument = db:0
backend_argument = distributed_lock:True
backend_argument = redis_expiration_time:600
The cache is exercised most for resource updates (as you might
expect) but does still sometimes get engaged for resource creates
(as described above).
A cache_key_mangler is used to ensure that keys generated by the
gnocchi dispatcher are in their own namespace.
[1] Metrics are not included because they are represented as
sub-dicts which are not hashable and thus cannot go in the
frozenset. Since the metrics are fairly static (coming from a yaml
file near you, soon) this shouldn't be a problem. If it is then we
can come up with a way to create a hash that can deal with
sub-dicts.
Closes-Bug: #1483634
Change-Id: I1f2da145ca87712cd2ff5b8afecf1bca0ba53788
The oslo.messaging-2.6.1 has broken Ceilometer Jenkins job two days, The
change[1] could hopefully fix the issue, but it is better to block the
oslo.messaging-2.6.1 to make Ceilometer Jenkins alive now.
[1] https://review.openstack.org/#/c/234372/
Related-Bug: #1505730
Change-Id: Ibb2a8c18651c601c844c3bc9d89f18ae032accf8
Depends-On: Id1e58a9db0d277de2f30de54db97040811f40ff2