vyos-cloud-init.git/doc/rtd/topics/debugging.rst, branch rolling

Remove 3.5 and xenial support (SC-711) (#1167)

2022-01-10T22:56:29+00:00

Includes: - Update tox.ini and .travis.yml accordingly - Cleanup tox.ini with new tox syntax and cloud-init dependencies - Update documentation accordingly - Replace/remove xenial references where additional testing isn't required - Remove xenial checks in integration tests - Replace yield_fixture with fixture in pytest tests Sections of code commented with lines like "Remove when Xenial is no longer supported" still exist as they're require additional testing.

Docs: Replace all freenode references with libera (#912)

2021-05-27T15:07:51+00:00

doc: move testing section from HACKING to its own doc (#739)

2020-12-18T20:06:58+00:00

Our HACKING doc is very long, making it hard to justify expanding or restructuring its content too much. This moves the testing section to its own doc, and adds section headers in to make finding/linking to testing guidelines easier. To avoid confusion, the title of debugging.rst is changed.

docs: add proposed SRU testing procedure (#167)

2020-01-16T22:36:37+00:00

Co-Authored-By: Daniel Watkins

docs: fix whitespace, spelling, and line length

2019-09-04T13:43:11+00:00

Cloud-init analyze module: Added ability to analyze boot events.

2019-07-15T21:50:33+00:00

This branch introduces a new command line feature for cloud-init. Currently, the cloud-init module has the capability to analyze events in cloud-init.log in three ways: 'show', 'blame', 'dump'. These changes add a fourth capability, called 'boot'. Running the command 'cloud-init analyze boot' will provide the user three timestamps. 1) Timestamp for when the kernel starts initializing. 2) Timestamp for when the kernel finishes its initialization. 3) Timestamp for when systemd activates cloud-init. This feature enables cloud-init users to analyze different boot phases. This would aid in debugging performance issues related to cloud-init startup or tracking regression.

docs: Fix example cloud-init analyze command to match output.

2018-08-07T14:35:29+00:00

Fix a typo in in documentation that showed 'analyze blame' but intended to show 'analyze dump'.

doc: fix all warnings issued by 'tox -e doc'

2018-03-15T17:32:09+00:00

Building doc would issue some warnings. This fixes all the warnings, and changes the "code blocks" that were listed as 'bash' to instead be 'shell-session'.

docs: Update RTD content for cloud-init subcommands.

2018-01-29T20:04:37+00:00

Give a bit more detailed information which others can quickly reference to discover new CLI subcommand functionality. This section was a bit stale as we've introduced cloud-init status, clean and analyze content that was a bit under represented. Since we've had a few request of externals who try to run cloud-init subcommands on the commandline instead of rebooting, it's probably worth a bit of content here to describe how those init and module subcommands work.

tools: Add tooling for basic cloud-init performance analysis.

2017-08-21T19:46:23+00:00

This branch adds cloudinit-analyze into cloud-init proper. It adds an "analyze" subcommand to the cloud-init command line utility for quick performance assessment of cloud-init stages and events. On a cloud-init configured instance, running "cloud-init analyze blame" will now report which cloud-init events cost the most wall time. This allows for quick assessment of the most costly stages of cloud-init. This functionality is pulled from Ryan Harper's analyze work. The cloudinit-analyze main script itself has been refactored a bit for inclusion as a subcommand of cloud-init CLI. There will be a followup branch at some point which will optionally instrument detailed strace profiling, but that approach needs a bit more discussion first. This branch also adds: * additional debugging topic to the sphinx-generated docs describing cloud-init analyze, dump and show as well as cloud-init single usage. * Updates the Makefile unittests target to include cloudinit directory because we now have unittests within that package. LP: #1709761