Mdi naming convention, Services naming convention, Mdi naming convention services naming convention – Grass Valley NewsBrowse Desktop Browsing System Installation v.2.0 User Manual
Page 32: Chapter 3 configuring the newsbrowse system

32
NewsBrowse Installation and Configuration Guide
25 May 2004
Chapter 3 Configuring the NewsBrowse System
MDI naming convention
You should use a consistent naming convention for the Managed Device Interfaces
(MDIs) in the system. The NewsBrowse system manages a device through an MDI.
Each type of device has its own MDI. The MDI software component usually is not
hosted on the same machine that it manages, so is it helpful to be able to differentiate
between the name of the MDI, the name of the machine that hosts the MDI, and the
name of the device the MDI manages. The following table illustrates a suggested
convention.
Services naming convention
Similar to MDIs, you need to have a naming convention for the Ingest Control service
and the Proxy Transfer service. These services run on encoders, but they need their
own name for configuration purposes, so is it helpful to be able to differentiate
between the configured name of the service, and the host (table) name of the encoder
on which the service runs. The following table illustrates a suggested convention.
MDI type
MDI name(s)
Comments
Proxy
PROXY1
There is but one Proxy MDI in the system. It manages the
storage locations on all the NAS machines.
Profile
SAN1
Manages the one designated Profile on an Open SAN
PROFILE1, PROFILE2,
PROFILE3,…
Manages a stand-alone Profile system. Enumerate in parallel
with the machine naming convention.
NTFS
NTFS1
There is but one NTFS MDI in the system. It manages NTFS
storage on one or more machines—typically the server and the
NAS machines.
Avalon Archive
ARCHIVE1
Manages the Avalon device
Service type
Service name(s)
Comments
Ingest Control
INGEST_CH1, INGEST_CH2,
INGEST_CH3
The Ingest Control service runs on single-channel
encoders. Enumerate in parallel with the host (table)
names of the encoders.
Proxy Transfer
SCAVENGE1, SCAVENGE2,
SCAVENGE3
For Proxy Transfer service running on sequential
encoders, use this naming convention. Enumerate in
parallel with the host (table) names of the encoders.
ISS1, ISS2, ISS3
For Proxy Transfer service running on Image Support
Servers, use this naming convention. Enumerate in
parallel with the host (table) names of the Image Support
Servers.