Web Services infrastructure for NetherLight.

learningsnortSecurity

Nov 3, 2013 (3 years and 10 months ago)

73 views

Web Services infrastructure for NetherLight.

Authors = Jeroen van der Ham, Paola Grosso


Version 1.0


October 14 2004


Initial draft.


Motivation

The network is an important resource in any Grid environments. If the network is a Grid
service, then it sho
uld be possible to inquire about this service with well
-
defined
interfaces. Web Services (and Grid Services) as described in the OGSI Specification can
be used to allow the Grid to access information on networks, network elements and
services.

NetherLight

Netherlight is an advanced optical infrastructure and proving ground for network services
optimized for high
-
performance applications.

Within NetherLight, we will focus on providing Web Services access to four of the
network elements in this network:

-

For
ce10 switch,;

-

GlimmerGlass Optical Cross Connect;

-

Catalyst 6509 switch;

-

Nortel HDXc (is this possible?)


Network elements virtualization

Our initial focus is to model and virtualize the various network elements in a re
-
usable
and general way.

We describe
any network element in terms of:

-

Properties, defined as long
-
lived or static information;

-

Services, defined as capabilities of the device;

-

Status, defined as the operational and transient information on the device.


We expect the client of the web se
rvices to inquire about the network element properties,
available services and status in a transparent way, without any predefined knowledge or
assumption about the network element being polled.

A scheme will describe the available data and information and

will be of the following
form:




Properties:

-

Description

o

Vendor

o

Setup (interfaces, blades)

o

List of available service (router or switch, photonic equipment)

-

Location

o

Physical location

o

Contact information

-

Topology

o

Closest network elements

-

L0 properties

-

L1

properties

-

L2 properties

o

Interfaces types

-

L3 properties

o

Management IP address

o

Management subnet number

o

Management subnet mask

o

Management address type


Services:

-

L0 services, if applicable

-

L1 services, if applicable

-

L2 services, if applicable

o

Available in
terfaces

o

VLANs

o

MTUs

-

L3 services, if applicable

o

IP MTU

o

Routing protocols

o

Autonomous system

Status:

-

L0 status, if applicable

o

dbLoss

-

L1 status, if applicable

o

Error counters

-

L2 status, if applicable

o

Spanning trees

o

Interface counters

o

Error counters

o

Packet rates

-

L3 status, if applicable

o

Default routes

o

Routing tables


Implementation

We have chosen to implement our Web Service infrastructure in Python, using the ZSI
package. ZSI provides an implementation of SOAP messaging in Python. We will
investigate the possibi
lity of using other server infrastructures (J2EE)

The server is <?>, a machine running <?>.


To do

Initial work is focused on:

-

the first XML schema, modeling network elements;

-

the first WSDL document describing access to the NetherLight Web Service;

-

the f
irst prototype, stress tested and benchmarked;

-

the first draft web page with instructions on how to use the service and how it has
been implemented.


Future possible work includes:

-

application of the network model to SURFnet6 infrastructure.

-

integrati
on of service within Grid infrastructure, making Grid application aware
of the network.

Documentation

More information can be found at: <URL>

Including instruction on how to poll our server.

References

OGSI (Open Grid Service Infrastructure) Primer

CIM (DM
TF)