Skip to content

Conversation

@brianneville
Copy link
Contributor

add RPC to allow network operator to
perform decommission of the device.

add RPC to allow network operator to
perform decommission of the device.
@coveralls
Copy link

coveralls commented Aug 27, 2025

Pull Request Test Coverage Report for Build 17272350828

Details

  • 0 of 90 (0.0%) changed or added relevant lines in 2 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage remained the same at 0.0%

Changes Missing Coverage Covered Lines Changed/Added Lines %
factory_reset/factory_reset_grpc.pb.go 0 27 0.0%
factory_reset/factory_reset.pb.go 0 63 0.0%
Files with Coverage Reduction New Missed Lines %
factory_reset/factory_reset_grpc.pb.go 1 0.0%
Totals Coverage Status
Change from base Build 17258669512: 0.0%
Covered Lines: 0
Relevant Lines: 12518

💛 - Coveralls

// To facilitate a response being returned to the caller, the reboot
// component of this RPC is asynchronous and will run after the RPC
// has returned a DecommissionResponse.
rpc Decommission(DecommissionRequest) returns (DecommissionResponse);
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not understanding the use case here
does this imply the device will actually no longer try to secure boot as well?
I am not seeing how this significantly different than just the Start with at most a new parameter?

Does this API actually have a different "caller" set which would make it at least a different auth requirement?

Copy link
Member

Choose a reason for hiding this comment

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

why not augment the Start RPC instead?

message DecommissionRequest{
// Time (in nanoseconds) that the Target should
// wait before issuing the reboot to complete the decommission.
// If unset, the Target will assume a default of 15000000000 (15 seconds)
Copy link

Choose a reason for hiding this comment

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

How the delay is calculated?

  • from the time the target has received a request (which implies that the entire operation takes <=15 seconds by default), or
  • from the time the target completed prep. steps and is ready to undergo a reboot?

If it's the former, I'd suggest removing the fixed default value, since the procedure can require more than 15 seconds of execution on the target device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants