Resource Manager API Guide (4.2.12)

Description of the APIs exposed by the Resource Manager package.

---

About this Guide

This NSO Resource Manager (RM) API Guide describes the APIs exposed by the Resource Manager package that you can use to allocate IPs from the IP resource pool and to allocate the IDs from ID resource pools.

Intended Audience

This guide is intended for Cisco advanced services developers, network engineers, and system engineers to install the RM package inside NSO and then utilize the APIs exposed by the RM package to allocate and manage IP subnets and IDs as required by other CFPs installed alongside this RM package inside NSO.

Additional Documentation

This documentation requires the reader to have a good understanding of NSO and its usage as described in the following NSO documentation:

• NSO Installation

• NSO Operation and Usage Guide

---

Resource Manager IP/ID Allocation APIs

The APIs exposed by the Resource Manager package are used to allocate IP subnets and IDs from the IP and ID resource pools respectively by the applications requesting the resources. The APIs help to allocate, update, or deallocate the resources. You can make API calls to the resource pools as long as the pool is not exhausted of the resources. If the pool is exhausted of resources or if the referenced pool does not exist in the database when there is a request, the allocation raises an exception. The APIs also support allocating Odd or Even IDs from the resource pools, provided the pool has available resources.

When a service makes multiple resource allocations from a single pool, the optional ‘name’ parameter allows the service to distinguish the different allocations. By default, the parameter value is an empty string.

Resource allocation can be synchronous or asynchronous.

The synchronized allocation API request uses Reactive FastMap to allocate resources while ensuring the interface appears synchronous. This means that as you create an allocation request from northbound, you can see the allocation results, such as the requested IP subnet or ID in the same transaction. If a northbound is making an allocation request and, in the same transaction, a configuration is being applied to a specific device, the commit dry-run receives the request response which is processed by the Resource Manager. The configurations are then pushed to the device in the same transaction. Thus, the northbound user can see the get-modifications in the commit dry-run.

During a resource request, the resource is allocated and stored in the create callback. This allocation is visible to other services that are run in the same or subsequent transactions and therefore avoids the recreation of resource when the service is redeployed. Synchronous allocation does not require service re-deploy to read allocation. The same transaction can read allocation. Commit dry-run or get-modification displays the allocation details as output.

Example

The following is an example for a Northbound service callback passed with required API parameters for both synchronous and asynchronous IPv4 allocations. The example uses pool-example package as a reference. The request describes the details it uses, such as the pool, device. Each allocation has an allocation ID. In the following example, the allocating service pulls one IPv4 address from the IPv4 resource pool. The requesting service then uses this allocated IP address to set the interface address on the device southbound to NSO.

Northbound Service Callback Example: Sync

Northbound Service Callback Example - Sync

class AllocateCallbacks(Service):
    @Service.create
    def cb_create(self, tctx, root, service, proplist):
        self.log.info('AllocateCallbacks create(service=', service._path, ')')
        self.log.info('requested allocation {} from {}'.format(service.device, service.pool))
        
        service_xpath = (
            "/allocating-service-async:allocating-service-async[name='{}']"
        )
        
        propslist = ip_allocator.net_request(
            service,
            service_xpath.format(service.name),
            "admin",
            service.pool,
            service.ipv4,
            service.subnet_size,
            False,
            "default",
            True,
            proplist,
            self.log
        )
        
        # Check
        net = ip_allocator.net_read("admin", root, service.pool, service.ipv4)
        self.log.info('Check n/w create(IP=', net, ')')
        
        if net:
            self.log.info(
                'received device {} ip-address value from {} is ready'.format(
                    service.device, service.pool
                )
            )
            
            template = ncs.template.Template(service)
            vars = ncs.template.Variables()
            vars.add("SERVICE", str(service.ipv4))
            vars.add("DEVICE_NAME", str(service.device))
            vars.add("IP", str(net))
            
            template.apply('device', vars)
        
        return propslist

Northbound Service Callback Example: Async

Northbound Service Callback Example - Async

class AllocateCallbacksAsync(Service):
    @Service.create
    def cb_create(self, tctx, root, service, proplist):
        self.log.info('AllocateCallbacksAsync create(service=', service._path,
        ')')
        self.log.info('requested allocation {} from {}'.format(service.device,
        service.pool))
        async[name='{}']")
        service_xpath = ("/allocating-service-async:allocating-service-
        ip_allocator.net_request(service,
        service_xpath.format(service.name),
        tctx.username,
        service.pool,
        service.ipv4,
        service.subnet_size)
        # Check
        net=ip_allocator.net_read(tctx.username, root, service.pool,
        service.ipv4)
        self.log.info('Check n/w create(IP=', net, ')')
        if net:
            self.log.info('received device {} ip-address value from {} is
            ready'.format(service.device, service.pool))
            template = ncs.template.Template(service)
            vars = ncs.template.Variables()
            vars.add("SERVICE", str(service.ipv4))
            vars.add("DEVICE_NAME", str(service.device))
            vars.add("IP", str(net))
            template.apply('device', vars

The payloads below demonstrate the Northbound service allocation request using the Resource Manager synchronous and asynchronous flows. The API pulls one IP address from the IPv4 resource pool and sets the returned IP address on the interface IOS1 device. The payloads demonstrate both synchronous and asynchronous flows.

Synchronous Flow

Synchronous Flow

admin@ncs% load merge alloc-sync.xml
[ok]
admin@ncs% commit dry-run
cli {
    local-node {
        data devices {
            device ios1 {
                config {
                    ip {
                        prefix-list {
                            + prefixes sample {
                                + permit 11.1.0.0/32;
                            + }
                            + prefixes sample1 {
                                + permit 11.1.0.1/32;
                            + }
                            + prefixes sample3 {
                                + permit 11.1.0.2/32;
                            + }
                            + prefixes sample4 {
                                + permit 11.1.0.3/32;
                            + }
                        }
                    }
                }
            }
        }
        +allocating-service sync-test-1 {
            + device ios1;
            + pool IPv4;
            + subnet-size 32;
            + ipv4 sample;
        +}
        +allocating-service sync-test-2 {
            + device ios1;
            + pool IPv4;
            + subnet-size 32;
            + ipv4 sample1;
        +}
        +allocating-service sync-test-3 {
            + device ios1;
            + pool IPv4;
            + subnet-size 32;
            + ipv4 sample3;
        +}
        +allocating-service sync-test-4 {
            + device ios1;
            + pool IPv4;
            + subnet-size 32;
            + ipv4 sample4;
        +}
    }
}

Asynchronous Flow

Asynchronous Flow

admin@ncs% load merge alloc-async.xml
[ok]
admin@ncs% commit dry-run
cli {
    local-node {
        data resource-pools {
            + ip-address-pool IPv4 {
                + allocation sample {
                    + username admin;
                    + allocating-service /allocating-service-
                      async[name='async-test'];
                    + redeploy-type default;
                    + request {
                        + subnet-size 32;
                    + }
                + }
            + }
        }
        + allocating-service-async async-test {
            + device ios1;
            + pool IPv4;
            + subnet-size 32;
            + ipv4 sample;
        + }
    }
}

IPv4 and IPv6 have separate IP pool types; there is no mixed IP pool. You can specify a prefixlen parameter for IP pools to allocate a net of a given size. The default value is the maximum prefix length of 32 and 128 for IPv4 and IPv6, respectively.

The following APIs are used in IPv4 and IPv6 allocations.

IP Allocations

Resource Manager exposes the API calls to request IPv4 and IPv6 subnet allocations from the resource pool. These requests can be synchronous or asynchronous. This topic discusses the APIs for these flows.

The NSO Resource Manager interface and the resource allocator provide a generic resource allocation mechanism that works well with services. Each pool has an allocation list where services are expected to create instances to signal that they request an allocation. The request parameters are stored in the request container, and the allocation response is written in the response container.

The APIs exposed by RM are implemented in Python as well as Java, so the NB user can configure the service to be a Java package or a Python package and call the allocator API as per the implementation. The NB user can also use NSO CLI to make an allocation request to the IP allocator RM package.

The IP resource pool supports two types of allocation methods, namely firstfree and sequential. You can specify the allocation method by setting the parameter allocation-method for an IP pool. The default allocation method is firstfree (legacy allocation method), where a released IP subnet can be reused immediately, while in the sequential allocation method, the released subnets are stored separately in a available-secondary set. When an allocation request is made and the requested subnet is not present in the available set, the subnets can be allocated from the available-secondary set.

By default, the available-secondary set is hidden and user must run the command unhide debug to view the details of the available-secondary set of an IP pool.

Using Java APIs for IP Allocations

This section covers the Java APIs exposed by the RM package to the NB user to make IP subnet allocation requests.

Creating Asynchronous IP Subnet Allocation Requests

The asynchronous subnet allocation requests can be created for a requesting service with:

• The redeploy type set to default type or set to redeployType.

• The CIDR mask length can be set to invert the subnet mask length for Boolean

  operations with IP addresses or set not to be able to invert the subnet mask length.

• Pass the starting IP address of the subnet to the requesting service redeploy type

  (default/redeployType).

The following are the Java APIs for asynchronous IP allocation requests.

Default Asynchronous Request

The requesting service redeploy type is default, and CIDR mask length cannot be inverted for the subnet allocation request. Make sure the NavuNode service is the same node you get in service create. This ensures the back pointers are updated correctly and RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        String poolName,
        String username,
        int cidrmask,
        String id)

API Parameters

| Parameter   | Type       | Description                                                     |
|-------------|------------|-----------------------------------------------------------------|
| service     | NavuNode   | NavuNode referencing the requesting service node.               |
| poolName    | String     | Name of the resource pool to request the subnet IP address from.|
| Username    | String     | Name of the user to use when redeploying the requesting service.|
| cidrmask    | Int        | CIDR mask length of the requested subnet.                       |
| id          | String     | Unique allocation ID.                                           |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, poolName, userName, cidrMask,
id);

Asynchronous Request with Invert CIDR Flag

The requesting service redeploy type is default, and the CIDR mask length can be inverted for the subnet allocation request. Make sure the NavuNode service is the same node you get in service create. This ensures the back pointers are updated correctly and RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        String poolName,
        String username,
        int cidrmask,
        String id,
        boolean invertCidr)

API Parameters

| Parameter        | Type       | Description                                                        |
|------------------|------------|--------------------------------------------------------------------|
| Service          | NavuNode   | NavuNode referencing the requesting service node.                  |
| poolName         | String     | Name of the resource pool to request the subnet IP address from.   |
| Username         | String     | Name of the user to use when redeploying the requesting service.   |
| cidrmask         | Int        | CIDR mask length of requested subnet.                              |
| id               | String     | Unique allocation ID.                                              |
| invertCidr       | Boolean    | If boolean value is true, the subnet mask length is inverted.      |

Common Example for the Usage of subnetRequest from Service

The code example below shows that the ⁣subnetRequest method can be called from the service by different types parameter values getting from the service object.

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, poolName, userName, cidrMask,
id, invertCidr.booleanValue());

@ServiceCallback(servicePoint = "ipaddress-allocator-test-servicepoint",
    callType = ServiceCBType.CREATE)
public Properties create(ServiceContext context,
                         NavuNode service,
                         NavuNode ncsRoot,
                         Properties opaque)
        throws DpCallbackException {
    LOGGER.info("IPAddressAllocatorTest Servicepoint is triggered");
    try {
        String servicePath = service.getKeyPath();

        CdbSession sess = cdb.startSession(CdbDBType.CDB_OPERATIONAL);
        try {
            String dPath = servicePath + "/deploys";
            int deploys = 1;

            if (sess.exists(dPath)) {
                deploys = (int) ((ConfUInt32) sess.getElem(dPath)).longValue();
            }

            if (sess.exists(servicePath)) { // Will not exist the first time
                sess.setElem(new ConfUInt32(deploys + 1), dPath);
            }

            NavuLeaf size = service.leaf("subnet-size");
            if (!size.exists()) {
                return opaque;
            }

            int subnetSize = (int) ((ConfUInt8) service.leaf("subnet-size").value()).longValue();
            String redeployOption = null;

            if (sess.exists(servicePath + "/redeploy-option")) {
                redeployOption = ConfValue.getStringByValue(
                        servicePath + "/redeploy-option",
                        service.leaf("redeploy-option").value()
                );
            }

            System.out.println("IPAddressAllocatorTest redeployOption: " + redeployOption);

            if (redeployOption == null) {
                IPAddressAllocator.subnetRequest(service, "mypool", "admin", subnetSize, "test");
            } else {
                RedeployType redeployType = RedeployType.from(redeployOption);
                System.out.println("IPAddressAllocatorTest redeployType: " + redeployType);

                IPAddressAllocator.subnetRequest(
                        service, redeployType, "mypool", "admin", subnetSize, "test", false
                );
            }

            boolean error = false;
            boolean allocated = sess.exists(servicePath + "/allocated");
            boolean ready = IPAddressAllocator.responseReady(service.context(), cdb, "mypool", "test");

            if (ready) {
                try {
                    IPAddressAllocator.fromRead(cdb, "mypool", "test");
                } catch (ResourceErrorException e) {
                    LOGGER.info("The allocation has failed");
                    error = true;
                }
            }

            if (ready && !error) {
                if (!allocated) {
                    sess.create(servicePath + "/allocated");
                }
            } else {
                if (allocated) {
                    sess.delete(servicePath + "/allocated");
                }
            }
        } finally {
            sess.endSession();
        }
    } catch (Exception e) {
        throw new DpCallbackException("Cannot create service", e);
    }
    return opaque;
}

Asynchronous Request with Invert CIDR Flag and Redeploy Type

The requesting service redeploy type is redeployType and CIDR mask length can be inverted for the subnet allocation request. Make sure the NavuNode service is the same node you get in service create. This ensures the back pointers are updated correctly and RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        RedeployType redeployType,
        String poolName,
        service node
        String username,
        int cidrmask,
        subnet IP address from
        String id,
        boolean invertCidr)

API Parameters

| Parameter    | Type        | Description                                                       |
|--------------|-------------|-------------------------------------------------------------------|
| service      | NavuNode    | NavuNode referencing the requesting service node.                 |
| poolName     | String      | Name of the resource pool to request the subnet IP address from.  |
| username     | String      | Name of the user to use when redeploying the requesting service.  |
| cidrmask     | Int         | CIDR mask length of the requested subnet.                         |
| id           | String      | Unique allocation ID.                                             |
| invertCidr   | Boolean     | If boolean value is true, the subnet mask length is inverted.     |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, redeployType, poolName,
userName, cidrMask, id, invertCidr.booleanValue());

Asynchronous Request with Specific Start IP Address

Pass a startIP value to the default type of the requesting service redeploy. The subnet IP address begins with the provided IP address. Make sure that the NavuNode service is the same node you get in service create. This ensures that the back pointers are updated correctly and that the RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr)

API Parameters

| Parameter     | Type        | Description                                                        |
|---------------|-------------|--------------------------------------------------------------------|
| service       | NavuNode    | NavuNode referencing the requesting service node.                  |
| poolName      | String      | Name of the resource pool to request the subnet IP address from.   |
| username      | String      | Name of the user to use when redeploying the requesting service.   |
| startIP       | String      | Starting IP address for the requested subnet.                      |
| cidrmask      | Int         | CIDR mask length of the requested subnet.                          |
| id            | String      | Unique allocation ID.                                              |
| invertCidr    | Boolean     | If boolean value is true, the subnet mask length is inverted.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, poolName, userName, startIp,
cidrMask, id, invertCidr.booleanValue());

Asynchronous Request with Specific Start IP Address and Re-deploy Type

Pass a startIP value to the redeployType of the requesting service redeploy. The subnet IP address begins with the provided IP address. Make sure that the NavuNode service is the same node you get in service create. This ensures that the back pointers are updated correctly and that the RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        RedeployType redeployType,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr)

API Parameters

| Parameter   | Type       | Description                                                       |
|-------------|------------|-------------------------------------------------------------------|
| service     | NavuNode   | NavuNode referencing the requesting service node.                 |
| poolName    | String     | Name of the resource pool to request the subnet IP address from.  |
| username    | string     | Name of the user to use when redeploying the requesting service.  |
| startIP     | String     | Starting IP address for the requested subnet.                     |
| cidrmask    | Int        | CIDR mask length of the requested subnet.                         |
| id          | String     | Unique allocation ID.                                             |
| invertCidr  | Boolean    | If boolean value is true, the subnet mask length is inverted.     |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, redeployType, poolName,
userName, startIp, cidrMask, id, invertCidr.booleanValue());

Asynchronous Request with Service Context

Create an asynchronous IP subnet allocation request with requesting service redeploy type as default and CIDR mask length cannot be inverted for the subnet allocation request. Make sure to use the service context you get in the service create callback. This method takes any NavuNode, should you need it.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        String poolName,
        String username,
        int cidrmask,
        String id)

API Parameters

| Parameter   | Type       | Description                                                      |
|-------------|------------|------------------------------------------------------------------|
| service     | NavuNode   | NavuNode referencing the requesting service node.                |
| poolName    | String     | Name of the resource pool to request the subnet IP address from. |
| username    | string     | Name of the user to use when redeploying the requesting service. |
| cidrmask    | Int        | CIDR mask length of the requested subnet.                        |
| id          | String     | Unique allocation ID.                                            |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, poolName, userName,
cidrMask, id);

Asynchronous Request with Context and Re-deploy Type

Create an asynchronous IP subnet allocation request with requesting service redeploy type as redeployType and CIDR mask length can be inverted for the subnet allocation request. Make sure to use the service context you get in the service create callback. This method takes any NavuNode, should you need it.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        RedeployType redeployType,
        String poolName,
        String username,
        int cidrmask,
        String id,
        boolean invertCidr)

API Parameters

| Parameter   | Type           | Description                                                                   |
|-------------|----------------|-------------------------------------------------------------------------------|
| Context     | ServiceContext | ServiceContext referencing the requesting context the service was invoked in. |
| service     | NavuNode       | NavuNode referencing the requesting service node.                             |
| poolName    | String         | Name of the resource pool to request the subnet IP address from.              |
| username    | String         | Name of the user to use when redeploying the requesting service.              |
| cidrmask    | Int            | CIDR mask length of the requested subnet.                                     |
| id          | String         | Unique allocation ID.                                                         |
| invertCidr  | Boolean        | If the boolean value is true, the subnet mask length is inverted.             |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, redeployType,
poolName, userName, cidrMask, id, invertCidr.booleanValue());

Asynchronous Request with Context and Specific Start IP

Pass a startIP value to the requesting service redeploy type, default. The subnet IP address begins with the provided IP address. CIDR mask length cannot be inverted for the subnet allocation request. Make sure to use the service context you get in the service create callback.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr)

API Parameters

| Parameter   | Type           | Description                                                                   |
|-------------|----------------|-------------------------------------------------------------------------------|
| Context     | ServiceContext | ServiceContext referencing the requesting context the service was invoked in. |
| service     | NavuNode       | NavuNode referencing the requesting service node.                             |
| poolName    | String         | Name of the resource pool to request the subnet IP address from.              |
| username    | String         | Name of the user to use when redeploying the requesting service.              |
| startIP     | String         | Starting IP address for the requested subnet.                                 |
| cidrmask    | Int            | CIDR mask length of the requested subnet.                                     |
| id          | String         | Unique allocation ID.                                                         |
| invertCidr  | Boolean        | If boolean value is true, the subnet mask length is inverted.                 |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, poolName, userName,
startIp, cidrMask, id, invertCidr.booleanValue());

Asynchronous Request with Specific Start IP, Context, Invert CIDR and Re-deploy Type

Pass a startIP value to the requesting service redeploy type, redeployType. The subnet IP address begins with the provided IP address. CIDR mask length can be inverted for the subnet allocation request. Make sure to use the service context you get in the service create callback.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        RedeployType redeployType,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr)

API Parameters

| Parameter   | Type           | Description                                                                   |
|-------------|----------------|-------------------------------------------------------------------------------|
| Context     | ServiceContext | ServiceContext referencing the requesting context the service was invoked in. |
| service     | NavuNode       | NavuNode referencing the requesting service node.                             |
| poolName    | String         | Name of the resource pool to request the subnet IP address from.              |
| username    | String         | Name of the user to use when redeploying the requesting service.              |
| startIP     | String         | Starting IP address for the requested subnet.                                 |
| cidrmask    | Int            | CIDR mask length of the requested subnet.                                     |
| id          | String         | Unique allocation ID.                                                         |
| invertCidr  | Boolean        | If boolean value is true, the subnet mask length is inverted.                 |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, redeployType,
poolName, userName, startIp, cidrMask, id, invertCidr.booleanValue());

Common Exceptions Raised by Java APIs for Allocation Not Successful

• The API throws the following exception error if the requested resource pool does not exist: ResourceErrorException

• The API throws the following exception error if the requested resource pool is exhausted: AddressPoolException

• The API throws the following exception error if the requested netmask is invalid: InvalidNetmaskException

Creating Synchronous or Asynchronous IP Subnet Allocation Requests

• Note that the sync parameter used to specify synchronous or asynchronous mode has been renamed to sync-alloc.

The sync_alloc parameter in the API determines if the allocation request is for a synchronous or asynchronous mode. Set the sync_alloc parameter to true for synchronous flow.

The subnet allocation requests can be created for a requesting service with:

• The redeploy type set to default type or redeployType type.

• The CIDR mask length can be set to invert the subnet mask length for Boolean operations with IP addresses or set to not be able to invert the subnet mask length.

• Pass the starting IP address of the subnet to the requesting service redeploy type (default/redeploytype).

The following are the Java APIs for synchronous or asynchronous IP allocation requests.

Default Java API for IP Subnet Allocation Request

The requesting service redeploy type is default and CIDR mask length can be inverted for the subnet allocation request. Set sync_alloc to true to make a synchronous allocation request with commit dry-run support. Make sure the NavuNode service is the same node you get in service create. This ensures the back pointers are updated correctly and RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        String poolName,
        String username,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameters

| Parameter    | Type     | Description                                                       |
|--------------|----------|-------------------------------------------------------------------|
| service      | NavuNode | NavuNode referencing the requesting service node.                 |
| poolName     | String   | Name of the resource pool to request the subnet IP address from.  |
| username     | String   | Name of the user to use when redeploying the requesting service.  |
| cidrmask     | Int      | CIDR mask length of the requested subnet.                         |
| id           | String   | Unique allocation ID.                                             |
| invertCidr   | Boolean  | Set value to true to invert the subnet mask length.               |
| sync_alloc   | Boolean  | Set value to true to make a synchronous allocation request.       |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, poolName, userName, cidrMask,
id, invertCidr.booleanValue(), testSync.booleanValue());

Java API for IP Subnet Allocation Request with Redeploy Type

The requesting service redeploy type is redeployType and CIDR mask length can be inverted for the subnet allocation request. Set sync_alloc to true to make a synchronous allocation request with commit dry-run support. Make sure the NavuNode service is the same node you get in service create. This ensures the back pointers are updated correctly and RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service, 
        RedeployType redeployType, 
        String poolName,
        String username,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameters

| Parameter   | Type     | Description                                                        |
|-------------|----------|--------------------------------------------------------------------|
| service     | NavuNode | NavuNode referencing the requesting service node.                  |
| poolName    | String   | Name of the resource pool to request the subnet IP address from.   |
| username    | String   | Name of the user to use when redeploying the requesting service.   |
| cidrmask    | Int      | CIDR mask length of the requested subnet.                          |
| id          | String   | Unique allocation ID.                                              |
| invertCidr  | Boolean  | Set value to true to invert the subnet mask length.                |
| sync_alloc  | Boolean  | Set value to true to make a synchronous allocation request.        |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, redeployType, poolName,
userName, cidrMask, id, invertCidr.booleanValue(),
testSync.booleanValue());

Java API for IP Subnet Allocation Request with Start IP Address

Pass a startIP value to the requesting service redeploy type, default. The subnet IP address begins with the provided IP address. Set sync_alloc to true to make a synchronous allocation request with commit dry-run support. Make sure that the NavuNode service is the same node you get in service create. This ensures that the back pointers are updated correctly and that the RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
    String poolName,
    String username,
    String startIp,
    int cidrmask,
    String id,
    boolean invertCidr,
    boolean sync_alloc)

API Parameters

| Parameter     | Type       | Description                                                      |
|---------------|------------|------------------------------------------------------------------|
| service       | NavuNode   | NavuNode referencing the requesting service node.                |
| poolName      | String     | Name of the resource pool to request the subnet IP address from. |
| username      | string     | Name of the user to use when redeploying the requesting service. |
| cidrmask      | Int        | CIDR mask length of the requested subnet.                        |
| id            | String     | Unique allocation ID.                                            |
| invertCidr    | Boolean    | Set value to true to invert the subnet mask length.              |
| sync_alloc    | Boolean    | Set value to true to make a synchronous allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, poolName, userName, startIp,
cidrMask, id, invertCidr.booleanValue(), testSync.booleanValue());

Java API for IP Subnet Allocation Request with Redeploy type, Start IP address and CIDR Mask

Pass a startIP value to the redeployType of the requesting service redeploy. The subnet IP address begins with the provided IP address. Set sync to true to make a synchronous allocation request with commit dry-run support. Make sure that the NavuNode service is the same node you get in service create. This ensures that the back pointers are updated correctly and that the RFM works as intended.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(NavuNode service,
        RedeployType redeployType,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameters

| Parameter     | Type       | Description                                                      |
|---------------|------------|------------------------------------------------------------------|
| service       | NavuNode   | NavuNode referencing the requesting service node.                |
| poolName      | String     | Name of the resource pool to request the subnet IP address from. |
| username      | String     | Name of the user to use when redeploying the requesting service. |
| startIP       | String     | Starting IP address for the subnet allocation request.           |
| cidrmask      | Int        | CIDR mask length of the requested subnet.                        |
| id            | String     | Unique allocation ID.                                            |
| invertCidr    | Boolean    | Set value to true to invert the subnet mask length.              |
| sync_alloc    | Boolean    | Set value to true to make a synchronous allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(service, redeployType, poolName,
userName, startIp, cidrMask, id, invertCidr.booleanValue(),
testSync.booleanValue());

Java API for IP Subnet Allocation Request with Service Context

Create an IP subnet allocation request with requesting service redeploy type as default and CIDR mask length cannot be inverted for the subnet allocation request. Make sure to use the service context you get in the service create callback. Set sync to true to make a synchronous allocation request with commit dry-run support.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        String poolName,
        String username,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameters

| Parameter      | Type           | Description                                                                    |
|----------------|----------------|--------------------------------------------------------------------------------|
| Context        | ServiceContext | ServiceContext referencing the requesting context the service was invoked in.  |
| service        | NavuNode       | NavuNode referencing the requesting service node.                              |
| poolName       | String         | Name of the resource pool to request the subnet IP address from.               |
| username       | String         | Name of the user to use when redeploying the requesting service.               |
| startIP        | String         | Starting IP address for the subnet allocation request.                         |
| cidrmask       | Int            | CIDR mask length of the requested subnet.                                      |
| id             | String         | Unique allocation ID.                                                          |
| invertCidr     | Boolean        | Set value to true to invert the subnet mask length.                            |
| sync_alloc     | Boolean        | Set value to true to make a synchronous allocation request.                    |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, poolName, userName,
cidrMask, id, invertCidr.booleanValue(), testSync.booleanValue());

Java API for IP Subnet Allocation Request with Service Context and Redeploy Type

Create an IP subnet allocation request with requesting service redeploy type as redeployType and CIDR mask length can be inverted for the subnet allocation request. Set sync to true to make a synchronous allocation request with commit dry-run support. Make sure to use the service context you get in the service create callback.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        RedeployType redeployType,
        String poolName,
        String username,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameter

| Parameter      | Type           | Description                                                                     |
|----------------|----------------|---------------------------------------------------------------------------------|
| Context        | ServiceContext | ServiceContext referencing the requesting context the service was invoked in.   |
| service        | NavuNode       | NavuNode referencing the requesting service node.                               |
| poolName       | String         | Name of the resource pool to request the subnet IP address from.                |
| username       | String         | Name of the user to use when redeploying the requesting service.                |
| cidrmask       | Int            | CIDR mask length of the requested subnet.                                       |
| id             | String         | Unique allocation ID.                                                           |
| invertCidr     | Boolean        | Set value to true to invert the subnet mask length.                             |
| sync_alloc     | Boolean        | Set value to true to make a synchronous allocation request.                     |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, redeployType,
poolName, userName, cidrMask, id, invertCidr.booleanValue(),
testSync.booleanValue());

Java API for IP Subnet Allocation Request with Service Context and Start IP Address

Pass a startIP value to the requesting service redeploy type, default. The subnet IP address begins with the provided IP address. CIDR mask length can be inverted for the subnet allocation request. Set sync to true to make a synchronous allocation request with commit dry-run support. Make sure to use the service context you get in the service create callback.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameters

