The ceilometer.hacking.checks Module¶

Guidelines for writing new hacking checks

• Use only for Ceilometer specific tests. OpenStack general tests should be submitted to the common ‘hacking’ module.
• Pick numbers in the range X3xx. Find the current test with the highest allocated number and then pick the next value.
• Keep the test method code in the source file ordered based on the C3xx value.
• List the new rule in the top level HACKING.rst file

ceilometer.hacking.checks.factory(register)[source]¶

ceilometer.hacking.checks.no_log_warn(logical_line)[source]¶

Disallow ‘LOG.warn(‘

https://bugs.launchpad.net/tempest/+bug/1508442

C301

ceilometer.hacking.checks.no_os_popen(logical_line)[source]¶

Disallow ‘os.popen(‘

Deprecated library function os.popen() Replace it using subprocess https://bugs.launchpad.net/tempest/+bug/1529836

C302