NOTE: This installation was performed with NexentaStor 3.0.4, later versions may have slight differences in the installation process and the GUI interface.
I’m going to skip on insulting your intelligence by providing screen shots of the installation process for Nexenta, or the configuration of the VM if you go that route. I will start with the assumption that you have NexentaStor (Community Edition) installed on either a physical system or a VM, if you have gone the physical route obviously your network interface names are going to be different than I show. Since I am using VT-d of an actual SAS controller card, the rest should be similar.
- Proceed and start the configuration wizard
- Select which detected network interface you wish to be your primary (management) – we get more advanced control after the wizard is complete
- Select your configuration option (static)
- Input your IP Address you wish to use
- Proceed through the network configuration defining your subnet mask, DNS servers and gateway
- Review your configuration settings. If your configuration is correct, select N(o). If you need to make a correction, select Y(es)
- Select if you wish to use HTTP or HTTPS for management access. SSL does add CPU overhead and may be less responsive as the system warns.
- Make note of your configured TCP port and change it if desired (default = 2000), this will be the port the web management GUI listens on.
- Make note of the provided URL and access it in order to continue configuration.
- Open the management GUI in a web browser (Flash enabled) to proceed with the configuration wizard (Wizard 1).
- Populate the fields to meet your configuration goals and proceed to the next step.
- Configure your passwords for the two default management contexts and proceed.
- Define your notification preferences and continue to the next step.
- Review your configuration settings and save your configuration.
- We are now into the “Wizard 2” stage, this is where we will configure the actual storage options.
- Review your current interface settings, you can edit the existing configuration or add a new one. If you wish to aggregate multiple links into a single logical interface you must add a new interface to get that option. I will leave these as they are and can edit them at another time.
- Next we are prompted to configure the iSCSI initiator service, this would be used to access another storage device for resources (e.g. to add NFS to an iSCSI only system such as a Dell/EQ). I am not using any other iSCSI systems so this is irrelevant.
- This next screen shows us the list of detected disk devices, if you had configured iSCSI on the previous screen and had mapped storage to this initiator those resources should also be visible. I currently have 2 1TB Seagate drives attached to the SATA controller I assigned through VT-d.
- In this next section we are asked to create volumes (storage pools). The process is to select the physical resources and assign it to the volume. You can select multiple devices and change the “Redundancy Type” to configure for RAID protection (None=stripe, Mirror, RAIDZ1 = ~RAID5, RAIDZ2 = ~RAID6, and RAIDZ3 = paranoid?)
I am starting with “none” as I will perform some testing comparing different options in a later post.
- In the lower section we configure the properties of the pool, including name, deduplication, and Sync settings (which we will discuss more later). I will leave all settings as default at this time.
- Verify your volume was created, if not a red error description will flash temporarily across the upper section of the screen.
- In this next portion we can create “folders”, each folder can have its own access type (NFS, CIFS, FTP, RSYNC, etc). I will add a single folder which I will configure for NFS, I am selecting a block size of 4KB to match that of most of my guest OS systems. I also am setting the file system to be case sensitive and to enable unicode.
- This is the final step of the guided wizard, we can make any additional changes through the actual management interface. Set the checkboxes to meet your comfort level, I will attempt to compare some of these options in a later post for performance impact.
- This completes the basic configuration, the rest will be done through the standard management interface.
NexentaStor Storage Concepts
Within the Nexenta, or perhaps Solaris ZFS storage management, there are :
- Datasets (ZFS Pools) which are made up of physical disk (or logical from outside array)
- Shares – logical units presented as file services (CIFS, NFS, RSYNC, FTP, etc)
- ZVols – logical units presented as block storage (iSCSI)
With that being said, there are really just 2 different processes for allocating storage depending on if it is file based or block based storage.
Again, I hope this helps someone. I will cover configuring storage and accessing it from ESX in a later post.