CentOS is my favorite Linux distribution because it is the closest to RedHat you can find (for a reason). And I like RedHat for the simple reason that it is the most supported Linux distribution for any enterprise applications. I know usually both RedHat and SuSE are supported, but SuSE and I was never a love story and I will save you the history of this little drama for this time.
So, the idea is not to run CentOS in a production environment, unless you really have the heart of a warrior and do not care about being supported by a rock solid editor, but instead to run your OnCommand Core lab on a free OS.
I used a CentOS 6 minimal install for this tutorial.
[EDIT] Please use caution when setting up your environment according to this article. In some case, especially when using BIND DNS server with non-default parameters, you may end-up with requests going to data LIF even if they are on the storage network and you set “-listen-for-dns-query false” on it.
I got an interesting question from a customer about the way DNS load balancing is served in a cluster.
For network topology reasons, they needed to serve DNS requests on a network different from the data network used by the clients to access storage.
The problem is that Data ONTAP only listens to DNS requests on data LIFs that has been configured for DNS load balancing. The obvious issue is that if you configure an additional LIF on the management network, the load balancer will start serving this IP to the clients, which might not be the optimum path or even not routed at all.
When you are running a lab in your own laptop, saving resources is a concern. Sometimes you would like to run multiple products in the same system but you can’t because of conflicting TCP/IP ports for example.
This is the case with 7MTT (login required) that conflicts with NetApp’s VMware VASA provider.
There are two things I love more in my work than everything else : how smart is the way we (NetApp) store data, and virtualization (especially VMware). When you realize how accessible are these technologies today, you understand it gets pretty easy to get your own lab running on your laptop, as long as you have a bunch of RAM available.
Ok, I must admit I’m not running “cheap” hardware, but like a lot of my coworkers, I chose to work on a high-end MacBook Pro with 16GB of RAM and a 512GB SSD drive. SSD and RAM is the key here, remove one or the other and that’s going to be painful. I use my lab all the time, it saves me the hassle of finding a lab and setup base environment, and if saves me time, it also makes my customer happier.