...
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1) Start with providing instance information, API key, Secret Key, and DNS Server IP; set up the connection
2) Split the metadata you want to have showing in the notes, and find the block with which it should associate
3) Update the block with the notes
|
...
Expand | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1) Start with providing instance information, API key, Secret Key, and DNS Server IP
2) Add a DNS server
3) Create a zone
4) Add Zone records
4) Link the Zone to the new DNS server and push
|
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
DHCPv2 functionality is enabled on a particular resource by attaching a DHCP Module as a child. A command to do this is as follows:
The special resource type “dhcp_module” indicates to ProVision that the DHCP system is enabled for the parent object. The attributes associated with the “dhcp_module” resource govern the DHCP system's behavior. Updating the attributes of a DHCP Server uses a Resource Update command:
This command appears rather complicated, but can be broken apart into reasonable pieces. The first section:
is familiar from other parts of ProVision. We are updating a resource of type “dhcp_module” whose resource id is 2178. The second section of the command details the update values, starting with
which contains a JSON-encoded string of all the fields specific to a DHCP server's function. When expanded into its full object form it is substantially easier to digest:
This object describes all the most common DHCP server configuration options. For a full explanation of each of the fields, see the Detailed API Specification later in this document. Please note that the object above must be passed to the DHCP system as a JSON-encoded string. It must be passed into the special “_dhcp_attributes” attribute for it to be functional, as in the example URL. |
...