| Parameter   | Type           | Description                                                                   |
|-------------|----------------|-------------------------------------------------------------------------------|
| Context     | ServiceContext | ServiceContext referencing the requesting context the service was invoked in. |
| service     | NavuNode       | NavuNode referencing the requesting service node.                             |
| poolName    | String         | Name of the resource pool to request the subnet IP address from.              |
| username    | String         | Name of the user to use when redeploying the requesting service.              |
| startIP     | String         | Starting IP address of the IP subnet allocation request.                      |
| cidrmask    | Int            | CIDR mask length of the requested subnet.                                     |
| id          | String         | Unique allocation ID.                                                         |
| invertCidr  | Boolean        | Set value to true to invert the subnet mask length.                           |
| sync_alloc  | Boolean        | Set value to true to make a synchronous allocation request.                   |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, poolName, userName,
startIp, cidrMask, id, invertCidr.booleanValue(),
testSync.booleanValue());

Java API for IP Subnet Allocation Request with Service Context and Start IP Address and Redeploy-type

Pass a startIP value to the requesting service redeploy type, redeployType. The subnet IP address begins with the provided IP address. CIDR mask length can be inverted for the subnet allocation request. Set sync to true to make a synchronous allocation request with commit dry-run support. Make sure to use the service context you get in the service create callback.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(ServiceContext context,
        NavuNode service,
        RedeployType redeployType,
        String poolName,
        String username,
        String startIp,
        int cidrmask,
        String id,
        boolean invertCidr,
        boolean sync_alloc)

API Parameters

| Parameter       | Type           | Description                                                                   |
|-----------------|----------------|-------------------------------------------------------------------------------|
| Context         | ServiceContext | ServiceContext referencing the requesting context the service was invoked in. |
| service         | NavuNode       | NavuNode referencing the requesting service node.                             |
| poolName        | String         | Name of the resource pool to request the subnet IP address from.              |
| username        | String         | Name of the user to use when redeploying the requesting service.              |
| startIP         | String         | Starting IP address of the IP subnet allocation request.                      |
| cidrmask        | Int            | CIDR mask length of the requested subnet.                                     |
| id              | String         | Unique allocation ID.                                                         |
| invertCidr      | Boolean        | Set value to true to invert the subnet mask length.                           |
| sync_alloc      | Boolean        | Set value to true to make a synchronous allocation request.                   |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

IPAddressAllocator.subnetRequest(context, service, redeployType,
poolName, userName, startIp, cidrMask, id, invertCidr.booleanValue(),
testSync.booleanValue());

Common Exceptions Raised by Java APIs for Allocation Not Successful

• The API throws the following exception error if the requested resource pool does not exist: ResourceErrorException

• The API throws the following exception error if the requested resource pool is exhausted: AddressPoolException

• The API throws the following exception error if the requested netmask is invalid: InvalidNetmaskException

Verifying Responses for IP Allocations – Java APIs

Once the requesting service requests allocation through an API call, you can verify if the corresponding response is ready. The responses return the properties based on the request.

The following APIs help you to check if the response for the allocation request is ready.

Java API to Check Allocation Request Using CDB Context

boolean com.tailf.pkg.ipaddressallocator.IPAddressAllocator. 
    responseReady(NavuContext context,
        Cdb cdb,
        String poolName,
        String id)

API Parameters

| Parameter   | Type         | Description                                           |
|-------------|--------------|-------------------------------------------------------|
| Context     | NavuContext  | A NavuContext for the transaction.                    |
| Cdb         | database     | A database resource.                                  |
| poolName    | String       | Name of the resource pool the request was created in. |
| id          | String       | Unique allocation ID for the allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

ready = IPAddressAllocator.responseReady(service.context(),cdb, poolName,
id);

returns True or False

Response

Returns true if a response for the allocation is ready.

Java API to Check Allocation Request Without Using CDB Context

The following API is recommended to verify responses for IP allocations.

boolean com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    responseReady(NavuContext context,
        String poolName,
        String id)

API Parameters

| Parameter   | Type         | Description                                           |
|-------------|--------------|-------------------------------------------------------|
| Context     | NavuContext  | A NavuContext for the transaction.                    |
| poolName    | String       | Name of the resource pool the request was created in. |
| id          | String       | Unique allocation ID for the allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

ready = IPAddressAllocator.responseReady(service.context(), poolName,
id);

returns True or False

Response

Returns true if a response for the allocation is ready.

Common Exceptions Raised by Java APIs for Errors

• ResourceErrorException: If the allocation has failed, the request does not exist, or the pool does not exist.

• ConfException: When there are format errors in the API request call.

• IOException: When the I/O operations fail or are interrupted.

Reading IP Allocation Responses for Java APIs

The following API reads the allocated IP subnet from the resource pool once the allocation request response is ready.

Subnet Read Java API to Read Allocation Using CDB Context

ConfIPPrefix
com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRead(Cdb cdb,
        String poolName,
        String id)

API Parameter

| Parameter   | Type     | Description                                           |
|-------------|----------|-------------------------------------------------------|
| cdb         | Database | A database resource.                                  |
| poolName    | String   | Name of the resource pool the request was created in. |
| id          | String   | Unique allocation ID for the allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

allocatedIP = IPAddressAllocator.subnetRead(cdb, poolName, id);

returns allocated IP subnet

Response

The API returns the allocated subnet IP.

From Read Java API to Read Allocation Using CDB Context

ConfIPPrefix com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    fromRead(Cdb cdb,
        String poolName,
        String id)

API Parameters

| Parameter   | Type     | Description                                           |
|-------------|----------|-------------------------------------------------------|
| cdb         | Database | A database resource.                                  |
| poolName    | String   | Name of the resource pool the request was created in. |
| id          | String   | Unique allocation ID for the allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

allocatedIP = IPAddressAllocator.fromRead(cdb, poolName, id);

returns allocated IP subnet

Response

Returns the subnet from which the IP allocation was made.

New Subnet Read Java API to Read Allocation

The following is the recommended API to read the allocated IP.

ConfIPPrefix com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRead(NavuContext context,
        String poolName,
        String id)

API Parameters

| Parameter   | Type     | Description                                           |
|-------------|----------|-------------------------------------------------------|
| cdb         | Database | A database resource.                                  |
| poolName    | String   | Name of the resource pool the request was created in. |
| id          | String   | Unique allocation ID for the allocation request.      |

Example

import com.tailf.pkg.ipaddressallocator.IPAddressAllocator;

allocatedIP = IPAddressAllocator.subnetRead(service.context(), poolName,
id);

returns allocated IP subnet

Response

Returns the allocated subnet for the IP.

Using Java APIs for Non-service IP Allocations

This non-service IP address allocation API is created from Resource Manager 4.2.12.

subnetRequest()

This API is used to request subnet from the IP address pool.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRequest(Maapi maapi,
        int th,
        RedeployType redeployType,
        String poolName,
        String username,
        String startIp
        int cidrmask,
        String id,
        Boolean invertCidr,
        Boolean sync_alloc
        )

API Parameters

| Parameter     | Type     | Description                                                         |
|---------------|----------|---------------------------------------------------------------------|
| maapi         | Maapi    | Maapi Object.                                                       |
| th            | int      | Transaction handle.                                                 |
| poolName      | String   | Name of the resource pool to request the subnet IP address from.    |
| Username      | String   | Name of the user to use when redeploying the requesting service.    |
| cidrmask      | Int      | CIDR mask length of the requested subnet.                           |
| invertCidr    | Boolean  | If boolean value is true, the subnet mask length is inverted.       |
| id            | String   | Unique allocation ID.                                               |
| sync_alloc    | Boolean  | Set value to true to make a synchronous allocation request.         | 
                             By default, it is false (asynchronous).                             |

Example

