public interface NodeApi
NodeAsyncApi
Modifier and Type | Method and Description |
---|---|
Set<Node> |
add(Iterable<NodeRequest> nodes)
Create a new node with the configuration defined by the request.
|
Node |
get(int id) |
PagedIterable<Node> |
list() |
IterableWithMarker<Node> |
list(PaginationOptions options) |
void |
remove(int id)
Remove a node from the account.
|
void |
remove(Iterable<Integer> ids)
Batch-remove nodes from the account.
|
void |
update(int id,
NodeAttributes attrs)
Update the properties of a node.
|
Set<Node> add(Iterable<NodeRequest> nodes)
When a node is added, it is assigned a unique identifier that can be used for mutating operations such as changing the condition or removing it. Every load balancer is dual-homed on both the public Internet and ServiceNet; as a result, nodes can either be internal ServiceNet addresses or addresses on the public Internet.
nodes
- configurations to createHttpResponseException
- If the corresponding request cannot be fulfilled due to insufficient or invalid
datavoid update(int id, NodeAttributes attrs)
This operation asynchronously updates the attributes of the specified node. Upon successful validation of the request, the service will return a 202 (Accepted) response code. A caller can poll the load balancer with its ID to wait for the changes to be applied and the load balancer to return to an ACTIVE status.
id
- node to getattrs
- what to changeLoadBalancerAttributes.fromLoadBalancer(T)
PagedIterable<Node> list()
IterableWithMarker<Node> list(PaginationOptions options)
Node get(int id)
id
- node to getvoid remove(int id)
The remove load balancer function removes the specified load balancer and its associated configuration from the account. Any and all configuration data is immediately purged and is not recoverable.
id
- node to removevoid remove(Iterable<Integer> ids)
The current default limit is ten ids per request. Any and all configuration data is immediately purged and is not recoverable. By chance one of the items in the list cannot be removed due to its current status a 400:BadRequest is returned along with the ids of the ones the system identified as potential failures for this request
ids
- nodes to removeCopyright © 2009-2013 jclouds. All Rights Reserved.