基于操作系统的网络管理新范式：NOX

需积分: 10 151 浏览量更新于2024-09-12 收藏 365KB PDF 举报

NOX： towards an Operating System for Networks NOX是一个旨在实现网络操作系统的项目，目标是解决企业网络管理的复杂性问题。该项目的提出者认为，传统的网络管理方式已经不能满足当前的需求，需要一个新的网络管理模式。在介绍NOX项目之前，需要了解当前企业网络管理的挑战。企业网络管理是一个复杂的任务，需要处理大量的网络设备、连接和配置。随着网络规模的增加，管理的难度也随之增加。当前的网络管理方式主要基于命令行界面（CLI）和简单网络管理协议（SNMP），但是这些方式已经不能满足当前的需求。 NOX项目的目标是实现一个基于操作系统的网络管理模式，类似于计算机操作系统管理计算机资源。NOX项目的架构基于三层结构：控制层、网络层和设备层。控制层负责网络管理的策略决策，网络层负责网络资源的分配，设备层负责具体的网络设备管理。 NOX项目的关键技术包括软件定义网络（SDN）和开源流协议（OpenFlow）。SDN是一种新的网络架构，允许网络管理员通过软件定义网络的行为。OpenFlow是一种开源的协议，允许控制器和网络设备之间的通信。NOX项目使用SDN和OpenFlow来实现网络资源的自动管理和优化。 NOX项目的优点包括：提高网络管理的效率、降低网络管理的成本、提高网络的可靠性和安全性。NOX项目的应用前景非常广阔，包括数据中心、企业网络、校园网络等。在NOX项目中，作者提出了一个新的网络管理模式，基于操作系统的管理方式。这种方式可以解决当前企业网络管理的挑战，提高网络管理的效率和降低成本。NOX项目的成功可以推动整个网络行业的发展。 NOX项目的技术架构包括： * 控制层：负责网络管理的策略决策 * 网络层：负责网络资源的分配 * 设备层：负责具体的网络设备管理 * SDN：软件定义网络架构 * OpenFlow：开源流协议 NOX项目的优点包括： * 提高网络管理的效率 * 降低网络管理的成本 * 提高网络的可靠性和安全性 * 广阔的应用前景 NOX项目的挑战包括： * 实现复杂的网络管理系统 * 解决与传统网络管理方式的兼容性问题 * 满足不同网络环境的需求 NOX项目是一个旨在解决企业网络管理的复杂性问题的项目，基于操作系统的管理方式可以提高网络管理的效率和降低成本。NOX项目的成功可以推动整个网络行业的发展。

NOX: Towards an Operating System for Networks

Natasha Gude

Nicira Networks

Teemu Koponen

HIIT

Justin Pettit

Nicira Networks

Ben Pfaff

Nicira Networks

Martín Casado

Nicira Networks

Nick McKeown

Stanford University

Scott Shenker

University of California,

Berkeley

ThisarticleisaneditorialnotesubmittedtoCCR.IthasNOTbeenpeerreviewed.

Authorstakefullresponsibilityforthisarticle’stechnicalcontent. Comments can be posted through CCR Online.

Categories and Subject Descriptors

C.2.1 [

Computer-Communication Networks

]: Network

Architecture and Design

General Terms

Design, Experimentation, Performance

Keywords

Architecture, Management, Network, Security

1 Introduction

As anyone who has operated a large network can attest,

enterprise networks are diﬃcult to manage. That they have

remained so despite signiﬁcant commercial and academic

eﬀorts suggests the need for a diﬀerent network manage-

ment paradigm. Here we turn to operating systems as an

instructive example in taming management complexity.

In the early days of computing, programs were written

in machine languages that had no common abstractions for

the underlying physical resources. This made programs hard

to write, port, reason about, and debug. Modern operating

systems facilitate program development by providing con-

trolled access to high-level abstractions for resources (e.g.,

memory, storage, communication) and information (e.g., ﬁles,

directories). These abstractions enable programs to carry

