Doc:latest/tutorial - Revision history

Stone: /* Customizing main.c */

2016-12-06T18:43:16Z

‎Customizing main.c

Stone: /* Customizing main.c */

2016-12-06T18:40:42Z

‎Customizing main.c

Stone: /* Customizing the csa101 Code */

2016-12-06T18:13:31Z

‎Customizing the csa101 Code

Stone: /* Creating a New Project Area */

2016-12-05T19:48:32Z

‎Creating a New Project Area

Prasad: /* Resource Editor View */

2014-11-14T09:10:56Z

‎Resource Editor View

Prasad: /* Component Editor View */

2014-11-14T09:10:40Z

‎Component Editor View

Prasad: /* Creating the csa101 Images */

2014-11-14T09:03:01Z

‎Creating the csa101 Images

Prasad: /* Component Service Instance Instance */

2014-11-14T08:54:27Z

‎Component Service Instance Instance

Prasad: /* Service Instance Instance */

2014-11-14T08:53:51Z

‎Service Instance Instance

Prasad: /* Service Group Instance */

2014-11-14T08:52:11Z

‎Service Group Instance

@@ Line 528: / Line 528: @@
 </pre></code>
 |}
-Notice the while loop condition. This function uses the <code>running</code> variable that was initialized to 0, but set to 1 when the application was told to become active. The loop will keep running until <code>running</code> is set to 0, when the application either stops or told to stop being active. The work of the application goes next: printing "Hello World!" along with the progress indicator.  You could replace this with the application's real task.  Finally, the command <code>sleep(2)</code> simply sleeps for two seconds so as not to fill log files too quickly.
+Notice the while loop condition. This function uses the <code>running</code> variable that was initialized to 0, but set to 1 when the application was told to become active.  The work of the application goes next: printing "Hello World!" along with the progress indicator.  You could replace this with the application's real task.  Finally, the command <code>sleep(2)</code> simply sleeps for two seconds so as not to fill log files too quickly.
-When <code>running</code> becomes zero, we return from the function.
+When <code>running</code> becomes zero, we return from the function.  This will happen when the application either quits or the AMF removes its "active" role.
 Next, the log stream is initialized in the <code>initializeAmf</code> function.

@@ Line 528: / Line 528: @@
 </pre></code>
 |}
-Notice the while loop condition. This function uses the <code>running</code> variable that was initialized to 0. The loop will keep running until <code>running</code> is set to non-zero. The work of the application: printing "Hello World!" along with the progress indicator.  Next the command <code>sleep(2)</code> simply sleeps for two seconds so as not to fill log files too quickly or completely swamp the CPU.
+Notice the while loop condition. This function uses the <code>running</code> variable that was initialized to 0, but set to 1 when the application was told to become active. The loop will keep running until <code>running</code> is set to 0, when the application either stops or told to stop being active. The work of the application goes next: printing "Hello World!" along with the progress indicator.  You could replace this with the application's real task.  Finally, the command <code>sleep(2)</code> simply sleeps for two seconds so as not to fill log files too quickly.
-When <code>running</code> becomes non-zero, we return from the function.
+When <code>running</code> becomes zero, we return from the function.
 Next, the log stream is initialized in the <code>initializeAmf</code> function.

@@ Line 430: / Line 430: @@
 To replace the generated files with the customized versions shipped with the SAFplus Platform SDK follow these instructions.
-<br>[[File:OpenClovis_Note.png]]  The sample applications containing the csa101 example can be found under the installation directory at <code><install_dir>/6.1/sdk/src/examples/eval</code>. We will refer to this directory in the remaining of this section as <code><eval_dir></code>.
+<br>[[File:OpenClovis_Note.png]]  The sample applications containing the csa101 example can be found under the installation directory at <code><install_dir>/6.1/sdk/src/examples/eval</code>.  For example, this directory is located at <code>/opt/clovis/6.1/sdk/src/examples/eval</code> for "default" installations.  We will refer to this directory in the remaining of this section as <code><eval_dir></code>.
 <ol>

← Older revision		Revision as of 19:48, 5 December 2016
Line 86:		Line 86:
	* Specify important build and boot parameters		* Specify important build and boot parameters

−
−	~~===Creating a New Project Area===~~
−	A project area is a directory on your system where you can develop SAFplus Platform models and generate the code corresponding to those models. The project area can hold multiple models allowing you to manage all of your models in one location. All the models in the same project area share the same SAFplus Platform source tree. This way any modifications made to the SAFplus Platform source tree are re-used across all the models that were created in that project area.
−
−	~~You create a project area using a script from the command line. To create a project area named '''projectarea1''' in the '''/home/clovis''' directory you should execute the following command:~~
−	~~<code><pre>~~
−	~~# cl-create-project-area /home/clovis/projectarea1~~
−	~~</pre></code>~~

	===Launching the SAFplus Platform IDE===		===Launching the SAFplus Platform IDE===

@@ Line 212: / Line 212: @@
 The '''Resource Editor''' shows the types of physical objects in our system. It gives us a place to create new objects and interact with the objects that already exist. The '''Resource Editor''' view for our model should look similar to the following figure.
