Interface LbNodeUsageSummary
-
- All Superinterfaces:
LbNodeUsageSummaryTypes,com.vmware.vapi.bindings.Service
- All Known Implementing Classes:
LbNodeUsageSummaryStub
public interface LbNodeUsageSummary extends com.vmware.vapi.bindings.Service, LbNodeUsageSummaryTypes
-
-
Field Summary
-
Fields inherited from interface com.vmware.nsx_policy.infra.LbNodeUsageSummaryTypes
_VAPI_SERVICE_ID
-
-
Method Summary
All Methods Instance Methods Abstract Methods Deprecated Methods Modifier and Type Method Description AggregateLBNodeUsageSummaryget(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages)Deprecated.voidget(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages, com.vmware.vapi.bindings.client.AsyncCallback<AggregateLBNodeUsageSummary> asyncCallback)Deprecated.voidget(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages, com.vmware.vapi.bindings.client.AsyncCallback<AggregateLBNodeUsageSummary> asyncCallback, com.vmware.vapi.bindings.client.InvocationConfig invocationConfig)Deprecated.AggregateLBNodeUsageSummaryget(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages, com.vmware.vapi.bindings.client.InvocationConfig invocationConfig)Deprecated.
-
-
-
Method Detail
-
get
@Deprecated AggregateLBNodeUsageSummary get(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages)
Deprecated.The API is used to retrieve the load balancer node usage summary of all nodes for every enforcement point. - If the parameter ?include_usages=true exists, the property node_usages are included in response. By default, the property node_usages is not included in response. - If parameter ?enforcement_point_path=exists, only node usage summary from specific enforcement point is included in response. If no enforcement point path is specified, information will be aggregated from each enforcement point.
NSX-T Load Balancer is deprecated.
Please take advantage of NSX Advanced Load Balancer.
Refer to Policy > Networking > Network Services > Advanced Load Balancing section of the API guide.Synchronous method overload. Result of the invocation will be reported as a method return value.
- Parameters:
enforcementPointPath- enforcement point path (optional)includeUsages- Whether to include usages (optional)- Returns:
- com.vmware.nsx_policy.model.AggregateLBNodeUsageSummary
- Throws:
com.vmware.vapi.std.errors.InvalidRequest- Bad Request, Precondition Failedcom.vmware.vapi.std.errors.Unauthorized- Forbiddencom.vmware.vapi.std.errors.ServiceUnavailable- Service Unavailablecom.vmware.vapi.std.errors.InternalServerError- Internal Server Errorcom.vmware.vapi.std.errors.NotFound- Not Found
-
get
@Deprecated AggregateLBNodeUsageSummary get(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages, com.vmware.vapi.bindings.client.InvocationConfig invocationConfig)
Deprecated.The API is used to retrieve the load balancer node usage summary of all nodes for every enforcement point. - If the parameter ?include_usages=true exists, the property node_usages are included in response. By default, the property node_usages is not included in response. - If parameter ?enforcement_point_path=exists, only node usage summary from specific enforcement point is included in response. If no enforcement point path is specified, information will be aggregated from each enforcement point.
NSX-T Load Balancer is deprecated.
Please take advantage of NSX Advanced Load Balancer.
Refer to Policy > Networking > Network Services > Advanced Load Balancing section of the API guide.Synchronous method overload. Result of the invocation will be reported as a method return value. Use
invocationConfigto specify configuration for this particular invocation.- Parameters:
enforcementPointPath- enforcement point path (optional)includeUsages- Whether to include usages (optional)invocationConfig- Configuration for the method invocation.- Returns:
- com.vmware.nsx_policy.model.AggregateLBNodeUsageSummary
- Throws:
com.vmware.vapi.std.errors.InvalidRequest- Bad Request, Precondition Failedcom.vmware.vapi.std.errors.Unauthorized- Forbiddencom.vmware.vapi.std.errors.ServiceUnavailable- Service Unavailablecom.vmware.vapi.std.errors.InternalServerError- Internal Server Errorcom.vmware.vapi.std.errors.NotFound- Not Found
-
get
@Deprecated void get(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages, com.vmware.vapi.bindings.client.AsyncCallback<AggregateLBNodeUsageSummary> asyncCallback)Deprecated.The API is used to retrieve the load balancer node usage summary of all nodes for every enforcement point. - If the parameter ?include_usages=true exists, the property node_usages are included in response. By default, the property node_usages is not included in response. - If parameter ?enforcement_point_path=exists, only node usage summary from specific enforcement point is included in response. If no enforcement point path is specified, information will be aggregated from each enforcement point.
NSX-T Load Balancer is deprecated.
Please take advantage of NSX Advanced Load Balancer.
Refer to Policy > Networking > Network Services > Advanced Load Balancing section of the API guide.Asynchronous method overload. Result of the invocation will be reported via the specified
asyncCallback.Invocation Result:
com.vmware.nsx_policy.model.AggregateLBNodeUsageSummaryOperation Errors:
InvalidRequest- Bad Request, Precondition Failed
Unauthorized- Forbidden
ServiceUnavailable- Service Unavailable
InternalServerError- Internal Server Error
NotFound- Not Found
- Parameters:
enforcementPointPath- enforcement point path (optional)includeUsages- Whether to include usages (optional)asyncCallback- Receives the status (progress, result or error) of the operation invocation.
-
get
@Deprecated void get(java.lang.String enforcementPointPath, java.lang.Boolean includeUsages, com.vmware.vapi.bindings.client.AsyncCallback<AggregateLBNodeUsageSummary> asyncCallback, com.vmware.vapi.bindings.client.InvocationConfig invocationConfig)Deprecated.The API is used to retrieve the load balancer node usage summary of all nodes for every enforcement point. - If the parameter ?include_usages=true exists, the property node_usages are included in response. By default, the property node_usages is not included in response. - If parameter ?enforcement_point_path=exists, only node usage summary from specific enforcement point is included in response. If no enforcement point path is specified, information will be aggregated from each enforcement point.
NSX-T Load Balancer is deprecated.
Please take advantage of NSX Advanced Load Balancer.
Refer to Policy > Networking > Network Services > Advanced Load Balancing section of the API guide.Asynchronous method overload. Result of the invocation will be reported via the specified
asyncCallback. UseinvocationConfigto specify configuration for this particular invocation.Invocation Result:
com.vmware.nsx_policy.model.AggregateLBNodeUsageSummaryOperation Errors:
InvalidRequest- Bad Request, Precondition Failed
Unauthorized- Forbidden
ServiceUnavailable- Service Unavailable
InternalServerError- Internal Server Error
NotFound- Not Found
- Parameters:
enforcementPointPath- enforcement point path (optional)includeUsages- Whether to include usages (optional)asyncCallback- Receives the status (progress, result or error) of the operation invocation.invocationConfig- Configuration for the method invocation.
-
-