How network admins can survive SDN
Network engineers with programming skills may be the best suited to make sure everything runs smoothly in the SDN/DevOps environment. The server admin and the application developer can define what the application or workload needs; but the network admin can make it work down to the device level, and ensure it stays up.
Salisbury recommends network admins become steeped in the software building blocks of SDN and DevOps: Linux; Puppet and Chef provisioning; Python scripting; and popular provisioning and orchestration projects such as Docker for containers and Openstack for virtual machines. Continue reading this article at Network World
Network programming skills from scripting to DevOps: What to learn
Whether they write modules or apps or just write some code directly on a switch, engineers should explore how programming skills can help them get more out of their infrastructure. There are plenty of opportunities to explore, and Edelman hopes that switch vendors open their platforms further to allow engineers with programming skills to do more.
“Over the next six months or year, there is going to be a need to keep doing what a few of us are doing … to educate the community on what tools are out there,” Edelman says. “Right now some network engineers are not even aware of tools like Puppet, Chef and Ansible. I’m not saying these are the right tools for the network space, but the more we can start thinking like DevOps engineers, it will help the way we approach networking in the future.” Continue reading this article at Tech Target
What are the responsibilities of a Server Admin, System Admin, and Network Administrator? What do these people do in a real job environment?
In a development environment, I have often been responsible for automating our procedures; for instance, I might be responsible for setting up nightly builds of our software, and setting up virtual machines for testing those builds. This requires a lot of scripting; it’s good to at least know BASH and PERL (or PYTHON) on the UNIX/Linux side.
As a network admin, I’d be responsible for configuring and maintaining our routers, switches, vpns, and firewalls. I’d be responsible for the first line of protection against Internet attacks: making sure there are no holes in our firewall, making sure that remote access is strictly controlled, auditing our safety procedures, etc. I’d also be responsible for making sure that machines that needed fast access to each other had it (a much bigger problem in previous years than now, but then again, now you have to deal with things like VPNs connecting your remote offices across the Internet, much cheaper than dedicated lines). Network admin can encompass a lot of territory; I’ve done things like wiring up phone closets and making my own ethernet cables. Continue reading this thread at Quora
The Return Of The IT Generalist
Will virtualization return us to this bygone age? Is this the time of the next generation of generalists in which a system or network administrator will have to understand all different aspects of the data center, progressively impacted by the DevOps trend? Cloud computing and virtualization continue to ignore staid IT organizational structures, defying categories, like mixing peanut butter and chocolate to come up with a new and improved version of the infrastructure.
Cisco’s recent announcement of its own particular flavor of the software-defined network (SDN), courtesy of its Insieme subsidiary, provides evidence of the new order. Cisco’s Application Centric Infrastructure (ACI) is part of the new wave of the fuzzy infrastructure, in which the traditional lines delineating groups are no longer clear as the data center becomes the application. Continue reading this
article at Network Computing
What is the difference between a network admin and a system admin?
The basic difference, according to Ars Tecnica and Wikipedia, is that Network Admins manage and maintain network configurations and network equipment (e.g., IP schemes, VLANs, switches, VPNs, routing, etc) while Systems Administrators manage and maintain system-level configurations and equipment (e.g., servers, applications, image deployment, AD/DHCP/DNS, etc). The source of the confusion is mainly that these things are not mutually exclusive. A SysAdmin may have to create a DHCP scope, but s/he’ll consult a NetAdmin for what that range ought to be. Additionally, who determines how certain shares are farmed out to the network? Well, they both have input into that. Further, who sets up and maintains the RDP over VPN functions? Again, they both do.
I hope that helps! Continue reading this thread at Spice Works
A Quick Guide to Network Administrator Course and Jobs
Employment Outlook and Demand for Network Administrators
Since the IT industry is growing rapidly and is expected to grow even more in coming years, network administrators have great job opportunities. These jobs are fairly compensated too. Though, your choice of organisation and expertise are the deciding factors in this case. The more skilled you are and bigger the responsibility, the better is the salary. With a relevant training and degree in network administration, you can work in almost any industry because almost all the industries are dependent on computer systems and networks for functioning. Continue reading this article at Linux
Network Administrator vs Web/Software Developer vs blend of both?
I picked up some C+ books to learn more about programming a few months ago and I can see why some people really enjoy it. The coding is quite logical. I am actually planning to change careers and make something out of Information Technology or Software development. I don’t mind going back to school or doing some distance to further my education. Both of these careers are different, but there’s some overlap and I wanted to see what you guys were doing and why you chose either.
I am under the impression that Network Administrators are usually on call and can be called in at 2am to fix a system error or if payroll systems are down. Whereas, Software Developers won’t be on call and have more flexibility to work from home if need be.
Do people usually have knowledge of both? Or is there a position that allows you to do both?
Why did you choose a particular field? Continue reading this thread at Red Flag Deals
How the Network Administrator Can Remain Relevant in the Age of IT Generalization
Now, things have somewhat come full circle. Two factors in particular are driving those changes: the migration to the Software-Defined Network and the DevOps movement. Together, these trends mean that fewer businesses are looking just for a ‘network administrator’ or ‘application developer’ and more companies are once again investing in IT generalists.
IT generalists don’t necessarily have to know everything about everything. But they do have to be able to step up to the plate no matter what task is currently at hand. For instance, with the SDN, network administrators will be less valued for their ability to understand abstract and uncommon CLI languages, but more important to the organization because they have both networking troubleshooting skills and the ability to do some scripting or coding as needed. Continue reading this article at NetScout
Orchestrating Server Agents in a DevOps Delivery Chain
Server agent orchestration, of course, includes much more than conflict prevention. Most agents are designed to improve server operations, or provide added functionality. As automated background utilities, they make major contributions to the performance of the DevOps delivery chain. In the larger picture, server agent orchestration means optimizing agent interaction for maximum efficiency, and leveraging agent synergy to provide maximum support for your operational needs. Whether you are using an agent provided by one or two vendors, or are employing a variety of agents (both proprietary and open-source), a well-orchestrated set of server agents should perform more like a unified suite of support utilities than a collection of unrelated applications. Continue reading this article at Intigua