CPC H04L 61/50 (2022.05) [G06F 9/45558 (2013.01); G06F 9/5083 (2013.01); G06F 9/54 (2013.01); G06F 9/547 (2013.01); H04L 12/4641 (2013.01); H04L 12/66 (2013.01); H04L 41/0893 (2013.01); H04L 41/18 (2013.01); H04L 41/5048 (2013.01); H04L 41/5077 (2013.01); H04L 45/42 (2013.01); H04L 45/586 (2013.01); H04L 49/70 (2013.01); H04L 61/103 (2013.01); H04L 63/0209 (2013.01); H04L 63/0218 (2013.01); H04L 63/0263 (2013.01); H04L 63/0272 (2013.01); H04L 63/20 (2013.01); H04L 67/10 (2013.01); H04L 67/1001 (2022.05); G06F 9/5077 (2013.01); G06F 2009/4557 (2013.01); G06F 2009/45562 (2013.01); G06F 2009/45595 (2013.01)] | 14 Claims |
1. A method of deploying a group of machines in a datacenter, the method comprising:
receiving a Custom Resource Definition (CRD) that defines an endpoint group of machines as a custom-specified resource in the datacenter, the endpoint group of machines serving as source machines or destination machines for data message flows passing through a network of the datacenter;
receiving an intent-based API (Application Programming Interface) request that refers to the CRD and defines a set of one or more attributes of a plurality of machines that are members of the endpoint group of machines;
performing an automated process to parse the intent-based API request and process the CRD to define the plurality of machines as members of the endpoint group;
using an identifier of the endpoint group to specify a middlebox service policy; and
distributing the middlebox service policy to a set of one or more middlebox services that apply the policy to at least a subset of the data message flows passing through the datacenter network.
|