You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloud-init runs as four separate services at early runtime. This could be instrumented in our integration test suite to run cProfile within each service to make introspecting cloud-init runtime easier for developers. This can be done manually, by modifying cloud-init-local.service, cloud-init.service, cloud-config.service, and cloud-final.service, for example ExecStart=python3 -m cProfile -o cloud-init-local.prof /usr/bin/cloud-init init --local in the case of cloud-init-local.service
This could follow a similar approach to 9001f07, which modifies the service files to run cloud-init under the coverage python module (see tests/integration_tests/assets/enable_coverage.py in that commit).
The text was updated successfully, but these errors were encountered:
Enhancement
Cloud-init runs as four separate services at early runtime. This could be instrumented in our integration test suite to run cProfile within each service to make introspecting cloud-init runtime easier for developers. This can be done manually, by modifying
cloud-init-local.service
,cloud-init.service
,cloud-config.service
, andcloud-final.service
, for exampleExecStart=python3 -m cProfile -o cloud-init-local.prof /usr/bin/cloud-init init --local
in the case ofcloud-init-local.service
This could follow a similar approach to 9001f07, which modifies the service files to run cloud-init under the coverage python module (see
tests/integration_tests/assets/enable_coverage.py
in that commit).The text was updated successfully, but these errors were encountered: