网络内服务虚拟化
当我们启动新4451-XCisco Live数月前,我们讨论过的大新事物之一是服务容器架构。除非你密切关注4451-X,否则你可能漏掉了整件事情。服务容器到底是什么?
简单说来,服务容器是网络内部运行的虚拟机器。这些虚拟机比典型服务器虚拟机更能提高网络本身的能力。服务容器可以为网络增加额外服务,如WAN优化化,
写一次 运行任何地方
创建服务容器的动机是写程序或服务一次并运行到任何地方的能力。传统上服务或特征是在操作系统内网络平台上实现的,通常是Cisco路由器和开关上CiscoIOS系统,这意味着服务与主机操作系统紧密相联并需要大写或完全重写到其他平台上
With Service Containers, you can take advantage of the portability offered by a virtualization layer. Take Cisco WAAS as an example. The same software can be written once and then run in a variety of locations depending on performance and scale needs. WAAS running on an appliance is the same software as vWAAS running in a datacenter or blade virtual machine which is the same software as ISR-WAAS running in a Service Container on the ISR 4451-X. That means the end-user gets the same experience and features across the board and that fewer Cisco engineers are needed to support WAAS in all of these locations. With Service Containers you get much of the benefit of a services blade, like a UCS E-Series module, without the complexity or additional hardware.
技术类
前面我指服务容器虚拟机类型 。 虽然完全正确, 服务容器似非你所熟悉的VM类型 。 大多数人都熟悉VM超视像从VMWARE、Citrix或微软等公司运行 。这些超视像摘取主机硬件或操作系统为VMS创建标准环境 。服务容器虚拟化使用几大开源轻量虚拟化技术
The two VM types used by Service Containers are called Kernel Virtual Machines (KVM) and Linux Virtual Containers (LxC). The two differ mainly in how tight they are coupled to the Linux kernel used in most network operating systems such as IOS XE and Nexus OS. LxC containers use many of the kernel resources of the host while KVM containers have their own independent kernel. This means that a KVM can be slightly more portable than an LxC container while an LxC might have a slight performance edge over a KVM. To the end-user, however, the container type is completely invisible since all of this is determined by the Service Container developer. That makes this great information for your next Cisco Trivial Pursuit night, but not something you ever need to worry about unless you plan to start developing your own Service Containers.
You might also hear folks at Cisco Trivial Pursuit night referring to Service Containers as onePK containers and that's not a bad way to look at these VMs either. That's because all of the networking platforms that support Service Containers are also supporting the one Platform Kit software development kit (SDK). onePK is revolutionizing the way applications interact with the network. Instead of requiring an application developer to write a complex function to parse the command line or SNMP interface to a router, onePK allows them to make a simple procedure call to quickly and consistently return exactly the piece of information needed by the application. Because of the ease of writing applications that use onePK to interact with network platforms, the majority of services you find running in a Service Container are using onePK rather than older, less reliable mechanisms such as CLI, SNMP or even XML when communicating with Cisco hardware.
橡皮路相遇
服务容器全然兴高采烈,你可能想知道在哪里能看到这些容器。可以想象,像这样的技术将先开始显示在更新平台上。事实上,服务容器已经躲在你眼皮下好几年了。该技术使用好几年催化器4500Sup7E,8E并更新主管提供嵌入式Wireshark,以便网络管理员远程抓取调试应用流量
上头思科云服务路由器CSR1000v服务容器执行WebAPI服务容器跨NexusForm应用提供高级网络建模应用和提供开箱允许自定义应用
最后但肯定非最小新4451-XCisco服务容器环境增强主机平台功能
微小地品味服务容器提供能力。你肯定看到服务容器4k、ISR 4451-X、CSR1000v、Nexus产品和其他新平台上推出新特征和新能力。最新资讯和更多离散服务容器信息请查下链路
关联性
TechwiseTV团队做得更好服务容器解释比我刚才做的
https://www.youtube.com/watch?v=jEhO6NUUais
刚录制webNars服务容器细节远超出我这里
令我吃惊的是,它不仅表示你拥有路由器,还表示网络系统可能我错过标价