Project: mesos
Issue MESOS-3013: Extend ContainerInfo to include "NetworkInfo" message
As per the [design doc|https://docs.google.com/document/d/17mXtAmdAXcNBwp_JfrxmZcQrs7EO6ancSbejrqjLQ0g], we need to enable frameworks to specify network requirements. The proposed message could be along the lines of: {code} /** * Collection of network request. * TODO(kapil): Add a high-level explanation/motivation. */ message NetworkInfo { // Specify IPAddress requirement. enum Protocol { IPv4 = 0, IPv6 = 1 } // TODO: Document how to use this field to request an // 1) IPv4 address // 2) IPv6 address // 3) Any of the above optional Protocol protocol = 1; // Statically assigned IPs provided by the Framework. optional string ip_address = 2; // A group is the name given to a set of logically-related IPs that are // allowed to communicate within themselves. For example, one might want // to create separate groups for dev, testing, qa and prod deployment // environments. repeated string groups = 3; // To tag certain metadata to be used by Isolator/IPAM. E.g., rack, pop, etc. optional Labels labels = 4; }; message ContainerInfo { … repeated NetworkInfo network_infos; … }; message ContainerStatus { repeated NetworkInfo network_infos; } message TaskStatus { … // TODO: Comment on the fact that this is resolved during container setup. optional ContainerStatus container; … }; {code}
Story points: 2