simgrid-doc 3.14.159-2 / usr / share / doc / simgrid / html / deployment.html

This file is indexed.

/usr/share/doc/simgrid/html/deployment.html is in simgrid-doc 3.14.159-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<title>SimGrid: Deploy the simulation</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="navtree.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="resize.js"></script>
<script type="text/javascript" src="navtreedata.js"></script>
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
  $(document).ready(initResizable);
</script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/searchdata.js"></script>
<script type="text/javascript" src="search/search.js"></script>
<script type="text/javascript">
  $(document).ready(function() { init_search(); });
</script>
<script type="text/x-mathjax-config">
  MathJax.Hub.Config({
    extensions: ["tex2jax.js"],
    jax: ["input/TeX","output/HTML-CSS"],
});
</script><script type="text/javascript" src="/usr/share/javascript/mathjax/MathJax.js/MathJax.js"></script>
<link href="stylesheet.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
 <tbody>
 <tr style="height: 56px;">
  <td style="padding-left: 0.5em;">
   <div id="projectname">SimGrid
   &#160;<span id="projectnumber">3.14.159</span>
   </div>
   <div id="projectbrief">Versatile Simulation of Distributed Systems</div>
  </td>
 </tr>
 </tbody>
</table>
</div>
<div id="navrow1" class="tabs">
    <ul class="tablist">
      <li><a href="http://simgrid.gforge.inria.fr/"><span>Home page</span></a></li>
      <li><a href="http://simgrid.gforge.inria.fr/documentation.html"><span>Online documentation</span></a></li>
      <li><a href="javadoc"><span>Java documentation</span></a></li>
      <li><a href="https://gforge.inria.fr/projects/simgrid"><span>Dev's Corner</span></a></li>
      <li>        <div id="MSearchBox" class="MSearchBoxInactive">
        <span class="left">
          <img id="MSearchSelect" src="search/mag_sel.png"
               onmouseover="return searchBox.OnSearchSelectShow()"
               onmouseout="return searchBox.OnSearchSelectHide()"
               alt=""/>
          <input type="text" id="MSearchField" value="Search" accesskey="S"
               onfocus="searchBox.OnSearchFieldFocus(true)" 
               onblur="searchBox.OnSearchFieldFocus(false)" 
               onkeyup="searchBox.OnSearchFieldChange(event)"/>
          </span><span class="right">
            <a id="MSearchClose" href="javascript:searchBox.CloseResultsWindow()"><img id="MSearchCloseImg" border="0" src="search/close.png" alt=""/></a>
          </span>
        </div>
</li>
    </ul>
  </div> 
<!-- end header part -->
<!-- Generated by Doxygen 1.8.13 -->
<script type="text/javascript">
var searchBox = new SearchBox("searchBox", "search",false,'Search');
</script>
</div><!-- top -->
<div id="side-nav" class="ui-resizable side-nav-resizable">
  <div id="nav-tree">
    <div id="nav-tree-contents">
      <div id="nav-sync" class="sync"></div>
    </div>
  </div>
  <div id="splitbar" style="-moz-user-select:none;" 
       class="ui-resizable-handle">
  </div>
</div>
<script type="text/javascript">
$(document).ready(function(){initNavTree('deployment.html','');});
</script>
<div id="doc-content">
<!-- window showing the filter options -->
<div id="MSearchSelectWindow"
     onmouseover="return searchBox.OnSearchSelectShow()"
     onmouseout="return searchBox.OnSearchSelectHide()"
     onkeydown="return searchBox.OnSearchSelectKey(event)">
</div>

<!-- iframe showing the search results (closed by default) -->
<div id="MSearchResultsWindow">
<iframe src="javascript:void(0)" frameborder="0" 
        name="MSearchResults" id="MSearchResults">
</iframe>
</div>

<div class="header">
  <div class="headertitle">
<div class="title">Deploy the simulation </div>  </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><p>When you want to simulate the behavior of your code with SimGrid, you need to tell SimGrid exactly what code (that you wrote) is supposed to be run by which host - so you need to assign processes/functions to hosts. The hosts in question here are the hosts of your platform model; see Section <a class="el" href="platform.html">Describing the virtual platform</a> for details on how to set one up.</p>
<p>This assignment of the form <code>code</code> -&gt; <code>host</code> is what the deployment file is all about, which will be discussed briefly here.</p>
<dl class="section note"><dt>Note</dt><dd>You can bypass the deployment file by hardcoding it in your user code, at least when you're using MSG.</dd></dl>
<p>The deployment file looks just like a <a class="el" href="platform.html">platform</a> file, except that in this case, only two different tags are used: <code>process</code> and <code>argument</code>, whereas the latter is just used to supply additional configuration options to the process; the order in which the <code>argument</code> tags are given is important and depends on the application.</p>
<h3>The process tag</h3>
<h4>Attribute list</h4>
<p>As already written above, the <code>process</code> tag is the tag that defines which host executes which function (from your application). Hence, the <code>host</code> and <code>function</code> attributes are mandatory; however, there are some optional attributes to the process tag. Here is a list of all attributes of this tag:</p>
<table class="doxtable">
<tr>
<th>Attribute name </th><th>Mandatory </th><th>Values </th><th>Description  </th></tr>
<tr>
<td>host </td><td>yes </td><td>String </td><td>Describes which host will be used to run this process. The host must be defined in the platform file! </td></tr>
<tr>
<td>function </td><td>yes </td><td>String </td><td>Name of a function that will be executed on this host; this function is written in userland code, for instance, C code. Valid values are functions that were registered by <a class="el" href="group__msg__simulation.html#ga21e94a4e7b26dea140b0c71a2a4f4352" title="Registers the main function of a process in a global table. ">MSG_function_register()</a> </td></tr>
<tr>
<td>start_time </td><td>no </td><td>int (Default: -1.0) </td><td>The simulated time when this function will start to be computed. </td></tr>
<tr>
<td>kill_time </td><td>no </td><td>int (Default: -1.0) </td><td>The simulated time when this function will end to be computed. By default, it stops only when it's done. </td></tr>
<tr>
<td>on_failure </td><td>no </td><td>DIE|RESTART (Default: "DIE") </td><td>What should be done when the process fails. </td></tr>
</table>
<h4>Examples</h4>
<p>Almost any <a class="el" href="group__msg__examples.html">MSG examples</a> include a deployment file.</p>
<h3>The argument tag</h3>
<p>This tag must always be contained by a <code>process</code> tag - it doesn't make sense without it.</p>
<p>The way this works is that the order of arguments must be pre-defined <em>by the user</em>: It is totally up to you what <em>your</em> code expects as arguments and in which order. The arguments will be passed to your code (that is: to the function executed by this process) in the order you declare them.</p>
<h4>Attribute list</h4>
<table class="doxtable">
<tr>
<th>Attribute name </th><th>Mandatory </th><th>Values </th><th>Description  </th></tr>
<tr>
<td>value </td><td>yes </td><td>String </td><td>Contains the value for this parameter </td></tr>
</table>
</div></div><!-- contents -->
</div><!-- doc-content -->
<!-- start footer part -->
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
  <ul>
    <li class="footer">Generated by
    <a href="http://www.doxygen.org/index.html">
    <img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.13 </li>
  </ul>
</div>
</body>
</html>

APT Browse - Built by Thomas Orozco.