Clustered-Data-Ontap

As folks adopt DevOps principals they are using common applications to help them get there. One of those is Docker and usually in the same sentence Kubernetes is mentioned next. To review, Docker is essentially a wrapper for Linux containers (LXC), which similar to FreeBSD jails or Solaris Zones, provides a method for applications (and their dependencies) to be isolated in separate namespaces all while sharing the host system’s kernel. Docker containers are extremely portable as they just need the host server to have a LXC-compatible kernel and the Docker application installed. Kubernetes takes this concept to the next level by automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. For a more detailed intro on what Kubernetes is check out the “Sources” section below. Now to the meat of the post, what is NetApp Trident and where does it fit in to the Docker/Kubernetes equation? Well according to NetApp Trident’s GitHub page, “Trident provides storage orchestration for Kubernetes, integrating with its Persistent Volume framework to act as an external provisioner for NetApp ONTAP, SolidFire, and E-Series systems. Additionally, through its REST interface, Trident can also provide storage orchestration for non-Kubernetes deployments.” In other words, Trident allows one to attach persistent storage from NetApp FAS, E-Series, or SolidFire system(s) to containers allowing applications such as databases to easily operate in a containerized environment. Below are the steps I compiled needed to not only stand up a small 3-node Kubernetes cluster but also to deploy the NetApp Trident plugin: ...

2017-07-13: Updated for version 1.3 of my container image which includes some updated dashboards 2017-05-21: Updated for version 1.2 of my container image which includes NetApp SDK 5.7 2016-11-15: Updated for version 1.1 of my container image which includes Grafana 3.1 and NetApp Harvest 1.3 2018-03-18: Updated for version 1.4.1 of my container image which includes bug fixes, Grafana 4.5.2 and NetApp Harvest 1.4 2020-01-18: Updated for version 1.6 of my container image which includes NetApp Harvest 1.6 (and is now hosted at hub.docker.com) This post is based on the original “How To Setup NetApp Harvest Using Docker” blog post however it has been tweaked to reflect the more simplistic deployment method which relies on a pre-built container image (vs building one from source). ...

One new feature in 8.2.2+ that hasn’t been given much press (thanks to Curtis @ NetApp U) is the ability to boot directly into the boot menu or maintenance mode from the loader prompt. This feature will mainly be helpful for field personnel who frequently setup up and build out NetApp Clustered Data ONTAP systems. See below for a list of commands that are required to boot a cDOT system into each respective area. ...

Today is hump day and with that comes some added motivation to update this blog with some new material! The following post discusses another common topic and that is the termination of CIFS sessions in cDOT. This task could be performed in 7-mode however the commands have since changed in cDOT. Refer to the following tutorial below to kill any unwanted CIFS for a specific Windows user: Display the current CIFS session(s) for the user and record the value(s) in the “Connection ID” column ...

After spending the last few weeks moving into my new place and having “fun” furnishing it, I am back on the road armed with more content! Within a few hours of being onsite today I got asked if it was possible to set NTFS permissions to files and/or folders within Clustered Data ONTAP (cDOT). This is another commonly asked question and the answer to it is yes, you can apply NTFS permissions to filesystem objects from within cDOT. Below I have included a summarized step by step tutorial on how to apply NTFS permissions to a given path (can be the root of a volume or a file or folder which resides within a cDOT volume): ...

I have run into a few scenarios where I have had to manually clear NFS locks on a given NetApp system. The recommended procedure for clearing these locks has changed over the years depending on the Data ONTAP version and now again with the release of Clustered Data ONTAP. 7-mode ONTAP Login to the appropriate 7-mode filer Transition into diag mode priv set diag Clear all the NFS locks ...