The DDS User Manual v1.0
Contents
1. configuration file rl anar lxg0527 gsi de p24 tmp test 0 this is a comment r2 user 1xi001 gsi de home user dds 0 125 user2 host tmp test 322. f force key arg wrkpkg wrkscript rms sandbox dir user env script server info file Description The dds user defaults command can be used to get and set global DDS options It also can be used to get different static settings related to the current deployment Options h help Shows usage options v version Shows version information Np verbos Causes the command to verbose additional information and error messages P path Shows default DDS user defaults config file path d default Generates a default DDS configuration file f force If the destination file exists removes it and creates a new file without prompting for confirmation Can only be used with the d default options c config arg This options can be used together with other options to specify non default location of the DDS configuration file By default the command uses DDS DDS cfg key arg Gets a value for the given key from the DDS user defaults wrkpkg Shows the full path of the worker package The path must be evaluated before use wrkscript Shows the full path of the worker script The path must be evaluated before use rms sandbox dir Shows the full path of the RMS sandbox directory It returns server sandbox_dir if it is not empty otherwise server work_dir is returned The path must be evaluated before use user env script Shows the full path of user
3. filesini a a ia e ers feetee ts 9 7 2 Topology file example vic iio tU EE EEES E E EE 9 7 3 Topology XML tag TelerenCe iss concedes ssend esh cess GavSeeeds E Pr TE veo ASEE OS dda dsaqdssssbecsbeesuesssssetesd 12 8 HOW to Start ee TN 18 Sil Enyironmen t esaea td a rta dis 18 A O NO 18 8 3 Deploy ABeMmts lira Rinde 18 8 3 1 Deploy Agents using SSH plug in ooocccnccnnccnnconnconnconoconncnnncnnnnnnronoronccnnconnccnnccnncons 18 8 4 Ch ck availability of Agents ninio a a a E E Rican sas 18 SI SEL TODO ici A A A A AO EEE 18 8 6 Activate Agents oeaio reee r EEPE ES aE E sesvandd sea se asas goss baja NEOA EEEIEE EEEE usaseste esse eds 19 9 HOW to Testi a 20 OR First SECON cen r A E a td 20 LO LUTO A EE A AER OPER 21 101 Tutorial iii a a lana dan 21 LOU Usa nin aE E A EEE E EE S E EE 21 10 12 Result reisge e e tania Hos a E E E a a oa E E 21 10 2AT tornal Li A A A EEE E tk ie Ae ead E E EERS 21 A A O 22 10 22 Result isteir si cela ieedeeaats 22 1 Command line interlace iia Pi R A E d n 23 USES A A A AAA A EE A 24 ddS COMMANGET O ietoa dian R REENA AOS ARIN 25 dds user detaullts ii a eects ot 26 dds s biiit Ati dd E ve ante ire 27 AO A A ia 28 dd te daran ti En ots vod E E A E E 29 dds topolO fy imita id das 30 dds gent emd A shai saageatey ea sot E E ees daete gst bat age dates eebatvban E E E bh 31 12 SSH pl g in ci A A ad eens age A eetiates 32 1231 Resource definition sto lira ro E A A VAE EEEE A
4. s environment script for workers if present The path must be evaluated before use server info fil Shows the full path of the DDS server info file The path must be evaluated before use 26 Command line interface Name dds submimt submits and activates DDS agents UNIX Linux OSX Synopsis dds submit h help v version l c configarg r rms arg ssh rms cfg arg n number arg Description The command is used to submit DDS agents to allocate resources for user tasks Once enough agents are online use the dds topology command to activate the agents 1 e distribute user tasks across agents and start them Options h help Shows usage options V version Shows version information Cc configarg Only for advanced users This options can be used to specify the location of the dds submit configuration file rms arg Defines a destination resource management system At the moment only the SSH plug in is supported therefore arg should be equal to ssh or localhost ssh rms cfg arg Specifies an SSH plug in resource definition file n number arg It can only be used with localhost It defines how many agents to spawn If omitted then the default value will be used which is equal to a number of logical cores of a given host 27 Command line interface Name dds info can be used to query different kinds of information from DDS commander server UNIX Li
5. stop status Description Using this command users can start stop restart status DDS commander server The command is actually a wrapper for the dds commander command DDS commander server which become a daemon process when started Options start Start DDS commander server At the server start DDS will detect availability of DDS WN bin packages and download them from the DDS repository if they are missing Users can provide an additional parameter s the parameter can be specified with start and restart When the parameter is provided DDS will check availability of a binary package compatible with the local system only To build a binary package for the local system just issue make j wn_bin make j install restart Restart DDS commander server stop Stop DDS commander server status Request the status information It will show process id of the DDS commander server daemon and the TCP port it listens on 24 Command line interface Name dds commander manages DDS facility UNIX Linux OSX Synopsis dds commander h help v version start stop Description 0 Warning The command must not be used directly Please use the dds server command instead 25 Command line interface Name dds user defaults get and set global DDS options UNIX Linux OSX Synopsis dds user defaults h help l v version I V verbose l p path d default c config arg
6. task gt lt declcollection gt Parents collection group Children No 13 Topology Tag collection group main Description Attributes No Description Specifies the unique ID of the already defined task lt task gt taskl lt task gt Parents group Children No Attributes No Description Specifies the unique ID of the already defined collection lt COmMect lone CO lMmeeronl lt collkectlom Parents main Children task collection Attributes id n Description Declares a group lt group id groupl1 n 10 gt lt task gt task1 lt task gt lt collection gt collectionl lt collection gt lt collection gt collection2 lt collection gt lt group gt Parents topology Children task collection group Attributes id Description Declares a main group lt main id main gt lt task gt task1 lt task gt lt collection gt collectionl lt collection gt lt group id groupl1 n 10 gt lt task gt task1 lt task gt lt collection gt collectionl lt collection gt lt collection gt collection2 lt collection gt lt group gt 14 Topology Tag exe required env optional properties optional id required Description lt main gt Parents decltask Children No Attributes reachable Description Defines path to the executable or script for the task lt exe reachable true gt appl 1 n lt exe gt Parents declta
7. AAA raro nds 32 111 List of Tables 4 1 DDS configuration variables ssis ss 20 06 innatas va e aE E EER ses eds eS 4 TAL Topology XML TAE A ta Peds eye eases A So A 12 7 2 Topology XML attributes oserei eses reeperi pesona oS OEE easier EEEE EEUE crono OES 16 12 1 DDS s SSH plug in configuration fields ooooncnncnnccnnccnnccnnccnnconnconnccnnconnconnconncnnncnnncnnronaroncnnos 32 List of Examples 7 1 A topology file example 12 1 An example of an SSH plug in configuration file oconocnnccnnccnncnnoconnconccnnccnnccnnccnnconnconnconnconnss 1 Introduction 1 1 The Dynamic Deployment System 1 2 Features 2 Requirements 2 1 Server Ul DDS UI Server WN run on Linux and Mac OS X General requirements e Incoming connection on dds commander port configurable e aC 11 compiler e cmake 2 8 11 or higher e BOOST 1 54 or higher built by a C 11 compiler with C 11 enabled e shell BASH Additional requirements for SSH plug in e A public key access or password less via ssh agend for example to destination worker nodes 2 2 Workers General requirements e Outgoing connection on dds commander s port configurable This is required by dds agent to be able to connect to DDS commander server shell BASH 3 Download 3 1 Download location Please use DDS s Download page to get the latest version and all other versions of DDS 3 2 DDS Version Number Scheme DDS v
8. The DDS User Manual v1 0 The DDS User Manual v1 0 Table of Contents 1 Introduction tl privata le rita tetas 1 1 1 The Dynamic Deployment System ooooccnnconoconcconcconccnnonnncnnncnn cono ronnoronconncrnncnnncnnnrnnrnnnrcnncnnn 1 1 2 Features oee aea ied Covaas eave AA EEEE ORE ade E NACA RS TOASA RESTEN 1 Qi REQUIEM A A decida 2 2A Serve Uli A A tete PaaS 2 22y WOPK ELS A A A A Ata 2 3 Download viii ibi RARA ao PAT Es Toa a A AS AE A SES EENIA uD IA IO AE pa SPAA eed 3 31 Download Joc tiom eee e e EEE tetera bes eee ieee olen doe oeeo eee 3 3 2 DDS Version Number Scheme siessen an a E E sheesh dansa Pe tees 3 4 E E Laotian RAS eae 5 Bee Be Delon OBA Tee Sees 4 Alle Step 1 Get the SOULCE vacias corrio iia dbs diadema eescendssecoseaiaeosesus serves AVETS 4 4 1 1 from DDS git repository 2 0 cece cee EE EErEE E EEAS seca sean EE EREEREER OTE 4 4 1 2 from DDS source tarball sisone i A ara UNA E POON 4 4 2 Step 2 Configure the SOurce lt c vecsesesscun a a Ee Er E S ses covbecv codubesyeasereecdcdesavercessececess 4 4 3 Step 3 Build and install coccion ssroi iris enana sae ePasndebectesdbee sabes yeh roots Rss 3 4 4 Step 4 DDS Environment nearen yess ios dees sad TEENER ES EESE 5 4 5 Step 5 DDS shared Installation cussies a Sei bok cages eeoa a ee E a Eas 6 X Configurator e A Savane cade iets E EEn A AA ds 7 Id EE EE T EEA EA 8 SN Y e eE E EE E EE E EE A E EEE EE EASES 9 BAS Topology
9. able which can be used inside the topology file as variable_name lt a td varit eyalue Ur7a lee lt var Jd van2 value Vvalue2u gt Parents topology Children No Attributes id Description Declares a property lt property id propertyl gt lt property id property2 gt declrequirement Parents topology Children hostPattern Attributes id Description Declares a requirement for tasks and collections 12 Topology Tag hostPattern decltask declcollection task Description lt declrequirement id requirement1 gt lt hostPattern value gsi de gt lt declrequirement gt Parents declrequirement Children no Attributes value type Description Declares a pattern of the host name lt hostPattern type hostname value gsi de gt Parents topology Children exe env requirement properties Attributes id Description Declares a task lt decltask id task1 gt lt exe reachable true gt appl 1 n lt exe gt lt env reachable false gt envl lt env gt lt requirement gt requirement1 lt requirement gt lt properties gt lt id access read gt propertyl lt id gt lt id access readwrite gt property2 lt id gt lt properties gt lt decltask gt Parents topology Children task Attributes id Description Declares a collection lt declcollection id collection1 gt lt task gt task1l lt task gt lt task gt task1 lt
10. al treatment preprocessing on them So basically tasks can write anything into the values of properties 256 char max Any of depended tasks can set properties Anytime property is set it will be propagated to other depended tasks see for details TODO key value propagation Tip For example if one task needs to connect with another task they can have the same property A server task can store its TCP IP port and host in the property Once the property set DDS will notice that and propagate it to other tasks Tasks can be grouped into collections and groups Both collections and groups can be used to group several tasks The main difference between collections and groups is that a collection requests from DDS to execute its tasks on the same physical machine if resource allow that This is useful if tasks suppose to communicate a lot or they want to access the same shared memory A set of tasks and task collections can be also grouped into task groups Another difference between groups and collection is that only groups can define multiplication factor for all its child elements Main group defines the entry point for task execution Only main group can contain other groups 7 1 Topology file At the moment we use an XML based file to store topologies XML is chosen because it can be validated against XSD schema DDS s XSD schema file can be found in DDS_LOCATION share topology xsd lt topology id myTopology gt Definition o
11. arting the cmake command it is recommended to delete everything in the build directory recursively This will guaranty a clean build every time the source configuration is restarted 4 3 Step 3 Build and install Issue the following commands to build and install DDS make j make install Installation Prefix Please note that by default DDS will be installed in HOME DDS X Y Z where X Y Z is a version of DDS However users can change this behavior by setting the install prefix path in the bootstrap script BuildSetup cmake Just uncomment the setting of CMAKE_INSTALL_PREFIX variable and change dummy MY_PATH_HERE to a desired path y WN package Users have a possibility to additionally build DDS worker package for the local platform In case if you have same OS types on all of the target machines and don t want to use WN packages from the DDS binary repository just issue make j wn_bin make install the commands will build and install a DDS worker package for the given platform 4 4 Step 4 DDS Environment In order to enable DDS s environment you need to source the DDS_env sh script Change to your newly installed DDS directory and issue cd DDS INSTALL DIRECTORY source DDS_env sh You need to source this script every time before using DDS in a new system shell Simplify it by sourcing the script in your bash profile Installation Now the installation is done But if you were preparing a shared installation the
12. attern tag which attribute value can be either a full host name or a regular expression which matches the required host name t ype defines the type of the host Pattern Can be either hostname if the requirement is defined based on the host name or wnname if the requirement is defined based on the SSH worker node name In the next block we define tasks For this the decltask tag is used A task must also have the id attribute which is required and has to be unique for all declared tasks The requirement element is optional and specifies the already declared requirement for the task The exe element defines path to executable The path can include program options even options with quotes DDS will automatically pars the path and extractor program options in runtime The exe tag has an optional attribute reachable which defines whether executable is available on worker nodes If it is not available then DDS will take care of delivering it to an assigned worker in run time In case when there is a script that for example sets environment has to be executed prior to main executable one can specify it using the env element The env tag also have reachable attribute If a task depends on some properties this can de specified using the properties tag together with a list of id elements which specify ID of already declared properties Each property has an optional access attribute which defines whether user task will read read write write or both read an
13. can be found in DDS_ LOCATION tutorials tutoriall The source code of tasks is located in DDS_SRC_DIR dds tutorials dds tutoriall Files of the tutorial e task type one executable of the task TaskTypeOne e task type two executable of the task TaskTypeTwo e tutoriall_topo xml a topology file e tutoriall_hosts cfg a configuration file for DDS SSH plug in 10 1 1 Usage Before running the tutorial make sure that 1 Default working directory tmp dds_wn_test must exist before running the tutorial The directory can be changed in tutoriall_hosts cfg 2 SSH passwordless access to the localhost is required cd DDS_LOCATION tutorials tutoriall dds server start s dds submit r ssh ssh rms cfg tutoriall_hosts cfg dds topology set tutoriall_topo xml dds topology activate 10 1 2 Result To check the result change to tmp dds_wn_test If the default setup was used then there will be WN directories located wn wn_1 wn_2 wn_3 wn_4 wn_5 DDS catches output of tasks and saves it in log files under names task_name _ date_time _outlerr log For example TaskType0ne_2015 07 16 11 44 42_6255430612052815609_out log 10 2 Tutorial 2 This tutorial demonstrates how to use DDS custom commands for user task and for utility After DDS is installed the tutorial can be found in DDS_LOCATION tutorials tutorial2 The source code of tasks is located in DDS_SRC_DIR dds tutorials dds tutorial2 21 Tutorials File
14. d start user tasks stop Requests DDS to stop execution of user tasks Stop the active topology validate arg Validates topology file against DDS s XSD schema 30 Command line interface Name dds agent cmd send commands to agent UNIX Linux OSX Synopsis dds agent cmd h help l v version command command arg getlog arg a all update key arg key arg value arg Description This command allows to send commands to DDS agents Options getlog arg Download log files from all active workers a all Download all log files update key arg TODO KEY TODO value TODO 31 12 SSH plug in 12 1 Resource definition DDS s SSH plug in is capable to deploy DDS agents on any resource machine available for password less access public key ssh agent etc To define resources for the SSH plug in we use a comma separated values CSV configuration file Fields are normally separated by commas If you want to put a comma in a field you need to put quotes around it Also 3 escape sequences are supported Table 12 1 DDS s SSH plug in configuration fields 1 2 3 4 5 id must be any a host name with additional SSH a remote working RESERVED unique string or without a params could be directory login in a form empty This id string Jogin host fqdn is used just to distinguish different DDS workers in the plug in Example 12 1 An example of an SSH plug in
15. d write readwrite a property Default is readwrite Collections are declared using the declcollection tag It contains a list of task tags with IDs which specified already declared tasks Task has to be declared before it can be used in the collection As for the task collection has an optional requirement element which is used to specify the requirement for the collection If the requirement defined for both task and collection than collection requirement has higher priority and is used for deployment The main tag declares the topology itself In the example our main block consists of one task task1 one collection collection1 and two groups group and group2 A group is declared using the group tag It has a required attribute id which is used to uniquely identify the group and optional attribute n which defines multiplication factor for the group In the example group consists of one task task and two collections collection and collection2 group2 consists of one collection collection 1 Topology 7 3 Topology XML tag reference Table 7 1 Topology XML tags Tag topology var property Description Parents No Children property task collection main Attributes id Description Declares a topology lt topology id myTopology gt Laon Derio Or wees properties collections and SEQUDS arol lt topology gt Parents topology Children No Attributes id value Description Declares a vari
16. ersion has a form of MAJOR MINOR PATCH where e MAJOR the major number is increased when there are significant jumps in functionality e MINOR the minor number is incremented when only minor features or significant fixes have been added e PATCH represents a number of commits patches to a current major minor pair a The DDS s version scheme reflects the fact that DDS is both a production system and a research project DDS uses odd minor version numbers to denote development releases and even minor version numbers to denote stable releases 4 Installation DDS supports Private and Shared installations A Private Installation it is when a user installs DDS for individual usage in his her local folder Any Private Installation can be used by other users as well It s just a matter of file privileges A Shared Installation 1t is when a site administrator installs DDS in some central location so it can be shared by many users This type of installation may be convenient for some users since they don t need to install DDS by their own In case of a shared Installation you need to execute one additional step see Section 4 5 Step 5 DDS shared Installation All the rest is the same as with Private Installations Be advised that in both cases DDS acts identically and always provides private clusters one for each user In case of a shared installation users share only binaries and configurations but each user gets its ow
17. f tasks properties and collections lt main name main gt Definition of the topology itself where also groups can be defined lt main gt lt topology gt The file is basically divided on two parts declaration and main part All properties tasks and collections should be defined in the declaration part of the file Users can define any number of topology entities in that block even some which are not going to be used in the main block In the main block the topology itself is defined Groups and multiplication factors are also defined in main block 7 2 Topology file example Example 7 1 A topology file example lt topology id myTopology gt lt var id appNameVar value appl 1 n taskIndex StaskIndex collectionIndex co Topology lt var id nofGroups value 10 gt lt property id propertyl gt lt property id property2 gt lt declrequirement id requirement1 gt lt hostPattern type hostname value gsi de gt lt declrequirement gt lt decltask id task1 gt lt requirement gt requirement1 lt requirement gt lt exe reachable true gt S appNameVar lt exe gt lt env reachable false gt envl lt env gt lt properties gt lt id access read gt propertyl lt id gt lt id access readwrite gt property2 lt id gt lt properties gt lt decltask gt lt decltask id task2 gt lt exe gt app2 lt exe gt lt properties gt lt id access write g
18. inds of information from DDS For example you can check how many agents are already online dds info n or query more detailed info about agents dds info 1 8 5 Set Topology To assign a topology to your deployment use How to Start dds topology set FULL PATH _ TO YOUR_TOPOLOGY FILE 8 6 Activate Agents Once you get enough online agents you can activate them Activation of agents means that DDS will use the given topology to distribute user tasks across available resources agents dds topology activate DDS will automatically check whether available resources are actually sufficient to execute the given topology 19 9 How to Test XXXX 9 1 First Section XXXX 10 Tutorials 10 1 Tutorial 1 This tutorial demonstrates how to deploy a simple topology of 2 types of tasks TaskTypeOne and TaskTypeTwo By default there will be deployed one instance of TaskTypeTwo and 5 instances of TaskTypeOne Additionally TaskTypeTwo subscribes on key value property from TaskTypeOne which name is TaskIndexProperty Once TaskTypeTwo receives values of TaskIndexProperty from all TaskTypeOne it will set the ReplyProperty property Number of instances can be changed in the topology file tutoriall_topo xml using instances option of TaskTypeOne Please note that number of worker nodes in the SSH plugin configuration file tutoriall_hosts cfg has to be changed accordingly After DDS is installed the tutorial
19. n DDS instance and can t disturb other users Each user can tune DDS by changing the DDS user defaults configuration in SHOME DDS DDS cfg 4 1 Step 1 Get the source 4 1 1 from DDS git repository git clone https github com FairRootGroup DDS git DDS master 4 1 2 from DDS source tarball Unpack DDS tarball tar xzvf DDS X Y Z Source tar gz Tar will created a new directory DDS X Y Z Source where X Y Z represents a version of DDS 4 2 Step 2 Configure the source Change to the DDS source directory cd DDS X Y Z Source You can adjust some configuration settings in the BuildSetup cmake bootstrap file The following is a list of variables Table 4 1 DDS configuration variables Variable Description CMAKE_INSTALL_PREFIX Install path prefix prepended onto install directories default HOME DDS DDS_Version CMAKE_BUILD_TYPE Set cmake build type Possible options are None Debug Release RelWithDebInfo MinSizeRel default Release BUILD_DOCUMENTATION Build source code documentation Possible options are ON OFF default OFF Installation Variable Description BUILD_TESTS Build DDS tests Possible options are ON OFF default OFF Now prepare a build directory for an out of source build and configure the source mkdir build cd build cmake C BuildSetup cmake y e If for some reason for example a missing dependency configuration failed After you get the issue fixed right before st
20. n please see the Section 4 5 Step 5 DDS shared Installation as well 4 5 Step 5 DDS shared Installation TODO 5 Configuration TODO 6 Quick Start Download DDS source tarball e Install DDS from source cd DDS INSTALLATION source DDS _env sh dds server start dds submit rms localhost dds info n dds info 1 dds topology set SDDS_LOCATION tests tutoriall_topo xml dds topology activate Enable DDS environment Start DDS commander server Deploy DDS agents on the localhost Use dds info to find out a number of agents which are online Use dds info to check detailed information about agents Set a topology Activate run the previously defined topology 7 Topology The definition of the topology by the user has to be simple and powerful at the same time Therefore a simple and powerful so called topology language has been developed The basic building block of the system is a task Namely a task is a user defined executable or a shell script which will be deployed and executed by DDS on a given Resource Management System In order to describe dependencies between tasks in a topology we use properties In run time properties will be turned into simple key value pairs DDS uses its key value propagation engine to make sure that once property is set by one task it will be propagated to other depended tasks DDS treats values of properties as simple strings and doesn t do any speci
21. nux OSX Synopsis dds info h help v version commander pid status n agents number l 1 agents list Description The command can be used to query different kinds of information from DDS commander server Options commander pid Return the pid of the commander server status Query current status of DDS commander server n agents number Returns a number of online agents Iy agents list Show detailed info about all online agents 28 Command line interface Name dds test allows to test the running system UNIX Linux OSX Synopsis dds test t transport Description This command allows test the system after run Options t transport Performs transport test 29 Command line interface Name dds topology topology related commands UNIX Linux OSX Synopsis dds topology h help l v version I V verbose set arg disable validation l activate l stop l validate arg Description This command allows to perform topology related tasks Options h help Shows usage options v version Shows version information V verbos Causes the command to verbose additional information and error messages set arg Sets the given topology for the currently running DDS session disable validation Switches off topology validation activate Requests DDS to activate agents 1 e distribute an
22. rent ways In the definition of the executable path one can use special tags taskIndex and collectionIndex to get the task and collection index respectivley Before the task execution these tags are replaced with real values The second possibility is to get task and collection index from environment Two environment variables are defined for each task DDS_TASK_INDEX and DDS_COLLECTION_INDEX For each user task a set of environment variables is populated Populated environment variables e DDS_TASK_PATH full path to the user task for example main group1 collection_12 task_3 e DDS_GROUP_NAME ID of the parent group e DDS_COLLECTION_NAME ID of the parent collection if any e DDS_TASK_NAME ID of the task e DDS_TASK_INDEX index of the task e DDS_COLLECTION_INDEX index of the collection In the example above we define 2 properties property and property2 As you can see the property tag is used to define properties id attribute is required and has to be unique for all properties Requirements is another nice feature of DDS Requirements is a way to tell the DDS that a task or collection has to be deployed to a particular computing node As of now only host name or worker node name which is defined in the SSH configuration file requirements are supported Requirements are defined using declrequirement tag id attribute is required and has to be unique for all requirements Pattern of the host name is defined using hostP
23. s of the tutorial e task custom cmd user task which receives and send DDS custom commands e ui custom cmd utility which connects to DDS commander and send custom commands to user tasks e tutorial2_topo xml a topology file e tutorial2_hosts cfg a configuration file for DDS SSH plug in 10 2 1 Usage Before running the tutorial make sure that 1 Default working directory tmp dds_wn_test must exist before running the tutorial The directory can be changed in tutoriall_hosts cfg 2 SSH passwordless access to the localhost is required cd DDS_LOCATION tutorials tutorial2 dds server start s dds submit r ssh ssh rms cfg tutorial2_hosts cfg dds topology set tutorial2_topo xml dds topology activate ui custom command 10 2 2 Result To check the result change to tmp dds_wn_test If the default setup was used then there will be WN directories located wn wn_1 wn_2 wn_3 wn_4 wn_5 DDS catches output of tasks and saves it in log files under names task_name _ date_time _outlerr log For example TaskType0ne_2015 07 16 11 44 42_6255430612052815609_out log After executing ui custom command there will be an output to the console with receiving and sending custom commands Also check output files of tasks 22 11 Command line interface Command line interface Name dds server wraps to manage DDS commander server daemon UNIX Linux OSX Synopsis dds server start s restart s
24. sk Children No Attributes reachable Description Defines the path to script that has to be executed prior to main executable lt env reachable false gt setEnv sh lt env gt Parents decltask Children id Attributes No Description Defines a list of dependent properties lt properties gt lt id gt propertyl lt id gt lt id gt property2 lt id gt lt properties gt Parents properties Children No Attributes access Description Defines an ID of the already declared property lt id gt propertyl lt id gt 15 Topology Table 7 2 Topology XML attributes Attribute id reachable access Description Use required Default No Tags topology property decltask declcollection group main Restrictions String with minimum length of 1 character Description Defines identificator ID for topology propertiy task collection and group ID has to be unique within its scope i e ID for tasks has to be unique only for tasks lt topology id myTopology gt Use optional Default true Tags exe env Restrictions truelfalse Description Defines if executable or script is available on the worker node lt exe reachable true gt app 1 lt exe gt lt env gt envl lt env gt Use optional Default 1 Tags group Restrictions unsigned integer 32 bit which is more or equal to 1 Description Defines multiplication factor for group lt exe reachable true g
25. t app 1 lt exe gt lt env gt env1 lt env gt Use optional Default readwrite Tags id Restrictions readlwritelreadwrite 16 Topology Attribute type Description Description Defines access type from user task to properties lt id access read gt propertyl lt id gt Use required Tags hostPattern Restrictions hostnamelwnname Description Defines the type of the host pattern lt hostPattern type wnname value wn2 gt 17 8 How to Start 8 1 Environment In order to enable DDS environment you need to source the DDS_env sh script The script is located in the directory where you installed PoD cd DDS INSTALLATION source DDS_env sh 8 2 Server Use the dds server command to start stop status DDS servers dds server start 3 3 Deploy Agents In order to deploy agents you can use different DDS plug ins 8 3 1 Deploy Agents using SSH plug in DDS s SSH plug in is the best and the fastest way to deploy DDS agents When you don t have an RMS or you want to use a Cloud based system or even if you want just to use resources around you like computers of your colleagues then the plug in is the best way to go First of all you need to define resources Then use dds submit to deploy DDS agents on the given resources dds submit rms ssh ssh rms cfg FULL PATH TO YOUR_SSHPLUGIN_RESOURCE_ FILE 8 4 Check availability of Agents Using dds info you can query different k
26. t propertyl lt id gt lt properties gt lt decltask gt lt declcollection id collection1 gt lt requirement gt requirement1 lt requirement gt lt tasks gt lt id gt task1 lt id gt lt id gt task2 lt id gt lt id gt task2 lt id gt lt tasks gt lt declcollection gt lt declcollection id collection2 gt lt tasks gt lt id gt task1 lt id gt lt id gt task1 lt id gt lt tasks gt lt declcollection gt lt main id main gt lt task gt task1 lt task gt lt collection gt collectionl lt collection gt lt group id groupl n S nofGroups gt lt task gt task1 lt task gt lt collection gt collectionl lt collection gt lt collection gt collection2 lt collection gt lt group gt lt group id group2 n 15 gt lt collection gt collectionl lt collection gt lt group gt lt main gt lt topology gt DDS allows to define variables which later can be used inside the topology file During the preprocessing all variable are replaced with their values Variables are defined using the var tag which has two attributes id and 10 Topology value Inside the file variable can be used as follows variable_name In the above example we define two variables appNameVar and nofGroups When a particular task or collection is multiplied sometimes it is necessary for the user to get the index of the task or collection instance This can be done in two diffe
Download Pdf Manuals
Related Search