Versions Compared

Old Version 2

changes.mady.by.user Shwetha S

Saved on

compared with

New Version Current

changes.mady.by.user Shwetha S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Authority delegation in Cloud Network Automation is the ability to assign full and exclusive control of IP addresses and DNS name spaces to a Cloud Platform Appliance. You can perform authority delegation only through the Grid Master. When you delegate the authority of IP addresses and DNS name spaces to a Cloud Platform Appliance, the Grid Master loses its authority over the scope of delegation for these IP addresses and name spaces as well as any objects within them. Note that authority delegation for an object can be explicitly assigned or inherited from parent objects. For information about how to delegate authority for supported object types, see Guidelines for Delegating below .
NIOS admin users who do not belong to admin groups with cloud API access are not allowed to create new cloud objects, nor can they modify or delete existing cloud objects in delegated spaces; but they can modify the permissions and certain extensible attribute values for these objects. Only admin users with cloud API access and the correct global and object permissions can be used to send cloud API requests to create, modify, and delete objects within the delegated scope.

...

Consider the authority delegation guidelines mentioned in the table below when you create, modify, or delete a network or network container. See Sample Cloud API RequestsAbout Cloud API RequestsRequest for a sample cloud API request. For information about how to create IPv4 and IPv6 networks from the Grid Master, see Adding IPv4 NetworksConfiguring IPv4 Networks and Adding IPv6 Networks.
For information about how to create IPv4 and IPv6 networks using network templates from the Grid Master, see Adding IPv4 Network TemplatesAbout IPv4 DHCP Templates and About IPv6 Network Templates.

Authority Delegation for Networks and Network Containers

...

Consider the authority delegation guidelines mentioned in the table below when you create, modify, or delete a DHCP range. See Sample Cloud API RequestsAbout Cloud API Requests for a sample cloud API request.
For information about how to create IPv4 and IPv6 ranges, see Adding IPv4 Address RangesConfiguring IPv4 Address Ranges and Modifying IPv6 Address Ranges.
For information about how to create IPv4 and IPv6 ranges using range templates, see Adding IPv4 Range Templates and Adding IPv6 Range Templates.

...

  • You can delegate authority for a fixed address only through inheritance from one of its parent objects, such as its associated network view, network container, network, or DHCP reserved range.

  • When you create or modify an IPv4 or IPv6 fixed address, you must include the following extensible attributes in the cloud API request: Tenant ID, Cloud API Owned, and CMP Type.

  • You can create a fixed address from the Grid Master using a fixed address template. Note that when you want to reference a template in the cloud API request, you must know the name of the template beforehand.

  • When performing any operations on a Cloud Platform Appliance, all discovery related attributes for a fixed address return the default values.

  • No DHCP service restart is required when performing any operations for a fixed address on the Cloud Platform Appliance unless automatic DHCP restart is disabled on the appliance. You can however perform a DHCP service restart on the Cloud Platform Appliance to which authority is delegated for a fixed address through a cloud API request.

  • You can create, modify, or delete an IPv4 or IPv6 fixed address and reservation on the Grid Master through Grid Manager if the fixed address or reservation is within the scope of a network view, network container, network, or DHCP reserved range whose authority has been delegated to a Cloud Platform Appliance.

See Sample Cloud API RequestsAbout Cloud API Requests for a sample cloud API request.
For information about how to create IPv4 and IPv6 fixed addresses, see Adding IPv4 Fixed AddressesConfiguring IPv4 Networks and Adding IPv6 Fixed Addresses.
For information about how to create IPv4 and IPv6 fixed address templates, see About IPv4 Fixed Address/Reservation Templates and Adding IPv6 Fixed Address Templates.

...

Consider the following authority delegation guidelines mentioned in the table below when you create, modify, or delete a DNS zone. See Sample Cloud API RequestsAbout Cloud API Requests for a sample cloud API request.
For information about how to create DNS zones, Configuring Authoritative Zones.

Authority Delegation for DNS Zones

...

Consider the following authority delegation guidelines mentioned in the table below when you create, modify, or delete a resource record, including A, AAAA, CNAME, PTR, MX, SRV, TXT, NAPTR records.
See Sample Cloud API RequestsAbout Cloud API Requests for a sample cloud API request.

...

Consider the following authority delegation guidelines mentioned in the table below when you create, modify, or delete a host record. See Sample Cloud API RequestsAbout Cloud API Requests for a sample cloud API request.

...

Cloud API Requests

Standard API and WAPI Requests

Comments

  • Authority delegation for a host record is inherited from both the DNS and DHCP portions of the record. For DNS, you can delegate authority for all DNS zones for which the host record is defined. For DHCP, you can delegate authority for the parent network view, network container, network, or DHCP range defined for the host record.

  • You can create, modify, or delete a host record or a host IP address whose authority is delegated to a Cloud Platform Appliance through Grid Manager. Note that when you create a host record, you must enable it for DNS within the delegated network view. Otherwise, you will not be able to save the host record.

  • The Cloud Platform Appliance can process a cloud API request that includes a host record only if it has gained authority for both DNS and DHCP portions of the host record, as follows:

    • All IP addresses enabled for DHCP within one or more delegation scopes are delegated to the same Cloud Platform Appliance.

    • All DNS records defined for one or more DNS zones have the same Cloud Platform Appliance assigned as the Grid primary.

  • IP addresses defined in the host record that is enabled DHCP follow the same rules for a fixed address. See the IPv4 and IPv6 Fixed Addresses section for more information.

  • Names or aliases defined in the host record follow the same rules set for resource records. See the DNS Resource Records section for more information.

  • When you create a host record through a cloud API request, you must include the following extensible attributes in the request: Tenant ID, Cloud API Owned, and CMP Type.

  • IP addresses defined in the host record that is enabled for DHCP follow the same rules set for a fixed address. See IPv4and IPv6 Fixed Addresses for more information.

  • Names or aliases defined in the host record follow the same rules set for resource records. See DNS Resource Records for more information.

  • Although no DHCP service restart is required, you can perform a DHCP service restart on a Cloud Platform Appliance through a cloud API request.



...