HLD: Management interface for Sonic Config Management operations #33
Conversation
bhaveshdell
changed the title
bhaveshdell
changed the title
ujayakrishnan
requested review from
rajendra-dendukuri,
ben-gale,
dutta-partha and
anand-kumar-subramanian
| EXEC Level <br> | ||
| Write to file /etc/sonic/config_db.json <br> | ||
|
|
||
| 2. Copy configuration from file to running and reload. <br> |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
| EXEC Level <br> | ||
| Write to file /etc/sonic/config_db.json <br> | ||
|
|
||
| 2. Copy configuration from file to running and reload. <br> |
There was a problem hiding this comment.
When "config reload" is executed, all the containers are reloaded. Does it mean the sonic-mgmt-framework container is also reloaded. This may kill the "copy" session initiated. Ensure that even if the session is terminated, user gets some feedback and does not loose connectivity forever. Also care needs to be taken that the "config reload" session initiated on the host o/s finishes and is not interrupted because management-container is restarted.
There was a problem hiding this comment.
The session will terminate due to mgmt-framework restart. User is prompted for confirmation with the warning message about connectivity loss. The session has to be re-initiated by the user.
mgmt-framework is the last service to restart.
No description provided.