out complicated tasks safely and eﬃciently on a wide variety

of computing hardware.

In contrast, networks are managed through low-level con-

ﬁguration of individual components. Moreover, these conﬁgu-

rations often depend on the underlying network; for example,

blocking a user’s access with an ACL entry requires knowing

the user’s current IP address. More complicated tasks re-

quire more extensive network knowledge; forcing guest users’

port 80 traﬃc to traverse an HTTP proxy requires knowing

the current network topology and the location of each guest.

In this way, an enterprise network resembles a computer

without an operating system, with network-dependent com-

ponent conﬁguration playing the role of hardware-dependent

machine-language programming.

What we clearly need is an “operating system” for networks,

one that provides a uniform and centralized programmatic

interface to the entire network.

Analogous to the read

and write access to various resources provided by computer

operating systems, a network operating system provides the

ability to observe and control a network.

A network operating system does not manage the network

itself; it merely provides a programmatic interface. Applica-

tions implemented on top of the network operating system

perform the actual management tasks.

The programmatic

interface should be general enough to support a broad spec-

trum of network management applications.

Such a network operating system represents two major

conceptual departures from the status quo. First, the net-

work operating system presents programs with a centralized

programming model

; programs are written as if the entire

network were present on a single machine (i.e., one would use

Dijkstra to compute shortest paths, not Bellman-Ford). This

requires (as in [3, 8, 14] and elsewhere) centralizing network

state. Second, programs are written in terms of high-level

abstractions (e.g., user and host names), not low-level con-

ﬁguration parameters (e.g., IP and MAC addresses). This

allows management directives to be enforced independent

of the underlying network topology, but it requires that the

network operating system carefully maintain the bindings

(i.e., mappings) between these abstractions and the low-level

conﬁgurations.

Thus, a network operating system allows management

applications to be written as centralized programs over high-

level names as opposed to the distributed algorithms over

low-level addresses we are forced to use today. While clearly a

desirable goal, achieving this transformation from distributed

algorithms to centralized programming presents signiﬁcant

technical challenges, and the question we pose here is: Can

one build a network operating system at signiﬁcant scale?

In the past, the term network operating system referred to

operating systems that incorporated networking (e.g., Novell

NetWare), but this usage is now obsolete. We are resurrect-

ing the term to denote systems that provide an execution

environment for programmatic control of the network.

In the rest of this paper, the term applications will refer

exclusively to management programs running on a network

operating system.

By centralized we allude to a shared memory programming

model. However, as we discuss in Section 3, diﬀerent memory

locations may have diﬀerent access overheads.

ACM SIGCOMM Computer Communication Review 105 Volume 38, Number 3, July 2008

下载后可阅读完整内容，剩余5页未读，立即下载

mypromise

粉丝: 3
资源: 7

基于操作系统的网络管理新范式：NOX

nox_setup_v6.0.7.5_full.exe

nox_setup_v7.0.0.5_full.exe夜神模拟器

nox_setup_v6.6.1.2_full.exe

qbittorrent-nox: command not found

openeuler上怎么源码编译安装ocaml-nox

centos7 安装qb

ubuntu 编译安装qemu-nox

linux vim vi 区别,Linux下 vi vim vim-gnome vim-tiny vim-gtk vim-nox的区别

CRIM', 'ZN', 'INDUS', 'CHAS', 'NOX', 'RM', 'AGE', 'DIS', 'RAD', 'TAX', 'PTRATIO', 'B', 'LSTAT', 'price'是什么意思

C:\Users\12483>D: D:\>D:\"Program Files\Nox\bin"\ 'D:\"Program Files\Nox\bin"\' 不是内部或外部命令，也不是可运行的程序 或批处理文件。

最新资源

C:\Users\12483>D: D:\>D:\"Program Files\Nox\bin"\ 'D:\"Program Files\Nox\bin"\' 不是内部或外部命令，也不是可运行的程序或批处理文件。