NavuContainer loop = (NavuContainer) service;
    Maapi maapi = service.context().getMaapi();
    int th = service.context().getMaapiHandle();
        ConfBuf devName = (ConfBuf) loop.leaf("device").value();
        IPAddressAllocator.subnetRequest(maapi, th, RedeployType.DEFAULT, poolName, "admin", null,
    32, allocationName, false, false);
        if (IPAddressAllocator.responseReady(maapi, th, poolName, allocationName)) {
            LOGGER.debug("responseReady for ipaddress is true.");
            ConfIPPrefix subnet = IPAddressAllocator.subnetRead(maapi, th, poolName, allocationName);
            LOGGER.debug(String.format("subnetRead maapi.Got the value for subnet : %s ",
    subnet.getAddress()));

subnetRead()

This API is used to read the allocated subnet from the IP address pool.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    subnetRead(Maapi maapi,
        int th,
        String poolName,
        String allocationName
        )

API Parameters

| Parameter       | Type   | Description                                                      |
|-----------------|--------|------------------------------------------------------------------|
| maapi           | Maapi  | Maapi Object.                                                    |
| th              | int    | Transaction handle.                                              |
| poolName        | String | Name of the resource pool to request the subnet IP address from. |
| allocationName  | String | Allocation name used to read allocated ID.                       |

Example

NavuContainer loop = (NavuContainer) service;
    Maapi maapi = service.context().getMaapi();
    int th = service.context().getMaapiHandle();
        ConfBuf devName = (ConfBuf) loop.leaf("device").value();
        IPAddressAllocator.subnetRequest(maapi, th, RedeployType.DEFAULT, poolName, "admin", null,
    32, allocationName, false, false);
        if (IPAddressAllocator.responseReady(maapi, th, poolName, allocationName)) {
            LOGGER.debug("responseReady for ipaddress is true.");
            ConfIPPrefix subnet = IPAddressAllocator.subnetRead(maapi, th, poolName, allocationName);
            LOGGER.debug(String.format("subnetRead maapi.Got the value for subnet : %s ",
subnet.getAddress()));

responseReady()

This API is used to check if the response is ready in case of an async subnet request.

void com.tailf.pkg.ipaddressallocator.IPAddressAllocator.
    responseReady(Maapi maapi,
        int th,
        String poolName,
        String allocationName,
    )

API Parameters

| Parameter       | Type   | Description                                                   |
|-----------------|--------|-------------------------------------------------------------------|
| maapi           | Maapi  | Maapi Object.                                                     |
| th              | int    | Transaction handle.                                               |
| poolName        | String | Name of the resource pool to request the subnet IP address from.  |
| allocationName  | String | Allocation Name.                                                  |

Example

NavuContainer loop = (NavuContainer) service;
    Maapi maapi = service.context().getMaapi();
    int th = service.context().getMaapiHandle();
        ConfBuf devName = (ConfBuf) loop.leaf("device").value();
        IPAddressAllocator.subnetRequest(maapi, th, RedeployType.DEFAULT, poolName, "admin", null,
    32, allocationName, false, false);
        if (IPAddressAllocator.responseReady(maapi, th, poolName, allocationName)) {
            LOGGER.debug("responseReady for ipaddress is true.");
            ConfIPPrefix subnet = IPAddressAllocator.subnetRead(maapi, th, poolName, allocationName);
            LOGGER.debug(String.format("subnetRead maapi.Got the value for subnet : %s ",
    subnet.getAddress()));

Common Exceptions Raised by Java APIs for Errors

• ResourceErrorException: If the allocation has failed, the request does not exist, or the pool does not exist.

• ResourceWaitException: If the allocation is not ready.

Using Python APIs for IP Allocations

Creating Python APIs for IP Allocations

The RM package exposes Python APIs to manage allocation for IP subnet from the resource pool.

Below is the list of Python APIs exposed by the RM package.

Default Python API for IP Subnet Allocation Request

The following API is used to create an allocation request for an IP address from a resource pool.

Use the API definition net_request found in the module resource_manager.ipaddress_allocator.

The net_request function is designed to create an allocation request for a network. It takes several arguments, including the requesting service, username, pool name, allocation name, CIDR mask (size of the network), and optional parameters such as invert_cidr, redeploy_type, sync_alloc, and root. After calling this function, you need to call net_read to read the allocated IP from the subnet.

def net_request (service,
    svc_xpath,
    username,
    pool_name,
    allocation_name,
    cidrmask,
    invert_cidr=False,
    redeploy_type="default",
    sync_alloc=False,
    root=None)

API Parameters

| Parameter        | Type     | Description                                                                                              |
|------------------|----------|----------------------------------------------------------------------------------------------------------|
| service          |          | The requesting service node.                                                                             |
| svc_xpath        | String   | XPath to the requesting service.                                                                         |
| username         | String   | Name of the user to use when redeploying the requesting service.                                         |
| pool_name        | Int      | Name of the resource pool to make the allocation request from.                                           |
| allocation_name  | String   | Unique allocation name.                                                                                  |
| cidrmask         |          | Size of the network.                                                                                     |
| invert_cidr      | Boolean  |                                                                                                          |
| redeploy_type    |          | Service redeploy action. Available options: default, touch, re-deploy, reactive-re-deploy, no-redeploy.  |
| sync_alloc       | Boolean  | Allocation type, whether synchronous or asynchronous. By default, it is asynchronous.                    |
| Root             |          | Root node. If sync is set to true, you must provide a root node.                                         |

Example

import resource_manager.ipaddress_allocator as ip_allocator

# Define pool and allocation names
pool_name = "The Pool"
allocation_name = "Unique allocation name"
sync_alloc_name = "Unique synchronous allocation name"

# Asynchronous network allocation
# This will try to allocate a network of size 24 from the pool named 'The Pool'
# using the allocation name: 'Unique allocation name'
ip_allocator.net_request(
    service,
    "/services/vl:loop-python[name='%s']" % (service.name),
    tctx.username,
    pool_name,
    allocation_name,
    24
)

# Synchronous network allocation
# This will try to allocate a network of size 24 from the pool named 'The Pool'
# using the allocation name: 'Unique synchronous allocation name'
ip_allocator.net_request(
    service,
    "/services/vl:loop-python[name='%s']" % (service.name),
    tctx.username,
    pool_name,
    sync_alloc_name,
    24,
    sync=True,
    root=root
)

Python API for IP Subnet Allocation Request with Start IP Address

The following API is used to create a static allocation request for an IP address from a resource pool. Use the API definition net_request_static found in the module resource_manager.ipaddress_allocator.

The net_request_static function extends the functionality of net_request to allow for the static allocation of network resources, specifically addressing individual IP addresses within a subnet. In addition to the parameters used in net_request, it also accepts subnet_start_ip, which specifies the starting IP address of the requested subnet. This function provides a way to allocate specific IP addresses within a network pool, useful for scenarios where certain IP addresses need to be reserved or managed independently. The function maintains similar error handling and package requirements as net_request, ensuring consistency in network resource management.

def net_request_static(service,
    svc_xpath,
    username,
    pool_name,
    allocation_name,
    subnet_start_ip,
    cidrmask,
    invert_cidr=False,
    redeploy_type="default",
    sync_alloc=False,
    root=None)

API Parameters

| Parameter        | Type     | Description                                                                                             |
|------------------|----------|---------------------------------------------------------------------------------------------------------|
| service          |          | The requesting service node.                                                                            |
| svc_xpath        | String   | XPath to the requesting service.                                                                        |
| username         | String   | Name of the user to use when redeploying the requesting service.                                        |
| pool_name        | Int      | Name of the resource pool to make the allocation request from.                                          |
| allocation_name  | String   | Unique allocation name.                                                                                 |
| cidrmask         |          | Size of the network.                                                                                    |
| invert_cidr      | Boolean  | Whether to invert the CIDR.                                                                             |
| redeploy_type    |          | Service Redeploy action. Available options: default, touch, re-deploy, reactive-re-deploy, no-redeploy. |
| sync_alloc       | Boolean  | Allocation type, whether synchronous or asynchronous. By default, it is asynchronous.                   |
| root             |          | Root node. If `sync` is set to true, you must provide a root node.                                      |

Example

import resource_manager.ipaddress_allocator as ip_allocator

# Define pool and allocation names
pool_name = "The Pool"
allocation_name = "Unique allocation name"
sync_alloc_name = "Unique synchronous allocation name"

# Asynchronous static IP allocation
# This will try to allocate the address 10.0.0.8 with a CIDR mask of 32
# from the pool named 'The Pool', using the allocation name: 'Unique allocation name'
ip_allocator.net_request_static(
    service,
    "/services/vl:loop-python[name='%s']" % (service.name),
    tctx.username,
    pool_name,
    allocation_name,
    "10.0.0.8",
    32
)

# Synchronous static IP allocation
# This will try to allocate the address 10.0.0.9 with a CIDR mask of 32
# from the pool named 'The Pool', using the allocation name: 'Unique synchronous allocation name'
ip_allocator.net_request_static(
    service,
    "/services/vl:loop-python[name='%s']" % (service.name),
    tctx.username,
    pool_name,
    sync_alloc_name,
    "10.0.0.9",
    32,
    sync=True,
    root=root
)

Reading the Allocated IP Subnet Once the Allocation is Ready

Use the API definition net_read found in the module resource_manager.ipaddress_allocator to read the allocated subnet IP. The net_read function retrieves the allocated network from the specified pool and allocation name. It takes the username, root node for the current transaction, pool name, and allocation name as parameters. The function interacts with the rm_alloc module to read the allocated network, returning it if available or None if not ready. It's important to note that the function should be used to ensure that the response subnet is received in the current transaction, avoiding aborts or failures during the commit.

def net_read(username,
    root,
    pool_name,
    allocation_name)

API Parameters

| Parameter        | Type    | Description                                                          |
|------------------|---------|----------------------------------------------------------------------|
| username         | String  | Name of the user to use when redeploying the requesting service.     |
| root             |         | A maagic root for the current transaction.                           |
| pool_name        | String  | Name of the resource pool to make the allocation request from.       |
| allocation_name  | String  | Unique allocation name.                                              |

Example

# After requesting allocation, we check if IP is allocated.
net = ip_allocator.net_read(
    tctx.username,
    root,
    pool_name,
    allocation_name
)

if not net:
    self.log.info("Alloc not ready")
    return

print("net = %s" % (net))

Using Python APIs for Non-Service IP Allocations

Creating Python APIs for IP Allocations

The RM package exposes Python APIs to manage non-service allocation for IP subnet from the resource pool. Below is the list of Python APIs exposed by the RM package.

Non-Service Python API for IP Subnet Allocation Request

The following API is used to create an allocation request for an IP address from a resource pool. Use the API definition net_request_tr found in the module resource_manager.ipaddress_allocator.

The net_request_tr function is designed to create a non-service allocation request for a network. It takes several arguments, including the requesting tr ( transaction backend) , username, pool name, allocation name, CIDR mask (size of the network), and optional parameters such as invert_cidr, redeploy_type, sync_alloc, and root. After calling this function, you need to call net_read to read the allocated IP from the subnet.

def net_request_tr (tr,
    username,
    pool_name,
    allocation_name,
    cidrmask,
    invert_cidr=False,
    redeploy_type="default",
    sync_alloc=False,
    root=None)

API Parameters

| Parameter       | Type     | Description                                                                                         |
|-----------------|----------|-----------------------------------------------------------------------------------------------------|
| tr              |          | The transaction backend.                                                                            |
| username        | String   | Name of the user to use when redeploying the requesting service.                                    |
| pool_name       | Int      | Name of the resource pool to make the allocation request from.                                      |
| allocation_name | String   | Unique allocation name.                                                                             |
| cidrmask        |          | Size of the network.                                                                                |
| invert_cidr     | Boolean  |                                                                                                     |
| sync_alloc      | Boolean  | Set value to true to make a synchronous allocation request. By default, it is false (asynchronous). |

Example

import resource_manager.ipaddress_allocator as ip_allocator

pool_name = "The Pool"
allocation_name = "Unique allocation name"
sync_alloc_name = "Unique synchronous allocation name"

# This will try to asynchronously allocate the network of size 24 from the pool named 'The Pool'
# using allocation name: 'Unique allocation name'
ip_allocator.net_request_tr(
    maagic.get_trans(root),
    tctx.username,
    pool_name,
    alloc_name,
    service.cidr_length,
    False,
    "default",
    False,
    None
)

# This will try to synchronously allocate the network of size 24 from the pool named 'The Pool'
# using allocation name: 'Unique synchronous allocation name'
ip_allocator.net_request_tr(
    maagic.get_trans(root),
    tctx.username,
    pool_name,
    alloc_name,
    service.cidr_length,
    False,
    "default",
    True,
    None
)

ID Allocations

RM package exposes APIs to manage ID allocation from the ID resource pool. The APIs are available to request ID, check if the allocation is ready and also to read the allocation once ready.

Using JAVA APIs for ID Allocations – Asynchronous Old APIs

The following are the asynchronous old Java APIs for ID allocation from the RM resource pool.

Default Java API for ID Allocation Request

The following API is used to create or update an ID allocation request with service redeploy type as default.

idRequest(NavuNode service,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId)

API Parameters

| Parameter    | Type      | Description                                                               |
|--------------|-----------|---------------------------------------------------------------------------|
| Service      | NavuNode  | NavuNode referencing the requesting service node.                         |
| poolName     | String    | Name of the resource pool to request the allocation ID from.              |
| Username     | String    | Name of the user to use when redeploying the requesting service.          |
| id           | String    | Unique allocation ID.                                                     |
| sync_pool    | Boolean   | Sync allocations with the ID value across pools.                          |
| Requested ID | Int       | Request the specific ID to be allocated.                                  |

Example

import com.tailf.pkg.idallocator.IdAllocator;
IdAllocator.idRequest(service, poolName, userName, id,
test_with_sync.booleanValue(), requestId);

Java API for ID Allocation Request with Redeploy Type

The following API is used to create or update an IP allocation request with requesting service redeploy type as redeployType.

idRequest(NavuNode service, RedeployType redeployType,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId)

API Parameters

| Parameter      | Type      | Description                                                                  |
|----------------|-----------|------------------------------------------------------------------------------|
| Service        | NavuNode  | NavuNode referencing the requesting service node.                            |
| redeployType   |           | The available options are: Default, Redeploytype, Touch, Reactive-re-deploy. |
| poolName       | String    | Name of the resource pool to request the allocation ID from.                 |
| Username       | String    | Name of the user to use when redeploying the requesting service.             |
| ID             | String    | Unique allocation ID.                                                        |
| sync_pool      | Boolean   | Sync allocations with the ID value across pools.                             |
| Requested ID   | Int       | Request the specific ID to be allocated.                                     |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(service, redeployType, poolName, userName, id,
test_with_sync.booleanValue(), requestId);

Java API for ID Allocation Request with Service Context

The following API is used to create or update an ID allocation request with requesting service redeploy type as default.

idRequest(ServiceContext context,
    NavuNode service,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId)

API Parameters

| Parameter    | Type          | Description                                                                  |
|--------------|---------------|------------------------------------------------------------------------------|
| context      | ServiceContext| Context referencing the requesting context that the service was invoked in.  |
| service      | NavuNode      | NavuNode referencing the requesting service node.                            |
| poolName     | String        | Name of the resource pool to request the allocation ID from.                 |
| Username     | String        | Name of the user to use when redeploying the requesting service.             |
| ID           | String        | Unique allocation ID.                                                        |
| sync_pool    | Boolean       | Sync allocations with the ID value across pools.                             |
| Requested ID | Int           | Request the specific ID to be allocated.                                     |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(context, service, poolName, userName, id,
test_with_sync.booleanValue(), requestId);

Java API for ID Allocation Request with Service Context and OddEven Allocation

The following API is used to create or update an ID allocation request with requesting service redeploy type as default.

idRequest(ServiceContext context,
    NavuNode service,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    IdType oddeven_alloc)

API Parameters

| Parameter     | Type          | Description                                                                  |
|---------------|---------------|------------------------------------------------------------------------------|
| context       | ServiceContext| Context referencing the requesting context that the service was invoked in.  |
| service       | NavuNode      | NavuNode referencing the requesting service node.                            |
| poolName      | String        | Name of the resource pool to request the allocation ID from.                 |
| Username      | String        | Name of the user to use when redeploying the requesting service.             |
| ID            | String        | Unique allocation ID.                                                        |
| sync_pool     | Boolean       | Sync allocations with the ID value across pools.                             |
| oddeven_alloc | IdType        | Request the Odd or Even ID to be allocated.                                  |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(context, service, poolName, userName, id,
test_with_sync.booleanValue(), oddeven_alloc);

Java API for ID Allocation Request with Service Context and Redeploy Type

Use the following API to create or update an ID allocation request with the requesting service redeploy type as redeployType.

idRequest(ServiceContext
    context,
    NavuNode service,
    RedeployType redeployType,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId)

API Parameter

| Parameter    | Type          | Description                                                                                                     |
|--------------|---------------|-----------------------------------------------------------------------------------------------------------------|
| context      | ServiceContext| Context referencing the requesting context that the service was invoked in.                                     |
| service      | NavuNode      | NavuNode referencing the requesting service node.                                                               |
| redeployType |               | Service redeploy action. The available options are: default, touch, re-deploy, reactive-re-deploy, no-redeploy. |
| poolName     | String        | Name of the resource pool to request the allocation ID from.                                                    |
| username     | String        | Name of the user to use when redeploying the requesting service.                                                |
| id           | String        | Unique allocation ID.                                                                                           |
| sync_pool    | Boolean       | Sync allocations with the ID value across pools.                                                                |
| requestedId  | Int           | Request the specific ID to be allocated.                                                                        |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(context, service, redeployType, poolName, userName,
id, test_with_sync.booleanValue(), requestId);

Java API for ID Allocation Request with Service Context, Redeploy Type and OddEven Allocation

Use the following API to create or update an ID allocation request with the requesting service redeploy type as redeployType.

idRequest(ServiceContext
    context,
    NavuNode service,
    RedeployType redeployType,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    boolean sync_alloc,
    IdType oddeven_alloc)

API Parameter

| Parameter    | Type          | Description                                                                                                     |
|--------------|---------------|-----------------------------------------------------------------------------------------------------------------|
| context      | ServiceContext| Context referencing the requesting context that the service was invoked in.                                     |
| service      | NavuNode      | NavuNode referencing the requesting service node.                                                               |
| redeployType |               | Service redeploy action. The available options are: default, touch, re-deploy, reactive-re-deploy, no-redeploy. |
| poolName     | String        | Name of the resource pool to request the allocation ID from.                                                    |
| username     | String        | Name of the user to use when redeploying the requesting service.                                                |
| id           | String        | Unique allocation ID.                                                                                           |
| sync_pool    | Boolean       | Sync allocations with the ID value across pools.                                                                |
| sync_alloc   | Int           | Request the specific ID to be allocated.                                                                        |
| oddeven_alloc| IdType        | Request the Odd or Even ID to be allocated.                                                                     |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(context, service, redeployType, poolName, userName,
id, test_with_sync.booleanValue(), oddeven_alloc);

Using JAVA APIs for Non-Service ID Allocations

The following API is used to create or update an ID allocation request with non-service.

idRequest()

This idRequest() method takes maapi object and transaction handle (th) as a parameter instead of ServiceContext object.

idRequest(Maapi maapi,
    int th,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId,
    boolean sync_alloc)

API Parameter

| Parameter   | Type   | Description                                                               |
|-------------|--------|---------------------------------------------------------------------------|
| maapi       | Maapi  | Maapi object.                                                             |
| th          | int    | Transaction handle.                                                       |
| poolName    | String | Name of the resource pool to request the allocation ID from.              |
| Username    | String | Name of the user to use when redeploying the requesting service.          |
| id          | String | Unique allocation ID.                                                     |
| sync_pool   | Boolean| Sync allocations with the ID value across pools.                          |
| requestedId | Int    | Request the specific ID to be allocated.                                  |
| sync_alloc  | Boolean| If the boolean value is true, the allocation is synchronous.              |

Example

NavuContainer loop = (NavuContainer) service;
Maapi maapi = service.context().getMaapi();
int th = service.context().getMaapiHandle();
ConfBuf devName = (ConfBuf) loop.leaf("device").value();
String poolName = loop.leaf("pool").value().toString();
String username = "admin";
String allocationName = loop.leaf("allocation-name").value().toString();
ConfBool sync = (ConfBool) loop.leaf("sync").value();

LOGGER.debug("doMaapiCreate() , service Name = " + allocationName);

long requestedId = loop.leaf("requestedId").exists()
    ? ((ConfUInt32) loop.leaf("requestedId").value()).longValue()
    : -1L;

/* Create resource allocation request. */
LOGGER.debug(String.format("id allocation Requesting %s , allocationName %s , requestedId %d",
    poolName, allocationName, requestedId));

IdAllocator.idRequest(maapi, th, poolName, username, allocationName, sync.booleanValue(),
    requestedId, false);

try {
    if (IdAllocator.responseReady(maapi, th, poolName, allocationName)) {
        LOGGER.debug(String.format("responseReady maapi True. allocationName %s.",
            allocationName));
        ConfUInt32 id = IdAllocator.idRead(maapi, th, poolName, allocationName);
        LOGGER.debug(String.format("idRead maapi: We got the id: %s.", id.longValue()));
    }

idRequest() with oddeven_alloc

This idRequest() method takes maapi object and transaction handle (th) as a parameter instead of ServiceContext object.

idRequest(Maapi maapi,
    int th,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    boolean sync_alloc,
    IdType oddeven_alloc)

API Parameter

| Parameter    | Type   | Description                                                               |
|--------------|--------|---------------------------------------------------------------------------|
| maapi        | Maapi  | Maapi object.                                                             |
| th           | int    | Transaction handle.                                                       |
| poolName     | String | Name of the resource pool to request the allocation ID from.              |
| Username     | String | Name of the user to use when redeploying the requesting service.          |
| id           | String | Unique allocation ID.                                                     |
| sync_pool    | Boolean| Sync allocations with the ID value across pools.                          |
| sync_alloc   | Boolean| If the boolean value is true, the allocation is synchronous.              |
| oddeven_alloc| IdType | Request the Odd or Even ID to be allocated.                               |

Example

NavuContainer loop = (NavuContainer) service;
Maapi maapi = service.context().getMaapi();
int th = service.context().getMaapiHandle();
ConfBuf devName = (ConfBuf) loop.leaf("device").value();
String poolName = loop.leaf("pool").value().toString();
String username = "admin";
String allocationName = loop.leaf("allocation-name").value().toString();
ConfBool sync = (ConfBool) loop.leaf("sync").value();
String oddevenStr = ConfValue.getStringByValue(servicePath + "/oddeven-alloc", service.leaf("oddeven-alloc").value());
IdType oddeven_alloc = IdType.from(oddevenStr);

LOGGER.debug("doMaapiCreate() , service Name = " + allocationName);

/* Create resource allocation request. */
LOGGER.debug(String.format("id allocation Requesting %s , allocationName %s , requestedId %d",
    poolName, allocationName, requestedId));

IdAllocator.idRequest(maapi, th, poolName, username, allocationName, sync.booleanValue(),
    false, oddeven_alloc);

try {
    if (IdAllocator.responseReady(maapi, th, poolName, allocationName)) {
        LOGGER.debug(String.format("responseReady maapi True. allocationName %s.",
            allocationName));
        ConfUInt32 id = IdAllocator.idRead(maapi, th, poolName, allocationName);
        LOGGER.debug(String.format("idRead maapi: We got the id: %s.", id.longValue()));
    }

idRead()

The following API is used to read the allocated ID.

idRead(Maapi maapi,
    int th,
    String poolName,
    String allocationName,
)

API Parameters

| Parameter     | Type   | Description                                                   |
|---------------|--------|---------------------------------------------------------------|
| maapi         | Maapi  | Maapi object.                                                 |
| th            | int    | Transaction handle.                                           |
| poolName      | String | Name of the resource pool to request the allocation ID from.  |
| allocationName| String | Allocation name.                                              |

Example

NavuContainer loop = (NavuContainer) service;
Maapi maapi = service.context().getMaapi();
int th = service.context().getMaapiHandle();
ConfBuf devName = (ConfBuf) loop.leaf("device").value();
String poolName = loop.leaf("pool").value().toString();
String username = "admin";
String allocationName = loop.leaf("allocation-name").value().toString();
ConfBool sync = (ConfBool) loop.leaf("sync").value();

LOGGER.debug("doMaapiCreate() , service Name = " + allocationName);

long requestedId = loop.leaf("requestedId").exists() ?
    ((ConfUInt32) loop.leaf("requestedId").value()).longValue() : -1L;

/* Create resource allocation request. */
LOGGER.debug(String.format("id allocation Requesting %s , allocationName %s , requestedId %d", 
    poolName, allocationName, requestedId));

IdAllocator.idRequest(maapi, th, poolName, username, allocationName, sync.booleanValue(), 
    requestedId, false);

try {
    if (IdAllocator.responseReady(maapi, th, poolName, allocationName)) {
        LOGGER.debug(String.format("responseReady maapi True. allocationName %s.", 
            allocationName));
        
        ConfUInt32 id = IdAllocator.idRead(maapi, th, poolName, allocationName);
        LOGGER.debug(String.format("idRead maapi: We got the id: %s.", id.longValue()));
    }
}

responseReady()

The following API is used to check whether the response is ready after the ID request in case of an asynchronous allocation request.

responseReady(Maapi maapi,
    int th,
    String poolName,
    String allocationName,
    )

API Parameters

| Parameter       | Type     | Description                                                    |
|-----------------|----------|----------------------------------------------------------------|
| maapi           | Maapi    | Maapi object.                                                  |
| th              | int      | Transaction handle.                                            |
| poolName        | String   | Name of the resource pool to request the allocation ID from.   |
| allocationName  | String   | Allocation Name.                                               |

Example

NavuContainer loop = (NavuContainer) service;
Maapi maapi = service.context().getMaapi();
int th = service.context().getMaapiHandle();
ConfBuf devName = (ConfBuf) loop.leaf("device").value();
String poolName = loop.leaf("pool").value().toString();
String username = "admin";
String allocationName = loop.leaf("allocation-name").value().toString();
ConfBool sync = (ConfBool) loop.leaf("sync").value();
LOGGER.debug("doMaapiCreate() , service Name = " + allocationName);

long requestedId = loop.leaf("requestedId").exists()
    ? ((ConfUInt32) loop.leaf("requestedId").value()).longValue()
    : -1L;

/* Create resource allocation request. */
LOGGER.debug(String.format("id allocation Requesting %s , allocationName %s , requestedId %d",
    poolName, allocationName, requestedId));

IdAllocator.idRequest(maapi, th, poolName, username, allocationName, sync.booleanValue(),
    requestedId, false);

try {
    if (IdAllocator.responseReady(maapi, th, poolName, allocationName)) {
        LOGGER.debug(String.format("responseReady maapi True. allocationName %s.", allocationName));
        ConfUInt32 id = IdAllocator.idRead(maapi, th, poolName, allocationName);
        LOGGER.debug(String.format("idRead maapi: We got the id: %s.", id.longValue()));
    }

Common Exceptions Raised by Java APIs for Errors

• The API may throw the below exception if no pool resource exists for the requested allocation: ResourceErrorException.

• The API may throw the below exception if the ID request conflicts with another allocation or does not match the previous allocation in case of multiple owner requests: AllocationException.

Verifying Responses for ID Allocations – Java APIs

RM package exposes responseReady Java API to verify if the ID allocation request is ready or not.

The following APIs are used to verify if the response is ready for an ID allocation request.

Java API to Check ID Allocation Ready Using CDB Context

boolean responseReady
    (NavuContext context, 
    Cdb cdb,
    String poolName, 
    String id)

API Parameters

| Parameter | Type        | Description                                                 |
|-----------|-------------|-------------------------------------------------------------|
| context   | NavuContext | A NavuContext for the current transition.                   |
| poolName  | Str         | Name of the resource pool to request the allocation ID from.|
| cdb       | database    | The resource database.                                      |
| id        | String      | Unique allocation ID.                                       |

Example

import com.tailf.pkg.idallocator.IdAllocator;

ready = IdAllocator.responseReady(service.context(), cdb, poolName, id);
returns True or False

Java API to Check ID Allocation Ready Without Using CDB Context

boolean responseReady
    (NavuContext context, 
    String poolName, 
    String id)

API Parameters

| Parameter   | Type         | Description                                                 |
|-------------|--------------|-------------------------------------------------------------|
| NavuContext |              | A NavuContext For the current transition.                   |
| poolName    | Str          | Name of the resource pool to request the allocation ID from.|
| ID          |              | Unique allocation ID.                                       |

Example

import com.tailf.pkg.idallocator.IdAllocator;

ready = IdAllocator.responseReady(service.context(), poolName, id);
returns True or False

Response

The API returns a true value if a response for the allocation is ready.

Common Exceptions Raised by Java APIs for Errors

• The API may throw the below exception if no pool resource exists for the requested allocation: ResourceException.

• The API may throw the below exception when there are format errors in the API request call: ConfException.

• The API may throw the below exception when the I/O operations fail or are interrupted: IOException.

Reading ID Allocation Responses for Java APIs

The following API reads information about specific allocation requests made by the API call. The response returns the allocated ID from the ID pool.

Java API to Read ID Allocation Once Ready Using CDB Context

The following API is used to verify the response for an asynchronous ID allocation request.

ConfUInt32 idRead
    (Cdb cdb,
    String poolName, 
    String id)

API Parameters

| Parameter | Type   | Description                                                  |
|-----------|--------|--------------------------------------------------------------|
| cdb       | Cdb    | A database resource.                                         |
| poolName  | Str    | Name of the resource pool to request the allocation ID from. |
| ID        | String | Unique allocation ID.                                        |

Example

import com.tailf.pkg.idallocator.IdAllocator;

allocatedID = IdAllocator.idRead(cdb, poolName, id);

returns allocated ID

Java API to Read ID Allocation Once Ready Without Using CDB Context

ConfUInt32 idRead
    (NavuContext context, 
    String poolName, 
    String id)

API Parameters

| Parameter  | Type        | Description                                                  |
|------------|-------------|--------------------------------------------------------------|
| context    | NavuContext | A Navu context for the current transaction.                  |
| poolName   | String      | Name of the resource pool to request the allocation ID from. |
| ID         | String      | Unique allocation ID.                                        |

Example

import com.tailf.pkg.idallocator.IdAllocator;

allocatedID = IdAllocator.idRead(service.context(), poolName, id);

returns allocated ID

Using JAVA APIs for ID Allocations – Synchronous/Asynchronous New APIs

The following are the synchronous/asynchronous new Java APIs exposed by the RM package for ID allocation from the resource pool.

Java API for ID Allocation Request Using Service Context

The following API is used to verify the response for a synchronous or asynchronous ID allocation request.

idRequest(ServiceContext context,
    NavuNode service,
    RedeployType redeployType,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId,boolean
    sync_alloc)

API Parameter

| Parameter    | Type          | Description                                                                  |
|--------------|---------------|------------------------------------------------------------------------------|
| context      | ServiceContext| A context referencing the requesting context the service was invoked in.     |
| service      | NavuNode      | Navu node referencing the requesting service node.                           |
| redeployType |               | Service redeploy action.                                                     |
| poolName     | String        | Name of the resource pool to request the allocation ID from.                 |
| username     | String        |                                                                              |
| id           | String        | Unique allocation ID.                                                        |
| sync_pool    | Boolean       | Sync allocations with the ID value across pools.                             |
| requestedId  | Int           | A specific ID to be requested.                                               |
| sync_alloc   | Boolean       | If the boolean value is true, the allocation is synchronous.                 |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(context, service, redeployType, poolName, userName,
id, test_with_sync.booleanValue(), requestId, syncAlloc.booleanValue());

Default Java API for ID Allocation Request

The following API is used to verify the response for a synchronous or asynchronous ID allocation request.

idRequest(NavuNode service,
    RedeployType redeployType,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    long requestedId,
    boolean sync_alloc)

API Parameters

| Parameter     | Type       | Description                                                                                       |
|---------------|------------|---------------------------------------------------------------------------------------------------|
| service       | NavuNode   | Navu node referencing the requesting service node.                                                |
| redeployType  |            | Service redeploy action. Options are: default, touch, re-deploy, reactive-re-deploy, no-redeploy. |
| poolName      | String     | Name of the resource pool to request the allocation ID from.                                      |
| username      | String     |                                                                                                   |
| id            | String     | Unique allocation ID.                                                                             |
| sync_pool     | Boolean    | Sync allocations with the ID value across pools.                                                  |
| requestedId   | Int        | A specific ID to be requested.                                                                    |
| sync_alloc    | Boolean    | Synchronous allocation.                                                                           | 

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(service, redeployType, poolName, userName, id,
test_with_sync.booleanValue(), requestId, syncAlloc.booleanValue());

Default Java API for ID Allocation Request with Odd/Even Allocation

The following API is used to verify the response for a synchronous or asynchronous ID allocation request with additional parameter i.e., oddeven_alloc

idRequest(NavuNode service,
    String poolName,
    String username,
    String id,
    boolean sync_pool,
    IdType oddeven_alloc)

API Parameters

| Parameter     | Type       | Description                                                                                       |
|---------------|------------|---------------------------------------------------------------------------------------------------|
| service       | NavuNode   | Navu node referencing the requesting service node.                                                |
| poolName      | String     | Name of the resource pool to request the allocation ID from.                                      |
| username      | String     |                                                                                                   |
| id            | String     | Unique allocation ID.                                                                             |
| sync_pool     | Boolean    | Sync allocations with the ID value across pools.                                                  |
| oddeven_alloc | IdType     | Request the Odd or Even ID to be allocated.                                                       |

Example

import com.tailf.pkg.idallocator.IdAllocator;

IdAllocator.idRequest(service, poolName, userName, id,
test_with_sync.booleanValue(), oddeven_alloc);

Common Exceptions Raised by Java APIs for Errors

• The API may throw the below exception if no pool resource exists for the requested allocation: ResourceErrorException.

• The API may throw the below exception if the ID request conflicts with another allocation or does not match the previous allocation in case of multiple owner requests: AllocationException.

Using Python APIs for ID Allocations

The RM package also exposed Python APIs to request ID allocation from a resource pool. The below APIs are Python APIs exposed by RM for ID allocation.

Python API for Default ID Allocation Request

Use the module resource_manager.id_allocator.

The id_request function is used to create an allocation request for an ID. It takes several arguments including the service, service xpath, username, pool name, allocation name, sync flag, requested ID (optional), redeploy type (optional), alloc sync flag (optional), root (optional) and oddeve_alloc (optional).

id_request(service, 
    svc_xpath, 
    username,
    pool_name, 
    allocation_name,
    sync_pool,
    requested_id=-1,
    redeploy_type="default",
    sync_alloc=False, 
    root=None,
    oddeven_alloc="default"):

API Parameters

| Parameter      | Type     | Description                                                                                            |
|----------------|----------|--------------------------------------------------------------------------------------------------------|
| service        |          | The requesting service node.                                                                           |
| svc_xpath      | Str      | XPath to the requesting service.                                                                       |
| username       | Str      | Name of the user to use when redeploying the requesting service.                                       |
| pool_name      | Str      | Name of the resource pool to make the allocation request from.                                         |
| allocation_name| Str      | Unique allocation name.                                                                                |
| sync_pool      | Boolean  | Sync allocations with this name across the pool.                                                       |
| requested_id   | Int      | A specific ID to be requested.                                                                         |
| redeploy_type  |          | Service redeploy action. Available options: default, touch, re-deploy, reactive-re-deploy, no-redeploy.|
| sync_alloc     | Boolean  | Allocation type, whether synchronous or asynchronous. By default, it is asynchronous.                  |
| root           |          | Root node. If sync is set to true, you must provide a root node.                                       |
| oddeven_alloc  | IdType   | A specific Odd/Even ID to be requested.                                                                |

Example

import resource_manager.id_allocator as id_allocator

pool_name = "The Pool"
allocation_name = "Unique allocation name"

# This will try to allocate the value 20 from the pool named 'The Pool'
# using allocation name: 'Unique allocation name'
# It will allocate the id asynchronously from the pool ‘The Pool’
id_allocator.id_request(
    service,
    "/services/vl:loop-python[name='%s']" % (service.name),
    tctx.username,
    pool_name,
    allocation_name,
    False,
    20,
    oddeven_alloc
)

# The below will allocate the id synchronously from the pool ‘The Pool’
id_allocator.id_request(
    service,
    "/services/vl:loop-python[name='%s']" % (service.name),
    tctx.username,
    pool_name,
    allocation_name,
    True,
    20,
    oddeven_alloc
)

vlan_id = id_allocator.id_read(tctx.username, root, 'vlan-pool', service.name)
if vlan_id is None:
    self.log.info(f"Allocation not ready...")
    return propList

self.log.info(f"Allocation is ready: {vlan_id}")
service.vlan_id = vlan_id

Python API to Read Allocated ID Once the Allocation is Ready

Use the API definition id_read found in the module resource_manager.id_allocator to read the allocated ID.

The id_read function is designed to return the allocated ID or none if the ID is not yet available. It first tries to look up the ID in the current transaction using the provided root , pool_name and allocation_name. If the ID is available in the current transaction, it returns the ID. If there is an error, it raises a LookupError. If the ID is not available in the current transaction, it calls id_read_async to asynchronously retrieve the ID.

id_read(username, root, pool_name, allocation_name)

API Parameters

| Parameter       | Type  | Description                                                                 |
|-----------------|-------|-----------------------------------------------------------------------------|
| username        | Str   | Name of the user to use when redeploying the requesting service.            |
| Root            |       | A maagic root for the current transaction.                                  |
| pool_name       | Str   | Name of the resource pool to make the allocation request from.              |
| allocation_name | Str   | Unique allocation name.                                                     |

Example

# After requesting allocation, we check if the allocated ID is available
id = id_allocator.id_read(tctx.username, root, pool_name, allocation_name)
    if not id:
        self.log.info("Alloc not ready")
        return
    print ("id = %d" % (id))

Using Python APIs for Non-Service ID Allocation

The RM package also exposes Python APIs to request ID allocation from a resource pool by passing the maapi object and transaction handle instead of the service. The below APIs are Python APIs for non-service ID allocation.

Use the module resource_manager.id_allocator.

id_request_tr

The id_request_tr function is used to create an allocation request for an ID. It takes several arguments including the tr, username, pool name, allocation name, sync flag, requested ID (optional), redeploy type (optional), alloc sync flag (optional), root (optional) and oddeven_alloc (optional).

id_request_tr(tr, username, 
    pool_name,
    allocation_name,
    sync_pool,
    requested_id=-1,
    redeploy_type="default",
    sync_alloc=False, 
    root=None,
    oddeven_alloc="default"):

API Parameters

| Parameter       | Type        | Description                                                                                         |
|-----------------|-------------|-----------------------------------------------------------------------------------------------------|
| tr              | Transaction | Transaction backend object.                                                                         |
| username        | Str         | Name of the user to use when redeploying the requesting service.                                    |
| pool_name       | Str         | Name of the resource pool to make the allocation request from.                                      |
| allocation_name | Str         | Unique allocation name.                                                                             |
| sync_pool       | Boolean     | Sync allocations with this name across the pool.                                                    |
| requested_id    | Int         | A specific ID to be requested.                                                                      |
| sync_alloc      | Boolean     | Set value to true to make a synchronous allocation request. By default, it is false (asynchronous). |
| oddeven_alloc   | IdType      | A specific Odd/Even ID to be requested.                                                             |

Example

@Service.create
def cb_create(self, tctx, root, service, proplist):
    self.log.info('LoopTrService create(service=', service._path, ')')
    pool_name = service.pool
    alloc_name = service.allocation_name if service.allocation_name else service.name
    id_allocator.id_request_tr(
        maagic.get_trans(root),
        tctx.username,
        pool_name,
        alloc_name,
        False,
        -1,
        "default",
        False,
        root,
        oddeven_alloc
    )
    id = id_allocator.id_read(tctx.username, root, pool_name, alloc_name)
    if not id:
        self.log.info("Alloc1 not ready")
        return
    self.log.info('LoopTrService id = %s' % (id))

Troubleshoot & Debug

Set the Java Debug

admin@ncs% set java-vm java-logging logger com.tailf.pkg level level-debug

Check the Log File

RM processing logs are in the file ncs-java-vm.log. Here is the example RM API entry point msg called from the services:

IPAddressAllocator Did-140-Worker-95:
- subnetRequest()
  poolName = multiService
  cidrmask = 32
  id = multiTest
  sync_alloc = false

IdAllocator Did-139-Worker-94:
- idRequest
  id = multiTest
  poolName = multiService
  requestedId = -1
  sync_pool = false
  sync_alloc = true

Use the RM Action Tool

Example

admin@ncs> request rm-action id-allocator-tool operation printIdPool pool multiService

Example

admin@ncs> request rm-action ip-allocator-tool operation fix_response_ip pool multiService