VPP/API Concepts

API Conventions

The VPP binary API is a message passing API. It supports the following API method types.

Request/Reply

The client sends a request message and the server replies with a single reply message. The convention is that the reply message is named as method_name + _reply.

Dump/Detail

The client sends a "bulk" request message to the server, and the server replies with a set of detail messages. These messages may be of different type. A dump/detail call must be enclosed in a control ping block (Otherwise the client will not know the end of the bulk transmission). The method name must end with method + "_dump", the reply message should be named method + "_details". The exception here is for the methods that return multiple message types (e.g. sw_interface_dump). The Dump/Detail methods are typically used for acquiring bulk information, like the complete FIB table.

Events

The client can register for getting asynchronous notifications from the server. This is useful for getting interface state changes, periodic counters and so on. The method name for requesting notifications is conventionally prefixed with "want_". E.g. "want_interface"events". Which notification types results from an event registration is not defined in the API definition.

A message from a client must include the 'client_index', an opaque cookie identifying the sender, and a 'context' field to let the client match request with reply.

Naming

• Reply/Request method. Request: name Reply: name+_reply
• Dump/Detail method. Request: name+_dump Reply: name+_details
• Event registration: Request: want_+name Reply: want_+name+_reply

Types

The API supports any C type including compound data types. Conventionally the API is restricted to the basic C types (u8, u16, u32, u64, i8, i16, i32, i64). Currently strings are represented as u8[].

Type issues

• Both binary arrays and strings are represented as u8[]. For example u8 mac_address[6] and u8 build_directory[256]. Proposed solution create a separate type for strings.
• Type checking by language wrappers is difficult because explicit types aren't used. E.g. an IPv6 address is represented as u8 ip6_prefix[16].
• Variable length arrays don't include type as in u8 char[0] and the count field is message specific, making it hard to auto-generate code for these message types.
• Use of pointers to shared memory e.g. get_node_graph_reply.

Method issues

• Dump/Details do not have an explicit definition of which message types can be returned.
• Event methods do not have an explicit definition of which messages types can be returned.
• Dump/Details calls have no way of returning failure to the client.

Examples

A request/reply call is structured as follows:

define show_version {
   u32 client_index;
   u32 context;
};

define show_version_reply {
   u32 context;
   i32 retval;
   u8 program[32];
   u8 version[32];
   u8 build_date[32];
   u8 build_directory[256];
};

With the reply message having the API method name concatenated with the string "_reply".

A Dump/Details call is structured as follows:

define map_domain_dump {
  u32 client_index;
  u32 context;
};

define map_domain_details {
  u32 context;
  u32 domain_index;
  u8 ip6_prefix[16];
  u8 ip4_prefix[4];
  u8 ip6_src[16];
  u8 ip6_prefix_len;
  u8 ip4_prefix_len;
  u8 ip6_src_len;
  u8 ea_bits_len;
  u8 psid_offset;
  u8 psid_length;
  u8 flags;
  u16 mtu;
  u8 is_translation;
};

Proposed changes / Open questions

1. Make a common message header containing length, context and client_index
2. Remove manual_java tags(??)
3. Fix calls with unconventional structures (e.g. cli_request / cli_reply, vnet_get_summary_stats / vnet_summary_stats_reply, bridge_domain / bridge_domain_sw_if_details, l2_fib_table / l2_fib_table_entry, *netconf*)
4. Remove unused calls (is_address_reachable)
5. Use compound data types where possible
6. Define new syntax to explicitly list valid reply messages types for events and _dump calls
7. Replace pointers to shared memory by adding content to message