CTSS_4_functional_spec.docx - TeraGrid Forum

perchmysteriousΔιαχείριση Δεδομένων

30 Νοε 2012 (πριν από 4 χρόνια και 7 μήνες)

172 εμφανίσεις

CTSS
4
User Info
Functional Spec
ification

CTSS

4

Documentation

Section of TeraGrid User Support

This section will replace the pages currently based at /userinfo/software/ctss.php on the TeraGrid public
Web site. The page group will consist of a main page,

two input pages, and results displays.

The

purpose
of
these pages is to help
users
easily
locate

and use

CTSS resources on the
TeraGrid. The
pages will
support both

new
and
returning users
,
to assist in
creating proposals
as well as
running jobs
.

Users s
hould be able to

easily find
:



software

b
ased on

use case scenario
s



documentation of

CTSS
software packages



resources on the TeraGrid
together with

the software and tasks they support

Users will be able to find computing tools installed on TeraGrid

resource
s, using searches by
:



Kit/Capability



Task/Use Case



Software Package

It
will be

easy to locate
the detailed User Support

documentation on CTSS

software
from

this
section
, as
well as to find tools and resources
using

either the use case
-
based

or the resource
-
based perspective
.
The
section

will present
some
fixed

views, and

offer

filter
s

to generate
more focused results
. At a glance,
users will be able t
o see the entire scope of CTSS

on the TeraGrid from both
the hardware and software
perspective
s
.

The
section
will also be a jumping off point for related services such as Inca, HPC Software
documentation, the Resource Catalog, and other services

to meet the needs of users writing proposals
.

Functional Component Diagram

The following diagram shows the elem
ents of the TeraGrid User Support CTSS 4 Web site
documentation section that are necessary to implement the objectives stated above.


CTSS 4 Main Page

This
will be

the
primary

page for CTSS documentation on
the
TeraGrid User Support

Web site
. It will
hav
e
four

sections:

top,
lower

left
,

lower center,
and
lower

right
. The top section will describe CTSS in
general, very brief terms to help the users determine if they are on the right page. The left and
center

lower sections will present

view options and inp
ut controls for accessing all CTSS documentation.
These

will give

users
multiple
ways to
access
CTSS assets on the TeraGrid,
supporting selection
s

based on

both
resource
s

and usage scenario
s
.

The mockup for this page is located at:

http://dev.teragrid.org/userinfo/software/ctss_new.php

The

page will be styled like the other User Support

overview pages, with a common top banner and
menu navigation
.
Within the page content area, there will be
a descriptive text section
above
,
and
three
columns below
, with
User Support
-
styled
column

headings
. The left column will
contain
select lists for

two
resource
-
oriented

results pages
,
the center
column will
conta
in links to four
interface
s

for views
driven by user needs
, and the right column will contain links to related pages and information.

CTSS Overview
Section
(top of
content area
)

This section
gives a very brief introduction to CTSS version four
.
It will
describe how the features

of this
section of the TeraGrid User Support site

can be used
,

and
it will
orient users to the rest of the interface.

It will be brief enough that a typical
user

will see the lower sections without scrolling.

View CTSS by Resource

(left
lower
third of
content area
)

Option
1


View

Capability Kits

This feature allows users to select one or more TeraGrid resources and view the kits installed on each.
The results will be grouped by site.

A select list
will present users with

all platforms and sites
. U
sers can
choose multiple items from the list by
holding the

control key.

The r
esult
s

page will be a table
of all Capability Kits as rows and the
selected sites as columns, showing
status of the kit on each platform. This could be

a WebMDS
result

wrapped in the TG User Support style,
so that expansion to
display

software could be included in this view.

That comes by default on the
WebMDS pages such as:


http://mds.teragrid.org:8080/webmds/webmds?info=tgisinfo&xsl=kitsregistration

K
it descriptions will also be presented
on this result page
, as the right
-
most column.
These descriptions

should be
brief
enough to fit in the table without forcing large whitespace areas in the other rows.

As
part of each kit row, a set of tasks will be li
sted beneath it.

Option

2


V
iew
A
ll
S
oftware

This feature
uses the same select list for input as
Option

1
.

The results page
allows

