Main Menu

Project Life Cycle

BoD_Service_requirements_to_cNIS.doc

BoD Service requirements and use cases for cNIS

Author: Maciej Łabędzki <labedzki@man.poznan.pl>

 

Date

Authors

Remarks

2012-06-22

Maciej Łabędzki

Update: requirements to adjusting GUI to autobahn needs

2012-06-05

Maciej Łabędzki

Update triggered by cNIS 3.1 release

2012-04-03

Maciej Łabędzki

Reference to "topology notifications" design document

2012-03-05

Maciej Łabędzki

Update according to AutoBAHN-cNIS Y4 Kickoff meeting agreements

2012-02-02

Maciej Łabędzki

Update – meeting with AutoBAHN Leader Radek Krzywania

2011-05-17

Maciej Łabędzki

New use cases from AutoBAHN, Jacek Ł. (PSNC)

2011-05-12

Maciej Łabędzki

New use case from Anand Patil (DANTE)

2011-04-21

Maciej Łabędzki

New use cases from AutoBAHN team

2009-09-16

Maciej Łabędzki

First requirements gathered from AutoBAHN’s development team.


Table of contents:

BoD Service requirements and use cases for cNIS               1

1               Requirements               3

1.1               [done] Managing links to external domains               3

1.2               [done] Distinguishing different kinds of external domains               3

1.3               List of external domains loaded from server               4

1.4               Notifying AutoBAHN about topology changes               4

1.5               Adjusting data model and GUI to specific needs of AutoBAHN               4

1.6               cNIS installer integrated with AutoBAHN               5

1.7               cNIS API for generating network diagrams and maps               5

1.8               [done] Network discovery should not destroy partitioning data               6

1.9               Partition i ng in MPLS               6

1.10               Pruning in AutoBAHN Service is no longer needed               7

1.11               Adjusting MPLS tab to AutoBAHN needs               7

1.12               Template for new requirement               8

 

 

 

1          Requirements

1.1           [done] Managing links to external domains

Status

Priority (1-5)

Reporter

Request date

Last update

Done

 

AutoBAHN

2009-07-27

 

 

 

 

Description

It should be possible to define (and manage) links to external domains. As cNIS stores information about network topology of a single administrative domain it should be possible to specify what links are connecting that domain with other ones.

The link should be described by following attributes: bandwidth, vlan, end port, external domain identifier.

Remarks

to be implemented before 2009-09-30

References

 

1.2           [done] Distinguishing different kinds of external domains

Status

Priority (1-5)

Reporter

Request date

Last update

Done

 

AutoBAHN

2009-07-27

 

 

 

 

Description

AutoBAHN needs to distinguish links to other AutoBAHN-enabled domains and so-called customer domains.

Remarks

To be implemented before 2009-09-30

The implemented solution is based on ‘key-value attributes’ idea.

References

 

1.3           List of external domains loaded from server

Status

Priority (1-5)

Reporter

Request date

Last update

Open

1

Jacek, Kostas

2009-07-27

2012-03-05

 

 

 

Description

List of cNIS neighbour domains (and their edge interfaces/ports) could be retrieved from some central server (like AutoBAHN Lookup Service). Domains retrieved automatically could be available to choose when defining a link to external domain (see 2.1 ).

The list should be updated every time new external domain link is added.

Remarks

 

References

 

1.4           Notifying AutoBAHN about topology changes

Status

Priority (1-5)

Reporter

Request date

Last update

In progress

5

AutoBAHN

2011-04-19

 

 

 

 

Description

cNIS should inform AutoBAHN about changes in stored network topology. It should be diff-like notification.

Remarks

 

References

LLDD_notifications_about_topology_changes.docx

1.5           Adjusting data model and GUI to specific needs of AutoBAHN

Status

Priority (1-5)

Reporter

Request date

Last update

Open

5

AutoBAHN

2011-04-19

2012-06-15

 

 

 

Description

GUI layout needs to be reorganized because it’s not as much intuitive as needed.

The ‘AutoBAHN’ tab shouldn’t be present any more and its functionality should be still accessible.

AutoBAHN needs different names for selected fields than cNIS currently uses. For example, the ‘businessID’ field in EthPhysicalPort should be called ‘MAC address’.

Ability to create custom fields (like in Atlassian JIRA) and specify the field’s value type.

Defining VLANs in form of ranges.

Some GUI elements should be moved to different locations/places.

There are many fields (and even tabs) that are useless for AutoBAHN. They need to be removed.

Remarks

Precise reqs are defined in the document referenced below. What about issues listed above?

References

“Adjusting GUI to AutoBAHN needs - requirements” document

1.6           cNIS installer integrated with AutoBAHN

Status

Priority (1-5)

Reporter

Request date

Last update

Open

4

AutoBAHN

2011-04-19

 

 

 

 

Description

AutoBAHN and cNIS installed with use of a single installation pack.

Remarks

It’s not clear if AutoBAHN needs a single installer for both (AB and cNIS) or not. To be discussed.

References

 

1.7           cNIS API for generating network diagrams and maps

Status

Priority (1-5)

Reporter

Request date

Last update

Open

 

AutoBAHN

2011-04-19

2012-03-05

 

 

 

Description

AutoBAHN sends a parameterized request to cNIS for generating a visualization of a network with highlighted elements.

For example, AutoBAHN client portal embeds cNIS network map component.

Ability to specify which elements on a map should be highlighted.

Ability to specify short text information to be presented near a specified element(s).

Presentation of ports/interfaces on the map/diagram for highlighted nodes.

Remarks

More details needed (technical and user stories)

References

 

1.8           [done] Network discovery should not destroy partitioning data

Status

Priority (1-5)

Reporter

Request date

Last update

Done

5

Anand Patil (DANTE – the AutoBAHN deployee)

2011-04-01

 

 

 

 

Description

For example, when a node already existing in cNIS database is discovered again and saved into the cNIS database again the partitioning data should not be lost. This relates to all elements that partitioning functionality is available for.

Remarks

 

References

https://issues.geant.net/jira/brows e / CNIS-765

1.9           Partitioning in MPLS

Status

Priority (1-5)

Reporter

Request date

Last update

In progress

 

Jacek Łukasik (PSNC)

2011-05-13

2012-06-05

 

 

 

Description

As AutoBAHN application downloads a whole topology information from cNIS no further filtering is needed.

Remarks

 

References

 

1.10       Pruning in AutoBAHN Service is no longer needed

Status

Priority (1-5)

Reporter

Request date

Last update

In progress

1

Jacek Łukasik (PSNC)

2011-05-17

 

 

 

 

Description

As AutoBAHN application downloads a whole topology information from cNIS no further filtering is needed.

Remarks

Pruning is a piece of functionality requested by AutoBAHN team in GN2.

References

 

1.11       Adjusting MPLS tab to AutoBAHN needs

Status

Priority (1-5)

Reporter

Request date

Last update

Open

1

Radek Krzywania (PSNC)

2012-02-02

 

 

 

 

Description

Rename “Tunnels” to “LSPs/Tunnels”

Remarks

To be completed

References

 

1.12       Template for new requirement

Status

Priority (1-5)

Reporter

Request date

Last update

 

 

 

 

 

 

 

 

Description

 

Remarks

 

References