Skip to content

Optimize rasctl to only send supported parameters when attaching a device #671

@uweseimet

Description

@uweseimet

Currently, in order to avoid a roundtrip, rasctl sends all potential device parameters to rascsi when attaching a new device. This does not cause issues because rascsi device ignore parameters they don't support.
Nevertheless, with more devices types with parameter support always sending everything is not that nice.

In order to send only the parameters supported by a device (which is a cleaner approach), when attaching a device rasctl would have to retrieve the list of supported parameters from the rascsi process first, using the existing functionality of the protobuf interface. This means, in order to attach a device two remote interface calls would be required.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions