Reflection of Internship Technology
When I started my internship at Nintendo of America I had managed to set the following objectives:
1) Learn how to setup and manage Zenoss (a service monitoring tool used to oversee overall service and hardware health)
2) Gain an intermediate experience with using Linux commands.
3) Get familiarity with virtualization and how design a virtualized environment for a specific purpose
Zenoss is quite its own monster in my opinion. It is similar to active directory in the sense where every piece of information is linked as a template to a class and thus functioning in a manner representative of object orientated programming. What steps did I take to tackle this monster? I enlisted the help of our service engineer Bryan Irvine who owns the service and is the subject matter expert to the entire company. Bryan showed me how to use Zenoss and how to actually go into Zenoss-Dev and implement changes and sample templates before pushing them to prod. I wrote some very basic python scripts and was able to create templates for a new API service used to run the Nintendo e-Shop environment that rolled out in March. From the time I started at Nintendo, I have read through the Zenoss user’s manual and watched a short seminar on it through YouTube. I used this tool everyday inside the Network Operations Center and feel pretty comfortable with it from a user’s perspective. From what I learned, I did not have to learn how to manage or setup Zenoss in order to perform my duties as a system administrator. That particular responsibility is that of our systems engineer. So to conclude, I did not complete my overall objective but at the same time, my objective was way too big. I learned that I should be more aware of what is expected of me before loading myself up with super high expectations. In terms of learning Linux commands, I learned the basics in the first 60 days of my internship. I did look over the Linux in a nutshell book at my desk and discovered how rarely I needed to
1) Learn how to setup and manage Zenoss (a service monitoring tool used to oversee overall service and hardware health)
2) Gain an intermediate experience with using Linux commands.
3) Get familiarity with virtualization and how design a virtualized environment for a specific purpose
Zenoss is quite its own monster in my opinion. It is similar to active directory in the sense where every piece of information is linked as a template to a class and thus functioning in a manner representative of object orientated programming. What steps did I take to tackle this monster? I enlisted the help of our service engineer Bryan Irvine who owns the service and is the subject matter expert to the entire company. Bryan showed me how to use Zenoss and how to actually go into Zenoss-Dev and implement changes and sample templates before pushing them to prod. I wrote some very basic python scripts and was able to create templates for a new API service used to run the Nintendo e-Shop environment that rolled out in March. From the time I started at Nintendo, I have read through the Zenoss user’s manual and watched a short seminar on it through YouTube. I used this tool everyday inside the Network Operations Center and feel pretty comfortable with it from a user’s perspective. From what I learned, I did not have to learn how to manage or setup Zenoss in order to perform my duties as a system administrator. That particular responsibility is that of our systems engineer. So to conclude, I did not complete my overall objective but at the same time, my objective was way too big. I learned that I should be more aware of what is expected of me before loading myself up with super high expectations. In terms of learning Linux commands, I learned the basics in the first 60 days of my internship. I did look over the Linux in a nutshell book at my desk and discovered how rarely I needed to