c996aff28d
Up until now, the protobuf files were all located under `python/spdk/sma/proto`. This was fine, as they were only used in SMA and we only generated python code. However, now, we would also like to to output code for other (e.g. go) languages too, so it no longer make sense to keep them under `python`. Only the protobuf files will be stored under `proto`. The autogenerated python code will remain under `python`, while the go code will be put in the `go` directory. While here, simplified the Makefile by removing a function generating rules based on a directory, because we keep all protobuf files in the same location. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I4dcb7b33cd6f2930732f04dee62e35571b09315b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15016 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Mellanox Build Bot
36 lines
1.1 KiB
Protocol Buffer
36 lines
1.1 KiB
Protocol Buffer
syntax = "proto3";
|
|
|
|
package sma.nvmf;
|
|
|
|
option go_package = "spdk.io/sma/nvmf";
|
|
|
|
// Defines an address of an NVMeoF endpoint
|
|
message Address {
|
|
// Transport type ("rdma" or "tcp")
|
|
string trtype = 1;
|
|
// Transport address (IP)
|
|
string traddr = 2;
|
|
// Transport service identifier (port number)
|
|
string trsvcid = 3;
|
|
}
|
|
// NVMeoF connection using discovery service
|
|
message VolumeDiscoveryParameters {
|
|
// One or more discovery endpoints
|
|
repeated Address discovery_endpoints = 1;
|
|
}
|
|
|
|
// Describes connection parameters for an NVMeoF volume (namespace)
|
|
message VolumeConnectionParameters {
|
|
// Subsystem that the volume is exposed through. A volume with a given
|
|
// GUID/UUID won't be created if it's attached to a different subsystem. This
|
|
// field is optional and can be left empty.
|
|
string subnqn = 1;
|
|
// Host NQN to use when connecting to the subsystem exposing the volume (and,
|
|
// if using discovery, to the discovery subsystem too).
|
|
string hostnqn = 2;
|
|
oneof connection_params {
|
|
// Connection through discovery service
|
|
VolumeDiscoveryParameters discovery = 3;
|
|
}
|
|
}
|