-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[hostcfgd] Delay hostcfgd and aaastatsd for faster boot time #7965
[hostcfgd] Delay hostcfgd and aaastatsd for faster boot time #7965
Conversation
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@jleveque could you please provide your feedback on this PR? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…allow 'hostcfgd' to start and configure tacas authorization. (#3741) - What is the motivation for this PR? After recent change introduced on this PR's: sonic-net/sonic-buildimage#7965 and sonic-net/sonic-buildimage#8117 'hostcfgd' will be delayed in 90 seconds. If the test will run before the daemon has started, it will fail the test. This is to align with the new change and make sure the test will pass. - How did you do it? Add a delay of 100 seconds before executing authorized commands. - How did you verify/test it? Run the test. Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@lguohan @qiluo-msft This PR is approved and all checkers passed, can we proceed and merge? |
This PR could not cleanly cherry-pick to 202012. Please submit another PR. |
@qiluo-msft there was already a PR for 202012 and it is merged. |
#### Why I did it hostcfgd is starting at the same time as 'create_switch' method is called on orchagent process. This introduce a degradation on the function execution time which eventually cause the fast-boot flow and a boot scenarion in general to run slower (~6 seconds). This change will delay the start time of this daemon. The aaastatsd will delay as well since it has a dependency on hostcfgd, so it is required to delay both. 90 seconds determined as the maximum allowed downtime for control plane to come back up on fast-boot flow. #### How I did it Add two timers for hostcfgd and aaastatsd services in order to delay the startup of these services. #### How to verify it Install an image with this change and observe the daemons start 90 seconds after the system boot.
…onic-net#7965)" This reverts commit 76d5223.
…ot time (sonic-net#7965)" (sonic-net#8705)" This reverts commit f4dea87.
…allow 'hostcfgd' to start and configure tacas authorization. (sonic-net#3741) - What is the motivation for this PR? After recent change introduced on this PR's: sonic-net/sonic-buildimage#7965 and sonic-net/sonic-buildimage#8117 'hostcfgd' will be delayed in 90 seconds. If the test will run before the daemon has started, it will fail the test. This is to align with the new change and make sure the test will pass. - How did you do it? Add a delay of 100 seconds before executing authorized commands. - How did you verify/test it? Run the test. Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
…e to hostcfgd delay on boot (sonic-net#3775) What is the motivation for this PR? After recent change introduced on this PR's: sonic-net/sonic-buildimage#7965 sonic-net/sonic-buildimage#8117 'hostcfgd' will be delayed in 90 seconds. If the test will run before the daemon has started, it will fail the test. This is to align with the new change and make sure the test will pass. Profiling the time it takes to configure tacacs after the daemon started can take time: main started -> Mon 12 Jul 2021 02:07:06 PM UTC 'tacacs_server_update' function finished -> Mon 12 Jul 2021 02:08:10 PM UTC Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
Signed-off-by: Shlomi Bitton shlomibi@nvidia.com
Why I did it
hostcfgd is starting at the same time as 'create_switch' method is called on orchagent process.
This introduce a degradation on the function execution time which eventually cause the fast-boot flow and a boot scenarion in general to run slower (~6 seconds).
This change will delay the start time of this daemon.
The aaastatsd will delay as well since it has a dependency on hostcfgd, so it is required to delay both.
90 seconds determined as the maximum allowed downtime for control plane to come back up on fast-boot flow.
How I did it
Add two timers for hostcfgd and aaastatsd services in order to delay the startup of these services.
How to verify it
Install an image with this change and observe the daemons start 90 seconds after the system boot.
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)