26. Using the FreeNAS® API¶
FreeNAS® provides a REST API which can be used as an alternate mechanism for remotely controlling a FreeNAS® system.
REST provides an easy-to-read, HTTP implementation of functions, known as resources, which are available beneath a specified base URL. Each resource is manipulated using the HTTP methods defined in RFC 2616, such as GET, PUT, POST, or DELETE.
As seen in Figure 26.1a, an online version of the API is available at api.freenas.org.
Figure 26.1a: FreeNAS® API Documentation
The rest of this section walks through some code examples to get you started using the APIs.
26.1. A Simple API Example¶
The api directory of the FreeNAS® github repository contains some API usage examples. This
section provides a walk-through of the newuser.py
script, shown below, as it provides a simple example that creates a user.
In order to create a customized script based on this example, you will need a FreeNAS® system running at least version 9.2.0. If you would like to test the scripts directly on the FreeNAS® system, create a user account. When creating this user account, select an existing volume or dataset for the user’s “Home Directory”. Once the user is created, start the SSH service using
. That user will now be able to ssh to the IP address of the FreeNAS® system in order to create and run scripts. Alternately, you can test your scripts on any system that has the software mentioned in the previous section installed.To customize this script, copy the contents of this example into a filename that ends in .py
. The text that is highlighted in red below should be
modified in your copy in order to match the needs of the user being created. The text in black should remain as-is. After saving your changes, run the script
by typing python scriptname.py. If all goes well, the new user account will appear in in the
FreeNAS® GUI.
Here is the example script with an explanation of the line numbers below it.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | import json
import requests
r = requests.post(
'https://freenas.mydomain/api/v1.0/account/users/',
auth=('root', 'freenas'),
headers={'Content-Type': 'application/json'},
verify=False,
data=json.dumps({
'bsdusr_uid': '1100',
'bsdusr_username': 'myuser',
'bsdusr_mode': '755',
'bsdusr_creategroup': 'True',
'bsdusr_password': '12345',
'bsdusr_shell': '/usr/local/bin/bash',
'bsdusr_full_name': 'Full Name',
'bsdusr_email': 'name@provider.com',
})
)
print r.text
|
Where:
Lines 1-2: import the Python modules used to make HTTP requests and handle data in JSON format.
Line 4: replace freenas.mydomain with the “Hostname” value in
. Note that your script will fail if the machine running the script is not able to resolve that hostname. If you are not using HTTPS to access the FreeNAS® system, change https to http.Line 5: replace freenas with the password that you use to access the FreeNAS® system.
Line 7: if you are using HTTPS and want to force validation of the SSL certificate, change False to True.
Lines 8-16: sets the values for the user being created. The “Users” resource describes this resource in more detail. The allowed parameters are listed in the “Json Parameters” section of that resource. Since this resource creates a FreeBSD user, the values that you input must be valid for a FreeBSD user account. Table 26.1a summarizes the valid values. Since this resource is using JSON, the possible boolean values are True or False.
Table 26.1a: Valid JSON Parameters for Users Create Resource
JSON Parameter | Type | Description |
---|---|---|
bsdusr_username | string | maximum 32 characters, though a maximum of 8 is recommended for interoperability; can include numerals but can not include a space |
bsdusr_full_name | string | may contain spaces and uppercase characters |
bsdusr_password | string | can include a mix of upper and lowercase letters, characters, and numbers |
bsdusr_uid | integer | by convention, user accounts have an ID greater than 1000 with a maximum allowable value of 65,535 |
bsdusr_group | integer | if “bsdusr_creategroup” is set to False, specify the numeric ID of the group to create |
bsdusr_creategroup | boolean | if set to True, a primary group with the same numeric ID as “bsdusr_uid” will be automatically created |
bsdusr_mode | string | sets default numeric UNIX permissions of user’s home directory |
bsdusr_shell | string | specify full path to a UNIX shell that is installed on the system |
bsdusr_password_disabled | boolean | if set to True, user is not allowed to login |
bsdusr_locked | boolean | if set to True, user is not allowed to login |
bsdusr_sudo | boolean | if set to True, sudo is enabled for the user |
bsdusr_sshpubkey | string | contents of SSH authorized keys file |
Note
when using boolean values, JSON returns raw lowercase values whereas Python uses uppercase values. This means that you should use True or False in your Python scripts even though the example JSON responses in the API documentation are displayed as true or false.
26.2. A More Complex Example¶
This section provides a walk-through of a more complex example found in the startup.py
script. Use the searchbar within the API documentation to
quickly locate the JSON parameters used in this example. This example defines a class and several methods which are used to create a ZFS volume, create a ZFS
dataset, share this dataset over CIFS, and enable the CIFS service. The responses from some methods are used as parameters in other methods. In addition to
the import lines seen in the previous example, this example imports two additional Python modules to provide parsing functions for command line arguments:
import argparse
import sys
It then creates a Startup class which is started with the hostname, username, and password provided by the user via the command line:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | class Startup(object):
def __init__(self, hostname, user, secret):
self._hostname = hostname
self._user = user
self._secret = secret
self._ep = 'http://%s/api/v1.0' % hostname
def request(self, resource, method='GET', data=None):
if data is None:
data =
r = requests.request(
method,
'%s/%s/' % (self._ep, resource),
data=json.dumps(data),
headers={'Content-Type': "application/json"},
auth=(self._user, self._secret),
)
if r.ok:
try:
return r.json()
except:
return r.text
raise ValueError(r)
|
A get_disks method is defined to get all the disks in the system as a disk_name response. The create_pool method will then use this information to create a ZFS pool named tank which will be created as a stripe. The volume_name and layout JSON parameters are described in the “Storage Volume” resource of the API documentation.
1 2 3 4 5 6 7 8 9 10 11 12 | def _get_disks(self):
disks = self.request('storage/disk')
return [disk['disk_name'] for disk in disks]
def create_pool(self):
disks = self._get_disks()
self.request('storage/volume', method='POST', data={
'volume_name': 'tank',
'layout': [
{'vdevtype': 'stripe', 'disks': disks},
],
})
|
The create_dataset method is defined which creates a dataset named MyShare
:
1 2 3 4 | def create_dataset(self):
self.request('storage/volume/tank/datasets', method='POST', data={
'name': 'MyShare',
})
|
The create_cifs_share method is used to share /mnt/tank/MyShare
with guest-only access enabled. The
cifs_name,
cifs_path,
cifs_guestonly JSON parameters, as well as the other allowable parameters, are described in the “Sharing CIFS” resource of the API documentation.
1 2 3 4 5 6 | def create_cifs_share(self):
self.request('sharing/cifs', method='POST', data={
'cifs_name': 'My Test Share',
'cifs_path': '/mnt/tank/MyShare',
'cifs_guestonly': True
})
|
Finally, the service_start method issues a command to enable the CIFS service. The srv_enable JSON parameter is described in the Services Services resource.
1 2 3 4 5 | def service_start(self, name):
self.request('services/services/%s' % name, method='PUT', data={
'srv_enable': True,
})
|