Ertugrul Bolat

Naming standards is a crucial thing in our job! This post is about time spent in naming standards, possible costs of developing naming standards and possible costs not to have a well-thought-out naming standard for the orchestration projects. First I need to say, our basic aim is to provide organization-wide uniqueness for a configuration. This is the first step in automation. If something about the naming standard is not well-considered, most probably the orchestration project will not fit in the budget. It will cost you a lot of reworks and you know how the story goes on after that particular point. In fact, on average every person/hour spent on qualitative work items saves 7.7 person/hours of quantitative work items globally. orchestration projects are not an exception! As every software project needs relatively constant requirements to decrease costs. Above all software projects, orchestration projects are the easiest one to solidify the requirements because responsi...

SAN Configuration is a time-consuming job. SAN zone configuration for one server lasted 1 hour or so. Now I will show you how it takes approximately 2 minutes including connecting :) I used FOS CLI and excel to create SAN zoning configuration scripts. I strongly recommend, instead of using the excel directly on your production environment, first test it in another environment. Since excel produces every SAN zoning possibilities, rule count can cause performance issues. In my production environment 3000 zone configurations are working perfectly well, but I didn't test in over 3000 zone configurations. Now, let's focus on the excel! You can download generalized excel from here You can see every SAN Switch and Storage combination has a tab at the bottom. There are 4 things to focus on, first one is the static data needed one time! This data is written in RED Please write down the aliases of Storage WWPN aliases (since tabs differ with storage data) and SAN Swit...

Yesterday I experienced an interesting case. A bulk copy was to be done with permissions. But somehow we couldn't use Robocopy. First of all, please use Robocopy in situations like this. You can just paste this on cmd         Robocopy.exe <Source Path> <Destination Path> /COPY:DATS /E That's all!!! Now let's focus on "the die is cast" situation. I had to write this simple copy-permissions function to copy JUST THE PERMISSIONS! You can get the script from here , Github. Now I think I can share how to use this simple thing! On Powershell, type 2 mandatory fields which are string "sourcePath" and string "targetPath" and an optional switch "logEnabled"           .\Copy-Permissions.ps1 -SourcePath "<Source Path>" -TargetPath "<Target Path>" OR           .\Copy-Permissions.ps1 -SourcePath "<Source Path>" -TargetPath "<Target Path>...