本文转自:https://www.ibm.com/developerworks/mydeveloperworks/blogs/e93514d3-c4f0-4aa0-8844-497f370090f5/entry/openstack_nova_scheduler_and_its_algorithm27?lang=en
Saturday, May 12, 2012
OpenStack nova-scheduler and its algorithm
Bridge (by the linux foundation)
本文转自:http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
Translations: russian , Turkish
A bridge is a way to connect two Ethernet segments together in a protocol independent way. Packets are forwarded based on Ethernet address, rather than IP address (like a router). Since forwarding is done at Layer 2, all protocols can go transparently through a bridge.
The Linux bridge code implements a subset of the ANSI/IEEE 802.1d standard. [1]. The original Linux bridging was first done in Linux 2.2, then rewritten by Lennert Buytenhek. The code for bridging has been integrated into 2.4 and 2.6 kernel series.
Translations: russian , Turkish
A bridge is a way to connect two Ethernet segments together in a protocol independent way. Packets are forwarded based on Ethernet address, rather than IP address (like a router). Since forwarding is done at Layer 2, all protocols can go transparently through a bridge.
The Linux bridge code implements a subset of the ANSI/IEEE 802.1d standard. [1]. The original Linux bridging was first done in Linux 2.2, then rewritten by Lennert Buytenhek. The code for bridging has been integrated into 2.4 and 2.6 kernel series.
Friday, May 11, 2012
Linux BRIDGE-STP-HOWTO
本文转自: http://www.faqs.org/docs/Linux-HOWTO/BRIDGE-STP-HOWTO.html
Linux BRIDGE-STP-HOWTO
Uwe Böhme
Johann-Heinrich-Abt-Straße 7
95213
Münchberg
Germany
+49/9251 960877
+49/9251 960878
uwe@bnhof.de
95213
Münchberg
Germany
+49/9251 960877
+49/9251 960878
uwe@bnhof.de
Lennert Buytenhenk
bridge code maintainer and developergnu.org
buytenh@gnu.org
Linux-网桥原理分析
本文转自: http://blog.chinaunix.net/uid-18824385-id-107165.html
1 前言
1 前言
本文的参考分析的源代码版本是2.6.15，我是边学习边总结，学习的过程中得益于Linux论坛（http://linux.chinaunix.net/bbs/）上大侠们总结分析的文档，他山之石可以攻玉，学习过程中我也会边学边总结，开源的发展在于共享，我也抛块砖，望能引到玉！
由于自身水平有限，且相关的参考资料较少，因此其中的结论不能保证完全正确，如果在阅读本文的过程中发现了问题欢迎及时与作者联系。也希望能有机会和大家多多交流学习心得！
KVM - Network
本文转自: http://benjr.tw/node/537
在 RHEL5 update4 KVM 下設定 Virtual machine 時 Network 有兩種選項. 1.Virtual network 2.Shared physical device 但預設的只有 Virtual network.
Tuesday, May 8, 2012
vir*工具管理KVM虚拟机
manage-kvm-machine-with-vir*-tools
Table of Contents
1 用vir*工具管理KVM虚拟机
1.1 使用virt-install安装虚拟机
- 你可能需要安装python-virtinst才可以使用virt-install
yum -y install python-virtinst
Monday, May 7, 2012
用Unix的设计思想来应对多变的需求
本文转自酷壳(coolshell.cn)
之前，@风枫峰 在“这是谁的错？”中说过开发团队对需求来者不拒，而@weidagang 也在“需求变更和IoC” 中说过用IoC来最大程度地解决需求变更。今天我也想从Unix设计思想的角度来说说什么是好的软件设计，什么样的设计可以把需求变更对开发的影响降低。（注意：这并不能解决用户或是PM的无理需求，面对无理需求，需要仔细分析需求，而用技术的手段无法搞定这个事，但是可以减轻需求变更带来的痛苦）
我曾经在《Unix传奇》的下篇中写过一些Unix的设计哲学和思想（这里重点推荐大家看一下《The Art of Unix Programming》，我推荐过多次了），以前也发过一篇“一些软件设计的原则”，不过，这些东西都太多了，记不住。其实，这么多年来，我的经验告诉我，无论是Unix设计，还是面向对象设计，还是别的什么如SOA，ECB，消息，事件，MVC，网络七层模型，数据库设计，等等，他们都在干三件事——解耦，解耦，还是解耦！所谓解耦，就是让软件的模块和模块间尽量少地依赖起来。
现实当中的例子
Subscribe to:
Posts (Atom)