cloudprofile¶

Configuration for cloud profile resource.

Properties¶

(click to see Operations )

Name	Data Type	Permissions	Description
name	<String>	Read-write	Name for the Cloud profile. Must begin with an ASCII alphanumeric or underscore (_) character, and must contain only ASCII alphanumeric, underscore, hash (#), period (.), space, colon (:), at (@), equals (=), and hyphen (-) characters. Cannot be changed after the profile is created. Minimum length = 1 Maximum length = 127
type	<String>	Read-write	Type of cloud profile that you want to create, Vserver or based on Azure Tags. Possible values = autoscale, azuretags
vservername	<String>	Read-write	Name for the virtual server. Must begin with an ASCII alphanumeric or underscore (_) character, and must contain only ASCII alphanumeric, underscore, hash (#), period (.), space, colon (:), at sign (@), equal sign (=), and hyphen (-) characters. Can be changed after the virtual server is created. CLI Users: If the name includes one or more spaces, enclose the name in double or single quotation marks (for example, "my vserver" or 'my vserver'). . Minimum length = 1
servicetype	<String>	Read-write	Protocol used by the service (also called the service type). Possible values = HTTP, FTP, TCP, UDP, SSL, SSL_BRIDGE, SSL_TCP, DTLS, NNTP, DNS, DHCPRA, ANY, SIP_UDP, SIP_TCP, SIP_SSL, DNS_TCP, RTSP, PUSH, SSL_PUSH, RADIUS, RDP, MYSQL, MSSQL, DIAMETER, SSL_DIAMETER, TFTP, ORACLE, SMPP, SYSLOGTCP, SYSLOGUDP, FIX, SSL_FIX, PROXY, USER_TCP, USER_SSL_TCP, QUIC, IPFIX, LOGSTREAM, MONGO, MONGO_TLS
ipaddress	<String>	Read-write	IPv4 or IPv6 address to assign to the virtual server.
port	<Integer>	Read-write	Port number for the virtual server. Range 1 - 65535 * in CLI is represented as 65535 in NITRO API
servicegroupname	<String>	Read-write	servicegroups bind to this server.
boundservicegroupsvctype	<String>	Read-write	The type of bound service. Possible values = HTTP, FTP, TCP, UDP, SSL, SSL_BRIDGE, SSL_TCP, DTLS, NNTP, RPCSVR, DNS, ADNS, SNMP, RTSP, DHCPRA, ANY, SIP_UDP, SIP_TCP, SIP_SSL, DNS_TCP, ADNS_TCP, MYSQL, MSSQL, ORACLE, MONGO, MONGO_TLS, RADIUS, RADIUSListener, RDP, DIAMETER, SSL_DIAMETER, TFTP, SMPP, PPTP, GRE, SYSLOGTCP, SYSLOGUDP, FIX, SSL_FIX, USER_TCP, USER_SSL_TCP, QUIC, IPFIX, LOGSTREAM, LOGSTREAM_SSL
vsvrbindsvcport	<Integer>	Read-write	The port number to be used for the bound service. Range 1 - 65535 * in CLI is represented as 65535 in NITRO API
graceful	<String>	Read-write	Indicates graceful shutdown of the service. System will wait for all outstanding connections to this service to be closed before disabling the service. Default value: NO Possible values = YES, NO
delay	<Double>	Read-write	Time, in seconds, after which all the services configured on the server are disabled.
azuretagname	<String>	Read-write	Azure tag name. Maximum length = 512
azuretagvalue	<String>	Read-write	Azure tag value. Maximum length = 256
azurepollperiod	<Double>	Read-write	Azure polling period (in seconds). Default value: 60 Minimum value = 60 Maximum value = 3600
__count	<Double>	Read-only	count parameter

Operations¶

(click to see Properties )

ADD
DELETE
GET (ALL)
GET
COUNT

Some options that you can use for each operations:

Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:
http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes
If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.
Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,
To do this, you must specify the username and password in the request header of the NITRO request as follows:
X-NITRO-USER: <username>
X-NITRO-PASS: <password>
Note: In such cases, make sure that the request header DOES not include the following:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in green

add¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile

HTTP Method: POST

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Content-Type:application/json

Request Payload:

{"cloudprofile":{
<b>      "name":<String_value>,
</b><b>      "type":<String_value>,
</b><b>      "vservername":<String_value>,
</b><b>      "servicetype":<String_value>,
</b><b>      "ipaddress":<String_value>,
</b><b>      "port":<Integer_value>,
</b><b>      "servicegroupname":<String_value>,
</b><b>      "boundservicegroupsvctype":<String_value>,
</b><b>      "vsvrbindsvcport":<Integer_value>,
</b>      "graceful":<String_value>,
      "delay":<Double_value>,
      "azuretagname":<String_value>,
      "azuretagvalue":<String_value>,
      "azurepollperiod":<Double_value>
}}

Response:

HTTP Status Code on Success: 201 Created

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

delete¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile/ name_value<String>

HTTP Method: DELETE

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

get (all)¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile

Query-parameters:

attrs

http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile? attrs=property-name1,property-name2

Use this query parameter to specify the resource details that you want to retrieve.

filter

http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile? filter=property-name1:property-val1,property-name2:property-val2

Use this query-parameter to get the filtered set of cloudprofile resources configured on NetScaler.Filtering can be done on any of the properties of the resource.

view

http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile? view=summary

Use this query-parameter to get the summary output of cloudprofile resources configured on NetScaler.

Note: By default, the retrieved results are displayed in detail view (?view=detail).

pagination

http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile? pagesize=#no;pageno=#no

Use this query-parameter to get the cloudprofile resources in chunks.

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{ "cloudprofile": [ {
      "name":<String_value>,
      "type":<String_value>,
      "vservername":<String_value>,
      "servicetype":<String_value>,
      "ipaddress":<String_value>,
      "port":<Integer_value>,
      "servicegroupname":<String_value>,
      "boundservicegroupsvctype":<String_value>,
      "vsvrbindsvcport":<Integer_value>,
      "azuretagname":<String_value>,
      "azuretagvalue":<String_value>,
      "azurepollperiod":<Double_value>,
      "graceful":<String_value>,
      "delay":<Double_value>
}]}

get¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile/ name_value<String>

Query-parameters:

attrs

http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile/ name_value<String> ? attrs=property-name1,property-name2

Use this query parameter to specify the resource details that you want to retrieve.

view

http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile/ name_value<String> ? view=summary

Use this query-parameter to get the summary output of cloudprofile resources configured on NetScaler.

Note: By default, the retrieved results are displayed in detail view (?view=detail).

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{  "cloudprofile": [ {
      "name":<String_value>,
      "type":<String_value>,
      "vservername":<String_value>,
      "servicetype":<String_value>,
      "ipaddress":<String_value>,
      "port":<Integer_value>,
      "servicegroupname":<String_value>,
      "boundservicegroupsvctype":<String_value>,
      "vsvrbindsvcport":<Integer_value>,
      "azuretagname":<String_value>,
      "azuretagvalue":<String_value>,
      "azurepollperiod":<Double_value>,
      "graceful":<String_value>,
      "delay":<Double_value>
}]}

count¶

URL: http:// <netscaler-ip-address> /nitro/v1/config/cloudprofile? count=yes

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload:

{ "cloudprofile": [ { "__count": "#no"} ] }