Creation of CVS repository for CrossGrid project proposal - PowerPoint PPT Presentation

1 / 36
About This Presentation
Title:

Creation of CVS repository for CrossGrid project proposal

Description:

... repository for CrossGrid project - proposal. Robert Pajak. ympajak_at_cyf-kr.edu.pl ... Powerful CS-RCS implements the major requirements of version control and ... – PowerPoint PPT presentation

Number of Views:104
Avg rating:3.0/5.0
Slides: 37
Provided by: admi1681
Category:

less

Transcript and Presenter's Notes

Title: Creation of CVS repository for CrossGrid project proposal


1
Creation of CVS repository for CrossGrid project
- proposal
  • Robert Pajak
  • ympajak_at_cyf-kr.edu.pl
  • ACK Cyfronet

2
Contents
  • CVS short description
  • CVS Server
  • CVS GUI clients
  • Other revision control systems
  • CS-RCS
  • EDMS
  • Proposals of CrossGrid Repository Architecture

3
Possible software configurations
  • CVS CVS GUI Client
  • CVS CVS Web Client
  • CS-RCS (Component Software Revision Control
    System)
  • EDMS (Engineering Data Management System)

4
CVS Concurrent Versions System
  • The dominant open-source network-transparent
    version control system.
  • Useful for everyone from individual developers to
    large, distributed teams
  • its client-server access method lets developers
    access the code from anywhere there's an Internet
    connection,
  • its client tools are available on most platforms.

5
CVS CVS GUI Client
  • CVS GUI clients exist for many platforms
  • WinCvs for Windows
  • MacCvs for MacOs
  • gCVS for Unix
  • Available at http//www.wincvs.org

6
WinCvs - Screenshot
7
CVS CVS Web Client
  • It allows users to edit files in a CVS
    repository, using only a web browser.
  • Available at http//stud.fh-heilbronn.de/zeller/c
    gi/cvsweb.cgi/

8
CVS Web Client - Screenshot
9
CS-RCS (Component Systems-RCS)
  • Based on the widely used GNU RCS,
  • Fully integrated with the Windows Explorer,
  • Provides the most intuitive and easy-to-use
    configuration management and change control
    solution in the market,
  • Supports multi-platform workgroups, making it the
    ideal solution for sites that share common files
    on UNIX and Windows platforms.

10
CS-RCS - continued
  • Handles all types of documents including
  • program files,
  • project files,
  • resource files,
  • HTML documents,
  • MS-Word documents,
  • pictures and drawings.

11
CS-RCS - continued
  • Uses any file server or local drive to store the
    archive repository.
  • Network connection to the archive repository can
    be LAN, corporate wide-area network (WAN),
    dial-in connection (RAS) and the Internet.

12
CS-RCS - Integration with Windows tools
  • CS- RCS is fully integrated with MS-Word
  • There is a special menu entry - RCS - which will
    be added to MS-Word. Integration is automatic
    when CS-RCS is installed.
  • All features can be accessed from MS-Words
    toolbar, making CS-RCS part of users everyday
    desktop.
  • Whenever a document is checked-in, CS-RCS updates
    MS-Word internal variables. It enables displaying
    the accurate revision number of important
    documents.

13
CS-RCS - Integration with Windows tools
(continued)
  • CS-RCS implements the Microsoft Common Source
    Code Control API. (Also called the SCC API or
    SCCI.) This API enables seamless integration of
    CS-RCS with many development tools for Windows,
    including
  • Microsoft Visual Studio products (including
    Visual C and Visual Basic)
  • CA Visual Objects
  • Allaire ColdFusion

14
CS-RCS - Integration with Windows tools
(continued)
  • Sybase PowerBuilder
  • Rational Rose
  • VisualAge for Java
  • MERANT Micro Focus Net Express
  • Forté C Application Environment
  • Programmers editors Multiedit, Codewright, Zeus
  • Bug Tracking Tools SeapineTestTrack

15
CS-RCS - Change Synchronisation Methods
  • Exclusive locking model - All work files are
    read-only. A user must lock the file in order to
    edit it. When the user check-in the changes, he
    must unlock the file in order to enable other
    users to edit it.
  • Concurrent changes model (CVS) - All users may
    always edit all files. When a file is checked in,
    CS-RCS merges the edits automatically into the
    repository. In case of conflicts, CS-RCS
    highlights them to assist the user in solving
    these conflicts.

