Several IPv6 friends and colleagues of mine are featured in this video along with myself. The video does a nice job of overviewing IPv6 and why you need to pay attention to it. Enjoy!
- Ed
Wednesday, October 03, 2012
Monday, October 01, 2012
DevOps and the impact on traditional System, Storage and Network Admins
There has been more discussion lately on DevOps and how they able to demand higher wages and that it should be a position that traditional System, Storage and Network Admins should be striving for long term. I have a slightly different opinion. I think the number of individuals that actually fit in the DevOps category to be very small and this is by the definition itself. It is very difficult to achieve the mastery involved in being both proficient at System/Storage/Network plus extensively development experience in several languages. I'm not talking scripting (though those that are good at scripting can do some impressive stuff) but those that can actually open up the source code for an application and fix it or tweak it to fit their needs.
My thoughts and questions around this topic are do traditional System, Storage and Network Admins have anything to fear over this new category of Operations? My initial thoughts are no, the roles that DevOps are filling in my experience have been on more complex environments with unique need requirements. They are typically part of very small teams tasked with getting large automation or deployment done. They want very technical people supporting the operations of the environment who can work and debug any part of the stack.
So what impact is this having in the industry? I do think that System, Storage and Network Administrators are now having to learn a lot more about each others jobs. With virtualization such a huge part in the landscape of data centers the lines are blurred. One thing has become abundantly clear to me, automation and scripting are incredibly important for admins to have as a skill. In order to take advantage of all the tools for cloud services (public, private or hybrid) all of them require understanding and using effectively automation and scripting. So my personal short list is learning PowerShell, System Center (several of the products), Hyper-V and if time allows, Orchestrator. Did I mention I spend my time focused on networking? Those tools, along with their counter parts in VMware are increasingly becoming important to understand to deploy data center network architectures appropriately. Additionally, Puppet, Chef or cfengine would be good skills sets to add to my tool belt soon. If only I had more time! What is on your short list to learn and why?
- Ed
My thoughts and questions around this topic are do traditional System, Storage and Network Admins have anything to fear over this new category of Operations? My initial thoughts are no, the roles that DevOps are filling in my experience have been on more complex environments with unique need requirements. They are typically part of very small teams tasked with getting large automation or deployment done. They want very technical people supporting the operations of the environment who can work and debug any part of the stack.
So what impact is this having in the industry? I do think that System, Storage and Network Administrators are now having to learn a lot more about each others jobs. With virtualization such a huge part in the landscape of data centers the lines are blurred. One thing has become abundantly clear to me, automation and scripting are incredibly important for admins to have as a skill. In order to take advantage of all the tools for cloud services (public, private or hybrid) all of them require understanding and using effectively automation and scripting. So my personal short list is learning PowerShell, System Center (several of the products), Hyper-V and if time allows, Orchestrator. Did I mention I spend my time focused on networking? Those tools, along with their counter parts in VMware are increasingly becoming important to understand to deploy data center network architectures appropriately. Additionally, Puppet, Chef or cfengine would be good skills sets to add to my tool belt soon. If only I had more time! What is on your short list to learn and why?
- Ed
Labels:
DevOps,
Hyper-V,
Microsoft,
Orchestrator,
PowerShell,
System Center
Friday, September 07, 2012
Windows Server 2012 RTM and Windows 8
On September 4th, 2012 Windows Server 2012 went RTM and is available for download in MSDN and Technet. To get up to speed there are some great resources available on the product and the huge amount of changes and enhancements Microsoft has put into this release.
To get a handle on it all Microsoft Press has made the Introducing Windows Server 2012 RTM edition available for free. You can download it as a PDF, Mobi or ePub format so there is no excuse not to go over to the site right now and get your free copy!
In terms of features, the Hyper-V update, PowerShell 3.0, Storage and Network updates are really important along with the obvious "cloud" enablement that Microsoft has been touting for awhile.
On a separate note, I haven't had time to install Windows 8 RTM onto my primary work laptop and I am considering waiting until the new Window 8 Intel specific hardware comes out after the new year which is about when my refresh cycle is up anyway. My other option is picking up a cost effective SSD and doing a clean build. In the meantime if I really need to test things out I have my Windows To Go stick to play with Windows 8 on my laptop with no fear of damaging my system or losing any data.
- Ed
To get a handle on it all Microsoft Press has made the Introducing Windows Server 2012 RTM edition available for free. You can download it as a PDF, Mobi or ePub format so there is no excuse not to go over to the site right now and get your free copy!
In terms of features, the Hyper-V update, PowerShell 3.0, Storage and Network updates are really important along with the obvious "cloud" enablement that Microsoft has been touting for awhile.
On a separate note, I haven't had time to install Windows 8 RTM onto my primary work laptop and I am considering waiting until the new Window 8 Intel specific hardware comes out after the new year which is about when my refresh cycle is up anyway. My other option is picking up a cost effective SSD and doing a clean build. In the meantime if I really need to test things out I have my Windows To Go stick to play with Windows 8 on my laptop with no fear of damaging my system or losing any data.
- Ed
Thursday, August 02, 2012
I am presenting at TechMentor in August on IPv6
If you are interested in visiting the Pacific Northwest in August (which is a great time of the year to visit!) then come check out the TechMentor Conference.This year it will be held at Microsoft HQ in Redmond on August 20-24, 2012.
The list of presenters is pretty impressive like Don Jones, Mark Minasi, Bruce Rougeau and Greg Shields. You will also get to hear from me on IPv6 (of course) and lots of other great speakers.
Here's a small sample of the topics that will be covered at TechMentor this year:
- Virtualization
- Application Delivery
- MCITP Certification
- PowerShell
You can use the discount code of TMRTU for a $300 discount off the 5 day value package.
- Ed
Wednesday, August 01, 2012
Windows 8 and IPv6
For those that missed the Microsoft blog post by Chris Palmer explaining the IPv6 support that Windows 8 will have it is worth a read. It is important enough that Steven Sinofsky posted it as a guest blog entry on his building Windows 8 page, which is pretty cool. With Windows 8 now RTM understanding how IPv6 works in the Windows OS environment is pretty important. This is the third client OS release from Microsoft with comprehensive IPv6 support (Vista, Windows 7 and now Windows 8) and the server side is equally as impressive (Windows Server 2008, 2008R2 and now 2012) so there is no excuse not to understand and start working with IPv6. After all, you have had since 2007 (Vista's release) to start working on your IPv6 skills!
The important take away from the post to me was that Windows 8 will not have full RFC 6555 (Happy Eyeballs) support in the way many in the industry wanted (Dan Wing and others.) Happy Eyeballs is an important stop gap solution to resolving much of the end user experience issues that happen when IPv6 isn't work correctly. The issues happen when IPv6 is turned on but broken (routing isn't working for example) but is still preferred over IPv4 connectivity. This situation will become more common as IPv6 is more widely deployed but not as well understood by IT Professionals and helpdesk staff. Their lack of comprehensive understanding of troubleshooting dual stack environments will make this issue more common in the next 1-2 years is my feeling. Hopefully this will change as wider adoption of IPv6 means a better understanding of the protocol and its importance.
In my conversations with many at Microsoft regarding IPv6 and RFC 6555 it comes to light that they see their client OS being deployed and supported much longer than many in the industry. One of the principal concerns with doing a full RFC 6555 implementation was that it likely won't be needed in 3-5 years and because of how RFC 6555 works it makes it much tougher to debug application behavior on the client. This is a huge concern for Microsoft as custom applications deployed in Enterprise environments is a large part of their business. Making client behavior different depending on the application that is running and per session spells disaster in the QA testing area.
There are other considerations too about why they chose the path they did for doing such a limited support of RFC 6555 but the reality is... it doesn't matter. You can't change it, Windows 8 will make use of a modified RFC 3484 solution outlined in Chris' blog post and quoted below:
"Windows 8 tests IPv6 connectivity when you connect to a new network that advertises IPv6 routabilty, and it will only use IPv6 if IPv6 connectivity is actually functioning. This approach is a modification of our implementation of RFC 3484. Instead of sorting addresses as a result of policy, we use the actual state of the network as input to our algorithm. On a misconfigured network, this approach improves the experience not only for browsers but also for apps that connect to dual-stack destinations using standard Windows APIs.
Windows 8 performs the network connectivity test when you first connect to a new network; it caches this information and repeats the test every 30 days. The actual test for connectivity is a simple HTTP GET to an IPv6-only server that is hosted by Microsoft. (For standards buffs, this is implemented between rules 5 and 6 of destination address sorting in our implementation of RFC 3484.) Windows performs a similar network connectivity test for IPv4 connectivity. If both IPv4 and IPv6 are functioning, IPv6 will be preferred.
To make sure that Windows 8 does not cause problems on enterprise networks, the functionality has two safeguards:
So there you have it. More details about how it all works can be found in Joseph Davies' Understanding IPv6, Third Edition, an excellent reference book on how Microsoft has implemented IPv6 in Windows. Full discloser, I was the technical editor for the book.
- Ed
The important take away from the post to me was that Windows 8 will not have full RFC 6555 (Happy Eyeballs) support in the way many in the industry wanted (Dan Wing and others.) Happy Eyeballs is an important stop gap solution to resolving much of the end user experience issues that happen when IPv6 isn't work correctly. The issues happen when IPv6 is turned on but broken (routing isn't working for example) but is still preferred over IPv4 connectivity. This situation will become more common as IPv6 is more widely deployed but not as well understood by IT Professionals and helpdesk staff. Their lack of comprehensive understanding of troubleshooting dual stack environments will make this issue more common in the next 1-2 years is my feeling. Hopefully this will change as wider adoption of IPv6 means a better understanding of the protocol and its importance.
In my conversations with many at Microsoft regarding IPv6 and RFC 6555 it comes to light that they see their client OS being deployed and supported much longer than many in the industry. One of the principal concerns with doing a full RFC 6555 implementation was that it likely won't be needed in 3-5 years and because of how RFC 6555 works it makes it much tougher to debug application behavior on the client. This is a huge concern for Microsoft as custom applications deployed in Enterprise environments is a large part of their business. Making client behavior different depending on the application that is running and per session spells disaster in the QA testing area.
There are other considerations too about why they chose the path they did for doing such a limited support of RFC 6555 but the reality is... it doesn't matter. You can't change it, Windows 8 will make use of a modified RFC 3484 solution outlined in Chris' blog post and quoted below:
"Windows 8 tests IPv6 connectivity when you connect to a new network that advertises IPv6 routabilty, and it will only use IPv6 if IPv6 connectivity is actually functioning. This approach is a modification of our implementation of RFC 3484. Instead of sorting addresses as a result of policy, we use the actual state of the network as input to our algorithm. On a misconfigured network, this approach improves the experience not only for browsers but also for apps that connect to dual-stack destinations using standard Windows APIs.
Windows 8 performs the network connectivity test when you first connect to a new network; it caches this information and repeats the test every 30 days. The actual test for connectivity is a simple HTTP GET to an IPv6-only server that is hosted by Microsoft. (For standards buffs, this is implemented between rules 5 and 6 of destination address sorting in our implementation of RFC 3484.) Windows performs a similar network connectivity test for IPv4 connectivity. If both IPv4 and IPv6 are functioning, IPv6 will be preferred.
To make sure that Windows 8 does not cause problems on enterprise networks, the functionality has two safeguards:
- If the enterprise has provided specific routing information to a particular destination, then Windows 8 will honor that preference, regardless of the connectivity determined by Windows. In enterprise environments, Windows assumes that network administrators who configure such routes specifically thought it was a good idea to use those routes.
- This change isn’t implemented on networks with web proxies. In these networks, the proxy provides connectivity to the Internet; so end-to-end testing of IPv6 connectivity is not useful. Instead, Windows 8 simply opens connections to the proxy in the most efficient manner possible.
So there you have it. More details about how it all works can be found in Joseph Davies' Understanding IPv6, Third Edition, an excellent reference book on how Microsoft has implemented IPv6 in Windows. Full discloser, I was the technical editor for the book.
- Ed
Subscribe to:
Posts (Atom)
