Design and implement IPAM grpc service for vL3 cases about api HOT 9 CLOSED

@denis-tingaikin How are renewals handled? How are expirations handled?

I'll provide a diagram of the interaction as soon as we get API consent.

from api.

@denis-tingaikin Why is the NSC getting a /30 instead of a /32?

from api.

@denis-tingaikin Do we need to tie this to IPContext, or could it simply deal in prefixes?

from api.

@denis-tingaikin How are renewals handled? How are expirations handled?

from api.

@denis-tingaikin Do we need to tie this to IPContext, or could it simply deal in prefixes?

Yes, I thought about this, so we also can go with

message IPAMServiceRequest {
   repeat string exclude_prefixes= 1;
}
message IPAMPrefix {
   string cidr = 1;
}
service IPAMService  {
   rpc Allocate (IPAMServiceRequest) returns (IPAMPrefix);
   rpc Free(IPAMPrefix) returns (google.protobuf.Empty);
}

from api.

@denis-tingaikin Why is the NSC getting a /30 instead of a /32?

Thanks! Fixed.

from api.

@denis-tingaikin Would it make sense to reflect the /32 assigned to the loopback interface for the VRF on VPP?

from api.

Finally we with @edwarnicke decided internally the next proto service

enum RequestType {
  UNDEFINED = 0;
  ALLOCATE = 1;
  DELETE = 2;
}

message IPAMRequest {
  RequestType type = 1;
  string prefix = 2;
  repeated string exclude_prefixes =3;
}

service IPAMService  {
  rpc Request (IPAMRequest) returns (stream IPAMRequest);
}

I've started to check corner cases for this service in the diagram of the interaction.

from api.

Completed by #128

from api.