16
CS-CVS - Windows front-end for the GNU CVS
  • The CS - CVS (Component Software - CVS) solution
    consists on two products
  • CS-RCS which provides full support for local RCS
    and CVS repositories. This version supports local
    CVS repositories.
  • CS-CVS which is an add-on product for CS-RCS.
    CS-CVS provides support for the CVS client-server
    architecture. (That is, the pserver, ntserver,
    rsh and ssh protocols.)

17
CS-CVS - Windows front-end for the GNU CVS
(continued)
  • CS-CVS add-on should be used to
  • Access remote repositories over corporate network
    or the Internet.
  • Gain better security on access to repository
    files.
  • Access legacy CVS repositories.

18
CS-RCS - Conclusion
  • The major benefits of CS-RCS
  • Powerful CS-RCS implements the major
    requirements of version control and configuration
    management systems.
  • Simple CS-RCS is simple to learn and easy for
    daily use. There are no daily administrative
    operations which require a full-time system
    administrator.
  • Unlimited There is no limit to the number of
    users, projects, files or revisions. The only
    limit is the repository server disk space.

19
CS-RCS - Conclusion (continued)
  • Reliable Over 20,000 users in more than 2000
    large and small organisations in 30 countries
    have been using CS-RCS since its first release
    in 1997.
  • True Open System The archive files are stored
    using the public GNU RCS format. This format can
    be imported by a majority of tools in today's
    market.

20
CS-RCS - Screenshot
21
EDMS - major subsystems
EDMS Web
User Interfaces
EDMS Common layer
CADIM/EDB
CDD
MP5
Data Management Systems
22
EDMS - major subsystems -continued
  • EDMS - Engineering Data Management System
  • CDD - CERN Drawing Directory application - a WWW
    utility for management of graphical documents
    (drawings)
  • CADIM / EDB and MP5 - two commercial
    applications using the Oracle database system

23
EDMS - Documents Management
  • Document Definition
  • Managing Document in a Structure
  • Document Lifecycle Release Procedures, Versioning

24
EDMS - Document attributes
Project Document number
Title
Status
EDMS internal ref.
Author(s)
File(s)
Date
Document type
25
EDMS - Document Search
  • Search mechanism allows a user to search for any
    text document or drawing in any project or only
    in a specific project using
  • number
  • title, abstract, keyword
  • authors
  • document type
  • year, modification date
  • status.

26
EDMS - Document Search Screenshot
27
EDMS - Structures
These structure nodes are called Projects in the
EDMS.
When the amount of data grows, it is convenient
to structure the documents. This has several
advantages - It is easier to find documents
(structure document meta data gives lots of
search possibilities) - It is possible to group
documents that are logically linked.
28
EDMS - Managing document in the structure
29
EDMS - Release procedures
  • Release procedure defines
  • possible document statuses,
  • possible transitions and required user privileges.

30
EDMS - Release procedures Screenshot
31
EDMS - Example of a Document Release Procedure
Released - Approved
32
CrossGrid Repository Architecture Proposal (1)
  • First solution
  • Local repository servers for each software module
    and documents
  • Central server in Karlsruhe (mirror of all local
    repositories software documents)
  • CVS server in Cyfronet (mirror of Karlsruhe
    repository software documents)

33
CrossGrid Repository Architecture Proposal (2)
  • Second solution
  • One central repository server in Karlsruhe for
    all software modules and documents (without local
    repositories)
  • CVS server in Cyfronet (mirror of Karlsruhe
    repository software documents)

34
CrossGrid Repository Architecture Proposal (3)
  • Third solution
  • Local repository servers for each software module
    and documents
  • Central server in Karlsruhe (mirror of all local
    repositories software documents)
  • Documents Repository in Cyfronet (all
    deliverables, reviews, minutes, etc. without
    software source codes) access through CrossGrid
    WWW sites.

35
CrossGrid Repository Architecture Proposal (4)
  • Other solutions - discussion

36
References
  • Presentations
  • CVS - Proposal of using Control Version System
    for CrossGrid project, Kick-off meeting, Poznan,
    29th-30th January 2002 Marcin Plóciennik
  • Presentation of CERN EDMS at LAPP, 28.02.2001,
    Elena Manola Poggioli CERN/EST Vincent Boninchi
    IN2P3
  • Links
  • http//www.wincvs.org
  • http//stud.fh-heilbronn.de/zeller/cgi/cvsweb.cgi
    /
  • http//www.componentsoftware.com/
  • http//cedar.web.cern.ch/CEDAR/tuto.html
Write a Comment
User Comments (0)
About PowerShow.com