-<span id='SAFplus Platform Resource Editor'></span>[[File:Resource_Editor.png|frame|center| '''SAFplus Platform Resource Editor''' ]]
+<span id='SAFplus Platform Resource Editor'></span>[[File:Resource_Editor1.png|frame|center| '''SAFplus Platform Resource Editor''' ]]
 This editor always has a '''Chassis''' object which is the root of all other objects in the editor. In our case it also has the '''SysBlade''' blade type that we created through the '''Project Creation Wizard'''. You will also notice that the '''SysBlade''' is attached to the '''Chassis''' using a '''Composition''' relationship indicating that '''SysBlade'''s reside within the '''Chassis'''.

@@ Line 223: / Line 223: @@
 The '''Component Editor''' shows the types of logical objects in our system. It gives us a place to create new objects and interact with the objects that already exist. The '''Component Editor''' view for our model should look similar to the following figure.
-<span id='SAFplus Platform Component Editor'></span>[[File:Tutorial_ComponentEditor.png|frame|center| '''SAFplus Platform Component Editor''' ]]
+<span id='SAFplus Platform Component Editor'></span>[[File:Component_Editor1.png|frame|center| '''SAFplus Platform Component Editor''' ]]
 This editor always has a '''Cluster''' object which is the root of all other objects in the editor. In our case it also has the '''SCNode''' node type and the '''csa101''' SAF Service Type (a combination of Service Group, Service Unit, Service Instance, Component Service Instance, and SAF Component) that we created through the '''Project Creation Wizard'''. These have all been automatically attached in a way that makes a working model.

@@ Line 822: / Line 822: @@
 Making the csa101 images will create software packages that can be deployed on target machines to run the example. The process of creating images is launched using the '''Project > Make Images''' menu item. Once selected the '''Make Images Configuration''' dialog appears.
 The '''Make Images Configuration''' dialog is used to indicate information about the environment on which the images will be deployed. This information is used to tailor the images to run on that environment. Here we will make the following modificaiton.
 <ul>
 <li>Enter a value for the '''Trap IP'''. This value specifies where the SNMP sub-agent will send traps at runtime. This field is optional but if specified must be a valid IP address. Enter a value of '127.0.0.1' in this field.
 <li>Enter a value for the '''TIPC Net ID'''. This value represents a unique identifier used by TIPC to set up interprocess communication across the deployed OpenClovis SAFplus Platform cluster. This field is required and should default to '1340'.
 <li>Check the '''Create Node Specific Images''' and '''Package Images into Tarballs''' check boxes. This will create tarballs of the images making them easy to deploy to various machines.
 <li>The table on this dialog will hold a row for each node instance defined in the model. In our case this is only one...SCNodeI0. For each of these instances we can define the slot number in the chassis on which the node will run and the network interface that the node will use for communication. In our case enter '1' for the Slot Number and 'eth0' for the Network Interface.

@@ Line 1,237: / Line 1,237: @@
 This screen displays the component service instance that was created by the Service Group Instance Wizard. This component service instance was created because the component service instance is associated with the parent service instance type (csa101SI) in our model.
-<span id='Component Service Instance Details'></span>[[File:Tutorial_CSIInstanceDetails.png|frame|center| '''Component Service Instance Details''' ]]
+<span id='Component Service Instance Details'></span>[[File:Component_Service_Instance_List_csa101CSII0.png|frame|center| '''Component Service Instance Details''' ]]
 The information on this screen is described below.

@@ Line 1,226: / Line 1,226: @@
 This screen displays the service instance that was created by the Service Group Instance Wizard. This service instance was created because the service instance type is associated with the parent service group type (csa101SG) in our model.
-<span id='Service Instance Details'></span>[[File:Tutorial_SIInstanceDetails.png|frame|center| '''Service Instance Details''' ]]
+<span id='Service Instance Details'></span>[[File:Service_Instance_List_csa101SII0.png|frame|center| '''Service Instance Details''' ]]
 The information on this screen is described below.

@@ Line 1,208: / Line 1,208: @@
 This screen displays the service group instance that was created by the Service Group Instance Wizard. This service group instance was created because the service group type '''csa101SG''' was selected on the wizard screen.
-<span id='Service Group Instance Details'></span>[[File:Tutorial_SGInstanceDetails.png|frame|center| '''Service Group Instance Details''' ]]
+<span id='Service Group Instance Details'></span>[[File:Service_Group_List_csa101SGI0.png|frame|center| '''Service Group Instance Details''' ]]
 The information on this screen is described below.
@@ Line 1,219: / Line 1,219: @@
 Clicking the '''Associated Service Units''' Edit... button will display the following dialog.
-<span id='Associated Service Units Dialog'></span>[[File:Tutorial_SG_SI_Association.png|frame|center| '''Associated Service Units Dialog''' ]]
+<span id='Associated Service Units Dialog'></span>[[File:Associated_Service_Units.png|frame|center| '''Associated Service Units Dialog''' ]]
 This dialog lists the service unit instances that can be associated with this service group instance. The list contains only one item, the service unit instance that was created by the wizard. This item is checked indicating that the wizard automatically chose this service unit instance to run within the service group instance.