Skip to content
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

Add a clarification of containerz behaviour after reboot/failover #3472

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,13 @@

Verify the correct behaviour of `gNOI.Containerz` when operating containers.

### Restart Behaviour
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest rephrasing this as a test procedure and moving into it's own subtest (for example, as CNTR-1.5 below)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, this seems a good way to cover it. We probably want a test that verifies this. We can do a reboot + a triggered switchover (using gNOI) to validate these things.


Containers running on the system are expected to be present and running after
a device reboot. Similarly, on a dual RP device it is expected that running
containers are also present and running on the backup RP or after a failover
to the backup.

## Procedure

This step only applies if the reference implementation of containerz is being
Expand Down
Loading