three groupings: by Compute Resource, by Kit, and by Site. Each Kit row in the
result will have a set of sub
-
rows containing

all the software packages that are part of that kit, and the
status of each package will be shown in the column of each selected resource.

Find Resources by Software

(
center

lower

third

of
content area
)

This feature supports the selection of resources bas
ed on software needs. It will provide four input
options: Kit/Capability, Task/Use Case, Software, and All Combined.
Each choice from this section will
navigate to an interface to select the criteria for that result.

The results page

present
s

the

set of re
sources
having
all the requested parameters
. This will help them
determine

where to
request
an allocation or where to run a job, for example.

Option 1



F
ind
R
esources
by Kit/Capability

The first option will be the most general, f
or

selecting at the Capability/Kit level. Users can select any or

all kits in CTSS 4. The results page will be a list of all resources that have those kits implemented.

Option 2


Find Resources by Task/Use Case Scenario

The second selection screen will pres
ent all the tasks or use case scenarios, which are subsets of each
kit, and allow users to choose use cases as the factor determining what platforms to display in the
result. Multiple
tasks

can be chosen
, from multiple kits, and the result will be platform
s that support all
of the selected tasks.

Option
3



Find Resources by Software Package

The third option will be
based on the
software package, allowing users to pick software from a list and
result in a display of all platforms that have the package insta
lled.

Option
4



Find Resources by Kit, Task, or Software

The fourth option will be a combination of all three of the above, using a hierarchical grouping by Kit,
Task, and Software. This interface

will present everything that exists in CTSS 4 on a single
form
,
with
each item as
a checkbox. Options
can be mixed and matched at will. The result will again be only the set
of platforms that supports all of the choices.

More Information Section

(right lower third of content area)

This part contains direct links
to many related internal and external CTSS documentation and tools, such
as the CTSS Kit Definitions,
user environment setup documentation, software, the Resource Catalog,
Inca, and CTSS version history.

CTSS 4 Backend Support

CTSS 4 uses the Monitoring and Discovery Service (MDS) to publish current availability and status
information of its components. The TeraGrid CTSS Web site section will be able to retrieve data from
MDS and display it to the user, based on predefined reque
sts and input from the user interfaces. Since
MDS queries are slow by Web page display standards, a cache mechanism may be used to store data in
a high
-
availability location. Changes to MDS content will be infrequent, so a very high percentage of the
views

should be completely accurate regardless of when they occur in relation to a cache update.
Further, cache updates could be maintained at a frequent enough rate that users would virtually never
see out
-
of
-
date views due to cache latency.

One possible long
term cache mechanism would use a PostgreSQL relational database in the TeraGrid
Central Database (TGCDB). A refresh program would be written to update the database with a timed
procedure, and

the CTSS

section pages would access this data via PostgreSQL que
ries.

Database and MDS Data Structure

This diagram shows the data available from MDS that will be accessible from these

documentation
pages, and relations among the elements returned in MDS queries.




User Support pages accessing this data cache would us
e the familiar query interface already in use on
many related pages, including those for the Resource Catalog. One possible schema for the MDS Kit
structures would look like this:



Resource

o

ResourceID

o

SiteID



Kit

o

KitID



Software

o

SoftwareID



Service

o

ServiceID

T
he Resource Primary Key would be this field:



ResourceID


The Kit Primary Key would include these fields:



ResourceID



(kit)Name



(kit)Version


The Kit Software Primary Key would include these fields:



ResourceID



(kit)Name



(kit)Version



(Software)Name



(Software)Version


The Kit Service Primary Key would include these fields:



ResourceID



(kit)Name



(kit)Version



(Service)Name



(Service)Version

Mapping Between TGCDB Resource Catalog and MDS Data

Regardless of whether a database is used for the MDS cache or no
t, some kind of mapping must be
designed and maintained to correlate MDS information with the Resource Catalog, specifically between
the MDS RESOURCEID and the resource_id in the user_services.resources table. Similarly, a mapping
must be generated between

the MDS SiteID and the existing institution_id in the
user_services.institutions table.

Additional data input fields must also be added to the Resource Catalog Admin Interface to support
information that is not provided by MDS but needed in the documentat
ion. This includes narrative kit
descriptions, page content titles, and URLs for detailed documents.