From the Blogosphere
Infrastructure 2.0 in the News: The Beat Goes On
Virtualization by itself isn’t enough; it needs an infrastructure 2.0 network
By: Greg Ness
Jan. 16, 2010 06:00 AM
Infrastructure 2.0 Session at Virtualization Expo
InformationWeek: Let's dive right in. Define the issue, as you see it.
You can read the entire interview here.
CNET blogger James Urquhart (Cisco’s Cloud Computing Market Strategist) referred to the interview in his blog entitled Understanding Infrastructure 2.0.
James did a great job highlighting the problems around manual address management at the core of the network:
"Take a look at the core TCP/IP and Ethernet networks that we all use today, and how enterprise IT manages those services. Not long ago, I wrote an article that described how most corporations relied heavily on manual labor to manage everything from IP addresses and domain names to routing and switching configuration. At the time, I cited a survey that indicated that a full 63 percent of enterprises were still using spreadsheets to manage IP addresses."
Unfortunately as we move into an era of data center virtualization and cloud computing, spreadsheets don’t cut it anymore.
You can read the rest of James’ excellent blog here, where he also points readers to several of his favorite infrastructure 2.0 blogs.
The common theme from both of these news sites is disconnect between virtualized, dynamic systems and static, manually managed networks. IT automation will require network automation and network automation will require DNS, DHCP and IPAM automation. Virtualization by itself isn’t enough; it needs an infrastructure 2.0 network.
You can follow my rants in real-time via Twitter at Archimedius.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week