OpenClovis Product Documentation - User contributions [en]

ClLog.xml

2012-02-21T03:50:05Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ buy xanax no prescription - xanax to buy

Doc:Sdkguide/infrastructure

2012-02-21T03:50:05Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ buy 2mg xanax - buy xanax online wthout prescription

Talk:High Availability (AMF) Questions

2012-02-21T03:50:05Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ order cheap xanax online - buy xanax 2mg

Doc:latest/sdkguide/highavailability

2012-02-21T03:50:05Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ purchase online generic xanax - order cheap xanax online

Doc:latest/sdkguide/commandref

2012-02-21T03:50:04Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ cheap xanax without a prescription - xanax online no prescription

Logging Questions

2012-02-21T03:50:04Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ buy xanax - order xanax cheap

Doc:latest/sdkguide/knowledgebase

2012-02-21T03:50:03Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ order xanax online no rx - generic xanax

Doc:latest/sdkguide/compdev

2012-02-21T03:50:03Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ xanax no prescriptions - xanax

Doc:latest/sdkguide/troubleshooting

2012-02-21T03:50:03Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ buy xanax online - buy generic xanax online

Doc:latest/sdkguide/basicinfrastructure

2012-02-21T03:50:03Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ order xanax no rx - buy xanax no prescription

Doc:latest/sdkguide/deploy

2012-02-21T03:50:03Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ xanax no prescriptions - buy generic xanax online

Logging Questions

2012-02-21T03:48:25Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ buy xanax no prescription - buy xanax cheap no prescription

ClLog.xml

2012-02-21T03:48:25Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ order xanax online no rx - cheap xanax without a prescription

Doc:Sdkguide/infrastructure

2012-02-21T03:48:25Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ buy xanax online - cheap xanax without a prescription

Talk:High Availability (AMF) Questions

2012-02-21T03:48:25Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ xanax to buy - buy xanax online wthout prescription

Doc:latest/sdkguide/highavailability

2012-02-21T03:48:25Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ xanax buy - buy xanax cheap

Doc:latest/sdkguide/deploy

2012-02-21T03:48:24Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ buy xanax online - xanax to buy

Doc:latest/sdkguide/knowledgebase

2012-02-21T03:48:24Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ xanax - xanax to buy

Doc:latest/sdkguide/compdev

2012-02-21T03:48:24Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ buy xanax online - order generic xanax online

Doc:latest/sdkguide/troubleshooting

2012-02-21T03:48:24Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ xanax buy online - cheap xanax

Doc:latest/sdkguide/commandref

2012-02-21T03:48:24Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ xanax to buy - xanax

Talk:Doc:latest/sdkguide/knowledgebase

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:latest/sdkguide/compdev

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:latest/sdkguide/troubleshooting

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:latest/sdkguide/commandref

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Logging Questions

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:Sdkguide/infrastructure

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:latest/sdkguide/highavailability

2012-02-21T03:48:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Doc:latest/sdkguide/basicinfrastructure

2012-02-21T03:48:23Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

http://www.buyxanaxitem.com/ xanax buy - cheap xanax online

Talk:Online Dating For Single Parents

2012-02-21T03:48:22Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:latest/sdkguide/basicinfrastructure

2012-02-21T03:48:22Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Doc:latest/sdkguide/deploy

2012-02-21T03:48:22Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Yahoo Chat For Pda

2012-02-21T03:48:22Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Talk:Love And Dating Websites

2012-02-21T03:48:22Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Doc:latest/sdkguide/preface

2012-02-21T03:48:21Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''Preface'''==

''OpenClovis Applications Service Platform (SAFplus Platform)'' is a modular, high-performance, scalable software platform (sometimes also referred to as ''middleware'') to facilitate the speedy development and run-time operation of highly-available and manageable communications systems.
SAFplus Platform has been primarily designed for complex, multi-processor, distributed systems, consisting of multiple processor cards or chassis, using heterogeneous CPU types and operating system versions.
SAFplus Platform has been fine-tuned for software applications that not only demand reliability and manageability, but also scalability and high performance.

In a typical SAFplus-enabled communication device, SAFplus Platform resides on every (or most) processor entities that need to be involved in the manageability and configuration of the device, or which need to perform redundant services in order to provide high availability.
On each of such processors SAFplus Platform is present in the form of a few run-time processes (daemons), while application-specific components that need to use any of the SAFplus Platform services communicate with these daemons using SAFplus Platform client libraries.
For most SAFplus Platform services, the SAFplus Platform middleware takes care of all needed inter-processor communication and data replication among the various processor entities, effectively tying these into one seamless cluster, hiding the inter-processor aspects from the SAFplus-based custom applications.

During development of an SAFplus-enabled communication system, system architects and software designers work with the ''OpenClovis Software Development Kit (SDK)''.
The SDK includes the ''OpenClovis Integrated Development Environment (IDE)'', a graphical user interface to define, model, and configure the system, as well as all the relevant source files, header files, run-time libraries, build tools that are needed to create, test, and debug the target system.

With this product, OpenClovis provides Original Equipment Manufactures (OEMs), Telecommuncations Equipment Manufacturers (TEMs) with an efficient and cost-effective solution for creating highly available, manageable products with short time-to-market.

This ''OpenClovis SDK User Guide'' provides system architects and software developers with further information about the OpenClovis SAFplus Platform and its companion SDK. It provides an overview of the SAFplus Platform architecture, the various SAFplus Platform components, and their interactions. This guide also helps you to understand how to work with the OpenClovis Software Development Kit (SDK) when modeling, configuring, building, and deploying SAFplus Platform and SAFplus Platform based applications on target systems.

===Audience===

''OpenClovis SDK User Guide'' is written for system architects, software designers, developers, and system integrators. To use this OpenClovis product, you must be aware of the fundamentals of operation, management, and configuration of telecommunication and networking systems. You must also be familiar with basic high availability concepts, C programming, UML notations, and have the basic knowledge of Linux.

===Documentation Conventions===

This user guide uses different fonts and symbols to differentiate between document elements and types of information. These conventions are summarized in the following table:
{| border="0" cellpadding="3"
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Notation
!style="color:#66b154; background:#09477c"| Description
|- style="color:#ffffff; background:#549cc6"
| style="color:black" |<code><pre>Code</pre></code>
| This font denotes the C code provided in various examples.
|- style="color:#ffffff; background:#549cc6"
|
Cross reference
|
This font denotes a hyperlink. You can click on the hyperlink text to access the reference location, which can be either a section within the User Guide or a URL link.
A cross reference refers to a section name accesses the first page of that section.
|- style="color:#ffffff; background:#549cc6"
|
'''Bold Text'''
|
Menu items and button names.
|- style="color:#ffffff; background:#549cc6"
|
''Italic Text''
|
Variables for which you enter values.
|}
 [[File:OpenClovis_Note.png]]This indicates the presence of notes or annotations, related to the context of the document.
 [[File:OpenClovis_Caution.png]]This indicates that certain precautionary measures must be taken before performing a particular task.
 [[File:OpenClovis_Info.png]]This indicates that additional information is provided to you.

===Document Organization===

OpenClovis SDK User Guide is organized into various chapters to provide information on specific areas. The following table introduces the chapter names and a brief overview of the content.

{| border="0" cellpadding="3"
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Chapter
!style="color:#66b154; background:#09477c"| Overview
|- style="color:#ffffff; background:#549cc6"
|
Chapter 1, Overview
|
This chapter helps you understand the conceptual information, advantages and key features of OpenClovis SAFplus Platform and IDE.
|- style="color:#ffffff; background:#549cc6"
|
Chapter 2, High Availability (HA)
|
This chapter provides an introduction to the basic concepts of HA and the relevant SAFplus Platform features and SAFplus Platform components, namely: Availability Management Framework (AMF), Checkpointing Service, and Group membership Service (GMS).
|- style="color:#ffffff; background:#549cc6"
|
Chapter 3, System Management
|
This chapter provides information about the various SAFplus Platform features and components for system management, such as: Clovis Object Registry (COR), Mediation Library, Transaction Service, Provisioning Library, Alarm Service, Chassis Management, and SNMP Sub-Agents
|- style="color:#ffffff; background:#549cc6"
|
Chapter 4, Communications Infrastructure
|
This chapter provides an overview of the features, services and relevant components of SAFplus Platform in the domain of inter-process and inter-processor data communication.
|- style="color:#ffffff; background:#549cc6"
|
Chapter 5, Basic Infrastructure
|
OpenClovis SAFplus Platform is built on a number of basic infrastructure elements, which are described in this chapter.
|- style="color:#ffffff; background:#549cc6"
|
Chapter 6, Hardware Platform Support
|
The specific benefits of the Platform Support Package, and its realization are described in this chapter.
|- style="color:#ffffff; background:#549cc6"
|
Chapter 7, Development Lifecycle and OpenClovis SDK
|
This chapter describes how the various SDK features fit in the workflow of a typical development life-cycle, and provides detailed information about the key phases, such as configuring, building, and deploying SAFplus-enabled systems.
|- style="color:#ffffff; background:#549cc6"
|
Chapter 8, "Starter" Models
|
This chapter summarizes the so-called starter models provided by OpenClovis to jump-start the development of your own application, as an alternative to starting from scratch.
|- style="color:#ffffff; background:#549cc6"
|
Appendix A, Glossary of Terms
|
This provides complete information about all the terms and definitions specific to OpenClovis SAFplus Platform and its components.
|}

===Related Documentation===

For additional information about the OpenClovis SAFplus Platform, SDK, and IDE, please refer to the following companion documents:
* '''OpenClovis Release Notes''' provides information about the software and the hardware required to install OpenClovis Application Service Platform (SAFplus Platform) and Integrated Development Environment (IDE). It contains the additional features and enhancements of the product since the previous release. It also summarizes the issues and limitations of the product and provides workarounds wherever applicable.
* '''OpenClovis SA Forum Compliance''' describes the level of compliance of OpenClovis SAFplus Platform and its Application Programming Interface (API) with the relevant Service Availability Forum specifications.
* '''OpenClovis Installation Guide''' provides the system requirements, installation procedure for OpenClovis SAFplus Platform, IDE, and the Evaluation System.
* '''OpenClovis Sample Application Tutorial''' provides the steps to create and build a sample model using OpenClovis IDE and OpenClovis SAFplus Platform. It also provides troubleshooting information for this process. This provides the logical first step in understanding the OpenClovis offering.
* '''OpenClovis Evaluation System User Guide''' provides all the required information to configure and run the sample models packaged within the Evaluation System. This document also provides good understanding of OpenClovis SAFplus Platform's functionality. This is the natural follow on to the ''OpenClovis Sample Application Tutorial'' as it builds on the example created in that document.
* '''OpenClovis IDE User Guide''' describes the usage of Integrated Development Environment (IDE), a graphical development environment that complements the SAFplus Platform platform. This guide helps you to understand how to use the various features of the IDE to build the application.
* '''OpenClovis Log Tool User Guide''' provides information about the usage of OpenClovis Log Tool. OpenClovis Log Tool is an interactive utility that allows you to view binary log files in a readable format and hence monitor system errors, warnings, and other log information. Log Tool allows you to format the <code>.log</code> files and filter them to view the required entries.
* '''OpenClovis API Reference Guide''' is provided for each component. It describes the Application Programming Interface (API), Service Model, and Management Information Model of the various OpenClovis Application Service Platform (SAFplus Platform) services. It helps the developer to understand the capabilities of the SAFplus Platform services and the APIs provided by these services.
* '''OpenClovis SAFplus Platform Console Reference Guide''' provides details about managing applications built on OpenClovis SAFplus Platform using the SAFplus Platform runtime debug console commands. SAFplus Platform Console commands can be used to manage, monitor, and test your application.

All the above document are available in both Portable Document Format (PDF) as well as a set of cross-referenced, browsable HTML pages. They can be found under the <code>/doc</code> subdirectory of the installed SDK (under the <code>/pdf</code> and <code>/html</code> subdirectories, respectively). Please refer to the installation guide for further information.

===OpenClovis Online Technical Support===

OpenClovis customers and partners can register on our website and receive personalized services and information. If you need any support or assistance while working on OpenClovis products, you can access the following: URL: http://www.openclovis.com Send your queries to: support@openclovis.com. Open source community support is available at:
http://www.openclovis.org/forum

===Documentation Feedback===

We are interested in hearing from our customers on the documentation provided with the product. Let us know your comments and suggestions on improving the documentation at OpenClovis Inc. Send your comments to:
support@openclovis.com Post your feedback on documentation at: http://www.openclovis.org/forum

Doc:latest/sdkguide/cominfrastructure

2012-02-21T03:48:20Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''Communication Infrastructure'''==

Intracluster Communications is a critical element in any tightly coupled distributed system, and is very different from standard TCP client/server communications paradigms. OpenClovis provides several communications facilities that are used by the SAFplus Platform framework and that should be used by customer software. OpenClovis provides an abstraction for simple low-latency LAN based direct message passing called IOC, and provides an implementation of the same over TIPC - the standard Linux inter-cluster low-latency communications mechanism. All OpenClovis services use IOC to communicate with peers except for GMS (Group management) which uses IP multicast. Therefore, a customer can port the entire SAFplus Platform to another messaging system simply by implementing the IOC interfaces.

These communications services are available on every SAFplus Platform node and are automatically integrated into EO-inized applications. They allow any component to directly communicate with any other component running on any node and allow components to be identified (addressed) either by location or by an arbitrary name (location transparent addressing). These "arbitrary names" can be move from component to component as need or failures dictate. The communications system also automatically provides component and node failure notifications via a heartbeat mechanism.

Higher level communications abstractions and tools such as events, remote procedure calls, and endian translation are also supported.

Components of Communication Infrastructure:
* [[#Event Service | Event Service]]
: Publish/Subscribe multipoint communications model.
* [[#Intelligent Object Communication (IOC)| IOC]]
: Low level messaging abstraction layer
* [[#Name Service | Name Service]]
: Identify nodes via names instead of physical addresses. Names can be transferred between nodes to implement failover.
* [[#Remote Method Dispatch (RMD)| Remote Method Dispatch (RMD)]]
: Call functions on other nodes
* [[#Interface Definition Language (IDL) | Interface Definition Language (IDL)]]
: Abstract definition language that can be used in mixed-endian environments to allow data do be automatically swapped.

[[File:SDK_ComInfrastructure2.png|center|frame|'''Communication Infrastructure''']]

===Event Service===

====Overview====

The Event Service is a publish/subscribe multipoint-to-multipoint communication mechanism that is based on the concept of event channels, where a publisher communicates asynchronously via with one or more subscribers over a channel. The publishers and subscribers are unaware of each others existence.

====Terms, Definitions====

* '''Event''': Any data that needs to be communicated to interested parties in a system is called an event. This data typically describes an action that was taken or a problem that was detected.
* '''Subscribers''': Entities interested in listening to an event
* '''Publishers''': Entities that generate the event. An entity can be both a publisher and a subscriber
* '''Event Channel''': A global or local communication channel that allows communication between publishers and subscribers. By sending events in channels, all events do not need to go to all Subscribers.
* '''Event Data''': Zero or more bytes of payload associated with an event
* '''Event Attributes''': The publisher can associate a set of attributes with the each event such as the event pattern, publisher name, publish time, retention time, priority, etc.
* '''Event Pattern''': The attribute which describes type of an event and categorizes it. This is used for filtering events.
* '''Event Filter''': The subscribers use filters based on the patterns exposed by the publisher to choose the events of interest, ignoring the rest.

====Features====

* SAF compliant implementation
* The publisher and the subscriber can be:
** In the same process address space
** Distributed across multiple processes on the same CPU/board
** Distributed across multiple processes on various CPU/boards
* Event Channels can be local or global
** Local channels for SAFplus Platform node internal events
** Global channels for SAFplus Platform cluster wide events
* Multiple subscribers and publishers can open the same channel
* Events are delivered in strict order of generation
* Guaranteed delivery
* At most once delivery
* Events can have
** Any payload associated with them
** Pattern defining the type of the event
** A specified priority
** A retention time for which the event is to be held before discarding
* Events published on a channel can be subscribed to, based on a filter that matches the event pattern
* Debug support by monitoring and logging
** Controlled at run time

====Architecture====
[[File:SDK_EMArchitecture.png|center|frame|'''Event Service Architecture''']]

The Event Service is based on RMD and IOC. It involves the communication between publishers and subscribers without requiring either side to explicitly "identify" the other side. That is, the publisher does not need to know who the subscribers are and vice versa. This is accomplished via an abstraction called an event channel. All events published to a channel go to all subscribers of the channel. To handle node specific events efficiently, a channel is categorized as local and global. The local channel is limited to a single node while a global channel spans across the nodes in the cluster. This feature is an extension to the SA Forum (SAF) event system where there is no such distinction and all channels are inherently global. An event published on a global channel requires a network broadcast while a local event does not use the network and is therefore very efficient.

====Flow====

[[File:SDK_EMFlow.png|center|frame|'''Event Service Flow''']]

To use the Event Service an understanding has to be established between the publisher and the subscriber. The type of the payload that shall be exchanged should be known to both and also if any pattern is used by the publisher it has to be made known to the subscriber.

Both the subscriber and publisher are required to do a Event Client Library initialize to use the Event Service. Both then open the channel, subscriber with the subscriber flag and publisher with publish flag. To both publish and subscribe to a channel, set both flags. This means that the subscriber and publisher can be the same entity. However, for the purposes of clarity in this description the logical separation of "subscriber" and "publisher" will be maintained.

The subscriber than subscribes to a particular event using a filter that will match specific event patterns that interests that subscriber. The publisher on the other hand will allocate an event and set it's attributes. It optionally sets the pattern to categorize the event. This pattern is matched against the filter supplied by the subscriber. The publisher then publishes the event on the channel. If channel is global the event is sent to all the event servers on the cluster who in turn deliver the event to any subscribers on that node. If the channel is local the event is delivered to the subscribers who have subscribed to this event locally. The event is delivered only to those subscribers which have an appropriate filter.

For further details on the usage of Event Service kindly refer to the OpenClovis API Reference Guide.

===Transparent Inter Process Communication (TIPC)===
TIPC provides a good communication infrastructure for a distributed, location transparent, highly available applications. TIPC is a Linux kernel module; it is a part of the standard Linux kernel and is shipped with most of standard distributions of Linux. It supports both reliable and unreliable modes of communications, reliable being desired by most applications (even if the hardware is reliable, buffering issues can make the program-to-program communications unreliable). Since TIPC is a Linux kernel module and works directly over the Ethernet, any communication that uses TIPC will be very fast compared to other protocols. The TIPC kernel module provides a few important features like topology service, signaling link protocol, location transparent addressing. This section describes only the features of TIPC as used by SAFplus Platform, although SAFplus Platform programs are welcome to access the TIPC APIs directly to use other features. For more details please refer to the tipc project located at http://tipc.sourceforge.net.

From TIPC view point the network is organized into a 5-layer structure.

* TIPC Network : This is the ensemble of all the computers interconnected via TIPC. This is a domain within which any computer can reach any other computer using the TIPC address.
* TIPC Zone : This is group of clusters is a zone.
* TIPC Cluster : A group of computers is called a cluster.
* TIPC Node : A node is a computer.
* TIPC Slave Node : It is same as a node, but will communicate with only one node in a cluster. This is unlike normal nodes which are connected to all the nodes in the cluster.

TIPC does not use "normal" ethernet MAC addresses or IP addresses. Instead it uses a "TIPC address" that is formed from these fields. In general, this complexity is hidden from the SAFplus Platform programmer since addresses are automatically assigned.

====TIPC features====
The list below describes some features of TIPC:
* Broadcast.
* Location Transparent Addressing.
* Topology Service.
* Link Level Protocol.
* Automatic Neighbor Detection.

====Broadcast====
TIPC supports unicast, multicast and broadcast modes of sending a packet. Depending on the intended mode the TIPC address has to be specified. The format of the address looks like (type, lower instance and upper instance).
* type : This is the port number of a component to which the packet is to be sent to.
* lower instance : This is the lowest address of the nodes to which the packet should go to.
* upper instance : It is the highest address of the nodes to which the packet should go to.
The lower instance and upper instance together form the range of address. If these 2 are same then the packet will be unicasted to that destination node. And if the the range covers all the nodes of a system then it is a broadcast packet and will be sent to all the nodes node in the system.

====Location Transparent Addressing====
An application can be contacted without having the knowledge of its exact location. This is possible through Location Transparent Addressing. A highly available application in a system while providing service to many of its clients might suddenly go down due to this some kind of failure in the system. And the same application can come up on another node/machine with the same Location transparent address. This way the clients can still reach the server with the same address, which they used to contact previously.

====Topology Service====
TIPC provides a mechanism of inquiring or subscribing for the availability of a address or range of addresses.

===Intelligent Object Communication (IOC)===

The Intelligent-Object-Communication(IOC) module of SAFplus Platform provides the basic communication infrastructure for an SAFplus Platform enabled system. The IOC is a compatibility layer on top of TIPC that will allow customers to port SAFplus Platform to other architectures. Therefore, all SAFplus Platform components use the IOC APIs rather than TIPC APIs. IOC exposes only the most essential TIPC features to make porting simpler. IOC also abstracts and simplifies some of the legwork required to connect a node into the TIPC network. Customers are encouraged to use the IOC layer (or higher lever abstractions like event and RMD) to ensure portability in their applications, or may use TIPC directly.

====IOC Architecture====

[[File:SDK_IOCArchitecture.png|center|frame|'''IOC Architecture''']]

====IOC Features====

* Reliable and Unreliable mode of communication.
* Broadcasting of messages.
* Multicasting of messages.
* Transparent/Logical Address to a component.
* An SAFplus Platform node arrival/departure notification.
* The arrival/departure notification of a component.

=====Reliable and Unreliable mode of communication=====
The IOC with the help of TIPC allows the applications to create a reliable or an unreliable communication port. All the communication ports are connectionless ports. This helps to achieve a high speed data transfer. Reliable communications are highly recommended and is the default used by OpenClovis SAFplus Platform. It should be used even within an environment with extremely low message loss at the hardware level (such as an ATCA chassis) because message loss may also occur in the linux kernel or network switch due to transient spikes in bandwidth utilization.

=====Broadcasting of messages=====
IOC supports the broadcasting of messages, qualified by destination port number. This means that a broadcast message sent from a component will reach all components on all nodes in the cluster that are listening to the communications port specified in the destination-address field of the message.

=====Multicasting of messages=====
Multicasting is sending of a message to only a group of components. Any component may join the group by registering itself with IOC for a specific multicast address. Thereafter any message sent to that multicast address will reach all the registered components in the cluster.

=====Location Transparent/Logical Address to a component=====
Transparent addressing support of IOC makes communication possible for an SAFplus Platform component with another another SAFplus Platform component without knowing the second one's physical address. Location Transparent addressing is commonly used in the case of redundant components that provide a single service. If the service uses a Location Transparent address, clients do not need to discover what component is currently providing the service; a client simply addresses a message to the Location Transparent Address, and that message is automatically sent to the component that is currently "active".

On the server side, it is the responsibility of the "active" component of the redundant pair to "register" with IOC for all messages sent to the Location Transparent Address.

=====SAFplus Platform node arrival/departure Notification=====
In a cluster having many SAFplus Platform nodes in a system, some SAFplus Platform components might be interested in knowing when a node in the cluster arrives and when one leaves. This feature of IOC informs such an event to all the interested SAFplus Platform components in the whole SAFplus Platform system. Components may use either a query or a callback based interface.

=====The arrival/departure notification of a component=====
This feature of IOC helps the components which are interested in other components' health status. The IOC with the help of TIPC will come to know about every SAFplus Platform components health in a system and it conveys this to all the interested SAFplus Platform components though a query or callback interface. Component arrival and departure is actually measured by when the component creates or removes its connection to TIPC, as opposed to when the process is created or deleted. The OpenClovis EO infrastructure always creates a default connection upon successful initialization, so this measurement is actually more accurate than process monitoring. A thread is automatically created in each process as part of the EO infrastructure to monitor all other components health status and to handle SAFplus Platform communications.

===Interface Bonding===

Any fully redundant solution requires physical redundancy of network links as well as node redundancy. This link-level redundancy is particularly important between application peers (i.e. between nodes in the cluster) because if peer communications fail at the ethernet level than it is not possible to distinguish certain link failure modes from node failure modes. In these cases each peer will assume that the other has failed, leading to a situation where all nodes assume the "active" role. In the worst case, each "active" node will service requests and so the state on each node will diverge (in practice the nodes tend to interfere with eachother, by both claiming the same IP address for example, resulting in loss of service). When the link failure is resolved, one of the 2 nodes will revert back to "standby" status, losing all state changes on that node. The solution to this "catastrophic" failure mode is simply to have link redundancy so that no single failure will cause the system to enter this state.

The simplest link redundancy solution can be implemented at the operating system layer and is called "interface bonding". In essence 2 "real" interfaces, say "eth0" and "eth1" are combined to form a single "virtual" interface called "bondN" (or "bond0" in this case) that behaves from the applications' perspective like a single physical interface. Policies can be chosen as to how to distribute or route network traffic between these 2 interfaces.

The OpenClovis SAFplus Platform can be configured to use a "bonded" interface for its communications in the exact same way as it is configured to use a different "real" interface (see the IDE user guide or XML configuration file formats for more information). Customers may want to configure their "bonded" interface in different ways based on their particular solution. Details describing how to enable bonding in operating system and OS distribution specific and is therefore beyond the scope of this document and the OpenClovis SAFplus Platform software. However a bonding configuration that is considered the "best practice" for use with OpenClovis SAFplus Platform is described in the following sections.

====Configuring the bonding====
The Interface Bonding is a Linux kernel module. To work with this the kernel should have been compiled with the "Bonding driver support" (for major distributions, this flag is often on by default). For more details on how to install bonding driver module into the kernel please refer to the "bonding.txt" in Linux Documentation's "networking" section.

<ol>
<li> Loading the kernel module
The following two lines are needed to be added to /etc/modprobe.conf or /etc/modules.conf

alias bond0 bonding
options bond0 mode=active-backup arp_interval=100 \
arp_ip_target=192.168.0.1 max_bonds=1

* mode : Specifies one of the bonding policies.
**active-backup : Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance.
* arp_interval : Specifies the ARP monitoring frequency in milli-seconds.
* arp_ip_target : Specifies the ip addresses to use when arp_interval is > 0. These are the targets of the ARP request sent to determine the health of the link to the targets. Specify these values in ddd.ddd.ddd.ddd format. Multiple ip addresses must be separated by a comma. At least one ip address needs to be given for ARP monitoring to work. The maximum number of targets that can be specified is set at 16.
* max_bonds : Specifies the number of bonding devices to create for this instance of the bonding driver. E.g., if max_bonds is 3, and the bonding driver is not already loaded, then bond0, bond1 and bond2 will be created. The default value is 1.

<li> Use the standard distribution techniques to define the network interfaces. For example, on Red Hat distribution create an ifcfg-bond0 file in /etc/sysconfig/network-scripts directory that resembles the following :

DEVICE=bond0
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Bonding
USERCTL=no

<li> All interfaces that are part of a bond should have SLAVE and MASTER definitions. For example, in the case of Red Hat, if you wish to make eth0 and eth1 a part of the bonding interface bond0, their config files (ifcfg-eth0 and ifcfg-eth1) should resemble the following:

DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

Use DEVICE=eth1 in the ifcfg-eth1 config file. If you configure a second bonding interface (bond1), use MASTER=bond1 in the config file to make the
network interface be a slave of bond1.

<li> Restart the networking subsystem or just bring up the bonding device if your administration tools allow it. Otherwise, reboot. On Red Hat distros you can issue 'ifup bond0' or '/etc/rc.d/init.d/network restart'.

<li> The last step is to configure your model to use bonding. This can be done in the IDE through the "SAFplus Platform Component Configuration.Boot Configuration.Group Membership Service.Link Name" field. This default can also be overridden on a per-node basis through the "target.conf" file, LINK_<nodename> variable.
</ol>

===Name Service===
====Overview====
Naming Service is mechanism that allows an object to be referred by its "friendly" name rather than its "object(service) reference". The "object reference" can be logical address, resource id, etc. and as far as Name Service is concerned, "object reference" is opaque. In other words, Naming service (NS) returns the logical address given the "friendly" name. Hence, Name Service helps in providing location transparency.This "friendly" name is topology and location agnostic.

====Basic concept====

The name service maintains a mapping between objects and the object reference (logical address) associated with the object. Each object consists of an object name, an object type, and other object attributes. The object names are typically strings and are only meaningful when considered along with the object type. Examples of object names are "print service", "file service", "user@hostname", "function abc", etc. Examples of object types include services, nodes or any other user defined type. The object may have a number of attributes (limited by a configurable maximum number) attached to it. An object attribute is itself a <attribute type, attribute value> pair, each of which is a string. Examples of object attributes are, <"version", "2.5">, <"status", "active"> etc.

The name service API provides methods to register/deregister object names, types, attributes and associated addresses. A process may register multiple services with the same address or multiple processes may register the same service name and attributes. Some object names, attributes and addresses may also be 'statically' defined at start time. It is the responsibility of the process that registers an object to remove it when the object is no longer valid. However in the case where a process undergoes an abnormal termination, the name service will automatically remove associated entries.

The name service provides the ability to query the name database in various ways. Clients may query the name service to obtain the address and attributes of a object by giving the object name and type. "Content-addressable" access is also provided. In other words, clients may give attributes and ask for object names that satisfy those attributes.

====Features====
* The name service maps "service names" to attributes, including addresses
* Service Providers register their "service name", "address" and attributes with the Name Service
* Service Users query the Name Service to get information about a service
* Service users can communicate with service providers without knowing their logical address or physical location
* Multiple service providers can register the same name. The name service maintains a reference count for each "name" registered
* The name service subscribes to component failure notification from AMF. If a component dies, the reference count for the services it has registered is decremented.
* Supports context based naming to allow partitioning of the name space
** Local name spaces are local to the Name Server on a SAFplus Platform node
** Global Name Spaces are global to the SAFplus Platform cluster
** Name spaces are dynamically created at run time
* Supports three type of queries
** Query based on "Service Name": Given a service name returns the address and service attributes
** Query based on "Service attributes": Given service attributes, returns the Service Name and address
** Query based on "name space context": Given a name space context, returns all names in that space

====Subcomponents====

Based on the responsibilities, the Name Service component can be further subdivided into following modules

* '''Core Module'''
:Responsible for supporting the creation and deletion of user defined contexts and processing the requests for registration, deregistration. Also responsible for supporting the various NS related queries

* '''Life cycle Management Module'''
:Responsible for initialization, finalization, restart and other management functionalities

* '''Syncup Manager Module'''
:Responsible for NS DB synchronization and backing up of DB in persistent memory

====Contexts and Scopes====
The name service supports different sets of name-to-object reference mappings(also referred to as "context"). A particular "name" is unique in the context. A process will specify the context and the scope of its service during registration with the name service.

'''Context'''

* '''User-defined set'''
Applications may choose to be a part of a specific set (or context). For that, first a context has to be created. For example, all the SAFplus Platform related services can be a part of a separate context.

* '''Default set'''
Name Service supports a default context for services that don't form a part of any specific context.

'''Scope'''

* '''Node-local scope'''
The scope is local to the node. That is, the service provider and the user should co-exist on the same blade.

* '''Global or cluster-wide scope'''
The service is available to any user on any of the blades.

====Registration and Deregistration====
As the name suggests, during registration, an entry (i.e mapping between "name" and logical address) for the component is added into the name service database and during deregistration the entry is deleted.
 
In a typical SAFplus Platform HA scenario, whenever a component comes up and ACTIVE HA state is assigned to it, it registers with the local name service giving a string name for the service, the logical address, context and scope (the application obtains the logical address by using CL_IOC_LOGICAL_ADDRESS_FORM). Next the entry is added to the local name service database. If the scope is cluster-wide, the local name service indirectly passes this information to the name service master. Based on the context, the name service master decides whether to store the entry in the default context or the given user defined context. The name service also stores the component identifier along with that entry so that the entry can be purged if the component dies.
 
Note that the Name Service does not care about the HA state assigned to the component. On the one hand, this means that the component author must handle registration and deregistration when the service becomes active or standby. On the other hand, this allows great flexibility since standby components can still register names. The name service maintains reference count of instances providing a given service. Whenever a component registers with the name service, this reference count is incremented and whenever a component dies or deregisters, this reference count is decremented by the name service. If nobody is refering to a particular entry, then that entry will be deleted. Whenever a component goes down gracefully, it is the responsiblity of the component to delete the service which it registered.

====Name Service entries====
The name service database contains the following entries Name to Logical Address mapping, CompId of the component hosting the service, Count of no. of instances for the given service, a set of user defined attributes - The attributes will be <attribute type, attribute value> pair, each of which is a string. Examples of object attributes are, <"version", "2.5">, <"status", "active"> etc. The upper limit on no. of attributes is user configurable.

====Querying Name Service====
Whenever a component wants to get the logical address of a service, it queries its local Name Server specifying the context. Context is needed because "name" is not unique across contexts i.e. Same "name" can map to different objects in different contexts. Local Name Server checks both the node-local and the cluster-wide entries.
The Name Service query is based on "Name". If an application queries the local NS EO, and an entry is not found in local NS database (there is a chance that NS updation message did not reach the NS/L), the NS/L EO contacts the NS/M EO, which looks up its cluster-wide entries and gets the information. If the information is found, NS/L updates its local database as well.

===Remote Method Dispatch (RMD)===

====Overview====

This service is generically known as RPC (Remote Procedure Calls). In a system with a single address space, function calls made are local to the address space. However, in a distributed system, the services sought by a caller may not always be available locally, but at some remote node. Remote Method Dispatch or RMD facilitates calls to the remote callee and returns the results to the caller. From the point of view of the caller, and RMD call looks exactly like a local function call. However, the function is actually executed on another node. Details like what node provides the service, how to communicate with this node, and platform specifics like endianess is hidden from the caller.

====Features====

* Similar to RPC - Remote Procedure Call
* Enables you to make a function call in another process, irrespective of the location of the process
* Communication takes place over low latency IOC/TIPC layer
* Reliable communication ("at most once" semantics)
* Support both synchronous and asynchronous flavors
* IDL can be used to generate client/server stubs for user components (and is of course used internally for SAFplus Platform components)
* Platform agnostic - works across mixed endian and mixed mode (32 bit and 64 bit)

====Types of RMD Calls====

* Sync (with or without Response)
** This call will block until a response is received
** Reliable - function caller knows whether or not it succeeded when the call returns
* Async with Response
** This will initiate the function call and include a callback function to handle the response
** Reliable - function caller knows whether or not it succeeded via the callback
* Async without Response
** This sends NULL for callback function
** Not reliable

====RMD Usage====

From the caller's perspective, RMD usage is essentially a function call if IDL was used to generate the client/server stubs. RMD functions can be defined, and code generated through the OpenClovis IDE; please refer to the ''OpenClovis IDE User's Guide'' chapter 'Defining IDL'

Underneath the IDL are calls to the RMD API which are rarely used directly but described here for completeness.

Irrespective of the type of the call the RMD API will require at least the following parameters:
* IOC address (destination address and port)
* Input message (Input arguments to the call)
* Output message (The returned arguments)
* flags
* RMD options

Additionally, in case of async call, a callback function and a cookie (piece of context data that is not used by RMD, but passed back to the callback) need to be passed.

As illustrated in the diagram below the address comprises of the node address and port on which the application/service provider is listening. The user is also required to specify the service he wants executed via a RMD number which comprises of the Client ID and Service ID. The former helps identify which client service is sought - this could be the native table which consists of the services exposed by the application or any other client table installed by the libraries to which the application is linked. The service number is the index of the service that is desired.

[[File:SDK_RMDAddressing.png|center|frame|'''RMD Addressing''']]

For further details on the RMD usage kindly refer ''OpenClovis API Reference Guide''.

====RMD IDL====

RMD is typically used via IDL so that the user is saved from the idiosyncrasies of the underlying architectures and such.

* RMD IDL simplifies building of RMDs
** Generates server and client stubs
** Stubs do marshalling and un-marshalling of arguments making them platform agnostic
** Select appropriate semantics
** Takes care of endianness and mixed mode issues
** Uses XDR (see internet RFC1014) notation
* OpenClovis/IDE enables the generation of RMDs and linking them to a client EO
* Any function installed in an EO client can be called remotely

====RMD/EO Interface====

[[File:SDK_RMD_EO_70.png|center|frame|'''EO Execution Interface''']]

RMD and EO are tightly knit as can be observed in the illustration above. The service provider or server exposes a certain set of services by installing it in the EO. The client application interested in the service makes a RMD call to the server with the desired arguments. The node address specifies the node on which the server resides and the port identifies the server process. The RMD number specifies the service that needs to be executed of a particular client residing on the server. This request is sent across over TIPC/IOC layer to the server. The receiver thread of the server picks up this request and queues the same into the EO job queue and wakes up one of the worker threads to process the request. The worker thread checks the service requested and processes the request in the context of the server. The client is totally unaware where the service is processed. It could be in the same process address space, on a process on the same node or a process on a remote node.

Please refer the Componentization section of this document for a better understanding.

===Interface Definition Language (IDL)===

The OpenClovis Interface Definition Language (IDL) is a library used by all EOs to communicate efficiently across nodes. Using IDL, OpenClovis SAFplus Platform services can communicates across mixed endian machines and mixed mode (32-bit and 64-bit architecture) setup. This it accomplishes by providing marshalling and unmarshalling functions for the various types of arguments. Thus IDL in combination with RMD is used to provide a simple and efficient means of communication across EOs.

====IDL Usage====

The IDL generation is done through a script that takes 2 arguments:
* the xml file which provides a definition of the user's EO and relevant data structures
* a directory in which to generate the code

It then generates client and server side code for the xml definition into the specified directory. The user then issues a top level build whereafter the server & client side libraries are generated. The user should link with the client side libraries and include the client and xdr headers in his code to make client calls. On the server side, the user is expected to provide actual function definitions corresponding to the service definitions present in the xml file. He is also expected to install the server stubs before using & uninstall them during termination using the install/uninstall functions provided on a per EO basis.

Code is generated as follows:
* Top level makefile that recursively descends into client & server
* The directory xdr in which, a .c & .h is generated for every custom defined data structure in the xml.
For every struture,corresponding marshal.c and unmarshall.c files will be generated.
* client - a .c & .h is generated in this directory. They contain the definition and declaration respectively of the sync client, async client and the async callback for each EO service defined in the xml. It also contains a makefile that generates a library out of the files in this directory and the xdr directory.
* server - a .c & .h is generated in this directory. They contain the definition and declaration respectively of the server stub and the server function for each EO service defined in the xml. It also contains a makefile that generates a library out of the files in this directory and the xdr directory.

The generated code inside the target directory looks like the following:

[[File:SDK_IDL_DirectoryStructure_80.png|center|frame|'''Directory Structure of Generated Code''']]

IDL translates the user's data structures passed through a function call to a message and vice versa. Therefore it requires the user to specify the function signatures. This is currently being done through xml. The user defines the EO through the xml along with the relevant data structures. The following section describes the xml definition in detail.

====IDL Specification====

The IDL script expects the EO interface definition from the user in XML format.

=====User-Defined Types=====
The IDL uses XDR representation to store application data internally while transferring it to another EO. Therefore, IDL requires the application to specify the data structures that will be transferred through RMD so that it can generate XDR functions required to marshal/un-marshal these data structures. Marshalling is the process of converting the native data to XDR format and un-marshalling is retrieving the data back to native format. There can be three user-defined types: structures, unions and enumerations. These are explained below.

======Enumerations======
Enumerations are like enums in C and are defined likewise.

======Structures======
These are like structures in C. Therefore, every structure defined is composed of data members. There is a restriction that structures within the structures are not allowed to be defined. However, this restriction can be overcome by defining the two structures separately and embedding one inside another as a data member. Data members have the following attributes:

'''name'''
This is the name of the data member and it is referred to within the structure by this name.

'''type'''
This can be one of the pre-defined Clovis data types or a user-defined type. It is the user's
responsibility to make sure that there are no circular inclusions. Circular inclusions happen when two or more UDTs include each other in their respective definitions in such a way that it creates a cyclic dependency amongst all the involved UDTs. The supported pre-defined Clovis data types are ClInt8T, ClUint8T, ClInt16T, ClUint16T, ClInt64T, ClUint64T, ClInt32T , ClUint32T.
ClNameT and ClVersionT.

======pointer======
This is an optional attribute. When this is enabled, it means that the data member is a pointer to the type specified. We cannot specify more than one level of indirection since it is necessary to specify the number of elements being pointed to for every level of indirection.

======lengthVar======
This attribute should be specified only if the data member is a pointer type, which means that the pointer attribute is set to true. This attribute specifies which data member in the structure will contain the number of elements being pointed to. It is an optional attribute. When no such attribute is specified for a pointer type data member, it is assumed that a single element is being pointed to.

======multiplicity======
This attribute is used to specify an array type of data member. The number of elements is specified through this attribute. This attribute must not be specified along with the pointer attribute. This is an optional attribute.

======Unions======
These are defined similar to structures. The difference is in terms of the interpretation and generation.

=====EO Interface=====

The EO has multiple tables called Clients into which the exported interface functions are installed. The user has to specify which functions are installed in which tables and then give a declaration of the functions themselves. Thus, an EO interface definition consists of one or more clients:

======Client======
A client has a Client-Id, which must either be a number or a constant. A client has multiple functions called Services. A Service has a name and zero or more Arguments. The Arguments to a Service are defined as follows:

'''Handle'''
The handle is the first parameter to be passed to a call on the client side or the server side. It is initialized with the address of the destination EO, and parameters like timeout, retries and priority on the call. For more details on handles, please refer to the SISP API Reference Manual.

'''Argument'''
An argument is similar to a data member, except for the following differences:
* It does not have a multiplicity
* It has an additional attribute where the user specifies if the argument is of type:
** [CL_IN]: argument is an input to the function.
** [C_inout]: argument is an input to the function and the function is expected to fill it up and pass it back to the caller.
** [out]: the function is expected to fill the argument and pass it back to the caller.
Since an inout or an out type of argument is supposed to be passed back to the user, it must always have the pointer attribute set to true.

====XDR marshalling and unmarshalling====

The IDL uses XDR to store data into a message. This is called marshalling of data. The reverse process i.e. Of retrieving data from the message into the native format is called unmarshalling of data. XDR stands for eXternal Data Representation Standard (described in RFC 1832). It is a means of storing data in a machine independent format. We will look at relevant sections of XDR in this section.

Data structures:
IDL recognizes the following data structures:
* ClInt8T
* ClUint8T
* ClInt16T
* ClUint16T
* ClInt32T
* ClUint32T
* ClInt64T
* ClUint64T
* ClNameT
* ClVersionT
* struct formed from other data structures
* union formed from other data structures
* enum

All data structures map to respective C structures except for 'union'.
In XDR, we need to know which member in a union is valid since it needs to be marshalled/unmarshalled. Therefore a union is implemented as a structure which aggregates the respective C-style union and a member called discriminant which takes appropriate values for every member of the C-style union.

=====Marshalling=====

In all of the marshalling algorithms, the message is written to only if non-zero. The message should be 0 if the veriable under consideration needs to be deleted. All data is converted to network byte order before writing to message.

=====Unmarshalling=====

In all of the unmarshalling algorithms, the message should always be non-zero. All data is converted to host order before reading from a message.

====IDL Stubs====

The IDL generates the following for every function installed in the EO interface:
* sync client stub
* async client stub
* server stub
* async callback

In addition, it generates 2 functions to install and uninstall the server functions into the EO.

A client function is defined by it's arguments.

'''Arguments'''
Arguments or parameters are marshalled into a message which are passed to the server functions and vice versa. Therefore it is necessary to understand what type of arguments can be available and how the marshalling/unmashalling can be done. There are 2 orthogonal classifications of arguments.

Classification based on direction of transfer:
* CL_IN - these are provided as an input to a function. In our case, they are sent to the server through input message
* CL_OUT - these are used to return results to the caller. In our case, these parameters are sent from the server to the client in the output message
* CL_INOUT - these act as both input as well as output arguments. Consequently in our case, they are sent in both directions.As of now we are not handling inout variables.

Classification based on passing:
* By value - these are passed as a copy. The original variables are not modifiable.
* By reference - these are passed as address. Therefore the original variables are modifiable. Since IDL marshalls/unmarshalls the These are further categorized as:
** without count - when pointers are passed without count, they are assumed to point to a single element
** with count - when a reference is passed with a count variable (an input basic type parameter), the count variable is assumed to contain the number of elements being pointed to.

Thus an argument can be classified into one of the following categories:
* CL_IN, by value (CL_OUT type parameters return results to the callee, they always need to be passed by reference)
* CL_IN, by reference without count
* CL_IN, by reference with count
* CL_OUT, by reference without count
* CL_OUT, by reference with count

=====IDL Sync Client Stub=====

The IDL sync client stub is generated from the EO definition provided in the xml file. A stub is generated for every function installed in the EO clients. The first argument of the stub is always the handle which contains the RMD parameters and it needs to be pre-initialized. For more information on the handle, please refer to the API guide.
It has the same signature as is specified in the xml file.

=====IDL Async Client Stub=====

Same as the sync stub except that the RMD call is asynchronous. Additional arguments are supplied for this - the callback to be invoked on successful invocation and also the cookie to be passed as an argument to the callback.

=====IDL Async Callback=====

This is the function that is called when an async call is made and the context from the server returns. It is similar to the part of sync client stub which is present after the sync RMD call returns.
This function is invoked from the RMD's context.

=====IDL Server Stub=====

The IDL server stub is invoked by RMD server library in response to a request from the client. This stub gets installed in the EO's client tables.
This stub does the reverse of the sync client stub. It extracts the in from the input message and calls the actual server function with these parameters. When the function returns, it packs the out parameters in a the output message and returns destroys the variables it created.

Doc:latest/installguide

2012-02-21T03:48:18Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''Preface'''==

''SAFplus Platform Installation Guide'' guide provides the system requirements, installation procedure for SAFplus Platform software development kit (SDK) and the Evaluation System.

===Audience===

''SAFplus Platform Installation Guide'' is designed for system integrators, designers, and system architects. To use the product, you must be aware of the fundamentals of design, development, operation, management and configuration of telecommunication and networking systems. You must also be familiar with C programming, UML notations, and have the basic knowledge of Linux.

===Documentation Conventions===

This guide uses different fonts and symbols to differentiate between document elements and types of information. These conventions are summarized in the following table.

{| border="0" cellpadding="3"
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Notation
!style="color:#66b154; background:#09477c"| Description
|- style="color:#ffffff; background:#549cc6"
|style="color:black" |<code><pre>Code</pre></code>
|
This font denotes the C code provided in various examples.
|- style="color:#ffffff; background:#549cc6"
|Cross reference
|
This font denotes a hyperlink. You can click on the hyperlink text to access the reference location, which can be either a section within the User Guide or a URL link.A cross reference refers to a section name and accesses the first page of that section.
|- style="color:#ffffff; background:#549cc6"
|
'''Bold Text'''
|
Menu items and button names.
|- style="color:#ffffff; background:#549cc6"
|
'''''Italic Text'''''
|
Variables for which you enter values.
|}

 [[File:OpenClovis_Note.png]]This indicates the presence of notes or annotations, related to the context of the document.
 [[File:OpenClovis_Caution.png]]This indicates that certain precautionary measures must be taken before performing a particular task.
 [[File:OpenClovis_Info.png]]This indicates that additional information is provided to you.

===Related Documents===

For additional information about OpenClovis products, refer to the following guides:
* '''[[Doc:latest/relnotes | SAFplus Platform Release Notes]]''' provides information about the software and the hardware required to install OpenClovis Application Service Platform (SAFplus Platform) and Integrated Development Environment (IDE). It summarizes the additional features and enhancements of the product since the previous release. It also summarizes the issues and limitations of the product and provides workarounds wherever applicable.
* '''[[Doc:latest/safcompliance | SAFplus Platform SA-Forum Compliance]]''' describes the level of compliance of OpenClovis SAFplus Platform and its Application Programming Interface (API) with the relevant Service Availability Forum Specifications.
* '''[[Doc:latest/installguide | SAFplus Platform Installation Guide]]''' provides the system requirements, installation procedure for OpenClovis SAFplus Platform, IDE, and the Evaluation System.
* '''[[Doc:latest/tutorial | SAFplus Platform Sample Application Tutorial]]''' explains the steps to create and build a sample model using OpenClovis IDE and OpenClovis SAFplus Platform. It also provides troubleshooting information for this process. This provides the logical first step in understanding the SAFplus Platform offering.
* '''[[Doc:latest/evalguide | SAFplus Platform Evaluation System User Guide]]''' provides all the required information to configure and run the sample models packaged within the Evaluation System. This document also provides good understanding of OpenClovis SAFplus Platform's functionality. This is the natural follow on to the ''OpenClovis Sample Application Tutorial'' as it builds on the example created in that document.
* '''[[Doc:latest/sdkguide | SAFplus Platform SDK User Guide]]''' provides information about SAFplus Availability/Scalability Platform architecture, various SAFplus Platform components, and their interactions. This guide helps you to configure the OpenClovis SAFplus Platform components, compile, and execute the SAFplus Platform code to build your custom application.
* '''[[Doc:latest/ideguide | SAFplus Platform IDE User Guide]]''' describes the usage of Integrated Development Environment (IDE), a graphical development environment that complements the SAFplus Platform. This guide helps you to understand how to use the various features of the IDE to build the application.
* '''[[Doc:latest/logtoolguide | SAFplus Platform Log Tool User Guide]]''' provides information about the usage of OpenClovis Log Tool. OpenClovis Log Tool is an interactive utility that allows you to view binary log files in a readable format and hence monitor system errors, warnings, and other log information. Log Tool allows you to format the <code>.log</code> files and filter them to view the required entries.
* '''SAFplus Platform API Reference Guide [http://www.openclovis.org/doc/latest/apirefs/index.html]''' is provided for each component. It describes the Application Programming Interface (API), Service Model, and Management Information Model of the various OpenClovis Application Service Platform (SAFplus Platform) services. It helps the developer to understand the capabilities of the SAFplus Platform services and the APIs provided by these services.
* '''[[SAFplus Platform Console Reference Guide]]''' provides details about managing applications built on SAFplus Platform using the SAFplus Platform runtime debug console commands. SAFplus Platform Console commands can be used to manage, monitor, and test your application.

===OpenClovis Online Technical Support===

OpenClovis customers and partners can register on our Web site and receive personalized services and information. If you need any support or assistance while working on OpenClovis products, you can access the following: URL: http://www.openclovis.com. Send your queries to: support@openclovis.com. Open source community support is available at: http://www.openclovis.org/forum.

===Documentation Feedback===

We are interested in hearing from our customers on the documentation provided with the product. Let us know your comments and suggestions on improving the documentation at OpenClovis Inc. Send your comments to: support@openclovis.com. Or even better, edit (or comment in) the page on our documentation wiki located at [http://help.openclovis.com http://help.openclovis.com].

=='''Prerequisites to Install'''==

This chapter provides an overview of the OpenClovis SDK solution comprising OpenClovis SAFplus Platform and IDE. It also provides the hardware and software requirements for running OpenClovis SDK and the Evaluation System.

===Overview===

OpenClovis provides a modular and cost-effective software platform for creating next-generation communication systems. OpenClovis SDK is designed for solution integrators, network equipment manufacturers (NEPs), and telecommunication equipment manufacturers (TEMs) to facilitate the creation of a broad range of telecommunication devices, including routers, switches, media gateways and wireless infrastructure nodes.

OpenClovis fits seamlessly with various distributions of Linux and hardware platforms such as AdvancedTCA, BladeCenter T, and other off-the-shelf proprietary hardware.

The OpenClovis solution comprises OpenClovis SAFplus Platform and OpenClovis IDE.

'''OpenClovis Application Service Platform (SAFplus Platform)''' is middleware that offers a comprehensive set of modular, portable, reusable software components designed to provide system management and high availability functionality. OpenClovis SAFplus Platform is the run-time part of the OpenClovis offering. It provides run-time services for your value add applications, offering a layered, hardware-platform independent application environment.

'''OpenClovis Integrated Development Environment (IDE)''' is designed to simplify and accelerate the development of application service platforms for the telecommunication marketplace. Coupled with the OpenClovis SAFplus Platform, this intuitive software solution streamlines the process of specifying the information model, high availability (HA) aspects, and the communication infrastructure of a system. OpenClovis IDE stores all information describing a project in well defined XML files that can be modified by the user. Modeling of system resources and relationships are specified using a graphical UML editor.

'''OpenClovis Evaluation System''' is a evaluation sample system based on SAFplus Platform that provides the user with a better understanding of the scope of the product, usage patterns, its quality and usability.

===Development Host Requirements===

This section provides the hardware and software requirements for installing OpenClovis SAFplus Platform and IDE. It is not necessary to install OpenClovis IDE on the target host, as all the modeling activities are performed on the development host. The system requirements for the development host is summarized in Table [[#Table_SysReq_DevHost|System Requirements for a Development Host]].



{| border="0" cellpadding="3" align="center" width="600"
|+ align="bottom" | '''System Requirements for a Development Host'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="150"| Requirement Type
!style="color:#66b154; background:#09477c"| Requirements
|- style="color:#ffffff; background:#549cc6"
|
Hardware
|
* Intel Pentium II (or higher)
* Hard Disk - 10 GB (minimum suggested)
* RAM - 512 MB (minimum suggested)
|- style="color:#ffffff; background:#549cc6"
|
Linux Distributions
|
* Red Hat Enterprise Linux 4
* Ubuntu Linux
* CentOS 4.0
* Gentoo Linux
* Fedora Linux
* Yellow Dog Linux 4
|- style="color:#ffffff; background:#549cc6"
|
 Third Party Packages
|
* glib-2.0 - 2.6.0
* glibc 2.3.2
* gcc 3.2.3
* beecrypt
* gdbm 1.8.0
* net-snmp 5.4
* openhpi 2.8.1
* openhpi-subagent 2.3.4
* Gtk
* Eclipse SDK 3.2.2
* EMF SDK 2.2.2
* GEF SDK 3.2.2
* JRE 1.5.0_03
* Python 2.4.1
|}

[[File:OpenClovis_Note.png]]The OpenClovis SDK installation process verifies the Third Party Packages, and installs any missing packages automatically, as a part of the SDK Installation.

===Target Host Requirements===

This section provides the hardware and software requirements for installing OpenClovis SAFplus Platform on the target host. These requirements are summarized in Table [[#Table_SysReq_TargetPlatform|System Requirements for the Target Platform]].



{| border="0" cellpadding="3" align="center" width="600"
|+ align="bottom" | '''System Requirements for the Target Platform'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="150"| Requirement Type
!style="color:#66b154; background:#09477c"| Requirements
|- style="color:#ffffff; background:#549cc6"
|
Hardware
|
'''ATCA Chassis'''
* CPU Types: Intel Xeon, AMD64, Itanium2
* Blades: Intel MPCBL0001, Intel MPCBL0030, Intel MPCBL0040, Huawei Tel8000
* Shelf Management: Pigeon Point ShMM500, RadiSys
|- style="color:#ffffff; background:#549cc6"
|
 Linux Distributions
|
'''ATCA Chassis'''
* Wind-River PNE LE 1.2 (2.6.10 kernel)
* Wind-River PNE LE 1.3 (2.6.14 kernel)
* Wind-River PNE LE 1.4 (2.6.14 kernel)
* Red Hat Enterprise Linux 4.0, 5.0, etc. or Centos equivalent
* Ubuntu 9+ or similar Debian based Linux
* MontaVista Carrier Grade Linux 5.0
|}

[[File:OpenClovis_Note.png]]These are the Linux distributions on which SAFplus Platform is tested and certified.

===SAFplus Platform SDK Packages===

The SAFplus Platform SDK Installation packages listed in Table [[#Table_Required_Installation_Packages | Required Installation Packages]].



{| border="0" cellpadding="3"
|+ align="bottom"| '''Required Installation Packages'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| File Names
!style="color:#66b154; background:#09477c"| Description
|- style="color:#ffffff; background:#549cc6"
|
openclovis-sdk-3.0.tar.gz
|
This file is the core installation tarball, to install SAFplus Platform, IDE, and the evaluation system.
|- style="color:#ffffff; background:#549cc6"
|
openclovis-sdk-3.0.md5
|
This file is used to perform the data integrity check of the downloaded SDK tar file.
|- style="color:#ffffff; background:#549cc6"
|
3rdparty-base-1.8.tar
|
This file contains the third party packages for SAFplus Platform SDK.
|- style="color:#ffffff; background:#549cc6"
|
3rdparty-base-1.8.md5
|
This file is used to perform the data integrity check of the downloaded third party tar file.
|- style="color:#ffffff; background:#549cc6"
|
crossbuild-i586-wrl-pnele1.3-2.6.14-1.6.tar.gz
|
This file is used to crossbuild SAFplus Platform for an i586 target with the PNELE 1.3 kernel.
|- style="color:#ffffff; background:#549cc6"
|
crossbuild-i586-wrl-pnele1.3-2.6.14-1.6.md5
|
This file is used to perform the data integrity check of the downloaded crossbuild tar file.
|- style="color:#ffffff; background:#549cc6"
|
crossbuild-i586-wrl-pnele1.4-2.6.14_mpcbl0001-1.0.tar.gz
|
This file is used to crossbuild SAFplus Platform for an i586 target with the PNELE 1.4 kernel.
|- style="color:#ffffff; background:#549cc6"
|
crossbuild-i586-wrl-pnele1.4-2.6.14_mpcbl0001-1.0.md5
|
This file is used to perform the data integrity check of the downloaded crossbuild tar file.
|}

[[File:OpenClovis_Note.png]]OpenClovis SDK is supplemented with a set of crossbuild packages for different CPU and Operating System combinations. The md5 and crossbuild packages are optional and maybe downloaded depending on your requirements.

=='''OpenClovis SDK Installation'''==

This chapter provides a step-by-step approach for installing OpenClovis SDK. Before proceeding with installation, ensure that all the required hardware and software are available on your system. You need not install the third-party packages, as the installation package installs the third-party packages along with OpenClovis SDK.

===Installation Procedure - Get Started===

To install Openclovis SDK on your local machine, go to the directory where you have downloaded the required installation files.

Before you install,
* Ensure you have write permissions for the current directory (directory where the installation files are downloaded) and the target directory (directory where you will install the application.)
* At least 500MB of free disk space.
* You can install the SDK either as a root user or a non root user. Installing as root user is not required for a single user host. When using the SDK for larger projects it is advisable to install as root, since multiple users can share the same SDK. Irrespective of the mode of installation, the SDK can be used to model and build code using non-root privileges.

To extract the SDK package, execute the following command:

<code><pre>
# tar -xzmf openclovis-sdk-3.0.tar.gz
</pre></code>

[[File:OpenClovis_Note.png]] The <code>m</code> option to <code>tar</code> ensures that the timestamps on the files within the SDK package are consistent with the host system. This is important, since discrepancies can adversely affect the build procedure.

To ensure that your system has all the prerequisite software packages required by the installation process, the SDK package contains preinstallation scripts for a variety of Linux distributions. Prerequisite packages are packages that are supplied by your distribution but may not have been installed on your system. Essentially this is the GNU compiler toolchain and programming utilities such as pkg-config, flex, and bison. These scripts enable the user to acquire and install the prerequisite software packages automatically. Some distributions provide these packages on your installation CDROMs, so you may be asked to insert them. Other distributions provide these packages via internet-based software repositories (notably Ubuntu). If your system does not have internet access, please see ''Appendix A: Installing the Prerequisites without Internet Access''. The following table covers the distributions supported by the preinstall scripts:

{| border="0" cellpadding="3" align="center" width="600"
|+ align="bottom" | '''Distributions supported by preinstall scripts'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="150"| Preinstall script
!style="color:#66b154; background:#09477c"| Distributions supported
|- style="color:#ffffff; background:#549cc6"
|preinstall-centOS4.sh
|CentOS 4
|- style="color:#ffffff; background:#549cc6"
|preinstall-debian.sh
|Debian Linux
|- style="color:#ffffff; background:#549cc6"
|preinstall-fedora-core-6.sh
|Fedora Core 6
|- style="color:#ffffff; background:#549cc6"
|preinstall-suse.sh
|SuSE Linux
|- style="color:#ffffff; background:#549cc6"
|preinstall-ubuntu.sh
|Ubuntu Linux
|- style="color:#ffffff; background:#549cc6"
|preinstall-rhel4.sh
|Red Hat Enterprise Linux 4
|}

[[File:OpenClovis_Note.png]] '''The preinstall scripts need to be run as root.'''

[[File:OpenClovis_Note.png]] The preinstall script installs SQLite as database engine by default. If you would like to select GNU Database Manager or Berkeley Database, please visit section ''Database Abstraction Layer (DBAL)'' in ''OpenClovis SDK User Guide'' for more information.

Please run the preinstall script corresponding with your Linux distribution by executing the following commands:
<code><pre>
# cd openclovis-sdk-3.0
# ./preinstall-<os>.sh
</pre></code>

[[File:OpenClovis_Note.png]] '''An installation of Red Hat EL4 with the default package set contains all the packages required for installing OpenClovis SDK. In particular, the 'Development Tools' package subset must be installed to cover these requirements.'''

Once the preinstall script completes, start the SDK installation by executing the following command:
<code><pre>
# ./install.sh
</pre></code>

After you execute the install command, the Welcome screen is displayed as illustrated in Figure [[#OpenClovis Installer Welcome Screen | OpenClovis Installer Welcome Screen]]. When prompted by the installer, the user can enter the name of the directory where the SDK should be installed or accept the default provided:


[[File:OpenClovisSDKInstallation_WelcomeScreen_wPreInstall.png|frame|center| '''OpenClovis Installer Welcome Screen''' ]]

The default directory for installation is <code>/opt/clovis</code> for root installation and <code>$HOME/clovis</code> for non root users as illustrated in Figure [[#OpenClovis Installer Welcome Screen | OpenClovis Installer Welcome Screen]]. The installation progress is illustrated in Figure [[#Installation Directory and Progress | Installation Directory and Progress]].


[[File:OpenClovisSDKInstallation_InstallationDirectories.png|frame|center| '''Installation Directory and Progress''' ]]

===Third Party Packages===

The required third party packages are installed in the following steps:
* Scans the system for existing third party packages.
* Displays the list of packages that are available, along with their version numbers.
* Displays the list of packages that are not available or that have a version mismatch.

[[File:OpenClovis_Note.png]] This display may vary at the time of your installation, depending on the packages that are available on your system. Figure [[#Third Party Packages - Availability Status | Third Party Packages - Availability Status]] demonstrates a typical display.


[[File:OpenClovisSDKInstallation_ThirdPartyPackages.png|frame|center| '''Third Party Packages - Availability Status''']]

To proceed with the installation, enter <code>y</code> for the message, <code>Proceed with the installation <y/n> [y]: </code>

Figure [[#Third Party Packages Installation Progress | Third Party Packages Installation Progress]] illustrates the approximate installation time and the installation status for each package.


[[File:OpenClovisSDKInstallation_3rdPartyPackageInstallationProgress.png|frame|center| '''Third Party Packages Installation Progress''']]

After installation of third party packages, the installer displays the message, <code>All SDK dependencies are now in place.</code> as illustrated in Figure [[#OpenClovis Packages Installation - Status | OpenClovis Packages Installation - Status]].


[[File:OpenClovisSDKInstallation_InstallationStatus.png|frame|center| '''OpenClovis Packages Installation - Status''']]

After completion of the third party packages, the installer prompts the user for the installation of the crossbuild toolchains.

===Crossbuild Toolchains===

Crossbuild toolchains are required to install SAFplus Platform on a platform that is different from the development host platform. For instance if the development host is x86 Intel based and the target platform is PowerPC based the user will need a crossbuild toolchain for that particular PowerPC based architecture.

For crossbuild toolchains, you will require the following:
* A cross compiler and related binary tools for the target CPU architecture.
* All the SAFplus Platform prerequisites that are pre-compiled for the target platform, so that all library files are available.

OpenClovis SDK comes with a standard set of pre-built crossbuild toolchain packages. The names of these packages help you to identify the CPU and OS combinations for which they have been built.

The SDK installer (<code>install.sh</code>) assists you in installing one or more of these toolchains as illustrated in Figure [[#Crossbuild Toolchains | Crossbuild Toolchains]]. Enter the crossbuild toolchain that you require to be installed from the available list. After the toolchains are installed, you can select any of these cross-tools for your project build.


[[File:OpenClovisSDKInstallation_Crossbuildtoolchains.png|frame|center| '''Crossbuild Toolchains''' ]]

If you would like to install more crossbuild toolchains at a later time, please download them and re-run <code>install.sh</code>. You may skip the remaining portions of the install process past the installation of crossbuild toolchains when you are prompted to do so.

===SAFplus Platform, IDE and Utilities===

 After installation of the toolchain, the system proceeds with the installation of SAFplus Platform, IDE and Utilities as illustrated in Figure [[#Installing SAFplus Platform, IDE and Utilities | Installing SAFplus Platform, IDE and Utilities]].


[[File:OpenClovisSDKInstallation_InstallingASP_IDE_Utilities.png|frame|center| '''Installing SAFplus Platform, IDE and Utilities''' ]]

 The installer creates the required binaries and prompts you to create optional symbolic links, so that the SDK commands can be accessed on your system in a well known location, as illustrated in Figure [[#Creating Symbolic Links | Creating Symbolic Links]]. The main SDK commands of interest to the user are:
<ul>
<li><code>cl-create-project-area</code>: Command to create a new OpenClovis SDK project area. A project area is the workspace for the OpenClovis SDK. It contains the IDE models and the generated source code. The user makes modifications to the generated source within this workspace and builds runtime images here as well. A typical project area has the following directory structure:
<code><pre>
<project_area>
|ide_workspace
|+<model>
| |+build
| | |+local
| | | |-Makefile
| | |+<crossbuild>
| | | |-Makefile
| |+src
| | |+app
| | |+config
| | |+doc
| | |-target.conf
| |+target
| |-Makefile
|-Makefile
</pre></code>

<li><code>cl-ide</code>: Command to start the OpenClovis IDE. Please note that you should have already created a project area using <code>cl-create-project-area</code> before using <code>cl-ide</code> to work within this project area.
</ul>


[[File:OpenClovisSDKInstallation_CreateSymbolicLinks.png|frame|center| '''Creating Symbolic Links''' ]]

Enter <code>Y</code> to create the symbolic links. The installer then prompts the user for a location to place the links with a default option <code>/usr/local/bin</code> if you are installing as root, or <code>$HOME/bin</code> for non root user installation.

If you choose not to create symbolic links and enter <code>N</code>, then you can either:
<ul>
<li>Add the installation directory to the shell path. For example with a bash shell:
<code><pre>
export PATH=$PATH:<install_dir>/sdk-3.0/bin
</pre></code>
<li>or access the SDK commands from the <code><install_dir>/sdk-3.0/bin/</code> directory. For example to create a new project area at <code><project-area_dir></code>:
<code><pre>
<install_dir>/sdk-3.0/bin/cl-create-project-area <project-area_dir>
</pre></code>
</ul>

After creating symbolic links, the installation of OpenClovis SDK is complete. All the required packages and crossbuild toolchains are installed and the directory where you have downloaded the installation packages can be discarded.

[[File:OpenClovis_Note.png]]If your installation is not successful, or if you encounter any problems during the installation, refer to the Chapter [[#Troubleshooting | Troubleshooting]].

===Next Steps===

After completing the Installation, the OpenClovis SDK Documentation set listed in the [[#Related Documents| Related Documents]] section is available in the <code>doc</code> folder located at <code><install_dir>/sdk-3.0</code> directory.

We recommend the following steps to get familiar with our product:

*'''Read and follow the OpenClovis Sample Application Tutorial''' - The ''Sample Application Tutorial'' will step you through the process of creating a high available system. It takes you from model conception all the way through deployment and running of the sytem. After going through this guide you will understand the basics of the OpenClovis offering.

*'''Read and follow the OpenClovis Evaluation System User Guide''' - ''Evaluation System User Guide'' will introduce you to more advanced modelling topics. These topics are introduced incrementally through a series of targeted tutorials. After completing this guide you will be ready to start building your own system.

=='''Troubleshooting'''==

This chapter describes some of the probable errors that you may encounter during the installation. This chapter also provides the solution to these errors.The errors that you may encounter are:

<ul>

<li>
'''Error''': Installation Failure, during third party installation.
 
'''Solution''': You can manually fix this error by getting more information from the corresponding log file under the log directory. You can also send the <code>log.tar.gz</code> to support@openclovis.com for more help.
The installation can be resumed after the errors are fixed. The installer will detect any new updates and proceed with the missing prerequisites.
 

<li>
'''Error''': <code>gcc (pkg-config, perl, md5sum) not found in your PATH</code>.
 
'''Solution''': Ensure that the directory where the <code>gcc</code> resides is in the <code>PATH</code> variable.
 

<li>
'''Error''': Not enough space on the target installation directory.
 
'''Solution''' : Change the target installation directory to the directory with at least 500MB free disk space.
 

<li>
'''Error''': <code><WORKING_DIRECTORY></code> is read-only.
 
'''Solution''': You need to have write permission for the current working directory to extract the contents of the archive, configure, and build. Ensure that you turn ON write permission using <code>chmod +w ...</code> command.
 

<li>
'''Error''': md5 checksums are used to check if the packages are correctly downloaded. If they are not downloaded correctly, the system displays the message: <code>It is not safe to install these packages, please download them again.</code>
 
'''Solution''':The installer checks the integrity of the downloaded packages. If the download is either incomplete or corrupt, download the packages again.
 

<li>
'''Error''': SAFplus Platform fails to start, reporting the underlying SQLite database version used is not-supported.
 
'''Solution''': Use SQLite version 3.3.13 or newer. The source code can be downloaded from http://www.sqlite.org/download.html. The user can install the latest version of SQLite if the specified version is
not present in this repository.
</ul>

=='''Appendix A: Installing the Prerequisites without Internet Access'''==

Some customers do not want their evaluation system to have internet access for security purposes. If this is your situation, please consider temporarily enabling internet access while running the "preinstall-<os>" script. At this point the evaluation system should only have the base OS installed, so there is no proprietary data on the system. Also note that the "preinstall" scripts are only about a page long so you can easily review them for security purposes.

However, if you still do not want to enable internet access one strategy that can be used is to go to a system with internet access (it must use the same Linux distribution and the same version), download them there, use a USB flash drive to move them to the unconnected system, and then install them on that system. If this approach is unacceptable (it does still use the internet), then perhaps the Linux distribution you chose is not appropriate -- instead use one that contains all packages on the installation CDROMs.

===Example Using Ubuntu 7.04===

Packages can be downloaded but not installed on Ubuntu by using the "-d" flag to the "apt-get" package manager. The files are downloaded to "/var/cache/apt/archives". It is recommended to remove (or move) all files in this directory first (it is just a cache, and so it will contain any packages that you have previously installed), so that the directory contains just the packages needed for the OpenClovis SDK:

rm /var/cache/apt/archives/*

Next edit the preinstall-ubuntu.sh script, search for all instances of "apt-get" and add the flags "-d --reinstall" just after the "apt-get" program. For example:

apt-get -d --reinstall -y --force-yes install build-essential

Next run this modified script on your internet-connected machine. This script will download 6MB of files (this list will vary by Linux distribution or version):

bison_1%3a2.3.dfsg-4build1_i386.deb
libgdbm-dev_1.8.3-3_i386.deb
build-essential_11.3_i386.deb
libltdl3-dev_1.5.22-4_i386.deb
e2fslibs-dev_1.39+1.40- WIP-2006.11.14+dfsg-2ubuntu1_i386.deb
libperl-dev_5.8.8-7build1_i386.deb
e2fsprogs_1.39+1.40-WIP-2006.11.14+dfsg-2ubuntu1_i386.deb
linux-headers-2.6.20-16-generic_2.6.20-16.32_i386.deb
flex_2.5.33-10build1_i386.deb
gawk_1%3a3.1.5.dfsg-4build1_i386.deb
gettext_0.16.1-1ubuntu2_i386.deb
pkg-config_0.21-1build1_i386.deb
libdb4.5-dev_4.5.20-1ubuntu1_i386.deb
uuid-dev_1.2- 1.39+1.40-WIP-2006.11.14+dfsg-2ubuntu1_i386.deb

Now copy these files to a new directory in your unconnected machine:

On the connected machine:
root@desktop:/# cp /var/cache/apt/archives/*.deb <your flash media>

On the unconnected machine:
root@desktop:/# mkdir /root/pkgs
root@desktop:/# cp <your flash media> /root/pkgs/

Finally, install them using the standard "dpkg" package installer:

root@desktop :/# cd /root/pkgs
root@desktop:~/pkgs# dpkg -i *.deb
(Reading database ... 113653 files and directories currently installed.)
...
root@desktop:~/pkgs#

At this point, you should be done installing the prerequisites! You should now continue the installation procedure at the step after installing prequisites.

Doc:latest/safcompliance

2012-02-21T03:48:17Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''Introduction'''==

Adherence to standards is a critical requirement for Next Generation Network
deployments. The Service Availability Forum (SA Forum) is the primary standards body in
the context of High Availability Middleware and enjoys the participation of over 95% of
Tier 1 TEMs. OpenClovis has been actively participating in the forum and helping to drive
the emerging Hardware Platform Interface (HPI) and Application Interface Specification
(AIS) standards based on its experience.

As a result of the close involvement of OpenClovis with the SA Forum, the OpenClovis
SAFplus Platform product has been aligned with SA Forum AIS architecture and functional partitioning
from its inception and has kept pace with the evolution in the specifications and in many
cases, anticipated new features and functionality.

Even as the specifications are evolving, the SA Forum is in the process of defining a test
suite that will establish compliance of a product to the specifications. While this activity is
in an advanced state for the HPI specifications, it has not yet taken off for AIS
specifications. Partial compliance test suites are expected to be available for HPI by end
of the 2006 calendar year.

It should be noted that where a specification is 'A' level (example: SAI-AIS-NTF-A.01.01
for the Notification Service), SAF is not obligated to preserve backward compatibility
while going to a 'B' level version of the specification. On the other hand, backward
compatibility with respect to API's will be preserved between different versions of the 'B'
level specifications (Example: between SAI-AMF-B01.01 and SAI-AMF-B02.01)

OpenClovis expects to formally establish the compliance of SAFplus Platform to the SA Forum AIS
standards as and when these compliance test suites become available. This document
details the level of alignment of OpenClovis SAFplus Platform with the SA Forum specifications.

=='''Standards Referenced'''==

The SA Forum specifications referred to in this document are available at http://www.saforum.org/home. The versions of the specifications referred to are

*SAI-Overview-B.02.01
*SAI-AIS-AMF-B.02.01
*SAI-AIS-MSG-B.02.01

*AIS-CKPT-B.01.01
*AIS-EVT-B.01.01
*AIS-CLM-B.01.01

*SAI-AIS_LOG-A.01.01
*SAI-AIS-IMM-A.01.01
*SAI-AIS-NTF-A.01.01
*SAI-AIS-NAM-A.01.01
*Hardware Platform Interface Specification B.01.01

=='''Compliance with Service Availability Forum AIS Architecture'''==

OpenClovis SAFplus Platform complies with the Service Availability Forum (SAF) Hardware Platform Interface (HPI) and Application Interface Specification (AIS) specifications. OpenClovis Inc. is actively participating in the SA Forum and helping to drive the emerging HPI and AIS standards based on its experience.

===Programming Model and Usage===

Section 3.1 of SAI-AIS-Overview-B.02.01 describes the SAF Application Interface programming model and the generally intended usage of the interfaces.

It introduces the area server as an abstraction that represents the server providing services for a specification area, for instance, Availability Management Framework, Group Membership Service and so on. The interface is defined as occurring between a user application that needs the services of the area server and an area implementation library.

OpenClovis SAFplus Platform adheres to the SAF area server-area implementation library abstraction and the SAF programming and usage model in providing various services.

===Availability Management Framework (AMF)===

The Availability Management Framework (AMF) is the most important software entity of the SAF AIS Specification. It provides service availability by coordinating redundant resources within a cluster to deliver a system without a single point of failure. AMF prescribes a way to model applications that needs to be highly available. In addition, AMF provides a set of APIs that must be used by these applications to be managed for high availability.

OpenClovis SAFplus Platform is implemented in complete accordance with the SAF AMF model and interfaces. This may be considered as the core of the SAF solution for high availability. The only limitation in the current release with respect to the AMF component model is that SAF defines a flexible mapping between components, processes and threads whereas OpenClovis SAFplus Platform supports only a single process per component. OpenClovis Inc. offers to support one-to-one relationship between a component and a process. However, a component can have multiple threads of execution within it.

===Application Interface Specification (AIS) Services===

The following OpenClovis SAFplus Platform components provide services that are functionally equivalent to SAF AIS specifications:
*Availability Management Framework (AMF)
*Checkpoint Service (CPS)
*Event Manager (EM)
*Group Membership Service (GMS)
*Messaging Service (MSG)

===SAFplus Platform AMF Features===
*'''HA model supported'''
** 2N
** M+N

*'''Auto Adjust'''
SAF SG auto adjust feature to adjust the SG based on the SU ranking giving preference to higher ranked ones for active assignments

*'''SI Dependency'''
SAF SI dependency across service groups

*'''CSI Dependency'''
SAF CSI dependency within the same SI for work assignments

*'''Component instantiation dependency'''
SAF component instantiation dependency for components within the same Service Unit configurable through instantiationLevel attribute.

*'''Reduction Procedure'''
SAF SG reduction procedure applied when the SG is running under reduced potential for computing and removing less optimal standby assignments to assign Service Instances.

*'''AMF NOTIFICATIONS'''
SAF HAStateChangeNotify and SIAssignmentStateChangeNotify notifications for applications to subscribe for AMF state transitions

*'''Preferred SI assignment'''
Preferred SI assignment that could be configured for SUs to control SI assignments. Coupled with the delayed SG startup configuration through restartDuration to control instantiation of all the preferred SUs, SI preference could be enforced during initial cluster startup for the Service units in the cluster.

*'''Proxy-Proxied support'''
Allow HA control of legacy application (non-SAF awared) via proxy

===SAFplus Platform Cluster/Group Membership Service (GMS) Features===
The SA-Forum CLM API is fully supported.

*'''Cluster Membership'''
CLM service manages the membership of the nodes. It manages the cluster formation during node joins and leaves.

*'''Tracking Cluster Membership'''
Any application can register for Cluster Track callback through which it can get the notification for any node joins and leaves in the cluster

*'''Getting Cluster Member information'''
API interface are available to get the information such as Address, node name etc, for any given cluster member node.

*'''Cluster node eviction/ejection'''
A cluster node can be administratively ejected from the cluster.

===SAFplus Platform Checkpointing Service (CPS) Features===
*'''Checkpoint/Section creation/deletion'''
CPS provides APIs for users to create/delete checkpoints and sections within the checkpoints.

*'''Granularity at Section level'''
CPS allows user to create a checkpoint and inside a checkpoint user can create any number of sections and read/write each sections independently.

*'''Checkpoint Status'''
CPS provides API to retrieve checkpoint status.

*'''Locking at Section level'''
CPS provides read/write locks at section level due to which multiple sections can be accessed simultaneously.

*'''Update options'''
CPS allows both Synchronous and Asynchronous update of the checkpoint replicas across the cluster

*'''Replica Management'''
CPS allows both collocated and non-collocated mode of checkpoint replicas

*'''Choosing replica at run time'''
User can use ActiveReplicaSet() APIs to set the active replica at run time.

*'''Retention time'''
CPS provides users to specify a retention time for which the checkpoint is retained even when no one is accessing the checkpoint

*'''Section Expiration Time'''
User can set an absolute expiration time for a section after which the section is deleted irrespective of its usage at that time.

*'''Section Iteration'''
Users can iterate through the sections of a checkpoint.

===SAFplus Platform Event Service features===
*'''Publish/Subscribe multipoint-to-multipoint communication mechanism'''
** Based on concept of event channels
** Publisher communicates asynchronously with one or more subscribers over an event channel
** Multiple publishers and subscribers can communicate over the same event channel; publishers can be subscribers on the same event channel
** Individual publishers and individual subscribers can communicate over multiple channels
*'''Events consist of standard header and one or more bytes of payload data'''
** i.e. Event Service does not impose any specific transfer syntax for the data
*'''Event channel management'''
** Event service provides APIs for opening, closing and deleting event channels
*'''Event operations'''
** Event service provides APIs for managing the event payload data, publishing the event, subscribing for the event etc

===Additional SAFplus Platform Services===

OpenClovis SAFplus Platform also provides various components that were implemented earlier than its implementation with SAF specifications. These components provide services that are functional equivalent to SAF AIS services as listed below:

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''SAFplus Platform Services Equivalent to SA Forum AIS Services'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| OpenClovis SAFplus Platform Components
!style="color:#66b154; background:#09477c"| Functionally Equivalent AIS Service
!style="color:#66b154; background:#09477c"| AIS Specification
|- style="color:#ffffff; background:#549cc6"
|
Clovis Object Repository (COR)
|
Information Model Management Service
|
SAI-AIS-IMM-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Alarm Manager (AM)
|
Notification Service
|
SAI-AIS-NTF-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Log Service
|
Logging Service
|
SAI-AIS-LOG-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Naming Service
|
Naming Service
|
SAI-AIS-NAM-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Platform Management Service
|
Platform Management Service
|
SAI-AIS-PLM-A.01.01
|- style="color:#ffffff; background:#549cc6"
|}

===IMM (OpenClovis Object Repository - COR) Features===
The OpenClovis Object Repository(COR) implements the IMM features. We are progressing on having API level compliance which will be available in R5.0.

The following are the IMM compliant features of COR:

*'''Object Mananger and Object Implementer'''
**COR provides a rich set of APIs to make configuration changes on a Managed Object (MO). It provides service to implement a MO by multiple Object Implementers (OI), so that the configuration changes on the MO can be validated by all the OIs. It provides APIs to make or remove an application as a OI for a MO.

*'''Runtime Attributes Management'''
**COR provides service to implement the runtime attributes of an object or all the object instances of a class. The Runtime attributes values can be cached or non-cached in COR. The cached runtime attributes values has to be updated by Primary Object Implementer (POI) periodically in COR. The value of non-cached runtime attributes will be updated by POI on request by COR. The values of cached runtime attributes can be persisted into storage devices.

*'''Configuration Attributes Management'''
**The Configuration attributes are always cached and persisted by COR. Any configuration change on these attributes by a OM will be implemented by all the OIs.

*'''Attribute Characteristics'''
**COR supports the following attribute characteristics.
***CONFIG - Indicates that the attribute is a configuration type attribute.
***RUNTIME - Indicates that the attribute is a runtime attribute.
***WRITABLE - Indicates that the configuration attribute can be modified.
***INITIALIZED - Indicates that value for the configuration attribute must be specified when the object is created.
***CACHED - Indicates that the value of the attribute is cached in COR.
***PERSISTENT - Indicates that the value of the attribute must be stored in a permanent manner by COR

*'''Object Class Management'''
**COR provides APIs to create, delete and modify the classes, and to make hierarchical relationship between the classes. It also provides service to inherit the existing class to create a new class.

*'''Tree organization of Objects'''
**COR organizes the MOs in a hierarchical manner supporting parent-child relationship, inheritance, association and containment relationships.

*'''Search Operations'''
**The search operations can be performed on a single MO, or a MO and its children, or a sub tree rooted from the given MO.
**We can either retrieve all the attributes in the MO matching the given criteria or only the matching attributes.

*'''Object Access'''
**COR bundle GET APIs can be used to retrieve the attributes values in a efficient manner by grouping the GET requests belonging different MOs into one single request to COR. The values of runtime non-cached attributes will be updated by POI on request by COR.

*'''Class Implementer'''
**COR provides APIs for the application to implement all the Object instances of a class, for both Configuration and Runtime attributes.

===SAF Notification Features===
OpenClovis SAFplus Platform is compliant with the following Notification features :

*'''Notification Types'''
**Alarm
**State Change
**Object Create/Delete
**Attribute Change

*'''Alarm Notification'''
**An alarm report is a notification of a specific event that may or may not represent an error. OpenClovis Alarm notification is fully compliant with ITU-T X.733 standard (which is recommended by SAF-NTF).

*'''State Change Notification'''
**OpenClovis AMF provides services for the following state change notifications to the Management Applications
***HA state of the SU changed
***SI partially/fully assigned
***Component arrived/departed
***Node arrived/departed

*'''Object Create/Delete and Attribute Change Notifications'''
**OpenClovis SAFplus Platform provides services for the notification of Managed Object Creation, Deletion and Attribute changes. It also supports the Management Applications to filter the attribute change notifications based on attribute identifiers.

*'''Notification Delivery Characteristics'''
**Guaranteed delivery
**At most once delivery
**Ordered delivery
**Persisted (Alarm notifications).

*'''Notification Filtering'''
**OpenClovis SAFplus Platform provides service for filtering the notifications based on one or more filter criteria which is particular to the notification type. It also provides the ability to correlate with the other notifications.

=='''Support for SAF AIS Interfaces'''==

OpenClovis SAFplus Platform complies with the SAF AIS interfaces for the following components:

===Availability Management Framework (AMF)===

OpenClovis Availability Management Framework (AMF) supports the following SAF AIS interfaces as mentioned in SAI-AIS-AMF-B.02.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of AMF'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saAmfInitialize()
* saAmfSelectionObjectGet()
* saAmfDispatch()
* saAmfFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Component Health Monitoring
|
* saAmfHealthCheckStart()
* saAmfHealthCheckStop()
* SaAmfHealthCheckCallbackT
* saAmfHealthCheckConfirm()
|- style="color:#ffffff; background:#549cc6"
|
Component Registration and Un-registration
|
* saAmfComponentRegister()
* saAmfComponentUnregister()
* saAmfComponentNameGet()
|- style="color:#ffffff; background:#549cc6"
|
Component Service Instance Management
|
* saAmfHAStateGet()
* SaAmfCSISetCallbackT
* SaAmfCSIRemoveCallbackT
* saAmfCSIQuiescingComplete()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of AMF'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Component Lifecycle Management
|
* SaAmfComponentTerminateCallbackT
* SaAmfProxiedComponentInstantiateCallbackT
* SaAmfProxiedComponentCleanupCallbackT
|- style="color:#ffffff; background:#549cc6"
|
Protection Group Management
|
* saAmfProtectionGroupTrack()
* SaAmfProtectionGroupTrackCallbackT
* saAmfProtectionGroupTrackStop()
|- style="color:#ffffff; background:#549cc6"
|
Component Error Reporting
|
* saAmfComponentErrorReport()
|- style="color:#ffffff; background:#549cc6"
|
Component Response
|
* saAmfResponse()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Unsupported API's of AMF'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Brief
!style="color:#66b154; background:#09477c"| Unsupported APIs
|- style="color:#ffffff; background:#549cc6"
|
Passive Monitoring of processes is not supported
|
* saAmfPmStart()
* saAmfPmStop()
|- style="color:#ffffff; background:#549cc6"
|
Freeing the memory allocated by the saAmfProtectionGroupTrack()
|
* saAmfProtectionGroupNotificationFree()
|- style="color:#ffffff; background:#549cc6"
|
Component Error Clear API is not supported.
|
* saAmfComponentErrorClear()
|}

===Checkpointing Service (CPS)===

OpenClovis Checkpointing Service (CPS) supports the following SAF AIS interfaces as mentioned in SAI-AIS-CKPT-B.01.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of CPS'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saCkptInitialize()
* saCkptSelectionObjectGet()
* saCkptDispatch()
* saCkptFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Checkpoint Management
|
* saCkptCheckpointOpen()
* saCkptCheckpointOpenCallabackT
* saCkptCheckpointOpenAsync()
* saCkptCheckpointClose()
* saCkptCheckpointUnlink()
* saCkptActiveReplicaSet()
* saCkptCheckpointRetentionDurationSet()
* saCkptCheckpointStatusGet()
|- style="color:#ffffff; background:#549cc6"
|
Section Management
|
* saCkptSectionIterationInitialize()
* saCkptSectionIterationNext()
* saCkptSectionIterationFinalize()
* saCkptSectionCreate()
* saCkptSectionExpirationTimeSet()
* saCkptSectionDelete()
* saCkptCheckpointWrite()
|- style="color:#ffffff; background:#549cc6"
|
Data Management
|
* saCkptSectionOverwrite()
* saCkptCheckpointRead()
* saCkptCheckpointSynchronize()
* saCkptCheckpointSynchronizeAsync()
* SaCkptCheckpointSynchronizeCallbackT
|}

===Event Manager (EM)===

OpenClovis Event Manager supports the following SAF AIS interfaces as mentioned in SAI-AIS-EVT-B.01.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of EM'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saEvtInitialize()
* saEvtFinalize()
* saEvtSelectionObjectGet()
* saEvtDispatch()
|- style="color:#ffffff; background:#549cc6"
|
Event Operations
|
* saEvtEventAllocate()
* saEvtEventFree()
* saEvtEventAttributesSet()
* saEvtEventAttributesGet()
* saEvtEventDataGet()
* saEvtEventPublish()
* saEvtEventSubscribe()
* SaEvtEventDeliverCallbackT
* saEvtEventUnsubscribe()
|- style="color:#ffffff; background:#549cc6"
|
Event Channel Operations
|
* saEvtChannelOpen()
* saEvtChannelOpenAsync()
* SaEvtChannelOpenCallbackT
* saEvtChannelUnlink()
* saEvtChannelClose()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Unsupported API's of EM'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Brief
!style="color:#66b154; background:#09477c"| Unsupported APIs
|- style="color:#ffffff; background:#549cc6"
|
Event Retention Time is not supported
|
* saEvtEventRetentionTimeClear()
|}

===Group Membership Service (GMS)===

OpenClovis Group Membership Service (GMS) supports the following SAF AIS interfaces as mentioned in AIS-CLM-B.01.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of GMS'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saClmInitialize()
* saClmSelectionObjectGet()
* saClmDispatch()
* saClmFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Group Membership Operations
|
* saClmClusterTrack()
* SaClmClusterTrackCallbackT
* saClmClusterTrackStop()
* saClmClusterNodeGet()
* saClmClusterNodeGetAsync()
* SaClmClusterNodeGetCallbackT
|}

===Messaging Service (MSG)===

OpenClovis Messaging Service (MSG) supports the following SAF AIS interfaces as mentioned in SAF-AIS-MSG-B.02.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of MSG'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saMsgInitialize()
* saMsgSelectionObjectGet()
* saMsgDispatch()
* saMsgFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Message Queue Operations
|
* saMsgQueueOpen()
* saMsgQueueOpenAsync()
* SaMsgQueueOpenCallbackT
* saMsgQueueClose()
* saMsgQueueStatusGet()
* saMsgQueueRetentionTimeSet()
* saMsgQueueUnlink()
|- style="color:#ffffff; background:#549cc6"
|
Management of Message Queue Groups
|
* saMsgQueueGroupCreate()
* saMsgQueueGroupInsert()
* saMsgQueueGroupRemove()
* saMsgQueueGroupDelete()
* saMsgQueueGroupTrack()
* SaMsgQueueGroupTrackCallbackT
* saMsgQueueGroupTrackStop()
* saMsgQueueGroupNotificationFree()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of MSG'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Message Send and Receive Operations
|
* saMsgMessageSend()
* saMsgMessageSendAsync()
* SaMsgMessageDeliveredCallbackT
* saMsgMessageGet()
* saMsgMessageDataFree()
* SaMsgMessagedReceivedCallbackT
* saMsgMessageCancel()
|- style="color:#ffffff; background:#549cc6"
|
Request and Reply Operations
|
* saMsgMessageSendReceive()
* saMsgMessageReply()
* saMsgMessageReplyAsync()
|}

=='''Software Management Framework (SMF)'''==

SMF Aligned In Service Software Upgrade (ISSU.
Supports application and OpenClovis SAFplus Platform middleware upgrade in a rolling (in-service) or single-step mode.

'''Single-Step'''
For deployment of non-backwards compatible software, or rapid deployment of software. This method stops the relevant services on all nodes (causing an outage) and then upgrades that software and restarts. Note that services are stopped at various granularity levels depending on what is being upgraded. In other words, application A can be taken out-of-service and upgraded across the cluster without affecting application B running on the same nodes.

'''Inservice Rolling'''
This is the most commonly known telecom quality upgrade method. For deployment of backwards-compatible software across the cluster, this method stops service in one "upgrade unit" at a time, upgrades the software and restarts before stopping the next "upgrade unit". This process continues iteratively until the entire cluster is upgraded. Since the available redundant capacity takes over for the unit being upgraded service will be unaffected.

=='''Hardware Platform Interface (HPI)'''==

SAFplus Platform has been integrated and tested with the following implementations of HPI B.01.01 specification.
* OpenHPI 2.8.1, 2.10.2, 2.16.0
* Radisys HPI 1.4

The following sections lists out the SAF HPI APIs that are used by SAFplus Platform. Platform provider shall provide at these HPI services in order to integration with OpenClovis SAFplus Platform

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''SAF HPI APIs used by SAFplus'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
General APIs
|
* saHpiVersionGet()
|- style="color:#ffffff; background:#549cc6"
|
Domain APIs
|
* saHpiSessionClose()
* saHpiSessionOpen()
* saHpiDiscover()
* saHpiRptEntryGet()
* saHpiRptEntryGetByResourceId()
* saHpiSubscribe()
* saHpiUnsubscribe()
* saHpiEventGet()
|- style="color:#ffffff; background:#549cc6"
|
Resource APIs
|
* saHpiRdrGet()
* saHpiAutoExtractTimeoutSet()
* saHpiAutoInsertTimeoutSet()
* saHpiHotSwapPolicyCancel()
* saHpiResourceActiveSet()
* saHpiResourceInactiveSet()
* saHpiHotSwapStateGet()
* saHpiHotSwapActionRequest()
* saHpiHotSwapIndicatorStateGet()
* saHpiResourceResetStateSet()
* saHpiResourcePowerStateSet()
|}

In addition to the above APIs SAFplus Platform also depends on the following events generated by HPI
# Hot Swap events (SAHPI_ET_HOTSWAP)
# Sensor events (SAHPI_ET_SENSOR)
# Resource Events (SAHPI_ET_RESOURCE)

=='''Modifications to SAF AIS Header files'''==

In a few instances, OpenClovis engineers found that the standard SAF-supplied header files caused errors and warnings on certain compilers. In these cases OpenClovis modified the standard SAF header file to work with these compilers. All of these changes broaden the set of compatible compilers. None of these changes modify the SAF APIs.

For example, in saAis.h, the following constant is defined:

#define SA_TIME_ONE_MINUTE 60000000000

However, the number defined is greater than a 32-bit integer, so it is actually required to append a size suffix:

#define SA_TIME_ONE_MINUTE 60000000000LL

Doc:latest/logtoolguide

2012-02-21T03:48:16Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''Preface'''==

 ''OpenClovis Log Tool User Guide'' provides information about the usage of OpenClovis Log Tool.
OpenClovis Log Tool is an interactive utility that allows you to view binary log files in a readable format and hence monitor system errors, warnings, and other log information. By analyzing this information, you can troubleshoot the errors. These log files are in raw format and hard to read. Log Tool allows you to format the files and filter them for the required entries.

===Documentation Conventions===

This guide uses different fonts and symbols to differentiate between document elements and types of information. These conventions are summarized in the following table:

{| border="0" cellpadding="3"
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Notation
!style="color:#66b154; background:#09477c"| Description
|- style="color:#ffffff; background:#549cc6"
|style="color:black" | <code><pre>Code</pre></code>
|
This font denotes various commands and their usage.
|- style="color:#ffffff; background:#549cc6"
|
Cross reference
|
This font denotes a hyperlink. You can click on the hyperlink text to access the reference location, which can be either a section within the User Guide or a URL link.
A cross reference refers to a section name accesses the first page of that section.
|- style="color:#ffffff; background:#549cc6"
|
'''Bold Text'''
|
Menu items and button names.
|- style="color:#ffffff; background:#549cc6"
|
''Italic Text''
|
Variables for which you enter values.
|}

 [[File:OpenClovis_Note.png]]This indicates the presence of notes or annotations, related to the context of the document.
 [[File:OpenClovis_Caution.png]]This indicates that certain precautionary measures must be taken before performing a particular task.
 [[File:OpenClovis_Info.png]]This indicates that additional information is provided to you.

===Document Organization===

This guide is organized into various chapters to provide information on specific areas. The following table introduces the chapter names and a brief overview of the content.
{| border="0" cellpadding="3"
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Chapter
!style="color:#66b154; background:#09477c"| Overview
|- style="color:#ffffff; background:#549cc6"
|
Preface
|
This chapter gives an introduction to OpenClovis Log Tool.
|- style="color:#ffffff; background:#549cc6"
|
Available Tools
|
This chapter helps you understand the conceptual information, advantages and key features of OpenClovis Log Tools. It provides information to access the available Log Tools, Command Line Log Tool and Offline GUI Log Tool.
|}
 

===Related Documents===

For additional information about OpenClovis products, refer to the following guides:
* '''OpenClovis Release Notes''' provides information about the software and the hardware required to install OpenClovis Application Service Platform (SAFplus Platform) and Integrated Development Environment (IDE). It contains the additional features and enhancements of the product since the previous release. It also summarizes the issues and limitations of the product and provides workarounds wherever applicable.
* '''OpenClovis SA Forum Compliance''' describes the level of compliance of OpenClovis SAFplus Platform and its Application Programming Interface (API) with the relevant Service Availability Forum Specifications.
* '''OpenClovis Installation Guide''' provides the system requirements, installation procedure for OpenClovis SAFplus Platform, IDE, and the Evaluation System.
* '''OpenClovis Sample Application Tutorial''' provides the steps to create and build a sample model using OpenClovis IDE and OpenClovis SAFplus Platform. It also provides troubleshooting information for this process. This provides the logical first step in understanding the OpenClovis offering.
* '''OpenClovis Evaluation System User Guide''' provides all the required information to configure and run the sample models packaged within the Evaluation System. This document also provides good understanding of OpenClovis SAFplus Platform's functionality. This is the natural follow on to the ''OpenClovis Sample Application Tutorial'' as it builds on the example created in that document.
* '''OpenClovis SDK User Guide''' provides information about OpenClovis Application Service Platform (SAFplus Platform) architecture, various OpenClovis SAFplus Platform components, and their interactions. This guide helps you to configure the OpenClovis SAFplus Platform components, compile, and execute the OpenClovis SAFplus Platform code to build your custom application.
* '''OpenClovis IDE User Guide''' describes the usage of Integrated Development Environment (IDE), a graphical development environment that complements the SAFplus Platform platform. This guide helps you to understand how to use the various features of the IDE to build the application.
* '''OpenClovis API Reference Guide''' is provided for each component. It describes the Application Programming Interface (API), Service Model, and Management Information Model of the various OpenClovis Application Service Platform (SAFplus Platform) services. It helps the developer to understand the capabilities of the SAFplus Platform services and the APIs provided by these services.
* '''OpenClovis SAFplus Platform Console Reference Guide''' provides details about managing applications built on OpenClovis SAFplus Platform using the SAFplus Platform runtime debug console commands. SAFplus Platform Console commands can be used to manage, monitor, and test your application.

===OpenClovis Online Technical Support===

OpenClovis customers and partners can register on our Web site and receive personalized services and information. If you need any support or assistance while working on OpenClovis products, you can access the following: URL: http://www.openclovis.com. Send your queries to: support@openclovis.com. Open source community support is available at: http://www.openclovis.org/forum

===Documentation Feedback===

We are interested in hearing from our customers on the documentation provided with the product. Let us know your comments and suggestions on improving the documentation at OpenClovis Inc. Send your comments to: support@openclovis.com. Post your feedback on documentation at: http://www.openclovis.org/forum

=='''Available Log Tools'''==

Log files come in 2 flavors, binary and ASCII. ASCII files are easily viewable using standard Linux editors and tools (vi, emacs, tail, etc). By default OpenClovis writes all of its logs in ASCII format. However you may want to change this to binary format or create your own binary format logs. For the binary format logs OpenClovis provides access using following tools :
* [[#Using Command Line Log Tool | Command Line Log Tool ]]
* [[#Using Offline GUI Log Tool | Offline GUI Log Tool ]]

===Using Command Line Log Tool===

The online log viewer is a command line utility which may be used to view the Log Records present in the binary log files. The online log viewer only works on binary log files. To view an ASCII log file simply open them with your favorite editor.

The online log viewer displays the log records after some required conversion. It converts the Severity, StreamId, ComponentId to their corresponding names. This conversion is done using information present in metadata file (cfg file) corresponding to each log file. By default, the online log viewer displays the following fields of a log record:
# SeverityName
# StreamName
# ComponentName
# ServiceId
# MessageId
# TimeStamp
# Message

[[File:OpenClovis_Note.png]]Its very rare that log viewer does not find the stream id to stream name mapping in cfg file. If it does not then it would display the stream id in place of stream name. Same holds true for component id to component name mapping. In this situation it would not be possible to apply filter on that field.

Online log viewer executable <code>'''asp_binlogviewer'''</code> is deployed in <code>'''bin'''</code> directory of the SAFplus Platform. This online log viewer may be used in following ways :
<ol>

<li> To view log records present in a log file (or a set of log files when multiple log files are present for a logical log file) in real time i.e. when logging is going on. In this case it seeks to the latest record and starts displaying the record from that point (which can even be the last record of the log file). As the Log Server writes, this Log Tool tails the files and prints it to the Console. It automatically detects file rollover and tails the new file.
 '''Usage''':
<code><pre>
asp_binlogviewer -l <log_file_prefix>
[-f <filter>]
[-t <msg_id_map_file>]
[-p <num_prev_recs>]
[-c <column(s)>]
[-a] [-h|--help]
</pre></code>

<li>To convert a binary log file to its corresponding text file (this text file contains the log records in exactly the same format as it is displayed on the console) :
 '''Usage''':
<code><pre>
asp_binlogviewer -L <log_file_path>
[-C <cfg_file_path>]
[-t <msg_id_map_file>]
[-h|--help]
</pre></code>
[[File:OpenClovis_Note.png]]User may convert a binary log file to its corresponding text file when logging is going on as well as when it has stopped.

</ol>

====Viewing log records in real time====

=====Specify the location of log files=====

*<code>-l</code>: This is the mandatory option for viewing records in real time.

It is used to specify the common prefix to log files (symbolic links to log files) on file system. <code><log_file_prefix></code> is common prefix of log file names.

'''Example''':
 The log files are <code>/tmp/logFile.0</code> <code>/tmp/logFile.1</code> and <code>/tmp/logFile.2</code>.

'''Usage''':
<code><pre>
$ASP_BINDIR/asp_binlogviewer -l /tmp/logFile
</pre></code>

=====Setting Filter on a header field=====

*-f : User may specify filter on one of the header fields

<code><filter></code> should be specified as:

"<header field><comparision operator><value>"

'''\<header field\> options:'''

* s - SeverityName
* r - StreamName
* c - ComponentName
* v - ServiceId
* t - TimeStamp
* m - MessageId

'''\<comparision operator\> options:'''

* <code>=</code> Equal To
* <code>!=</code> Not Equal To
* <code><</code> Less Than
* <code><=</code> Less Than and Equal To
* <code>></code> Greater Than
* <code>>=</code> Greater Than and Equal To

'''Possible \<value\> in a filter:'''

'value' should be:

*String for following fields : SeverityName, StreamName, ComponentName
*HH:MM:SS for TimeStamp
*Integer for following fields : ServiceId, MessageId

'''Example''':
 Set filter on stream name (StreamName) 'CL_LOG_APPLICATION'

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -l <log_file_prefix> -f "r=CL_LOG_APPLICATION"

For time stamp having value greater than 4.30pm...

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -l <log_file_prefix> -f "t>16:30:00"

=====Specify TLV mapping file=====

*-t : This option is used when log files contain records of TLV (tag length value) format.

Specify complete path to TLV mapping file.

'''Example''':
 <code>tlvmap.txt</code> contains the TLV mapping for log records of log file /tmp/sys.0

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -l /tmp/sys -t tlvmap.txt

Following is a sample TLV map file which contains message id to TLV message mapping. TLV File content should be in following format :
<code><pre>
Message_ID<space>Message containing %TLV
</pre></code>
where <code><space></code> is a single space.

[[File:OpenClovis_Note.png]]All the %TLV are replaced by their corresponding values from log record's tag, length, value information for that message id.

Following are the sample content of a TLV map file tlvmap.txt :
<code><pre>
5 Component %TLV was unble to start on node %TLV
6 State Change: Entity [%TLV] Operational State (%TLV -> %TLV) AMF (%TLV)
7 Registering Component %TLV via eoPort %TLV
8 Extending %TLV byte pool of %TLV chunkSize
</pre></code>

This file contains the message id to string mapping for TLV (tag lengh value) messages. '%TLV' of tlv strings are replaced by the corresponding value found in the log record.

=====Display previous log records=====

* -p: Display <code><num_prev_recs></code> previous log records and exit

<code><num_prev_recs></code> is the number of previous log records to be displayed. If user specifies a number greater than the maximum log records or number of log records actually present in all the log files then entire log is displayed.

'''Example''':
 View 10 previous records

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -l <log_file_prefix> -p 10

=====Display only selected fields of Log Record=====

*-c : Display selected field(s) of Log Record

User may choose to display only selected fields of log record. This can be achieved by using -c option where the numbers are separated by ',' .

The default columns are :
# SeverityName
# StreamName
# ComponentName
# ServiceId
# MessageId
# TimeStamp
# Message

'''Example''':
 Display only the following fields: StreamName, ServiceId, TimeStamp

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -l <log_file_prefix> -c 2,4,6

=====Display records present in entire log file(s)=====
*-a : Display entire log and exit

This option displays all the log records present in a log file or all log files when multiple log files are present for single logical file.

'''Example''':
 Display all the log records which file <code>/tmp/sys.0</code> contains

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -l /tmp/sys -a

====Convert a binary log file to text file====

=====Specify complete path to log file=====

* -L : <log_file_path> is complete path to a log file.

* -C : <cfg_file_prefix> is prefix to cfg (metadata) file. This is an optional argument which is required when log file name and prefix of cfg file are different.

* -t : If log file contains TLV messages then please specify TLV file path using this option.

If log file is <code>/tmp/logFile</code> the corresponding text file will be <code>/tmp/logFile.txt</code>

'''Example''':
 When log file name and prefix of cfg files are the same (log file is <code>/tmp/sys_2007-04-18T18:58:36</code> and cfg file is <code>/tmp/sys_2007-04-18T18:58:36.cfg</code>) :

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -L /tmp/sys_2007-04-18T18:58:36

'''Example''':
 When log file name and prefix of cfg files are different (log file is <code>/tmp/sys_2007-04-18T18:58:37</code> and cfg file is <code>/tmp/sys_2007-04-18T18:58:36.cfg</code>) :

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -L /tmp/sys_2007-04-18T18:58:37 \
-C /tmp/sys_2007-04-18T18:58:36

====For detailed help use --h or --help====

*--help | -h : Display help and exit

'''Usage''':
$ASP_BINDIR/asp_binlogviewer -h

$ASP_BINDIR/asp_binlogviewer --help

====Command line log tool Output Format====

As the Log Server writes, this Log Tool tails the files and prints it to the Console. It automatically detects file rollover and tails the new file.

The output is of the form:

<code><pre>
SEVERITY STREAMNAME COMPONENTNAME SERVICEID MESSAGEID TIMESTAMP MESSAGE
</pre></code>

For example,

<code><pre>
DEBUG applogs cpmServer_SysController_1 10 0 {Mon Jan 22 17:41:08 2007} \
( 0x6d 0x53 0x27 0x2a 0x97 0x22 0x1e 0x34 )
</pre></code>

where,

*<code>Debug</code> is the Severity
*<code>applogs</code> is the Stream Name
*<code>cpmServer_SysController_1</code> is the Component Name
*<code>10</code> is the Service ID
*<code>{Mon Jan 22 17:41:08 2007}</code> is the Time Stamp
*<code>0</code> is the Message ID which indicates that it is BUFFER type Binary Message. Message ID 1 is for ASCII message and it is not supported by log viewer, Message IDs other than 0 and 1 are of TLV type Binary Message.
*<code>( 0x6d 0x53 0x27 0x2a 0x97 0x22 0x1e 0x34 )</code> This is the hex value of each message byte separated by a space.
*online log viewer doesn't interpret the message part in case of BUFFER type records, it simply prints each byte of the message.
 

===Using Offline GUI Log Tool===

OpenClovis Offline Log Tool is an interactive GUI utility that allows you to view log files in a readable format and provides support for navigation, filtering and sorting of the log records. The Offline Log Tool only works on binary log files. To view ASCII log file simply open them with your favorite editor.

====Getting Started====

This provides information to launch the GUI Log Tool and helps you familiarize with its features.

=====How To Launch? =====

The Log Tool is installed in the <code>'''<installation_directory>/sdk-3.0/bin'''</code> directory during OpenClovis SDK installation.

If you have created the symbolic links during OpenClovis SDK installation, execute the following command:
<code><pre># cl-log-viewer</pre></code>

If you have not created the symbolic links during OpenClovis SDK installation, go to the <code>'''<installation_directory>/sdk-3.0/bin'''</code> directory and execute the following command:
<code><pre># cl-log-viewer</pre></code>

Alternatively, you can go to the <code>'''<installation_directory>/sdk-3.0/logviewer'''</code> directory and execute the following command:
<code><pre># ./logViewer.sh</pre></code>

Using 'cl-log-viewer' approach to launch the Log Tool is encouraged.

The '''Log Tool''' window is displayed.

[[File:LogTool_MainWindow.jpg|frame|center|'''Log Tool Main Window''']]
 

* [[#Using Menus | Using Menus]]
* [[#Using Toolbar | Using Toolbar]]

=====Using Menus=====

Log Tool has the following three menus:
* '''File''' - The File menu has options that allow you to open a file, close the current open file, close all open files, and exit the tool.
* '''Tools''' - The Tools menu has options that allow you to create and save filters, access the saved filters, and configure settings for the filter location and the mapping file.
* '''Help''' - The Help menu provides information about the Log Tool.

=====Using Toolbar=====

The add-on icons for the Log Tool are as shown.

[[File:LogTool_ToolBar.jpg|frame|center| '''Log Tool Toolbar''']]
* '''Open Stream''' icon - Use this icon to open a Log file.
* '''Close Stream''' icon - Use this icon to close a Log file.
* '''Create Advanced Filter''' icon - Use this icon to create, apply, and save filters.
* '''Saved Filters''' - Use this icon to apply the saved filter to a set of records.
* '''Exit Log Tool''' - Use this icon to close the '''Log Tool''' window.
 

====Viewing Log Files====

This section provides information to open log files, use filters to customize views, configure the user directory, and mapping file locations.

'''Key Topics''' :
* [[#Opening Log File | Opening Log File]]
* [[#Sorting Log Records | Sorting Log Records]]
* [[#Navigating Log Records | Navigating Log Records]]

=====Opening Log File=====

To open a Log file:

<ol>
<li>From the '''File''' menu, click '''Open''' or press '''Ctrl+O'''. The '''File Selection Dialog''' dialog box is displayed.
[[File:LogTool_FileSelectionDialog.jpg|frame|center|'''File Selection Dialog''']]
<li>Enter the following:
* '''Log File''' - Click '''Browse'''. The '''Select Log File''' dialog box is displayed. Specify the binary Log file that you need to view. The log file has the log records in the binary format. Click '''OK'''. The '''Select Log File''' dialog box closes.
[[File:LogTool_SelectLogFile.jpg|frame|center| '''Select Log File''' ]]
* '''Config File''' - Click '''Browse'''. The '''Select Config File''' dialog box is displayed. Specify the configuration file that configuration data (such as record length, component ID mapping, and stream ID mapping) for the log file. Click '''OK''' . The '''Select Config File''' dialog box closes.
[[File:LogTool_SelectConfigFile.jpg|frame|center|'''Select Config File''']]
<li>In the '''File Selection Dialog''' dialog box, click '''OK'''. The selected Log file opens in the '''Log Tool''' window.
</ol>

Validations are performed to check if you have specified the correct files. If the files are not correct, the corresponding error message is displayed.
[[File:LogTool_OpenedLogFile.jpg|frame|center|'''Opened Log File''']]

=====Sorting Log Records=====

You can click each column header to sort the entries. Every time you click the column header, the direction of sorting changes. Sorting is applicable for the current batch of records only.

=====Listing Log Records=====

The following options are provided for listing Log Records:
* Click '''First''' to view the first batch of records.
* Click '''Next''' to view the next batch of records.
* Click '''Previous''' to view the previous batch of records.
* Click '''Last''' to view the last batch of records.

====Using Filters====

This chapter provides information on using basic filter, creating and saving filter and using saved filters.

A typical log file generally contains large number of entries. When you need to troubleshoot a problem, only certain entries may be relevant. For example, you may need to view logs with severity level 3. You can use filters to view the log file based on certain criteria to create customized views. You can also save the filter criteria and use it at a later time.

'''Key Topics''' :
* [[#Using Basic Filter | Using Basic Filter]]
* [[#Creating and Saving Filter | Creating and Saving Filter]]
* [[#Using Saved Filter | Using Saved Filter]]

=====Using Basic Filter=====

Basic filter comprises the drop-down lists available in the '''Log Tool''' window.

To filter records using the basic filter:
<ol>

<li>From the first drop-down list, select the filtering option. The options available are:
* Record Number
* Severity
* StreamId
* ComponentId
* ServiceId
* TimeStamp
* MessageId
* Message

<li>From the second drop-down list, select the type of filtering. The options in this list is displayed based on your selection in the first drop-down list.

<li>Based on these two selections, you can perform one of the following:
* In the text box, enter the filter criteria.
* In the value selector, specify a value.

If you select '''TimeStamp''' as the filter type in the first drop-down list, you need to specify the date and the time as the values.

<li>Click '''Filter'''. The records are filtered and displayed based on the specified criteria.
Figure [[#Filtered List | Filtered List]] shows the records filtered based on Severity 2.
[[File:LogTool_FilteredList.jpg|frame|center|'''Filtered List''']]

<li>Click '''Clear''' to clear the applied filter and display the records from the start of the file.
</ol>

The following table provides information about the various filter options and the types:

{| align="center" border="0" cellpadding="3"
|+ align="bottom" | '''Filter Options and Types'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Filter Option
!style="color:#66b154; background:#09477c"| Filter Type
|- style="color:#ffffff; background:#549cc6"
|Message
|
* Is
* Is Not
* Contains
* Does Not Contain
* Starts With
* Does not start with
* Ends With
* Does not End With
|- style="color:#ffffff; background:#549cc6"
|
Severity
 
StreamId
 
ComponentId
 
ServiceId
 
TimeStamp
 
Record Number
 
MessageId
|
* =
* <
* >
* <=
* >=
* Between
* Range
|}

=====Creating and Saving Filter=====

You can create and save filters so that you can apply the saved filters to a set of records at a later time.

To create a filter:
<ol>
<li>From the '''Tools''' menu, click '''Advanced Filter''' or press '''Ctrl+F'''. The '''No previous Filter''' dialog box is displayed if you are creating a filter for the first time. Otherwise, the '''Advanced Filter''' window is displayed.
[[File:LogTool_NoPreviousFilter.jpg|frame|center|'''No Previous Filter''']]

<li>Click '''OK'''. The '''Advanced Filter''' window is displayed.
[[File:LogTool_AdvancedFilter.jpg|frame|center|'''Advanced Filter''']]

<li>Enter the following information:
* '''Filter Name''': This is the name for the new filter.
* '''Filter Type''': Select the type of the filter. The available options are:
** AND - Select this option if you need all the criterion to be satisfied.
** OR - Select this option if at least one of the criteria has to be satisfied.
* Click '''Create Filter Criterion''' to specify the criterion in the drop-down lists.
* From the first drop-down list, select the filtering option.
* From the second drop-down list, select the type of filtering. The options in this list is displayed based on your selection in the first drop-down list.
* Based on these two selections, in the text box, enter the filter criteria or specify a value. If you select '''TimeStamp''' as the filter type in the first drop-down list, you need to specify the date and the time as the values.

<li>Click '''Apply''' to apply the filter to the existing records.
<li>Click '''Save''' to save the filter.
</ol>

Click '''Remove''' to remove a filter criteria.

Click '''Cancel''' to cancel creating the filter.

=====Using Saved Filter=====

To use a saved filter:
<ol>
<li>From the '''Tools''' menu, click '''Saved Filters''' or press '''Ctrl+S'''. The '''Saved Filter''' dialog box displays the list of saved filters. [[File:LogTool_SavedFilters.jpg|frame|center|Saved Filters]]

<li>Select the filter that you need to apply and click '''Apply'''. The selected filter is applied to the existing records.

<li>To add more filters, click '''Add'''. The '''Advanced Filter''' window is displayed. For information to create and save a filter, refer to the section [[#Creating and Saving Filter | Creating and Saving Filter]].

<li>To remove a saved filter, select the filter and click '''Remove'''. The selected filter is removed from the list.

<li>Click '''OK''' to close the '''Saved Filters''' dialog box.

<li>Click '''Cancel''' to cancel the process of applying a saved filter.
</ol>

====Configuring User Directory and Mapping File Location====

To configure the location for user-defined filters and mapping files:
<ol>
<li>From the '''Tools''' menu, click '''Settings''' or press '''Ctrl+T'''. The '''Settings''' window is displayed.
[[File:LogTool_ConfigureLocation.jpg|frame|center|'''Settings''']]

<li>Enter the following information:
* '''User Directory''': This is the directory where the created filters are saved. This must be an existing directory.
* '''TLV Mapping File''': This is the directory where the mapping file for the MessageId is stored. A log file represents the MessageIds in a sequence of bytes. The mapping file contains the string representation for these MessageIds. If you specify a mapping file, then the corresponding string representation for the MessageId is displayed when you open the Log file using the Log Tool. If you do not specify the mapping file, then the MessageId is displayed as a sequence of bytes.
<li>Click '''Apply''' to apply the configured locations to the current open Log file.
<li>Click '''OK''' to save the settings.
</ol>

Click '''Restore Defaults''' to restore the default locations.

Click '''Cancel''' to cancel the settings.

====Closing Log File(s)====

To close a Log file, from the '''File''' menu, click '''Close''' or press '''Ctrl+C'''. The Log file that is currently open is closed.

To close all open Log files, from the '''File''' menu, click '''Close All''' or press '''Ctrl+Shift+C'''. All Log files that are open are closed.

====Exiting Log Tool====

To exit from Log Tool, from the '''File''' menu, click '''Exit''' tor press '''Ctrl+X''' . The '''Log Tool''' window closes.

Doc:latest/tutorial

2012-02-21T03:48:15Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

==Preface==
The ''SAFplus Platform Sample Application Tutorial'' is a comprehensive tutorial designed to highlight the steps involved in using SAFplus software to design and build a high availability system. In this tutorial you will learn to:
* Design a model using the SAFplus IDE
* Generate code from this model to provide middleware support
* Customize this code for a particular application
* Build and deploy the customized code
* Run the system to see the SAFplus Platform software in action

===Audience===
 ''SAFplus Platform Sample Application Tutorial'' is designed for system integrators, designers, and system architects. To use SAFplus Platform, you should be aware of the fundamentals of operation, management, and configuration of telecommunication and networking domains. You should also be familiar with C programming, UML notations, and have the basic knowledge of Linux.

 This document assumes that you have installed the SAFplus Platform SDK, following the installation steps found in the ''SAFplus Platform Installation Guide''.

===Documentation Conventions===
This guide uses different fonts and symbols to differentiate between document elements and types of information. These conventions are summarized in the following table.
{| border="1" cellpadding="5"
|- style="background:#cdd6e6"
!style="background:#d3e3ff"| Notation
!style="background:#d3e3ff"| Description

|-
|style="background:#ffccaa" | <code><pre>Code</pre></code>
|This font denotes the C code provided in various examples. This font denotes function and variable names.

|-
|style="background:#ffffaa" | <code><pre>Output</pre></code>
|Terminal output.

|-
|style="color:blue" | Cross reference
|This font denotes a hyperlink. You can click on the hyperlink text to access the reference location, which can be either a section within the guide or a URL link. A cross reference refers to a section name and accesses the first page of that section.

|-
| <code>Filenames</code>, <code><DIR></code>
| Files names, Directory paths.

|-
|<code>$ Commands ''group_identifier''</code>
| Commands to be run from a shell. Italic text indicate an argument. This can be replaced with your desired value.
|}

 [[File:OpenClovis_Note.png]]This indicates the presence of notes or annotations, related to the context of the document.
 [[File:OpenClovis_Caution.png]]This indicates that certain precautionary measures must be taken before performing a particular task.
 [[File:OpenClovis_Info.png]]This indicates that additional information is provided to you.

As mentioned in the ''SAFplus Platform Installation Guide'' the default directory for installation is <code>/opt/clovis</code> for root installation and <code>$HOME/clovis</code> for non root users. Throughout this document we will use <code><install_dir></code> to refer to the installation directory.

===Related Documents===
For additional information about OpenClovis products, please refer to the following guides:
* '''[[Doc:latest/relnotes | SAFplus Platform Release Notes]]''' provides information about the software and the hardware required to install OpenClovis SAFplus Availability/Scalability Platform and Integrated Development Environment (IDE). It summarizes the additional features and enhancements of the product since the previous release. It also summarizes the issues and limitations of the product and provides workarounds wherever applicable.
* '''[[Doc:latest/safcompliance | SAFplus Platform SA-Forum Compliance]]''' describes the level of compliance of OpenClovis SAFplus Platform and its Application Programming Interface (API) with the relevant Service Availability Forum Specifications.
* '''[[Doc:latest/installguide | SAFplus Platform Installation Guide]]''' provides the system requirements, installation procedure for OpenClovis SAFplus Platform, IDE, and the Evaluation System.
* '''[[Doc:latest/tutorial | SAFplus Platform Sample Application Tutorial]]''' explains the steps to create and build a sample model using OpenClovis IDE and OpenClovis SAFplus Platform. It also provides troubleshooting information for this process. This provides the logical first step in understanding the SAFplus Platform offering.
* '''[[Doc:latest/evalguide | SAFplus Platform Evaluation System User Guide]]''' provides all the required information to configure and run the sample models packaged within the Evaluation System. This document also provides good understanding of OpenClovis SAFplus Platform's functionality. This is the natural follow on to the ''OpenClovis Sample Application Tutorial'' as it builds on the example created in that document.
* '''[[Doc:latest/sdkguide | SAFplus Platform SDK User Guide]]''' provides information about SAFplus Availability/Scalability Platform architecture, various SAFplus Platform components, and their interactions. This guide helps you to configure the OpenClovis SAFplus Platform components, compile, and execute the SAFplus Platform code to build your custom application.
* '''[[Doc:latest/ideguide | SAFplus Platform IDE User Guide]]''' describes the usage of Integrated Development Environment (IDE), a graphical development environment that complements the SAFplus Platform. This guide helps you to understand how to use the various features of the IDE to build the application.
* '''[[Doc:latest/logtoolguide | SAFplus Platform Log Tool User Guide]]''' provides information about the usage of OpenClovis Log Tool. OpenClovis Log Tool is an interactive utility that allows you to view binary log files in a readable format and hence monitor system errors, warnings, and other log information. Log Tool allows you to format the <code>.log</code> files and filter them to view the required entries.
* '''SAFplus Platform API Reference Guide [http://www.openclovis.org/doc/latest/apirefs/index.html]''' is provided for each component. It describes the Application Programming Interface (API), Service Model, and Management Information Model of the various OpenClovis Application Service Platform (SAFplus Platform) services. It helps the developer to understand the capabilities of the SAFplus Platform services and the APIs provided by these services.
* '''[[SAFplus Platform Console Reference Guide]]''' provides details about managing applications built on SAFplus Platform using the SAFplus Platform runtime debug console commands. SAFplus Platform Console commands can be used to manage, monitor, and test your application.

===OpenClovis Online Technical Support===
OpenClovis customers and partners can register on our Web site and receive personalized services and information. If you need any support or assistance while working on OpenClovis products, you can access the following: URL: http://www.openclovis.com. Send your queries to: support@openclovis.com. Open source community support is available at: http://www.openclovis.org/forum.

===Documentation Feedback===
We are interested in hearing from our customers on the documentation provided with the product. Let us know your comments and suggestions on improving the documentation at OpenClovis Inc. Send your comments to: support@openclovis.com. Or even better, edit (or comment in) the page on our documentation wiki located at [http://help.openclovis.com http://help.openclovis.com].

==Our Example: The csa101 System==
The ''SAFplus Platform Sample Application Tutorial'' will take you through a series of examples each introducing a key concept of the product. Each example builds on the example before it so it is important to go through them in order. The examples are named so that it is easy to determine their sequence. The examples all begin with the letters '''csa''' (standing for Clovis Sample Application) and end with a number. Our first example will be '''csa101'''.

The purpose of our first example is to highlight basic component management. It introduces the basic skeleton of a SAFplus Platform based application component and illustrates how it interacts with the System. It demonstrates basic component registration and life-cycle management.

We will keep this first example very simple. It will consist of the SAFplus Platform running a small component named '''csa101'''. All that this component will do is continuously print 'Hello World!' to a log file. While this component is not very exciting, it will allow us to easily see when the application is in a running state and when it is not. This will allow us to focus on the infrastructure of SAFplus Platform and how the application interfaces with it.

For this example we will assume that we have a chassis with five slots. We will have one type of blade in our example, a '''System Controller'''.
 [[File:OpenClovis_Note.png]]With the type of model we are developing we would typically define two blade types to install in these slots. The first blade type would be a '''System Controller''' blade (which is responsible for running the SAFplus Platform software which manages application startup, shutdown, failover, etc.) and the second blade type would be a '''Payload''' blade (which is responsible for running our custom '''csa101''' application). However, for the purpose of simplifying the deployment of our system, we will define only the '''System Controller''' blade type and have both the SAFplus Platform and component application run on this one blade. This will allow the example to be run on a single PC.

==Creating the csa101 Model==
The first step in setting up our example is to create a model which represents the system that we will eventually deploy. This is done through the '''SAFplus Platform IDE'''. In this chapter we will step through the following tasks:
* Create a project area
* Launch the '''SAFplus Platform IDE'''
* Create the IDE project
* Specify the Resource model (the types of physical hardware in our system)
* Specify the Component model (the types of components or applications in our system)
* Specify which Components run on which Resources
* 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===
You can launch the '''SAFplus Platform IDE''' from the command line. If you chose to create symbolic links during installation you can simply enter <code>'''cl-ide'''</code> from any directory. If you did not create symbolic links during installation you can either:

<ul>
<li>Add the installation directory to the shells search path and then launch the IDE. For example with a bash shell,
<code><pre>
# export PATH=$PATH:$install_dir/sdk-5.0/bin
# cl-ide
</pre></code>
or
<li>Execute the command
<code><pre>
# <install_dir>/sdk-5.0/bin/cl-ide
</pre></code>
</ul>

The splash screen for SAFplus Platform IDE is displayed as illustrated in Figure [[#SAFplus Platform IDE Opening Screen | SAFplus Platform IDE Opening Screen]].

[[File:Tutorial_GettingStartedIDE_OpeningScreen.png|frame|center| '''SAFplus Platform IDE Opening Screen''' ]]

You will then be prompted to select a workspace in which to do your work as illustrated in Figure [[#SAFplus Platform IDE Workspace Launcher | SAFplus Platform IDE Workspace Launcher]].

[[File:Tutorial_GettingStartedIDE_WorkspaceLauncher.png|frame|center| '''SAFplus Platform IDE Workspace Launcher''' ]]

The workspace you select should correspond to the project area that you created in the previous section (in this case "/home/clovis/projectarea1"). Note that the workspace includes a subdirectory of "/ide_workspace". This is done strictly for organizational purposes. It keeps the IDE models separate from the generated SAFplus Platform models and code.
<ul>
<li>Select the workspace and click '''OK''' to launch SAFplus Platform IDE as illustrated in the Figure [[#SAFplus Platform IDE Welcome Screen | SAFplus Platform IDE Welcome Screen]].
</ul>

[[File:Tutorial_WelcomeScreen.png|frame|center| '''SAFplus Platform IDE Welcome Screen''' ]]

The '''SAFplus Platform''' IDE is launched and you are now looking at the main work area. For more information about the components of this main work area including the SAFplus Platform IDE menu and toolbar, see ''SAFplus Platform IDE User Guide''.

===Creating the Sample Project===
We will now create a project within the '''SAFplus Platform IDE'''. This project will hold both the resource model and the component model for our example system. The resource model is a physical view of the resources (the chassis, the blade types, etc.) in our system. The component model is a logical view of the components (applications, etc.) in our system.

We will be using the '''New Project Wizard''' to create our project. The wizard captures some high-level information about the system that we are building and performs a lot of the basic setup for us.

[[File:OpenClovis_Note.png]]The same model that we are building through the wizard could also be created manually through the Resource and Component Editors. For more information on the Resource and Component Editors see ''SAFplus Platform IDE User Guide''.

To launch the '''New Project Wizard''' select '''File''' > '''New''' > '''Project''' from the IDE menu bar.

The '''New Project Wizard''' is displayed and '''Clovis System Project''' is selected by default as illustrated in Figure [[#New Project Wizard | New Project Wizard]].

[[File:Tutorial_GettingStartedIDE_NewProjectWizard.png|frame|center| '''New Project Wizard''' ]]

Click '''Next'''. The '''Clovis System Project''' window is displayed as illustrated in Figure [[#Clovis System Project | Clovis System Project]].

[[File:Tutorial_NewProject.png|frame|center| '''Clovis System Project''' ]]

Enter the following information:

<ul>
<li>'''Project Name''' : Enter the name of your new project as '''SampleModel'''.
 [[File:OpenClovis_Note.png]]Do not use spaces or special characters for the project name. The project name can be alphanumeric, but cannot start with a number or have only numbers.
 Select '''Use default''' to use the same directory mentioned in the '''Directory''' field.

<li>'''SDK Location''': Enter the location where the SAFplus Platform SDK was installed. For e.g. if the SDK was installed at location /opt/clovis, then the SDK location is /opt/clovis/sdk-<version>.

<li>'''Project Area Location''': Enter the location where the generated source code for the model should be stored.
 [[File:OpenClovis_Note.png]]This can be any existing directory but is usually the project area that was created in the previous section.

<li>'''Python Location''': Enter the location where Python 2.5.0 is installed on your system. If Python 2.5.0 was installed by SAFplus Platform SDK, the directory is <code>'''<installation_directory>/buildtools/local/bin'''</code>.
</ul>

Click '''Next'''. The '''Add New Blade Type''' window is displayed. This dialog is used to define the blade types that are in our system.

[[File:Tutorial_AddBlade.png|frame|center| '''Add New Blade Type''' ]]

Remember that the system we are modelling has only one blade type...a System Controller.
<ul>
<li>Use the '''Add''' button to add a new blade type to the list. Name this blade type 'SysBlade' (for System Controller blade).
</ul>

Click '''Next'''. The '''Add New SAF Node Type''' window is displayed. This dialog is used to define the type of logical node that will be run on the corresponding blade type defined in the previous dialog.

[[File:Tutorial_AddNode.png|frame|center| '''Add New SAF Node Type''' ]]

Node types represent groups of software. They are classified as either a System Controller class or a Payload class. This distinction gives the node type certain characteristics which cause it to behave in a well-defined manner. Since we have only a System Controller in our system we will add a node type of class System Controller.

<ul>
<li>Use the '''Add''' button to add a new node type to the list. Name the node type 'SCNode' and ensure that its node class is 'System Controller (SAF Class B)'.
</ul>

Click '''Next'''. The '''Specify Program Names''' window is displayed. This dialog is used to create programs or SAF Service Types and associate them with the SAF Node Types specified in the previous dialog.

[[File:Tutorial_DefineProgramNames.png|frame|center| '''Specify Program Names''' ]]

In our system we need one SAF Service Type which represents our high availability software (csa101 that continously prints "Hello World!").

<ul>
<li>Use the '''Add''' button to add a program name to the list. Change the program name to 'csa101' and associate the program with the 'SCNode' node type.
</ul>

Click '''Finish'''. This will create the sample model using the blade type, node type, and program name information collected through the 'New Project Wizard' dialogs.

===Viewing the Model===

====The SAFplus Platform IDE Perspective====
Once the wizard pages are closed you will be returned to the main IDE view also known as the '''SAFplus Platform IDE Perspective'''. On the left hand side of this view you will see the '''Clovis Workspace''' pane which contains the new project you just created with all project related files and folders. The folders are displayed based on your filter settings. With the default filter settings, the folders shown in Figure [[#Clovis Workspace|Clovis Workspace]] is displayed in the '''Clovis Workspace''' pane. For information about filter settings, refer ''SAFplus Platform IDE User Guide''.

[[File:Tutorial_GettingStartedIDE_ClovisWorkspace.png|frame|center|Clovis Workspace]]

By default, the '''Resource''' and '''Component''' Editor views are available for the created project. To view them, click '''Clovis''' on the menu bar at the top of the screen and select '''Resource Editor''' or '''Component Editor''' from the menu. You can also click '''Resource Editor''' or '''Component Editor''' icons from the tool bar as shown in Figure [[#SAFplus Platform IDE Tool Bar | SAFplus Platform IDE Tool Bar]].

[[File:Tutorial_Toolbar.png|frame|center| '''SAFplus Platform IDE Tool Bar''' ]]

====Resource Editor View====
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.

[[File:Tutorial_ResourceEditor.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'''.

On the right hand side of the editor view you will see the '''Palette''' which can be expanded and collapsed. Expanding the '''Palette''' you will see the list of objects that can be dragged onto the editor view to add to our model. Once an object is on the editor view you can view and change its properties by right clicking on the object and selecting '''Properties...''' from the context menu.

For more information about the '''Resource Editor''' view see ''SAFplus Platform IDE User Guide''.

====Component Editor View====
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.

[[File:Tutorial_ComponentEditor.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.

On the right hand side of the editor view you will see the '''Palette''' which can be expanded and collapsed. Expanding the '''Palette''' you will see the list of objects that can be dragged onto the editor view to add to our model. Once an object is on the editor view you can view and change its properties by right clicking on the object and selecting '''Properties...''' from the context menu.

For more information about the '''Component Editor''' view see ''SAFplus Platform IDE User Guide''.

===Configuring the Components===
The '''New Project Wizard''' that we used to create our project configured the system using the most common options. We will have to make a few changes to this model in order for our example to work. We will make these changes in the '''Component Editor''' view.

In the Component Editor you will notice seven different objects that were created by the wizard. The first two of these are:
<ul>
<li>Cluster: The root object of all other objects in the Component Editor view.
<li>SCNode: This is the SAF Node Type that we specified during project creation.
</ul>

The next five objects all make up the Program or SAF Service Type that we specified on the last dialog of the New Project Wizard. These objects are:

<ul>
<li>csa101SG: This is the Service Group representing our high availability software component.
<li>csa101SU: This is the Service Unit that is logically associated with the SCNode SAF Node Type.
<li>csa101SI: This is the Service Instance
<li>csa101CSI: This is the Component Service Instance
<li>csa101: This is the SAF Component which represents our program or executable.
</ul>

We will be making changes to the Service Group (csa101SG), the Service Instance (csa101SI), and the SAF Component (csa101).

====Configuring the Service Group====
To make changes to the Service Group double-click on the box titled '''csa101SG'''. The '''Service Group Details''' dialog is displayed.

[[File:Tutorial_ServiceGroupDetails.png|frame|center| '''Service Group Details''' ]]

<ul>
<li>The first change we want to make is to the '''Redundancy Model'''. The '''Redundancy Model''' is the strategy that is used by the SAFplus Platform system to recover from a node failure. For our simple model (which only has one node) we are not going to rely on any failover recovery so change the '''Redundancy Model''' to 'No Redundancy' as shown.
 [[File:OpenClovis_Note.png]]You will notice that when you change the redundancy model some of the other fields are modified automatically and become read-only. This is to ensure integrity of the redundancy models.

<li>The second change that we want to make is to the '''Admin State'''. The '''Admin State''' defines the state of the component when the system is first brought up. In our case we want to change the '''Admin State''' to be 'Locked Initialized'. This means that when the system first starts up this '''Service Group''' (and its subcomponents) will be initialized but not yet put into a running state. So our csa101 application will not yet start printing "Hello World!".

<li>When you are finished making the changes click the '''OK''' button to commit the changes.
</ul>

====Configuring the Service Instance====
To make changes to the Service Instance double-click on the box titled '''csa101SI'''. The '''Service Instance Details''' dialog is displayed.

[[File:Tutorial_ServiceInstanceDetails.png|frame|center| '''Service Instance Details''' ]]

<ul>
<li>The only change we want to make here is to the '''Number of standby assignments'''. This value represents the number of components that will be waiting to take over during a node failure and goes hand-in-hand with the '''Redundancy Model''' that we selected for the Service Group. Since we selected 'No Redundancy' for our '''Redundancy Model''' we need to set this value to 0...since we are not supporting any failover in this model.

<li>When you are finished making the changes click the '''OK''' button to commit the changes.
</ul>

====Configuring the SAF Component====
To make changes to the SAF Component double-click on the box titled '''csa101'''. The '''SAF Component Details''' dialog is displayed.

[[File:Tutorial_SAFComponentDetails.png|frame|center| '''SAF Component Details''' ]]

The SAF Component represents our high availabilty program or executable. We need to pass a command line argument to this executable. The reason for this argument is to force the program to print the 'Hello World!' output to a special log file for our viewing. We will look at this more closely when we customize our code.

<ul>
<li>To add command line parameters click the '''Edit...''' button corresponding to the '''Command line Arguments''' label.
</ul>

The '''Command line Argument Details''' dialog is displayed.

[[File:Tutorial_CommandLineArgs.png|frame|center| '''Command line Argument Details''' ]]

<ul>
<li>Click the '''New''' button to add a new value to the list.
<li>Click on the new value in the list and it will become editable. Change the value to '''-p'''.
<li>Click the '''OK''' button to save and close the dialog.
<li>Click the '''OK''' button on the '''SAF Component Details''' dialog to commit the changes to the SAF Component and close the dialog.
<li>Save the component model using the '''File > Save''' menu item.
</ul>

===Configuring Physical Instances===
The configuration of our logical models is complete. During this process we have defined all of the 'types' of objects in our system. Now it is time to configure actual instances of those objects so that they can be built and deployed.

Object instance configuration is done through the Availability Management Framework (AMF) via the '''AMF Configuration''' dialog.

<ul>
<li>To launch this dialog go to the the '''Clovis''' menu and select '''AMF Configuration...'''
</ul>

The '''AMF Configuration''' dialog is displayed.

[[File:Tutorial_AMFConfig.png|frame|center| '''AMF Configuration Dialog''' ]]

You will note from the instructions on this page that the physical instances representing the objects in our model can be created manually or by using wizards. Using the wizards will save us both typing and time so we will use these instead of creating each instance manually.

====Creating Node Instances====
First we will create actual instances of the Node Types (in our case only one Node Type...SCNode) we created in our model.

<ul>
<li>Double-click AMF Configuration in the left hand pane. The Node Instance List appears.
<li>Click on Node Instance List. The right hand pane displays the fields we must fill out to create our node instance.
</ul>

In the right hand pane:

<ul>
<li>Select SCNode for the '''Node Type'''.
<li>Select SysBlade for the '''Blade type'''.
<li>Enter 1 for the '''Node Count'''.
</ul>

The complete form should look like the following.

[[File:Tutorial_AMFNodeWizardDetails.png|frame|center| '''Node Wizard Details''' ]]

<ul>
<li>Click the '''Create Instance Tree''' button to create our node instance.
</ul>

Expanding the '''Node Instance List''' branch of the '''AMF Configuration''' tree in the left-hand pane reveals a new node instance named SCNodeI0 (indicating SCNode Instance 0).

====Creating Service Group Instances====
Now we will create actual instances of the Service Groups that we defined in our model.

<ul>
<li>Click on Service Group List. The right hand pane displays the fields we must fill out to create our service group instance.
</ul>

In the right hand pane:

<ul>
<li>Select csa101SG (the only service group type we defined) for the '''Service Group Type'''.
*The '''Associated Node Instances''' list will be populated with all of the node instances that can be associated with the selected service group type.
<li>Select SCNodeI0 from the '''Associated Node Instances''' list.
</ul>

The completed form should look like the following.

[[File:Tutorial_AMFSGWizardDetails.png|frame|center| '''Service Group Wizard Details''' ]]

<ul>
<li>Click the '''Create Instance Tree''' button to create our service group instance.
</ul>

 
If you now completely expand the '''AMF Configuration''' branch of the tree in the left-hand pane you will see the following.

[[File:Tutorial_AMSConfigDetails.png|frame|center| '''AMF Configuration Instance Details''' ]]

Notice that not only have the wizards created the node and service group instances for you, they have also filled out the entire instance tree. This was accomplished based on two key sets of information. The first of these is the association that was made between the service group type and the node instance in the '''Service Group Wizard'''. The second set of information is the component model that we created through the New Project Wizard and the Component Editor.

 [[File:OpenClovis_Note.png]]For more information regarding the specific properties of the generated instances see [[#Appendix B: AMF Configuration Instance Details|Appendix B: AMF Configuration Instance Details]].

 
Thats it. We are done modelling the csa101 example!
<ul>
<li>Click the OK button to commit our changes and close the dialog.
</ul>
Now its time to generate the framework code.

==Generating the csa101 Code==
In this step we generate the source code for our example. The code that will be created is the framework code that handles all of the low level functionality provided by SAFplus Platform.

To generate the source code go to the '''Project''' menu and select '''Generate Source'''. Several progress dialogs will appear and after a few seconds code generation will be complete.

The source code and configuration XML files are generated and placed in subdirectories of the '''Project Area Location''' that we specified in the '''New Project Wizard'''. You can review this location by using the '''Project > Properties''' menu to get to the '''Project Properties''' dialog and then selecting '''Clovis System Project''' in the left hand pane.

You can review the generated code from within the SAFplus Platform IDE. To do this go to the '''Clovis Workspace''' pane and expand the '''SampleModel''' node. The node tree should look like the following.

[[File:Tutorial_CWCodeTree.png|frame|center| '''Clovis Workspace Code Tree''' ]]

The code of particular interest to our example is in the SampleModel/src/app/csa101 branch of the tree. This is the code for our csa101 example. The csa101 example consists of two C modules (<code>clCompAppMain.c</code> and <code>clCompCfg.c</code>) and two header files. There is also a make file that will be used for building the application. The <code>clCompAppMain.c</code> file implements our 'Hello World!' application.

 [[File:OpenClovis_Note.png]]If you run code generation a second time you will be presented with a dialog box asking if you would like to make a backup copy of the existing source code before proceeding. You can answer No to this dialog.

==Customizing the csa101 Code==
While the code that was generated in the previous section can be built and run we want to make some changes to it so that we can easily see what our example is doing. For our example we will be changing one source file (<code>clCompAppMain.c</code>) and two make files.
 [[File:OpenClovis_Note.png]]In a real production situation this is the point where you would customize the code to perform the specific tasks of your product.

You will notice in the C file that there are several places where you see the following comment block.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>

/*
---BEGIN_APPLICATION_CODE---
*/

// ...

/*
---END_APPLICATION_CODE---
*/
</pre></code>
|}

Makefiles have a similar convention but with a slightly different syntax.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|Makefile
|-
|<code><pre>

# ---BEGIN_APPLICATION_CODE---

# ---END_APPLICATION_CODE---
</pre></code>
|}

These are sections of the file where it is safe to enter custom application code without having to worry about that code being overwritten if you were to again perform '''Generate Source''' for your model. This is important since the typical development cycle is an iterative process where you will return to the IDE to make modifications to your model.

To simplify the process of building and running the csa101 example, OpenClovis, Inc. has already made the necessary code customizations and shipped this code with the SAFplus Platform SDK. At this point you can simply replace the generated source files with these customized versions to avoid typing in the changes. We will go over each customization below and explain what was done.

To replace the generated files with the customized versions shipped with the SAFplus Platform SDK follow these instructions.
 [[File:OpenClovis_Note.png]] The sample applications containing the csa101 example can be found under the installation directory at <code><install_dir>/sdk-5.0/src/examples/eval</code>. We will refer to this directory in the remaining of this section as <code><eval_dir></code>.

<ol>
<li>Exit the SAFplus Platform IDE using the '''File > Exit''' menu item. If you are prompted to save changes before exiting answer yes.
<li>Navigate to the source code work area.
<code><pre># cd /home/clovis/projectarea1/ide_workspace/SampleModel/src/app</pre></code>
<li>Using your favorite editor open the file <code>Makefile</code> that resides in this directory. This is the application make file.
<li>Add the following line to this file within the first <code>BEGIN_APPLICATION_CODE</code> and <code>END_APPLICATION_CODE</code> comment block.
<code><pre>SUBDIRS += ev</pre></code>
This will instruct the build process to build our custom output library.
<li>Save this file and exit the editor.
<li>Execute the following command to copy the output package to our working area.
<code><pre># cp -r <eval_dir>/src/app/ev .</pre></code>
<li>Navigate to the component code work area.
<code><pre># cd csa101</pre></code>
<li>Execute the following command to copy the csa101 source code.
<code><pre># cp <eval_dir>/src/app/csa101/clCompAppMain.c .</pre></code>
<li>Execute the following command to copy the component make file.
<code><pre># cp <eval_dir>/src/app/csa101/Makefile .</pre></code>
<li>Restart the SAFplus Platform IDE.
<code><pre># cl-ide</pre></code>
</ol>

===Customizing clCompAppMain.c===
The <code>clCompAppMain.c</code> file is the C module which will implement our 'Hello World!' behavior. We have to make changes in several parts of this file.
 [[File:OpenClovis_Note.png]]If you copied the files as instructed in the section above then these changes have already been made to the files. Use this section to review and understand the changes.

<ol>
<li>In the include section of this file we have added a new include for <code>ev.h</code>. This refers to a special output library that we copied to our work area in the previous section. This output library is used to redirect output from the application to a component specific log. This is purely cosmetic but it will allow us to easily monitor what is happening when we run our example. (The following code begins at line 44 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
---BEGIN_APPLICATION_CODE---
*/

#include "clCompAppMain.h"
#include "../ev/ev.h"

/*
---END_APPLICATION_CODE---
*/
</pre></code>
|}

<li>Next we define a couple of static variables that will keep track of the state of our application and a function to aid in showing when the application is running. (The following code begins at line 79 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
---BEGIN_APPLICATION_CODE---
*/

static int running = 0;
static int exiting = 0;

static char*
show_progress(void)
{
static char bar[] = " .";
static int progress = 0;

/* Show a little progress bar */
return &bar[sizeof(bar)-2-(progress++)%(sizeof(bar)-2)];
}

/*
---END_APPLICATION_CODE---
*/
</pre></code>
|}

The <code>running</code> flag will be used to indicate whether the current application is active or suspended while <code>exiting</code> is a flag that indicates that the main() function returns, causing the exit of the application.

The function <code>show_progress</code> returns a pointer to a c string with a number of spaces followed by a '.' character. The number of spaces in the string cycles from zero to an upper bound. This is used later on to provide visual indication of the progress of the application's output.

<li>Next we have added a function <code>hello_func</code> to print the output. (The following code begins at line 118 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>

void *hello_func(void *unused)
{
while (!exiting)
{
if (running)
{
clprintf(CL_LOG_SEV_INFO, "csa101: Hello World! %s\n", show_progress());
}
sleep(1);
}

return NULL;
}

</pre></code>
|}

Notice the while loop condition. This function uses the <code>exiting</code> variable that was initialized to 0. The loop will keep running until <code>exiting</code> is set to non-zero. The if condition within the while loop checks the value of the <code>running</code> variable. The work of the application: printing "Hello World!" along with the progress indicator will only be done when the <code>running</code> variable is set non-zero. Next the command <code>sleep(1)</code> simply sleeps for a second so as not to fill log files too quickly or completely swamp the CPU.

When <code>exiting</code> becomes non-zero, we return from the function.

<li>Next we have added a function to initialize the special output library mentioned earlier (which is at line 245 in the source file).

<li>Next we create a thread and call the function <code>hello_func</code> in the new thread context. (The following code begins at line 252 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/
clprintf(CL_LOG_SEV_INFO, "csa101: Instantiated as component instance %s.\n", appName.value);

clprintf(CL_LOG_SEV_INFO, "%s: Waiting for CSI assignment...\n", appName.value);

rc = clOsalTaskCreateDetached("hello_thread", CL_OSAL_SCHED_OTHER, CL_OSAL_THREAD_PRI_NOT_APPLICABLE, 0, hello_func, NULL);
CL_ASSERT(rc == CL_OK);

/*
* ---END_APPLICATION_CODE---
*/

</pre></code>
|}

<li>Next we indicate to our app when we are exiting. (The following code begins at line 284 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/

exiting = 1;
clEvalAppLogStreamClose(gEvalLogStream);

/*
* ---END_APPLICATION_CODE---
*/

</pre></code>
|}

We set the <code>exiting</code> variable to 1. This will cause the loop in our <code>hello_func</code> function to exit.

<li>Next we will put in code to manage the state of our application. (The following code begins at line 453 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
void clCompAppAMFCSISet(SaInvocationT invocation,
const SaNameT *compName,
SaAmfHAStateT haState,
SaAmfCSIDescriptorT csiDescriptor)
{
/*
* ---BEGIN_APPLICATION_CODE---
*/

// ...

/*
* ---END_APPLICATION_CODE---
*/

/*
* Print information about the CSI Set
*/

clprintf (CL_LOG_SEV_INFO, "Component [%.*s] : PID [%d]. CSI Set Received\n",
compName->length, compName->value, mypid);

clCompAppAMFPrintCSI(csiDescriptor, haState);

/*
* Take appropriate action based on state
*/

switch ( haState )
{
case SA_AMF_HA_ACTIVE:
{
/*
* AMF has requested application to take the active HA state
* for the CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/

clprintf(CL_LOG_SEV_INFO, "csa101: ACTIVE state requested; activating service\n");
running = 1;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);
break;
}

</pre></code>
|}

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>

case SA_AMF_HA_STANDBY:
{
/*
* AMF has requested application to take the standby HA state
* for this CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/

clprintf(CL_LOG_SEV_INFO, "csa101: New state is not the ACTIVE; deactivating service\n");
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);
break;
}

case SA_AMF_HA_QUIESCED:
{
/*
* AMF has requested application to quiesce the CSI currently
* assigned the active or quiescing HA state. The application
* must stop work associated with the CSI immediately.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
clprintf(CL_LOG_SEV_INFO, "csa101: Acknowledging new state\n");
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);
break;
}

</pre></code>
|}
{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
case SA_AMF_HA_QUIESCING:
{
/*
* AMF has requested application to quiesce the CSI currently
* assigned the active HA state. The application must stop work
* associated with the CSI gracefully and not accept any new
* workloads while the work is being terminated.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
clprintf(CL_LOG_SEV_INFO, "csa101: Signaling completion of QUIESCING\n");
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfCSIQuiescingComplete(amfHandle, invocation, SA_AIS_OK);
break;
}
</pre></code>
|}

We have modified the <code>clCompAppAMFCSISet</code> callback function to let our application know what to do when the state changes. In the case where the state changes to <code>SA_AMF_HA_ACTIVE</code> we set the <code>running</code> variable to 1. This will cause our application to begin printing the 'Hello World!' message. For any other state change we set the <code>running</code> variable to 0 which will cause the message to stop printing. For any state change we print out a message indicating the new state of the application.

<li>The last change that we make is to indicate to our application when the component is being disassociated with the workflow. (The following code begins at line 588 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
void clCompAppAMFCSIRemove(SaInvocationT invocation,
const SaNameT *compName,
const SaNameT *csiName,
SaAmfCSIFlagsT csiFlags)
{
....

/*
* Add application specific logic for removing the work for this CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);

return;
}
</pre></code>
|}

In the <code>clCompAppAMFCSIRemove</code> callback function we indicate to our application that we are no longer running so that the while loop in the <code>hello_func</code> function stops printing our 'Hello World!' message.
</ol>

===Customizing the Component MakeFile===
We have to make a small change to the component <code>MakeFile</code> so that it knows about our special output library during the build. To do this we add the following lines. This file is located in <code>/home/clovis/projectarea1/ide_workspace/SampleModel/src/app</code>

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|Component MakeFile
|-
|<code><pre>
# ---BEGIN_APPLICATION_CODE---

SUBDIRS += ev

# ---END_APPLICATION_CODE---
</pre></code>
|}

===Customizing the Application MakeFile===
We have to make sure that our special output library is built along with our application. To do this we change the line listing the sudirectories to make as follows. This file is located in the directory <code>/home/clovis/projectarea1/ide_workspace/SampleModel/src/app/csa101</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|Application MakeFile
|-
|<code><pre>
# ---BEGIN_APPLICATION_CODE---

...

# Library added for demo console handling for the evaluation kit
ASP_LIBS += libeval.a

# ---END_APPLICATION_CODE---
</pre></code>
|}

We are finished customizing our application code!

==Building the csa101 Code==

Now that we have finished customizing the code it is time to build it. The build process is launched using the '''Project > Build Project''' menu item. Once selected the '''Build Configuration''' dialog appears.

[[File:Tutorial_BuildConfigDetails.png|frame|center| '''Build Configuration Details''' ]]

The '''Build Configuration''' dialog is used to gather specific information about the build we are about to perform. Using this dialog you can rebuild the same model using different cross builds, or including different chassis managers. We don't have to make any changes to this dialog since the default settings make sense for our sample application.

 [[File:OpenClovis_Note.png]]If you have prebuilt the SAFplus Platform libraries then you can check the '''Use pre built SAFplus''' checkbox and include the location of the prebuilt libraries. For more information about pre-building SAFplus Platform libraries, see ''SAFplus Platform SDK User Guide''.

 [[File:OpenClovis_Note.png]]The '''Include SNMP for North Bound Access''' control is checked by default. This just means that Net SNMP will be started along with our system. If you want end-to-end connectivity you will need to supply an SNMP Sub Agent and a MIB. See the ''SAFplus Platform SDK User Guide'' for more details.

 [[File:OpenClovis_Note.png]]In the '''Project''' menu if the '''Build Project''' entry is not highlighted, then click in the right pane i.e. '''Clovis Workspace''' pane and click the '''Project''' menu again. This not highlighting of the '''Build Project''' is because the '''Clovis Workspace''' is not selected properly because of moving focus to some other pane.

 Click the '''OK''' button to begin the build. If this is the first time that the project is being built, or if you have made changes to any setting on this screen, you will initially see a progress dialog indicating that the project is being configured. The configuration step is setting up the project for building. After the configuration has completed you will see a progress dialog indicating that the code is being built.

==Creating the csa101 Images==

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.

[[File:Tutorial_MakeImagesConfigDetails.png|frame|center| '''Make Images Configuration Details''' ]]

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.
<li>Click '''OK''' to begin the make image process. A dialog box will appear and after a few seconds the the make images process will be complete.
</ul>

The images will be populated at <project_area>/target/SampleModel/images. Each node-specific image is provided as a directory containing the run-time files (binaries, libraries, prerequisites, and configuration files) as well as a tarball with the same content. e.g. For our model containing one node (<code>SCNodeI0</code>) the following files and directories are generated for deployment on the run-time system.
<code><pre>
<project_area>
|+target
|+<model>
|+images
|+SCNodeI0
| |+bin
| |+etc
| |+lib
| |+modules
| |+share
|-SCNodeI0.tgz
</pre></code>

The rest of the steps in this example are all done from the command line so we can exit the IDE. To do this use the '''File > Exit''' menu item.

==Deploying the csa101 Images==
Now that the image has been built we must deploy it so that we can run and observe our example. Since we are assuming that the example will be run on the same machine as the images were built this is a fairly trivial exercise. Use the following steps to deploy the runtime image.

<ol>
<li>First we create a directory where we will install the image. In our case we will use <code>/root/asp</code>.
<code><pre>
# cd /root
# mkdir asp
</pre></code>
<li>Next we navigate to that directory and untar the deployment package.
<code><pre>
# cd /root/asp
# tar xzvf /home/clovis/projectarea1/target/SampleModel/images/SCNodeI0.tgz
</pre></code>
</ol>

The System Controller is now installed and ready to run.

[[File:OpenClovis_Note.png]] If you were going to run the example on a machine other than the one where the images were built you would first copy the installation tarball to that machine before performing the above steps.

==Running the csa101 Example==
There are two parts to running the csa101 example. First we must start SAFplus Platform, and then we interact with the system components.

===Starting SAFplus Platform===

To start SAFplus Platform on System Controller node.
<ol>
<li>Open a shell.
<li>Run the following commands
<code><pre>
# cd /root/asp
# etc/init.d/asp start
</pre></code>
</ol>

[[File:OpenClovis_Note.png]] This assumes that you are running the SAFplus Platform example on the same PC that you are executing these commands. If you are running SAFplus Platform on a different machine then you should first ssh to that machine before executing the commands.

[[File:OpenClovis_Note.png]] If SAFplus Platform fails to start properly it could be due to the machine's firewall being enabled. SAFplus Platform will not run on a machine which has firewall enabled. See the ''Environment Related Observation'' section of the ''SAFplus Platform Release Notes'' for more information.

[[File:OpenClovis_Note.png]] By default the network interface used by the Group Membership Service is set to eth0. During the make images phase of the tutorial we also set the ethernet interface for node SCNodeI0 to be eth0. During image generation these configuration parameters are written to two files in the deployment package.
*<code>/root/asp/etc/clGmsConfig.xml</code>
*<code>/root/asp/etc/asp.conf</code>

There may be an occasion where you want to switch this interface for a machine on which you are deploying. If you would like to switch this interface on a machine without having to go through the process of rebuilding and redeploying, you can edit these two files and change the 'eth0' references to the interface you would like to use.

===Interacting with the System Components===
Once SAFplus Platform is up and running the next step is to start csa101 by informing SAFplus Platform that it should start the application. The Evaluation System's model tells SAFplus Platform that csa101 is locked for instantiation. This means that the process will not be started when SAFplus Platform comes up. This method of starting csa's is used for the Evaluation System, allowing users to interact with csa's and clearly see their output/functionality. Usually this would not be the case with applications, where they would run when SAFplus Platform begins.

At this point it would help to be familiar with the Service Availability Forum's notions of Service Unit, Service Group, and administrative state. The Service Availability Forum's Application Interface Specification (available from http://www.saforum.org/) is a good place to start.

In brief, the sample applications in the Evaluation System are part of service units which in turn are part of service groups. Service groups (and the service units that make up the service groups) can be in "administrative" states which include "LockInstantiation", "LockAssignment", and "Unlocked". There are other states, but these are the ones we care about for the purposes of this Evaluation System. If the administrative state of a service unit is "LockInstantiation" then the application that is part of that service unit will not even be started. If the administrative state is "LockAssignment" then the application will be started, but it will not be assigned any work. If the administrative state is "Unlocked" then it will not only be started, but will have a workload assigned to it, which is to say that it will start doing work (or start providing service), rather than idly sit waiting for work.

The administrative state of a service unit or service group can change from LockInstantiation to LockAssignment, from LockAssignment to Unlocked, or back to LockInstantiation, from Unlocked to LockAssignment. A picture might help here:

 [[File:eval_AdministrativeStateDiagram.png|frame|center| '''Partial Service Group Administrative State Diagram''' ]]

As the figure shows, the administrative state of a service unit (or service group) can change from "LockInstantiation" to "LockAssignment" and from there to "Unlocked", or back to "LockInstantiation". One way to change the administrative state of a service group is with the SAFplus Platform Console command line interface.

To use the SAFplus Platform Console:
<ol>
<li> Open a terminal on the Development Machine. (Or ssh into System Controller node as root, if you are running SAFplus Platform on a machine other than the development machine.)
<li> Change to image bin directory: <code><pre># cd /root/asp/bin</pre></code>

<li> Start the SAFplus Platform Console <code><pre># ./asp_console</pre></code>

<li> From within the SAFplus Platform Console: <code><pre>
cli[Test]-> setc 1
cli[Test:SCNodeI0]-> setc cpm
cli[Test:SCNodeI0:CPM]-> amsLockAssignment sg csa101SGI0
</pre></code>

The above changes the administrative state of the group csa101SGI0 from "locked-for-instantiation" to "locked-for-assignment".
 [[File:OpenClovis_Note.png]]For the command <code>cli[Test]-> setc 1</code>, the 1 represents the physical slot number of the System Controller within the Chassis. Remember that we set our System Controller to be in slot 1 in the make images dialog.

<li>Now lets tail the application log file so that we can see whats going on. In another window, as root, run:
<code><pre>
# tail -f /root/asp/var/log/csa101I0Log.latest
</pre></code>

You should see the following:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa101I0Log.latest
|-
|<code><pre>
Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00034 : INFO)
Component [csa101I0] : PID [10849]. Initializing

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00035 : INFO)
IOC Address : 0x1

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00036 : INFO)
IOC Port : 0x80

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00037 : INFO)
csa101: Instantiated as component instance csa101I0.

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00038 : INFO)
csa101I0: Waiting for CSI assignment...
</pre></code>
|}

<li>Next change the administrative state of the csa101SGI0 service group to "unlocked" by running (in the SAFplus Platform Console) :
<code><pre>
# cli[Test:SCNodeI0:CPM]-> amsUnlock sg csa101SGI0
</pre></code>

In the window where you're running the "tail -f" you should see:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa101I0Log.latest
|-
|<code><pre>
Tue Jul 15 21:36:17 2008 (SCNodeI0.10849 : csa101_EO.---.---.00049 : INFO)
csa101: ACTIVE state requested; activating service

Tue Jul 15 21:36:18 2008 (SCNodeI0.10849 : csa101_EO.---.---.00050 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:19 2008 (SCNodeI0.10849 : csa101_EO.---.---.00051 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:20 2008 (SCNodeI0.10849 : csa101_EO.---.---.00052 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:21 2008 (SCNodeI0.10849 : csa101_EO.---.---.00053 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:22 2008 (SCNodeI0.10849 : csa101_EO.---.---.00054 : INFO)
csa101: Hello World! .
</pre></code>
|}

As you can tell from the output log our component is up and running! It is continuously printing our 'Hello World!' output.

<li>Now change the state of the csa101SGI0 service group back to "locked-for-assignment" by running (in the SAFplus Platform Console):
<code><pre>
# cli[Test:SCNodeI0:CPM]-> amsLockAssignment sg csa101SGI0
</pre></code>

In the tail -f output you should see:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa101I0Log.latest
|-
|<code><pre>
Tue Jul 15 21:39:29 2008 (SCNodeI0.10849 : csa101_EO.---.---.00241 : INFO)
csa101: Hello World! .

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00242 : INFO)
Component [csa101I0] : PID [10849]. CSI Set Received

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00243 : INFO)
CSI Flags : [Target One]

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00244 : INFO)
CSI Name : [csa101CSII0]

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00245 : INFO)
HA State : [Quiesced]

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00246 : INFO)
csa101: Acknowledging new state

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00249 : INFO)
Component [csa101I0] : PID [10849]. CSI Remove Received

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00250 : INFO)
CSI : csa101CSII0

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00251 : INFO)
CSI Flags : 0x2
</pre></code>
|}

Our component has been put into Lock Assignment state so our 'Hello World!' output has stopped printing to the log.

<li>At this point you can either unlock the service group to change its state to "unlocked" or you can lock it for instantiation to change it to state "locked-for-instantiation". The latter will cause the csa101 process to die. From state "locked-for-assignment", it is possible to change the state to "locked-for-instantiation" by running (in the SAFplus Platform Console):
<code><pre>
cli[Test:SCNodeI0:CPM]-> amsLockInstantiation sg csa101SGI0
cli[Test:SCNodeI0:CPM] -> end
cli[Test:SCNodeI0] -> end
cli[Test] -> bye
</pre></code>
</ol>

===Stopping SAFplus Platform===

To stop SAFplus Platform on the System Controller
<ol>
<li>Open a shell.
<li>ssh into the System Controller node as root.
<li>Once logged in, run the following command
<code><pre>
# cd /root/asp
# etc/init.d/asp stop
</pre></code>
</ol>

==Summary and Next Steps==
In the csa101 example we learned the following.

<ul>
<li>How to create a system model using the '''SAFplus Platform IDE'''.
<li>How to generate the source code.
<li>How to customize this source code to fit a specific application.
<li>How to configure and build the customized source code.
<li>How to make runtime images and deploy them to target machines.
<li>How to start and stop '''SAFplus'''.
<li>How to interact with system components using the '''SAFplus Platform Console'''.
</ul>

The next logical step would be to run through the '''SAFplus Platform Evaluation System User Guide'''. This guide goes over more complex system configurations and introduces new concepts.

For more in depth information on the '''SAFplus Platform IDE''' see the '''SAFplus Platform IDE User Guide'''.

For more in depth information on the '''SAFplus Platform SDK''' see the '''SAFplus Platform SDK User Guide'''.

==Appendix A: target.conf Settings==

Below is a description of the values in the settings in the <code>target.conf</code> file.

<ol>
<li>'''TRAP_IP''' (Mandatory): Specifies where the SNMP SubAgent should send traps at runtime. If you do not have an SNMP SubAgent in your model specify '''127.0.0.1''' as the value. e.g.:
<code><pre>
TRAP_IP=127.0.0.1
</pre></code>
<li>'''CMM_IP''' (Mandatory if deployed on an ATCA chassis): Specifies the IP address of the target system's chassis management module or shelf manager. ATCA chassis Example:
<code><pre>
CMM_IP=169.254.1.2
</pre></code>
<li>'''CMM_USERNAME''' and '''CMM_PASSWORD''' (Mandatory if deployed on an ATCA chassis): Specifies the username and password required for the OpenClovis SAFplus Platform Chassis Manager to connect to the target system's chassis management module. e.g.:
<code><pre>
CMM_USERNAME=root
CMM_PASSWORD=password
</pre></code>
<li>'''INSTALL_PREREQUISITES=YES|NO''' (Mandatory): Specifies whether the target images will include 3rd party runtime prerequisites or not. Say '''YES''' if the target nodes do not meet the target host requirements specified in the Installation section of this document. e.g.:
<code><pre>
INSTALL_PREREQUISITES=YES
</pre></code>
<li>'''INSTANTIATE_IMAGES=YES|NO''' (Mandatory): Specifies whether <code>make images</code> will generate node-instance specific images instead of only generating node-type specific images. This option is a development optimization for advanced users of SAFplus Platform SDK. If unsure, say '''YES'''. e.g.:
<code><pre>
INSTANTIATE_IMAGES=YES
</pre></code>
<li>'''CREATE_TARBALLS=YES|NO''' (Mandatory): Specifies whether the node-instance specific images created will be packaged into tarballs for deployment onto the target system. If unsure, say '''YES'''. e.g.:
<code><pre>
CREATE_TARBALLS=YES
</pre></code>
<li>'''TIPC_NETID''' (Mandatory): Specifies a unique identifier used by TIPC to set up interprocess communication across the deployed OpenClovis SAFplus Platform cluster. This is an unsigned 32-bit integer, and must be unique for every model that is deployed. e.g.:
<code><pre>
TIPC_NETID=1337
</pre></code>
<li>'''Node Instance Details''': These specify the node-instance specific parameters required for deploying the model. For each node in the model there is a corresponding entry in the file:
<ol>
<li>'''SLOT_<node instance name>''' (Mandatory): Specifies which slot the node is located in. The first slot is slot 1 -- DO NOT USE SLOT NUMBER 0, it is invalid. When deployed to an ATCA chassis, the physical slot in which the blade is actually installed will override this value. When deployed to regular (non-ATCA) systems, this is a logical slot and must be unique for every node in the cluster. e.g.:
<code><pre>
SLOT_SCNodeI0=1
</pre></code>
<li>'''LINK_<node instance name>''' (Optional): Specifies the ethernet interface used by the node for OpenClovis SAFplus Platform communication with the rest of the cluster. If unspecified, this defaults to <code>eth0</code>. e.g.:
<code><pre>
LINK_SCNodeI0=eth0
</pre></code>
<li>'''ARCH_<node instance name>''' (Optional if '''ARCH''' is specified): Specifies the target architecture of the node as a combination of machine architecture (MACH) and linux kernel version. This is only required on a per-node basis if the target cluster has heterogeneous architectures across the nodes. If it is a homogeneous cluster, a single '''ARCH''' parameter (described below) will suffice. e.g.:
<code><pre>
ARCH_SCNodeI0=i386/linux-2.6.14
</pre></code>
<li>'''ARCH''' (Optional if node-specific '''ARCH_''' parameters are specified): Specifies the target architecture of all nodes in a homogeneous cluster as a combination of machine architecture (MACH) and linux kernel version. Note: The build process automatically populates this variable based on the last target the model is built for.e.g.:
<code><pre>
ARCH=i386/linux-2.6.14
</pre></code>
</ol>
For example, if we have a three-node cluster with the following details:
{| border="0" cellpadding="3" align="center" width="600"
|+ align="bottom" | '''Example Node Instance Detail'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Node Name
!style="color:#66b154; background:#09477c"| Slot Number
!style="color:#66b154; background:#09477c"| Link Interface
!style="color:#66b154; background:#09477c"| Architecture
|- style="color:#ffffff; background:#549cc6"
|SCNodeI0
|1
|eth0
|i386/linux-2.6.14
|- style="color:#ffffff; background:#549cc6"
|PayloadNodeI0
|3
|eth0
|i386/linux-2.6.14
|- style="color:#ffffff; background:#549cc6"
|PayloadNodeI1
|4
|eth1
|ppc/linux-2.6.9
|}
we would specify the node instance details as:
<code><pre>
SLOT_SCNodeI0=1
SLOT_PayloadNodeI0=3
SLOT_PayloadNodeI1=4

LINK_SCNodeI0=eth0
LINK_PayloadNodeI0=eth0
LINK_PayloadNodeI1=eth1

ARCH_SCNodeI0=i386/linux-2.6.14
ARCH_PayloadNodeI0=i386/linux-2.6.14
ARCH_PayloadNodeI1=ppc/linux-2.6.9
</pre></code>
</ol>

==Appendix B: AMF Configuration Details==
This appendix gives brief descriptions of configuration details for instances of different entities (like Node, Service Group, Service Unit etc) that are present in the '''Clovis''' -> '''AMF Configuration''' dialog box.

===Node Instance===
This screen displays the node instance that was created by the Node Instance Wizard. This node instance was created because the node type '''SCNode''' was selected on the wizard screen.

[[File:Tutorial_NodeInstanceDetails.png|frame|center| '''Node Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Node Instance Name''': This field holds the name of the node instance. This name must be unique. The name that was generated combines the node type (SCNode), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''Node Type''': This field holds the node type that was selected on the wizard screen.
<li>'''MOID''': This is the unique identifier for the node instance. It was generated by the wizard. The format of this ID is a string representing the one and only instance of the chassis (\Chassis:0) defined in the Resource Editor followed by a string representing the first and only instance of the blade type (\SysBlade:0) that was selected in the Node Instance Wizard.
 [[File:OpenClovis_Note.png]]'''MOID''' is an acronym for Managed Object Identifier. It must be unique and is used to identify which hardware chassis and blade type this instance will run on.
</ul>

===Service Unit Instance===
This screen displays the service unit instance that was created by the Service Group Instance Wizard. This service unit instance was created because the service unit type is associated with both the selected node type (SCNode) and the selected service group type (csa101SG) in our model.

[[File:Tutorial_SUInstanceDetails.png|frame|center| '''SU Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''SU Instance Name''': This field holds the name of the service unit instance. This name must be unique. The name that was generated combines the service unit type (csa101SU), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''Service Unit Type''': This field holds the type of the service unit instance.
</ul>

===Component Instance===
This screen displays the component instance that was created by the Service Group Instance Wizard. This component instance was created because the component type is associated with the created parent service unit type (csa101SU) in our model.

[[File:Tutorial_ComponentInstanceDetails.png|frame|center| '''Component Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Component Instance Name''': This field holds the name of the component instance. This name must be unique. The name that was generated combines the component type (csa101), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''Component Type''': This field holds the type of the component instance.
</ul>

===Service Group Instance===
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.

[[File:Tutorial_SGInstanceDetails.png|frame|center| '''Service Group Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''SG Instance Name''': This field holds the name of the service group instance. This name must be unique. The name that was generated combines the service group type (csa101SG), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''ServiceGroup Type''': This field holds the type of the service group instance.
<li>'''Associated Service Units''': This button is used to associate service unit instances with this service group instance. Creating this association indicates that the selected service unit(s) will run within this service group instance.
</ul>

Clicking the '''Associated Service Units''' Edit... button will display the following dialog.

[[File:Tutorial_SG_SI_Association.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.

===Service Instance Instance===
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.

[[File:Tutorial_SIInstanceDetails.png|frame|center| '''Service Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Service Instance Name''': This field holds the name of the service instance. This name must be unique. The name that was generated combines the service instance type (csa101SI), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''ServiceInstance Type''': This field holds the type of the service instance.
</ul>

===Component Service Instance Instance===
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.

[[File:Tutorial_CSIInstanceDetails.png|frame|center| '''Component Service Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Component Service Instance Name''': This field holds the name of the component service instance. This name must be unique. The name that was generated combines the component service instance type (csa101CSI), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''ComponentServiceInstance Type''': This field holds the type of the component service instance.
</ul>

Talk:Index.php

2012-02-21T03:47:42Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

<a href=http://ritualus.ru/css/guest/index.php?showforum=1>сколько калорий в горчичном хлебе</a>
кровь из носа, резкое похудение симптомы
<a href=http://arhmuseum.ru/images/guest/index.php?showforum=1>солярий похудеть</a>
красивая женская фигура
<a href=http://www.nex-demo.com/joomla09/forums/viewtopic.php?f=9&t=106383&p=173076#p173076>количество килокалорий в продуктах</a>
диета при прободной язвеободная язва желудка диета
<a href=http://www.ridder-hansl.info/index.php?topic=60872.new#new>что можно есть на белковой диете</a>
подбор диеты + от елены малышевой
<a href=http://www.vanschuylenbergh.com/vanallesewa/forum/viewtopic.php?p=558604#558604>диета 5 кг 1 неделя</a>
рефераты на англ. языке, тема диета
<a href=http://technicallylost.com/wp-includes/guest/index.php?showforum=1>диетические фрукты и овощи</a>
вес список кремлевской диеты
<a href=http://forums.dreadarmy.com/index.php?topic=17068.new#new>скачать бесплатно дыхательная гимнастика бодифлекс ирины макаровой</a>
японская бессолевая диета меню
<a href=http://www.cistercium.es/foro/viewtopic.php?f=2&t=54996&p=63537#p63537>книга диетолога ковалькова</a>
худеем + по крови
<a href=http://69.163.158.57/phpBB3/viewtopic.php?f=3&t=22346&p=44264#p44264>калорийность бкльенов</a>
дневники сидящих на японской диете
<a href=http://digiscriptinc.com/js__/guest/index.php?showforum=1>гречневая крупа. калорийность</a>
чистка кишечника реитами народной медицины
<a href=http://beta.cornerstonexp.org/includes/guest/index.php?showforum=1>калорийность пахлавы по-бакински</a>
бросила курить поправилась на 10кг хочу за месяц похудеть
<a href=http://archeologistsforum.takislab.com/viewtopic.php?f=3&t=181094&p=357751#p357751>диетический шоколад рецепт</a>
персональный повар диетолог vip
<a href=http://www.arsa.nmc.ac.th/forum/index.php/topic,4193.new.html#new>кто на сколько похудел на овсяной диете?</a>
похудела за какое то время
<a href=http://inresto.ru/js/guest/index.php?showforum=1>как правильно пить энерджи диет</a>
можно ли заниматься тяжелой атлетикой диабетикам
<a href=http://www.solicc.org/phpBB3/viewtopic.php?f=3&t=46242&p=76214#p76214>лечебные диеты 3, 4</a>
аттестационной материал медсестры по диетпитанию
<a href=http://coconutsounds.com/webboard/index.php?topic=8.0>мигрень диетотерапия</a>
медицина сахарный диабет припараты для лечения
<a href=http://belarent.ru/images/guest/index.php?showforum=1>калорийность урюка</a>
сул из сельдерея диета
<a href=http://forum.blipadeal.com/forum/viewtopic.php?f=3&t=11448&p=14308#p14308>похудение водой</a>
центр лечения диабета
<a href=http://www.job-pile.com/viewthread.php?tid=97750&pid=150016&page=25&extra=#pid150016>сколько килокалорий в курином яйце</a>
диета abc меню
<a href=http://www.cktoolspro.com/webboard/index.php?topic=4756.new#new>диета + при дивертикулезе сигмовидной кишки</a>
лида похудение москва

== волшебная таблетка афродиты похудение ==

[url=http://www.dev.arbitersoflight.net/forums/viewtopic.php?f=5&t=9434&p=17202#p17202]диета боннская екакой эффект[/url]
она похудела
[url=http://sailorcreek.hadirectory.co.uk/wp-content/plugins/zingiri-forum/mybb/showthread.php?tid=91424&pid=106520#pid106520]антипуриновая диета № 6[/url]
диета и режим кормящей матери
[url=http://hungariangods.uw.hu/viewtopic.php?p=10496#10496]калорийность овощного салата с маслом[/url]
диета для уменьшения объемов
[url=http://www.honspot.com/forums/viewtopic.php?f=2&t=42124&p=53664#p53664]оптимальный вес по брунхарду[/url]
медицинские центры где вставляют иглу для похудения
[url=http://newsletter.bitsaa.org/forum/viewtopic.php?f=2&t=29835&p=38370#p38370]как вызвать рвоту + чтобы похудеть[/url]
проверенная диета ангела
[url=http://www.recipes.ozinetworks.com/forums/viewtopic.php?f=10&t=46550&p=56380#p56380]лекарство + от сахарного диабета япония[/url]
я толкнул ее ногой-худая кошка шмыгнула мимо
[url=http://digicapsig.com/forum/viewtopic.php?pid=17834#p17834]как питаться правильно и сбросить вес[/url]
rjrntkb энерджи диет
[url=http://pepc.rynetproject.com/forum/viewtopic.php?f=2&t=105334&p=212735#p212735]сколько калорий + в вареной говядине[/url]
панкреатическая диета №5
[url=http://igrobukvoteka.ru/forum/viewtopic.php?p=179611#179611]диета при угрозе сахар[/url]
диета + на сосисках
[url=http://www.papercenter.vooa.pl/index.php?topic=26121.new#new]алкоголизм, наркомании, внешнее проявление, борьба за здоровый образ жизни[/url]
таблица калорий готовых продуктов
[url=http://0of.ru/showthread.php?3919-%D0%BA%D0%B0%D1%80%D1%82%D0%BE%D1%84%D0%B5%D0%BB%D1%8C-%D0%BA%D0%B0%D0%BB%D0%BE%D1%80%D0%B8%D0%B9%D0%BD%D0%BE%D1%81%D1%82%D1%8C&p=5906#post5906]проекты по диабету 2009[/url]
белковые диеты для бодибилдеров
[url=http://www.dvvpu.org.ua/forum/viewtopic.php?f=5&t=7175&p=17705#p17705]аптечные таблетки для похудения[/url]
диета если повышен сахар в крови
[url=http://linkedin.seo7.net/sutra363.html#363]похудение от алексея[/url]
голодание и омолаживание
[url=http://www.minecraft1.co.uk/showthread.php?27537-45-%E4%ED%E5%E2%ED%E0%FF-%EE%F7%E8%F1&p=36132#post36132]сколькл калорий в кусочке медовика[/url]
таблетки помогающие похудеть
[url=http://onggong.w1.net/phpbb/viewtopic.php?p=215238#215238]сахарный диабет 1 типа гипегликемия[/url]
всё о сахарный диабете
[url=http://www.recaida.com/forumrec/viewtopic.php?p=54576#54576]эффективное похудение фото до и после[/url]
чем полезна грейфруктовая диета
[url=http://www.saxophonestocollect.com/forum/viewtopic.php?p=57132#57132]бодифлекс пресс[/url]
вода как диета
[url=http://nintendo-nebula.net/forums/showthread.php?tid=4662&pid=5279#pid5279]результат японская диета[/url]
фито чай + для похудения
[url=http://www.pol.ubu.ac.th/election54/webboard/index.php?topic=9939.new#new]почки + при сахарном диабете[/url]
калорийность мед
[url=http://prophotoguru.com/forums/viewtopic.php?f=16&t=68074&p=103276#p103276]диета-суп из лука порей[/url]
худеем правильно королева

== таблетки для похудения лидо отзывы ==

[url=http://hotelrenata.com/images/guest/index.php?showforum=20]велосипед калории[/url]
девушки выпили чай для похудения
[url=http://www.wiangchai.go.th/webboard/index.php?topic=78878.new#new]продажа б/у книги старые по диете[/url]
диабет 2ст
[url=http://www.gingermanc.co.uk/forum/showthread.php?tid=76680&pid=84955#pid84955]обертывание пленкой + для похудения[/url]
абсцесс голодание
[url=http://www.solocap.com/forums/viewtopic.php?f=10&t=6959&p=8805#p8805]диабет и сои[/url]
сколько надо набрать гликемических индексов различных продуктов при сахорном диабете
[url=http://melbournegaming.org/showthread.php?tid=3293&pid=4214#pid4214]диетадлшя усиления обмена веществ[/url]
антиоксидантная терапия у больных дисциркуляторной энцефалопатией отягощенной сахарным диабетом тип
[url=http://ff-kettenreith.at/forum/showthread.php?tid=436382&pid=444429#pid444429]звезда похудела[/url]
отвар шалфеядля похудения
[url=http://limusin-zurich.ru/includes/guest/index.php?showforum=1]мониторная очистка кишечника санкт петербург стоимость[/url]
мартынова людмила ивановна диет сестра пильнинской больници
[url=http://forum.servicepointvalcurone.it/viewtopic.php?p=103712#103712]без регистрации бесплатно похудеть[/url]
продукты кремлевской диеты
[url=http://duniaforum.com/showthread.php?59515-%EF%EE%F2%E5%F0%FF-%EA%E0%EB%EE%F0%E8&p=72235#post72235]биология доклад здоровый образ жизни[/url]
какое животное дает самое жирное молоко
[url=http://www.wiengkalong.in.th/webboard/index.php?topic=1489.new#new]рецепты от диетолога[/url]
как похудеть с помощью народных средств
[url=http://ipages.iitsweb.com/forum/viewtopic.php?pid=2888#p2888]картинки ожирение фитотерапия[/url]
роль физической культуры в обмене веществ
[url=http://therealhistory.org/forum/viewtopic.php?f=2&t=101247&p=158520#p158520]прошай диабет[/url]
что поможет похудению
[url=http://forum.boboho.net/showthread.php?5967-%EA%E0%EA-%F1%EF%E0%F1%E8%F2%E5-%E7-amp&p=8026&posted=1#post8026]сахарный диабет диета по группе крови[/url]
как похудеть в руках и ногах?
[url=http://forum.immunoterapia.ru/smf/index.php?topic=4393.new#new]истра лечебное голодание[/url]
очень жесткая но эффективная диета
[url=http://apoll.ru/includes/guest/index.php?showforum=1]голодание против паразитов[/url]
блюда из куриных грудок для диеты
[url=http://www.eliasranzschleifer.com/forums/viewtopic.php?f=12&t=169463&p=258197#p258197]диета для упругости[/url]
капсулы для похудания дали состав
[url=http://1izen.com/wp-content/plugins/zingiri-forum/mybb/showthread.php?tid=73479&pid=78057#pid78057]кислородное голодание у дететей первого года жизни[/url]
голодание пчел
[url=http://esed.upn.mx/modules.php?name=Forums&file=viewtopic&p=1018945#1018945]калорийность котлеты зразы[/url]
диета + при раке пищевода
[url=http://rchsteachers.org/forum/index.php?topic=72580.new#new]как вылечить диабет второго типа[/url]
лечебное питание при холецистите панкреатите
[url=http://ishimsad24.ru/templates/guest/index.php?showforum=1]распорядлк дня для похудения[/url]
сколько калорий в геркулесовой каше

== какая диета прописана при тахикардии ==

[url=http://www.la2-shift.com/forum/showthread.php?p=47529&posted=1#post47529]лечебное питание пациентов с патологией органов пищеварения.рефераты.[/url]
молоко с медом отзывы похудение
[url=http://bu96.ru/showthread.php?p=12804&posted=1#post12804]можно ли похудеть с помощью турбослим?[/url]
какую пищу можно есть расчет калорий за сутки
[url=http://madvertiserblogs.com/talkalabama/index.php?topic=120262.new#new]рецепт хлеба диет[/url]
возможно ли похудеть в великом посту
[url=http://ingenierodesoftware.megabyet.net/foros/index.php?topic=51500.new#new]лечим простуду при сахарном диабете у ребенка[/url]
рецепт диабет
[url=http://nayaritconsandoval.org/foro/viewtopic.php?f=2&t=194357&p=262979#p262979]обертывание для похудения в бане[/url]
новые диеты для похудания
[url=http://www.baerental-party.at/forum/showthread.php?tid=42095&pid=51075#pid51075]скачать программу ускоренного снижения веса[/url]
капсулы меридиан для похудения купить в петербурге
[url=http://akvom.ru/includes/guest/index.php?showforum=1]изменение обмена веществ при голодании[/url]
супер низкоклорийные диеты
[url=http://forum.nascutiaici.com/viewtopic.php?f=6&t=85748&p=135182#p135182]невралгия и сахарный диабет[/url]
лечебное питание роддом
[url=http://www.xn---21-5cdabe8ao5azmmz8ah.xn--p1ai/includes/guest/index.php?showforum=1]диеты для беременных[/url]
индивидуальная астрологической диеты
[url=http://jalues.bplaced.net/hsm//thread.php?sid=b833b4c4a6aaab31e45ce8eec096992f&postid=45416#post45416]диетический стол №10п[/url]
где скачать книгу как похудеть, не отходя от жизни
[url=http://www.chiangrai.rmutl.ac.th/radio/forums/index.php?topic=387.new#new]можно ли похудеть занимаясь ездой на велосипеде[/url]
низкокалорийный салат из крабовых палочекрецепт
[url=http://info.thetradeindia.com/forum/viewtopic.php?p=27283#27283]диссертация. диабетическая стопа[/url]
понятие кома при сахаарном диабете
[url=http://www.leetsins.com/showthread.php?tid=1149&pid=2870#pid2870]низкокалорийные блюда из мяса[/url]
dizao стройная фигура отзыв
[url=http://www.cergy-pontoise.1formatik.com/viewtopic.php?f=2&t=148763&p=242537#p242537]как стать стройной и сексуальной[/url]
китайская косметика чай сантиметр, таблетки для похудения
[url=http://www.dykal.net/forums/showthread.php?p=30738&posted=1#post30738]диета при раке яичника[/url]
целлюлита на попе
[url=http://www.2.mtzspb.z8.ru/includes/guest/index.php?showforum=1]и похудении[/url]
диабетика в проиморском крае
[url=http://jiangxiyiliao.tk/viewthread.php?tid=237418&pid=320987&page=12&extra=#pid320987]lierac от целлюлита[/url]
диета от светланы ахтаровой орт
[url=http://biophysics.vn/showthread.php?7073-%D0%BC%D0%B0%D0%BA-%D0%BA%D0%B0%D0%BB%D0%BE%D1%80%D0%B8%D0%B8&p=8592#post8592]обматывание пленкой для похудения[/url]
до чего доводит похудение ужасные кадры
[url=http://fz152.ru/includes/guest/index.php?showforum=1]диета мелани гриффит форум[/url]
способствуют ли оливки похуденияю
[url=http://www.oncoradioteca.com/foro//viewtopic.php?p=393098#393098]сколько стоит персональная диета малышевой[/url]
диета для живота без цитрусов

== что представляют из себя таблетки для похудения анжелика ==

[url=http://www.sohomotor.com/shop/forum/viewtopic.php?p=8986&sid=b36f4cb80f87647dec98a74925e9817b#8986]правильный вес похудеть[/url]
таблица калорийности сыр эменталь
[url=http://forum.undefeatedkal.net/viewtopic.php?f=19&t=10338&p=14469#p14469]все о фитнесе диета[/url]
диета из каш отзывы
[url=http://www.luckydiva.net/webboard/index.php?topic=21519.0]похудение ксюши бородиной[/url]
диета доктора аткинса отзывы
[url=http://komandor54.ru/includes/guest/index.php?showforum=1]очень сиьон замедленный обмен веществ[/url]
быстро вывести из диабетической комы человека
[url=http://3quote.co.za/images/guest/index.php?showforum=1]что поможет похудению бизнес[/url]
капсулы для похудения китайские zhen de snou
[url=http://www.alphawolves.net46.net/phpBB3/viewtopic.php?f=4&t=2424&p=2800#p2800]диета при молочнице что можно[/url]
4 степень ожирения
[url=http://decor-studio.com.ua/images/guest/index.php?showforum=1]офоризмы о диете[/url]
почему появляется целлюлит
[url=http://spartak-sib.ru/includes/guest/index.php?showforum=1]кремлевская диета 14 дней[/url]
25 кадр похудение форумы отзывы
[url=http://forum.webjabber.net/viewtopic.php?p=90198#90198]диета при кисте молочной железы[/url]
самые толстые люди которые похудели
[url=http://deathwatch.xippyforum.com/viewtopic.php?f=5&t=24301&p=41469#p41469]малахов плюс мёд для похудения[/url]
редуксин таблетки для похудания
[url=http://forum.wakakaksite.net/showthread.php?tid=5794&pid=8997#pid8997]лечнеие сахарного диабета народными средствами[/url]
сахарный диабет глюкометры
[url=http://www.inglesagora.com.br/aefforum/viewtopic.php?f=9&t=115105&p=137732#p137732]торт низкокалорийный приготовить[/url]
можно ли похудеть за день на 2 килограмма?
[url=http://kortowiada-2011.pl/forum/showthread.php?tid=9747&pid=10159#pid10159]санатории по лечению ожирения в белоруссии[/url]
вкусные диетические блюда при желче-каменной болезни и болезни поджелудочной железы
[url=http://www.corygrantconcrete.com/css/guest/index.php?showforum=1]здоровый образ жизни физкультура и спорт[/url]
перловая диета для похудения
[url=http://techandhack.com/viewtopic.php?f=1&t=110468&p=158025#p158025]как убрать целлюлит с рук[/url]
сбалансированная диета и формы питания спортсменов
[url=http://buloto.com/bbs//viewthread.php?tid=190484&pid=213527&page=25&extra=#pid213527]программа похудения на тренажорах[/url]
вендинг похудение
[url=http://www.namphi214.com/webboard/index.php?topic=28091.new#new]девушка умерла от диеты d gjlvjcrjdmt[/url]
трофические язвы на почве сахарного диабета
[url=http://forum.w3connect.com/showthread.php?tid=28664&pid=38196#pid38196]после родов восстановление менструального[/url]
перечень блюд для больных сахарным диабетом
[url=http://www.iced-silver.net/test/phpbb2-22/viewtopic.php?p=141144#141144]пояс для похудания nobil rex 101[/url]
быть худой
[url=http://johnnydeppitalia.com/forum/index.php?topic=600.new#new]межпозвонковой грыжи голоданием[/url]
упражнения для пресса и талии

== основные принципы диетотерапии сахарного диабета ==

[url=http://hostfirm.ru/logs/guest/index.php?showforum=1]правильно худеем гимнастика[/url]
диета здоровье форум закрыт
[url=http://www.punbb.tk/viewtopic.php?pid=63168#p63168]снижение веса по методу хайруллина[/url]
похудеть с худеем за неделю
[url=http://trikotaj-optom.ru/includes/guest/index.php?showforum=1]можно ли похудеть от зеленого чая?[/url]
лучшие лекарственные средства для похудения
[url=http://forum.autoshop.am/viewtopic.php?f=10&t=96404&p=211703#p211703]самые лучшие таблетки для похудения в области живота[/url]
как похудеть за месяц без препаратов
[url=http://www.i1y.com/vb/showthread.php?10112-%E4%E8%E5%F2%E0-%EF%F0%E8-%E7%E0%E1%EE%EB%E5%E2%E0%ED%E8%E8-%EF%F0%FF%EC%EE%E9-%EA%E8%F8%EA%E8&p=19059#post19059]людмила денисенко худеем + с удовольствием[/url]
столовой потому как диета является неотъемлемой частью любого лечения
[url=http://www.7mileislandreview.com/phpBB3/viewtopic.php?f=1&t=69746&p=87238#p87238]диагноз сахарный диабет на казахском языке[/url]
вред + и польза диет
[url=http://www.jeugdhonkstiensgea.nl/phpBB2/viewtopic.php?p=726376#726376]форум анарексия как похудеть[/url]
форум раздельное питание
[url=http://www.skillfaker.org/phpBB/viewtopic.php?f=8&t=29&p=30849#p30849]омар хаям лучше голодать[/url]
справочник диет психоневрологических больных
[url=http://discussion.myhotspot.co/viewthread.php?tid=307523&pid=441247&page=1&extra=#pid441247]похудеть по аюрведе[/url]
диета подробная
[url=http://almines.mines-paris.eu/forum/viewtopic.php?pid=30546#p30546]диабет измерение сахара[/url]
капсулы для похудения частные оьявления
[url=http://club.yuntech.edu.tw/%7Eelsa/bbs/viewthread.php?tid=121053&pid=145106&page=10&extra=#pid145106]алан карр как быстро похудеть[/url]
лечебные диеты стол 1-15
[url=http://anorexiaparentforum.com/viewtopic.php?f=11&t=448536&p=651170#p651170]fenugreek кто нибудь использовал для похудения[/url]
школьный предмет "здоровый образ жизни"
[url=http://www.todonoticias.cat/forum/index.php?topic=22971.new#new]иголки для похудения в тюмени[/url]
очищение организма похудение в звенигороде
[url=http://www.dotaall.ru/distribution/viewtopic.php?f=4&t=34086&p=47467#p47467]10 лучших диет[/url]
как мужчине убрать жир с живота и боков
[url=http://thanatos.co/forum/showthread.php?tid=51632&pid=57373#pid57373]диета в великий пост 2010[/url]
калорийности соевого мяса
[url=http://www.soeste-angelcenter.de/phpBB3/viewtopic.php?f=11&t=5443&p=6792#p6792]скачать видео материалы гимнастику для похудания[/url]
низкоуглеводные и моложирные диеты
[url=http://el-diarus.com/images/guest/index.php?showforum=1]диета 4 2[/url]
можно ли похудеть при помощи арабских танцев?
[url=http://www.legion.co.il/phpBB3/viewtopic.php?f=7&t=119962&p=241543#p241543]овсяная диета с кефиром[/url]
как можно похудеть на 5кг за две недели пивной диетой
[url=http://metafrost.net/forums/index.php?topic=7276.new#new]калории в котлете[/url]
лечебное голодание россии
[url=http://itu.dk/people/jhma/forum/viewtopic.php?f=1&t=53650&p=77838#p77838]диета стол № 5 рецепты[/url]
справочник калорийности продуктов

== антицеллюлитный крем фирмы salon ==

[url=http://cpu.de/includes/guest/index.php?showforum=1]диабет плюс[/url]
аэробные тренировки для похудения
[url=http://www.legendmodz.com/showthread.php?tid=6798&pid=9028#pid9028]похудеть быстро высокоэффективная программа похудения на hudoba ru[/url]
сахарный диабет 2 типа средней степени тяжести история болезни
[url=http://finantare-nerambursabila.ro/forum/showthread.php?tid=47650&pid=53762#pid53762]президентская диета 2-я фаза[/url]
антицеллюлитный массаж во
[url=http://www.agenciainterative.com.br/forum/viewtopic.php?f=10&t=156513&p=231350#p231350]самая худая порнозвезда[/url]
помогите подобрать диету
[url=http://www.bionic-gaming.com/forum/viewtopic.php?f=3&t=93812&p=148129#p148129]психология лишниего веса и стресса диплом скачать[/url]
свекольная диета заболевания
[url=http://www.webturkeymaster.com/showthread.php?p=265600#post265600]биология обмен веществ трансформация энергии[/url]
эко диета
[url=http://www.f1news.eu/index.php/index.php/f1-forum/editpost/389-oem_adobe_indesign/0]похудела на диете протасова[/url]
голодая на сколько похудеешь
[url=http://www.irunlikeamother.com/wp-includes/guest/index.php?showforum=1]кэролин хамфрис ?дневная диета[/url]
похудение без диет
[url=http://www.nusapromo.com/showthread.php?p=146300#post146300]гастит диета[/url]
сахарный диабет инсулинопотребный
[url=http://berlinforums.artoflivingpa.org/viewtopic.php?f=2&t=20&p=22662#p22662]лечебное питание и диеты при язве желудка[/url]
меню 1000 калорий
[url=http://gross.tritonplus.ru/includes/guest/index.php?showforum=1]как похудеть без вреда для организма[/url]
диета для похудания с витаминами
[url=http://loadeddicers.com/showthread.php?2750-%E4%E8%E5%F2%E0-%E9%EE%E3%F3%F0%F2-amp&p=3365#post3365]фрутовая диета по калориям[/url]
сахарный диабет классификация, тип
[url=http://arabcon.net/viewtopic.php?f=12&t=118126&p=174381#p174381]можно ли беременнить при диабет 2 типа[/url]
препарат для похудания израиль
[url=http://crusify.net/thread-99-post-20816.html#pid20816]раздельное питание меню + на неделю[/url]
как часто проводить сухое голодание
[url=http://fa.planet-iwd.de/index.php?topic=9.new#new]какие таблетки для похудения можно купить в каждой аптеке[/url]
средство для похудения гарциния
[url=http://www.mulss.com/swap/viewtopic.php?f=4&t=37009&p=42553#p42553]разгрузочные дни в диетотерапии[/url]
диетическое меню длядвухгодовалого ребенка рецепты
[url=http://qz.huiyoubaby.com/bbs//viewthread.php?tid=484753&pid=543957&page=11&extra=#pid543957]в чем суть диеты соколовского[/url]
меню при диабете второго типа
[url=http://yibowang.de/forum/viewtopic.php?p=446256#446256]криветки при диабете[/url]
несахарный диабет при беременности
[url=http://www.ferforjeforum.com/showthread.php?pid=59088]диета по дням для 1 группы крови[/url]
больные дети сахарным диабетом
[url=http://lamitadmas1foro.com.ar/showthread.php?p=43159#post43159]переделанные песни на тему мы за здоровый образ жизни[/url]
рефераты на тему калорийность продуктов или как похудеть

== гарньер. роликовый крем от целлюлита. отзывы ==

[url=http://www.thetinmansgarage.com/wp-includes/guest/index.php?showforum=1]скачать стрельникова еда которая лечит диабет[/url]
3 группа крови диета таблица
[url=http://www.britestudent.com/forums/us/viewtopic.php?f=4&t=176140&p=304152#p304152]орз при диабете лечение[/url]
реферат на тему здоровый образ жизни и гимнастика
[url=http://flashclub.ch/flog/forums/showthread.php?tid=58348&pid=98972#pid98972]где в омске можно записаться к диетологу[/url]
леннджервзаимосвязь обмена веществ в организме
[url=http://www.wyspex.ru/includes/guest/index.php?showforum=1]лечение диета поджелудочная железа[/url]
куркума похудение
[url=http://www.lv88-gucci88.com/shop/forum/viewtopic.php?p=434232&Twesid=c2ca6f06c10ef23594c05df6affcd97b#434232]сахарный диабет, тиология, патогенез[/url]
антицеллюлитный крем домашних условиях
[url=http://www.board.m2-turkiye.org/showthread.php?p=9113#post9113]кремлевская диета, бульонный кубик у.е[/url]
вакцина от диабета итамар раз
[url=http://www.mountainflower.in.th/board/index.php?topic=46133.new#new]как похудела ира дубцова[/url]
целлюлит + у мужчин фото
[url=http://www.buddhistischejugend.at/forum/viewtopic.php?f=4&t=4667&p=5740#p5740]правильное питание + в школьной столовой[/url]
диеты для снижения веса для детей от 13 лет
[url=http://mirsvadeb.kz/bb/viewtopic.php?f=2&t=115600&p=219993#p219993]диета при язве луковицы 12 п.к[/url]
рецепт овощного диетического рагу
[url=http://redbusdrivers.co.uk/forum/viewtopic.php?f=2&t=257664&p=417904#p417904]лечебной антицеллюлитной косметики[/url]
процедуры + для похудения отзывы
[url=http://mohamedgabr.com/forum/viewtopic.php?f=2&t=142667&p=225703#p225703]калорийность пищи и нормы питания[/url]
калорийность бигуса
[url=http://andalasia.net/forum/viewtopic.php?f=21&t=30315&p=49259#p49259]диета + для эффективного похудения ног[/url]
диета с грибами и ананасом
[url=http://www.aevumspa.com/bbs//forum.php?mod=viewthread&tid=107&pid=337&page=23&extra=#pid337]бальзам шостаковского от диабетической стопы[/url]
мнение мужчин идеальная фигура
[url=http://www.behindthetill.com/forum/viewtopic.php?f=3&t=48683&p=60661#p60661]договор фрайчайзинка аптек сахарного диабета[/url]
похудела на 60 килограммов
[url=http://cthybridforum.com/viewtopic.php?f=4&t=176876&p=351427#p351427]сахарный диабет + при гипотериозе[/url]
коллектив и здоровый образ жизни
[url=http://fcnnet.farmcrisisnetwork.co.uk/forum/viewtopic.php?pid=82954#p82954]где купить dvd 25 кадр для похудения[/url]
диабет 2 й степени
[url=http://jogoseducativos.buscasulfluminense.com/wp-includes/guest/index.php?showforum=1]молочно-рисовая диета[/url]
иглоукалывание для похудения в питере
[url=http://www.friendship.plootek.eu/forum/viewtopic.php?f=19&t=42738&p=53223#p53223]книга по подсчету калорий[/url]
диетологи питание
[url=http://virtuozos.free.fr/viewtopic.php?p=3074#3074]низко калорийные рецепты[/url]
вопросы и ответы по диабету
[url=http://fa.planet-iwd.de/index.php?topic=9.new#new]здоровый образ жизни как ценность и факторы, его определяющие[/url]
можно ли есть сыр когда сидишь на диете?

== жиры животного происхождения в косметических средствах вредные для кожи ==

[url=http://essentialsln.com/wp-includes/guest/index.php?showforum=1]нормальный вес ребёнка в 30 недель[/url]
программа бодифлекс
[url=http://bctoyotas.net/forums/index.php?topic=171867.new#new]диета тому кто ходит в тринажорный зал[/url]
витэкс крем массажный антицеллюлитный
[url=http://bartowpost0003.com/viewtopic.php?f=2&t=226757&p=422290#p422290]12 шагов к сыроедению[/url]
диетология в тюмени
[url=http://www.suaxesaigon.com/forum/showthread.php?t=198&p=473#post473]о препаратах для похудения[/url]
диетический каталог сайтов site er
[url=http://www.videoanalytics.net/forums/viewtopic.php?p=13016#13016]избавление от лишнего веса в перми[/url]
сильно похудела от бодифлекса
[url=http://paradoxmt2.org/forum/showthread.php?p=7538#post7538]роль в обмене веществ надф[/url]
диета на 3 дня минус 12 кг
[url=http://dp.forum.o3.ua/index.php?topic=119892.new#new]гармония средство для похудения китай[/url]
настой травы помогающий подтягивать кожу при похудении
[url=http://avrora-style.ru/includes/guest/index.php?showforum=1]похудеть от сельдерея[/url]
2 ст ложки кофе 1 ст ложка крема похудение столовая
[url=http://genatcvale.ru/includes/guest/index.php?showforum=1]клиника доктор барминталь - метод похудание[/url]
диабет и
[url=http://politicalirish.s2.bizhat.com/politicalirish-post-19403.html#19403]фитнесс боди гель скраб для похудения для душа[/url]
чага настойка диабет
[url=http://xbox360pl.host56.com/showthread.php?tid=3753&pid=5711#pid5711]как быстро похудеть в области живота[/url]
мясо молочная диета
[url=http://forum.webet2win.com/index.php?topic=23940.new#new]похудение с помощью узи[/url]
скачать видео диеты
[url=http://andrecatering.su/language/guest/index.php?showforum=1]что сделать чтоб быстро похудели ноги у мужчин?[/url]
блокатор калорий фаза форум
[url=http://tutton.org/phpbb/viewtopic.php?f=8&t=46671&p=70963#p70963]дарницкий хлеб калории[/url]
сколько в сале калорий
[url=http://whatscienceis.com/forum/viewtopic.php?f=2&t=144125&p=317690#p317690]диета 5 при хроническом индуративном панкреатите[/url]
исцеление сахарного диабета авакян
[url=http://chainomania.k-e-d-r.ru/logs/guest/index.php?showforum=1]день диабетика в нижнем новгороде[/url]
хитозан коррекция веса
[url=http://www.symulator-farmy.eu/showthread.php?tid=3316&pid=12823#pid12823]вода помогла похудеть[/url]
как похудеть и убрать второй подбородок
[url=http://decor-studio.com.ua/images/guest/index.php?showforum=1]диеты кефирные и раздельное питание[/url]
диета 5-й постный стол
[url=http://www.xlys.com.my/forum/viewthread.php?tid=342898&pid=457730&page=3&extra=#pid457730]инна дом 2 похудела[/url]
инсулинотерапия при диабетической стопе - критерии перевода на инсулин
[url=http://www.sonicworld.org.uk/forum/viewtopic.php?f=7&t=117374&p=203536#p203536]похудение в бёдрах бесплатно скачать[/url]
можно ли похудеть при помощи сухого вина и сыра

== big adult nude ==

free carbian women porn
sexy heels video
incest boy fucks mother
nudity public pussy
queen of the elephants xxx torrent
lavoie michelle nude wallpaper
fucked by a real man
dream double dildo
matt gay porn
britney spears upskirt nude upskirts

== cherry doll porn star ==

filme gretchen porn
gay porn free picture bear
cliphunter porn clip
free xxx dump
hard kiddie porn
men sucking dick
spanish fly xxx
big black bootie girls fucking
redhead milf anal
amateur rough sex

== sexual abuse teens consequences depression ==

bollywood xxx nations
is cild porn anime illegal
djecije porn slike
sex sleeping video woman
lisa kudrow nude videos
bbw fuck clip
black girl masturbation video
lee porn tommy video
saggy pussy lips
free xxx picture thumbnail

== dildo deep inside ==

girls masturbating in cartoon underwear
cruz free nude penelope pic
free bisexual mpeg movie galleries
free lesbian scissoring porn
the radiology group milford
nude desert camping
free hot sexy porn
free pocket pc porn videos
nude latina butts
porn feature videos

== im fucking my cousin ==

video libero sexy
stacy dash xxx pics
sexy teen porn star
playboy photos of farrah fawcett nude
brad pitt nudes pics
fuck man shemale
gallery lingerie porn video
free movies with eva angelina/porn igloo
pussy penetration picture
film stars sex videos

== fuck hard for money ==

girls fucking in sexy outfits
free hardcore porn uk
celebrity free xxx pics
cock and fucking
free mini uk porn clips
ashanti nude pic
classy babes fucking
victoria pendleton nude
lichelle marie pornstarslikeitbig
photos of nude brothers

== lela nude futurama ==

funeral home milford
big tits and round asses dick sucking
free porn za
katie nude pic
dick sucking sluts
video fuck free
hot guys masturbating
fresh teen pussy videos
girl getting dildo
young man sucking dick

== bollywood celebrity nude photo ==

wife and girlfriend nude picks
porn sex bollywood
christine lakin nude pic
lexxi nude tyler
stormy water clip porn star
in pink pussy
hot grandma pussy
nude photo of miley cyrus
find free sex in geary oklahoma
tiffany thiessen nude photo

== advanced male masturbation technique ==

samantha fox pornstar
fuck i u wanna
raven riley blowjob pictures
female porn star imfd
xtube redtube pornhub
colombiano de foto porn
blonde blue eyed pussy
danilee derick getting fucked
xxx big cock porn clips
douglas nude sirtis uk

== private video of granny nude ==

gay man masturbating naked
porn thumb search
rap to hardcore
lankan porn site sri
xxx cotton candy
huge tit lesbians fucking
pamila anderson fuck
naked girls eating pussy
amature nude forum
sixteen weet skin nude

== dad fucking duaghter ==

gallery india porn
woman forced to fuck
bollywood sex video clips
climax prestige porn films
nude giada delarurntis photos
sex video of a scots teacher
bbw squirt sex
porn tv free
men and women fuck
tom byron pornstar mpegs

== jennifer lopez nude in u turn ==

sims 2 nude patches
thumbnail movies pierced tongue blowjob
free indian gay sex
nude black women feet
nude avatar the last airbender fanart
static youporn com
pussycat dolls don t cha kaskade
free indian sex story true
free manga porn movies
how i became a porn star

== teen girly porn ==

leila melani nude
hardcore animal celebrity sex
attached free no porn string
hot mature older porn sexy woman
fuck hard xxx
free porn site trailer web
10 minute porn clips
free traci lords pictures nude
crystal naked pics arizona xxx
7xxx aluminium ttt

== sex pictures of sailor moon ==

celebrity free pic sexy
nude sexy picture of jennifer lopez
punk girl hardcore
chat sex teeny
free lesbian xxx trailer
clip free sex vedio
blonde fuck series
desktop porn star
latin porn lady
intercorse xxx movies

== fuck mature video ==

teen picks free porn
piss and fuck
sexy young milfs
xxx personals emery south dakota
animals sucking dick
women who take big black dicks
boys teen nude
free photo naked sex
s m bondage hardcore
wide pussy thumbs

== young nude fucking ==

christy carlson romano nude pics
nude teen bath
dutch holland sex porn
gangster gay porn
centerfold gallery nude
nude redhead photography
belle bond xxx
free nude video clips
nudeactresses org password
sexy model posing nude

== luttrell nude rachel ==

free wife swap sex movies
bleach hentai porn
xxx teen titans game
japanese porn tv show
fuck latina rose sativa
blogs exhib sexes amateurs
pussycat dollls i hate this part
fake list nude
full hot free porn
little ass fucked

== justin timberlake sexyback free download ==

hardcore partying pool
shoutcast tv porn
glamour porn video
joley fisher nude
america guide naughty porn
cheapest dvd xxx
free xxx manga and hentai
fucked drunk teens
nude kiddy tgp
large breasted european women nude

== nude little gay boys ==

mature porn images models over 30
free xxx cum in your trailer
milf in black lingerie
free male sex video
ass fuck redhead
first porn timer
bear free fuck movie police
mexican woman sucking dick
celeb get fucked
i'm on my fucking lunch break wav

== invasion porn public video ==

fantasy xxx pictures
bbw smut vids
fuck kidnap mom
cam hidden pussy video
porny je taime porny
cunt milf movie
mature sex for tonight
free porn bbw passwords
black wives sex videos
free xxx playboy movie trailers

== strip poker loser nude picture ==

reporter locker room nude
free msn sexy wink
teen sex under water
free japan sex movies
free sex girls of delhi
kiddy girls porn
xxx elephant toons
milf gang bang trailer
usaf ssgt woman porn
database movie porn

== male nude artist alb nm ==

[URL=http://chargil-pagated.ru/free-sample-of-eve-sextape.html]free sample of eve sextape[/URL]
young son fuck his mother
[URL=http://tensistic-callel.ru/best-porn-preview.html]best porn preview[/URL]
blowjob myspace graphics
[URL=http://ottoes-mirrorise.ru/young-blond-women-nude-movie-galleries.html]young blond women nude movie galleries[/URL]
manga anime girls fan sites porn
[URL=http://frequinter-catalian.ru/sexy-lesbian-latin-girls.html]sexy lesbian latin girls[/URL]
milf fake boob
[URL=http://televelop-circulosis.ru/castaic-free-sex.html]castaic free sex[/URL]
fucking housewife mature muscle stud young
[URL=http://farminish-psycholar.ru/sexy-underwear-for-full-figure-woman.html]sexy underwear for full figure woman[/URL]
ass jack porn
[URL=http://passembles-spearance.ru/empornium-confirmation-email.html]empornium confirmation email[/URL]
anal clip free video xxx
[URL=http://disambula-attributin.ru/granny-fuck-thumbs.html]granny fuck thumbs[/URL]
son fucks grandmother
[URL=http://emergesternel-ravelena.ru/porn-star-courtney-cummz.html]porn star courtney cummz[/URL]
milf cruiser jillian
[URL=http://tensistic-callel.ru/fuck-hole-wall.html]fuck hole wall[/URL]
clip latin sex teen
[URL=http://spacetami-attites.ru/asian-bride-mail-nude-order.html]asian bride mail nude order[/URL]
free media player gay porn
[URL=http://redited-extensort.ru/hardcore-fuck-trailer.html]hardcore fuck trailer[/URL]
kid models nude
[URL=http://constrait-goldkett.ru/gay-man-oral-sex-story.html]gay man oral sex story[/URL]
toon porn games
[URL=http://kudrostate-nucleanor.ru/amanda-bynes-nude-photos.html]amanda bynes nude photos[/URL]
dj chuck t sexxxplicit r&b vol 47
[URL=http://dzusova.ru/xxx-gay-treasure-trail.html]xxx gay treasure trail[/URL]
nude pictures of mary-kate and ashley olsen
[URL=http://imporaries-unitivism.ru/ass-fucking-asians.html]ass fucking asians[/URL]
amy fischer nudes
[URL=http://zhuravlevatz.ru/arab-free-hot-sex.html]arab free hot sex[/URL]
young girls virgin pussy galleries
[URL=http://unbroek-themselvet.ru/porn-internet-jobs-in-pennsylvania.html]porn internet jobs in pennsylvania[/URL]
stil dont give a fuck lyrics
[URL=http://remaints-riversey.ru/greek-porn-film.html]greek porn film[/URL]
free nude spy cam downloads
[URL=http://comestonese-separama.ru/first-sex-teen-video.html]first sex teen video[/URL]
asia from pussy cat dolls
[URL=http://huntern-dispruce.ru/sitemap.html]sitemap[/URL]
welivetogether pussy maintenance
[URL=http://groundard-hamilitary.ru/senate-sub-committee-of-lesbian-economic-affairs.html]senate sub-committee of lesbian economic affairs[/URL]
celeb manila nude
[URL=http://pumpedal-backgroups.ru/ass-big-black-fucked-getting-woman.html]ass big black fucked getting woman[/URL]
porn username and passwor
[URL=http://farminish-psycholar.ru/how-to-get-xxx-videos-on-itouch.html]how to get xxx videos on itouch[/URL]
pussy cat dolls video free download

== fucking niggers white woman ==

[URL=http://autosten-derican.ru/sexy-teen-redhead.html]sexy teen redhead[/URL]
secrete amature sex videos
[URL=http://imagicial-sapprovide.ru/free-date-transsexual.html]free date transsexual[/URL]
african women porn
[URL=http://bistorstart.ru/black-woman-lesbian-video.html]black woman lesbian video[/URL]
gay xxx pictures
[URL=http://disched-limination.ru/karyn-parsons-nude-pics.html]karyn parsons nude pics[/URL]
mature bisexual personals
[URL=http://willion-developini.ru/dry-vaginas-porn.html]dry vagina's porn[/URL]
black clip free movie pussy
[URL=http://bradshed-shoreogram.ru/celebrity-amine-porn.html]celebrity amine porn[/URL]
kizlari porn turk
[URL=http://econdard-northodor.ru/teen-having-sex-porn.html]teen having sex porn[/URL]
amiel fucking lovesong
[URL=http://beginnno-echuanic.ru/horny-milfs-in-rhode-island.html]horny milfs in rhode island[/URL]
cartoon disney pornography
[URL=http://birga-ep.ru/pics-of-tawnee-stone-having-sex.html]pics of tawnee stone having sex[/URL]
cheerleader xxx video
[URL=http://budcenter.ru/dirty-fat-pussy.html]dirty fat pussy[/URL]
gals movie porn star
[URL=http://primariang-mussociate.ru/porn-video-streaming-sites.html]porn video streaming sites[/URL]
young tight pussy video
[URL=http://goramatras.ru/video-chat-adult-software.html]video chat adult software[/URL]
regular sex videos
[URL=http://windonin-besient.ru/anal-sex-threads.html]anal sex threads[/URL]
claudia atkins porn star
[URL=http://prepant-servenic.ru/are-iitian-girl-sexy.html]are iitian girl sexy[/URL]
beauty blog nude
[URL=http://arranean-holicist.ru/funny-clips-of-lesbians-stripping-each-other.html]funny clips of lesbians stripping each other[/URL]
russian teen drunk nude
[URL=http://bundard-reforeign.ru/cartoon-download-free-sexy.html]cartoon download free sexy[/URL]
porn puppet play bondage
[URL=http://courseshoe-forcestricted.ru/watch-kid-rock-porn-video.html]watch kid rock porn video[/URL]
dance pole sexy video
[URL=http://holfo-cheminance.ru/horny-lesbian-wife.html]horny lesbian wife[/URL]
download 3gp sex video
[URL=http://inserview-glenwork.ru/smooth-shaven-pussy.html]smooth shaven pussy[/URL]
hardcore sample video
[URL=http://entially-luthere.ru/nude-picks-of-rating-site-girls.html]nude picks of rating site girls[/URL]
figured full porn
[URL=http://harborving-lincount.ru/eleven-years-old-little-hairless-pussy-deflowering.html]eleven years old little hairless pussy deflowering[/URL]
carmella bing nude pic
[URL=http://countary-oligate.ru/like-motherfuck-all-yall.html]like motherfuck all yall[/URL]
ret tube free porn
[URL=http://britable-abourhood.ru/lesbian-clubs-in-miami-florida.html]lesbian clubs in miami florida[/URL]
nude travel guide
[URL=http://ecosc.ru/teeny-little-girl-stars.html]teeny little girl stars[/URL]
nude anime video

== nude pics pregnant ==

[URL=http://zhuravlevatz.ru/ass-gaping-hole-pussy-young.html]ass gaping hole pussy young[/URL]
teen sexually transmitted diseases
[URL=http://liminates-presiege.ru/christy-carlson-ramono-nude.html]christy carlson ramono nude[/URL]
nude colleen haskell
[URL=http://arubaonline.ru/ebony-girls-fucks-white-guys.html]ebony girls fucks white guys[/URL]
fuck french teacher
[URL=http://dor4.ru/helter-fucking-skelter.html]helter fucking skelter[/URL]
green pics nude
[URL=http://birga-ep.ru/nude-pictures-beyonce.html]nude pictures beyonce[/URL]
black free nude woman
[URL=http://darbarawake-separticular.ru/condom-porn-pre-transsexual.html]condom porn pre transsexual[/URL]
reese witherspoon nude video
[URL=http://startise-theistian.ru/pictorial-resource-guide-to-sexual-positions.html]pictorial resource guide to sexual positions[/URL]
free gallery grind lesbian porn trib
[URL=http://militariff-capitalyzing.ru/free-jenna-jameson-lesbian-clips.html]free jenna jameson lesbian clips[/URL]
secure free porn
[URL=http://frequinter-catalian.ru/real-xxx-incest.html]real xxx incest[/URL]
free gay pornsite passwords
[URL=http://hairmarter-reichhead.ru/cross-dressing-masturbation.html]cross dressing masturbation[/URL]
of big black dicks
[URL=http://alucomposite-nsk.ru/good-books-to-read-for-teen-girls.html]good books to read for teen girls[/URL]
anne heche nude picture
[URL=http://clusita-colled.ru/teen-innocent-nude-pic.html]teen innocent nude pic[/URL]
nude old teacher
[URL=http://emergesternel-ravelena.ru/free-picture-of-sexy-black-female-celebrity.html]free picture of sexy black female celebrity[/URL]
gay male penis porn
[URL=http://primariang-mussociate.ru/nude-art-met.html]nude art met[/URL]
fit girls fucked
[URL=http://rareligious-carolinary.ru/sexy-short-shorts-galleries.html]sexy short shorts galleries[/URL]
dergan free lisa nude
[URL=http://emphicago-trange.ru/first-her-lesbian-movie-sex.html]first her lesbian movie sex[/URL]
girl geting fucked hard
[URL=http://ottoes-mirrorise.ru/classic-porn-orgasms.html]classic porn orgasms[/URL]
teen wife fucking
[URL=http://presemble-pudonyms.ru/sitemap.html]sitemap[/URL]
black jack nude strip
[URL=http://presemble-pudonyms.ru/bang-brazil-gang-sex-video.html]bang brazil gang sex video[/URL]
sex videos without regristration
[URL=http://acquel-econdard.ru/jimmy-kimmel-fucking-ben-aflack.html]jimmy kimmel fucking ben aflack[/URL]
school girls fucking
[URL=http://simulting-nassic.ru/final-fantasy-lulu-nude.html]final fantasy lulu nude[/URL]
mistress plump bbw
[URL=http://groundard-hamilitary.ru/virgin-inserting-dildo.html]virgin inserting dildo[/URL]
gauge porn star pic
[URL=http://northeir-acropsy.ru/nude-teachers-videos.html]nude teachers videos[/URL]
how do women masturbate their pussies
[URL=http://disagreek-punister.ru/porn-site-account.html]porn site account[/URL]
hot girl getting fucked up

== vicky leandros nude pics ==

[URL=http://mdteatron.ru/gig-gangel-nude-2257.html]gig gangel nude 2257[/URL]
amateur nude tit
[URL=http://beutylady.ru/playboy-blonde-porn.html]playboy blonde porn[/URL]
nude pics of elisha cuthbert
[URL=http://coversee-endards.ru/emo-girl-hot-porn.html]emo girl hot porn[/URL]
dildo with vibrator
[URL=http://holfo-cheminance.ru/witcher-cards-nude.html]witcher cards nude[/URL]
dildos in mens asses
[URL=http://explosing-lagandhra.ru/nude-scene-angelina-jolie-beowulf.html]nude scene angelina jolie beowulf[/URL]
hour long teen sex videos
[URL=http://photopes-watern.ru/pornmovie-on-line.html]pornmovie on line[/URL]
nude strip poker pics
[URL=http://lastus-largence.ru/anime-gay-sex-picture.html]anime gay sex picture[/URL]
pussy slapping fuck
[URL=http://parinam-centries.ru/girl-partys-then-is-fucked-hard.html]girl partys then is fucked hard[/URL]
free porno pictures of britney spears
[URL=http://farminish-psycholar.ru/new-england-patriots-cheerleaders-nude-photos.html]new england patriots cheerleaders nude photos[/URL]
justene jaro pussy
[URL=http://pullina-numentieth.ru/sweet-krissy-masturbation-video.html]sweet krissy masturbation video[/URL]
xxx tgp movies free
[URL=http://monarian-sprintend.ru/bipasha-basu-nude-pictures.html]bipasha basu nude pictures[/URL]
first nude sex teacher video
[URL=http://art-i-diz.ru/female-mature-sexy.html]female mature sexy[/URL]
audrey nude tatou
[URL=http://russiandistiller.ru/katie-moss-nude-photos.html]katie moss nude photos[/URL]
explosive xxx videos
[URL=http://minkordan-effeminor.ru/porno-links-xp.html]porno links xp[/URL]
free sexy psp backgrounds
[URL=http://londonment-compreside.ru/tight-black-porn-star-gallery.html]tight black porn star gallery[/URL]
abby winters nude amatures
[URL=http://britable-abourhood.ru/dancing-nude-sexy.html]dancing nude sexy[/URL]
sexy carrie underwood pictures
[URL=http://knauf-kreps.ru/foto-woman-sex.html]foto woman sex[/URL]
free nude teen bbs
[URL=http://fraginal-catastimately.ru/bollywood-sex-nude-photo.html]bollywood sex nude photo[/URL]
fuck my jeans brenda
[URL=http://sieterles-overhaps.ru/cheeleaders-getting-fucked.html]cheeleaders getting fucked[/URL]
absolutely free xxx porno pics
[URL=http://mosquestina-econduced.ru/vicksburg-girls-nude.html]vicksburg girls nude[/URL]
howard stern and pornstar houston
[URL=http://liminates-presiege.ru/dita-von-tesse-dildo.html]dita von tesse dildo[/URL]
dee lilly nude
[URL=http://argely-cultipate.ru/free-hot-reading-sex-steamy-story.html]free hot reading sex steamy story[/URL]
fill her pussy with cum
[URL=http://flattempt-massang.ru/teens-fuck-daddy.html]teens fuck daddy[/URL]
wilfs getting fucked
[URL=http://infraside-harbonato.ru/porn-star-nick-manning.html]porn star nick manning[/URL]
dolly parton nude naked

== face fucker info remember ==

[URL=http://sincertain-christoral.ru/free-image-galleries-teen-sex.html]free image galleries teen sex[/URL]
passwords for pinkyxxx com
[URL=http://heative-fuchstood.ru/teen-girl-message-board.html]teen girl message board[/URL]
kate beckinsale nude photos free
[URL=http://liminised-cyclicated.ru/arse-fucking-movies.html]arse fucking movies[/URL]
free xxx cumfacials mature jpg
[URL=http://czechosis-opposities.ru/mature-sexparty-free.html]mature sexparty free[/URL]
double sided dildo video
[URL=http://resouri-extentific.ru/wants-pussy-eaten.html]wants pussy eaten[/URL]
amature nude male models
[URL=http://dysregular-terrule.ru/angeline-jolie-porn.html]angeline jolie porn[/URL]
nude naked sports
[URL=http://estices-populato.ru/true-fuck-stories.html]true fuck stories[/URL]
core hard man naked porn sex xxx
[URL=http://entially-luthere.ru/big-fuck-nurse-tit.html]big fuck nurse tit[/URL]
picture sexy vintage
[URL=http://restablish-sentercome.ru/completely-nude-pictures.html]completely nude pictures[/URL]
penny arcade fucktard
[URL=http://greatments-sellows.ru/pussy-ripped-by-cock.html]pussy ripped by cock[/URL]
anal sex trailer video
[URL=http://ecca-art.ru/celebrity-bald-pussy.html]celebrity bald pussy[/URL]
hardcore tgp voyeur
[URL=http://castical-namesent.ru/gallery-nude-teenie-thong-ass.html]gallery nude teenie thong ass[/URL]
kimora lee simons nude
[URL=http://argely-amadhood.ru/motorsports-milford-holliston.html]motorsports + milford + holliston[/URL]
sex movie pics free downloads
[URL=http://follodore-histols.ru/mardi-gras-new-orleans-nude.html]mardi gras new orleans nude[/URL]
best place for porn europe
[URL=http://s-en.ru/xxxpass-se-index3.html]xxxpass se index3[/URL]
valentine stacy sample porn boobs
[URL=http://wakemons-milinguin.ru/handjob-porn-videos.html]handjob porn videos[/URL]
perry lake abate nude pic gallery
[URL=http://mological-pagandar.ru/index.html]big booty wet pussy[/URL]
clean pornagraphy from my computer for free
[URL=http://nadejdafond.ru/genuine-electrolux-xxx-cord.html]genuine electrolux xxx cord[/URL]
teenage girls free nude ivana
[URL=http://primariang-mussociate.ru/free-dirty-young-girl-porn.html]free dirty young girl porn[/URL]
bound + fucked
[URL=http://judgementallad-southwestware.ru/black-girl-suck-white-dick.html]black girl suck white dick[/URL]
sex squirting teen
[URL=http://alexandel-concernize.ru/heel-leg-sexy-woman.html]heel leg sexy woman[/URL]
photos in an girl nude camps
[URL=http://acquel-econdard.ru/fat-bitches-fucked.html]fat bitches fucked[/URL]
free galleries mature women nude
[URL=http://nization-jarrane.ru/lady-tribe-nude.html]lady tribe nude[/URL]
che hame sexxxxxxxxxxxxxxxxxxx
[URL=http://passembles-spearance.ru/nude-pics-vids-ex-wife.html]nude pics vids ex wife[/URL]
teen male models nude

== fat chick porn clip ==

[URL=http://retress-accommon.ru/big-tits-exposed.html]big tits exposed[/URL]
nude life drawing model for artist
[URL=http://econdary-stalgian.ru/little-nude-pic-taylor.html]little nude pic taylor[/URL]
free indian pussy video
[URL=http://emergesternel-ravelena.ru/lo-mejor-de-porno-gratis.html]lo mejor de porno gratis[/URL]
video sex games
[URL=http://arranean-holicist.ru/dead-little-girl-getting-fucked-in.html]dead little girl getting fucked in[/URL]
free registered sex offender map
[URL=http://news-medic.ru/free-diaper-lesbian.html]free diaper lesbian[/URL]
nude pic of laura san giacomo
[URL=http://fisched-paratisfy.ru/actress-indian-masala-nude.html]actress indian masala nude[/URL]
babe the goose porn
[URL=http://williament-billiams.ru/home-made-forbidden-porn.html]home made forbidden porn[/URL]
medical exam fetish porn
[URL=http://nization-jarrane.ru/cam-free-sex-xxx.html]cam free sex xxx[/URL]
bandera nude vaitiare
[URL=http://concompute-scholak.ru/gay-nude-calenders.html]gay nude calenders[/URL]
double pussy eating
[URL=http://posterpart-princoln.ru/home-movie-amateur-fucking.html]home movie amateur fucking[/URL]
xnxx mature movie
[URL=http://focusines-prerogen.ru/lesbian-ove-myspace-layouts.html]lesbian ove myspace layouts[/URL]
extraits gratos xxx
[URL=http://beutylady.ru/ass-latino-porn.html]ass latino porn[/URL]
nude arabian girls
[URL=http://biz-style.ru/playboy-nude-playmates-fanpage.html]playboy nude playmates fanpage[/URL]
nude pics alyssa milano
[URL=http://parated-yaltire.ru/free-gay-porn-site-password.html]free gay porn site password[/URL]
all porn guys
[URL=http://epidnews.ru/nicole-sheridan-the-new-anal-gangbang-su.html]nicole sheridan the new anal gangbang su[/URL]
tits n pussy
[URL=http://teacheva-adequal.ru/one-lucky-guy-porn.html]one lucky guy porn[/URL]
nude picture rapper trina
[URL=http://zonest-judicing.ru/girl-picture-pre-teen.html]girl picture pre teen[/URL]
nude beach amateur pictures
[URL=http://outrecht-rangela.ru/woman-wearing-sexy-pantie.html]woman wearing sexy pantie[/URL]
hot college women xxx
[URL=http://steilprom.ru/free-porn-windows-media-player.html]free porn windows media player[/URL]
totally spies porn pics
[URL=http://art-i-diz.ru/mandy-moore-xxx.html]mandy moore xxx[/URL]
japanese schoolgirls fuck their teachers
[URL=http://pumpedal-backgroups.ru/free-porno-mature-masterbation.html]free porno mature masterbation[/URL]
daphnie and velma porn
[URL=http://beginnno-echuanic.ru/lesbo-sex-pics.html]lesbo sex pics[/URL]
girls pussy hair
[URL=http://vibraries-ethnicians.ru/lesbian-diaper-slave.html]lesbian diaper slave[/URL]
nude pictures of girls and boys
[URL=http://remony-deutenant.ru/paris-hilton-free-sex-movie.html]paris hilton free sex movie[/URL]
taylor swift pussy

== free hot sexy porn video ==

[URL=http://conqually-pointered.ru/free-new-sex-pic.html]free new sex pic[/URL]
nude photography line-up
[URL=http://imkos.ru/nude-pics-of-privaten-gwen.html]nude pics of privaten gwen[/URL]
mistress plump bbw
[URL=http://collowing-specimate.ru/boy-mature-pic-shocking-woman.html]boy mature pic shocking woman[/URL]
hardcore patrick porn star tera
[URL=http://distaneous-shouldberg.ru/hot-tan-legs-mini-skirt-sexy.html]hot tan legs mini skirt sexy[/URL]
best male masturbation techesniqu
[URL=http://predouble-plantigue.ru/forced-sex-pictures.html]forced sex pictures[/URL]
ls nude magazine
[URL=http://orkness-scaffect.ru/sexy-legs-girls-pictures.html]sexy legs girls pictures[/URL]
egyptian sex picture
[URL=http://portrek-reichment.ru/www-eat-pussy.html]www eat pussy[/URL]
he men nude
[URL=http://liminates-presiege.ru/youngest-nude-porn-ever.html]youngest nude porn ever[/URL]
shawnna pussy poppin
[URL=http://timashevsk-info.ru/hard-porn-torrent.html]hard porn torrent[/URL]
pussy naked women
[URL=http://eukaryotirical-wealthousand.ru/hott-girls-having-sex.html]hott girls having sex[/URL]
porn mp4 clips
[URL=http://contieth-assical.ru/how-to-dress-sexy-black-woman.html]how to dress sexy black woman[/URL]
free streaming mpg porn
[URL=http://rcop.ru/sexy-country-music-singers-breasts-pictures.html]sexy country music singers breasts pictures[/URL]
nude egyptian woman pic
[URL=http://bendlass.ru/pink-girl-fuck.html]pink girl fuck[/URL]
asia d'argento pornostar
[URL=http://unoffic-safeguaran.ru/barley-legal-teen-porn.html]barley legal teen porn[/URL]
anal sex redhed women
[URL=http://constrait-goldkett.ru/ray-jay-sex-video.html]ray jay sex video[/URL]
bw nude male
[URL=http://storiants-constrench.ru/getting-first-blowjob.html]getting first blowjob[/URL]
well fucked pussy
[URL=http://news-medic.ru/2007-boston-lesbian-stalking-case.html]2007 boston lesbian stalking case[/URL]
star wars xxx
[URL=http://faculate-baltimate.ru/beulah-ecw-nude.html]beulah ecw nude[/URL]
milford middle school in
[URL=http://hundricharts-persioning.ru/american-gladiator-gay-porn.html]american gladiator gay porn[/URL]
moms teaching teens how to fuck clips
[URL=http://factoraging-prisinthias.ru/girl-sex-clips.html]girl sex clips[/URL]
reality shower porn
[URL=http://art-i-diz.ru/kitty-carrol-fucked.html]kitty carrol fucked[/URL]
become a pornsta
[URL=http://emergesternel-ravelena.ru/gay-hairy-masculine-porn-video.html]gay hairy masculine porn video[/URL]
what the fuck the game
[URL=http://remony-deutenant.ru/sexy-canadian-girls-naked.html]sexy canadian girls naked[/URL]
couple mature porn
[URL=http://provideologic-licensort.ru/laura-crevalle-nude.html]laura crevalle nude[/URL]
lesbians porn with pussy free sex movies

== tamika porn star ==

[URL=http://sufficially-allegenergy.ru/diorskin-nude-makeup.html]diorskin nude makeup[/URL]
porn penis small
[URL=http://spicion-gregarded.ru/index.html]antonio sabato jr - nude[/URL]
free porn sex forums
[URL=http://estices-populato.ru/black-anal-sex-pictures.html]black anal sex pictures[/URL]
fuck hottest ass bbw gallery huge
[URL=http://biz4yours.ru/fake-hayek-nude-salma.html]fake hayek nude salma[/URL]
beast porn sex site
[URL=http://dominenes-cuisit.ru/skyy-black-porn-star.html]skyy black porn star[/URL]
krystal picture sexy steal
[URL=http://chiatric-chaheen.ru/erica-boyer-porn.html]erica boyer porn[/URL]
free interracial gay sex video
[URL=http://healthough-earlem.ru/cam-home-nude.html]cam home nude[/URL]
priest fucks nun
[URL=http://mcdonative-totallie.ru/sex-stories-with-pics.html]sex stories with pics[/URL]
sabian masturbation video
[URL=http://symptoman-populatio.ru/old-woman-sex-pictures.html]old woman sex pictures[/URL]
pornoforall porkyhost com
[URL=http://contieth-assical.ru/youtube-wheatus-teenage.html]youtube wheatus teenage[/URL]
naughty julie blowjob video stairs
[URL=http://arubaonline.ru/action-in-lady-porn.html]action in lady porn[/URL]
web cam porn gratis
[URL=http://in-hollywood.ru/mature-sex-taiwanese-video.html]mature sex taiwanese video[/URL]
cock spandex trunks she her pussy
[URL=http://easteur-marchbishops.ru/collection-nude-private.html]collection nude private[/URL]
porn star obsession free movie
[URL=http://cyprior-jerseased.ru/fantasy-nude-pic.html]fantasy nude pic[/URL]
fuck i'm irish shirt
[URL=http://ottoes-mirrorise.ru/asian-girls-with-big-tits.html]asian girls with big tits[/URL]
free girls scared and fucking
[URL=http://chargil-pagated.ru/porn-free-bi-sexual.html]porn free bi sexual[/URL]
fucked lady very young
[URL=http://farminish-psycholar.ru/free-interracial-porn-teen.html]free interracial porn teen[/URL]
what the fuck ringtone
[URL=http://forumpsp.ru/amateur-movies-porn.html]amateur movies porn[/URL]
nude beach live cams
[URL=http://thesios-extering.ru/perfect-blonde-with-luscious-pussylips.html]perfect blonde with luscious pussylips[/URL]
pornos de jovencitas
[URL=http://ligative-becautiful.ru/bitch-fuck-porn.html]bitch fuck porn[/URL]
free hot fuck clips
[URL=http://countary-oligate.ru/daisy-dukes-nude.html]daisy dukes nude[/URL]
can flexril fuck you up
[URL=http://canalogue-badenza.ru/tila-tequial-porn.html]tila tequial porn[/URL]
eating pussy movie
[URL=http://afficer-hattemport.ru/brittney-speares-nude.html]brittney speares nude[/URL]
teenage sex clips
[URL=http://knauf-kreps.ru/dildo-mature-old.html]dildo mature old[/URL]
clip fucking mature woman

== cartoon porn flash games ==

[URL=http://conqually-pointered.ru/naked-bodybuilders-nude-muscle-men.html]naked bodybuilders nude muscle men[/URL]
sarasota older pussy
[URL=http://ottoes-mirrorise.ru/gallery-hairy-natural-pussy.html]gallery hairy natural pussy[/URL]
teen porn gallerits
[URL=http://unbroek-themselvet.ru/female-masterbation-to-orgasm-phone-sex.html]female masterbation to orgasm phone sex[/URL]
shrivelled granny porn
[URL=http://estaurani-karpose.ru/2-mature-dildo.html]2 mature dildo[/URL]
free adult group sex
[URL=http://dominenes-cuisit.ru/russian-brides-with-nude-photos.html]russian brides with nude photos[/URL]
drugged fucked raped
[URL=http://tracterime-figurated.ru/big-black-dick-sex.html]big black dick sex[/URL]
sebastian x cartoon porn
[URL=http://secondoles-retreation.ru/teen-fuck-in-shower.html]teen fuck in shower[/URL]
big cock fuck pussy virgin
[URL=http://advancophor-endence.ru/comforter-girl-teen.html]comforter girl teen[/URL]
dildo orgasm videos
[URL=http://tagallow-purporal.ru/pic-hunter-lesbian.html]pic hunter lesbian[/URL]
milfs with big cunts
[URL=http://art-i-diz.ru/free-dragon-ball-z-porn-video.html]free dragon ball z porn video[/URL]
and show your pussy
[URL=http://conqually-pointered.ru/gianna-michaels-xxx.html]gianna michaels xxx[/URL]
big ebony fatties free fucking mature tit
[URL=http://creperum.ru/lesbian-doctors-having-sex.html]lesbian doctors having sex[/URL]
hairy mature fat pussy
[URL=http://flagstantic-civilior.ru/american-teens-girl.html]american teens girl[/URL]
lesbian doubledildo porn
[URL=http://orkness-scaffect.ru/gay-porn-access.html]gay porn access[/URL]
the real cancun nudes
[URL=http://londonment-compreside.ru/gay-porn-modles-wanted.html]gay porn modles wanted[/URL]
long haired men porn
[URL=http://emperaturn-posities.ru/adult-entertainment-free-movie-porn.html]adult entertainment free movie porn[/URL]
older men fucking younger men
[URL=http://biz4yours.ru/boob-licking-movie-pussy.html]boob licking movie pussy[/URL]
nude drew barrymore
[URL=http://quitary-ophereby.ru/larry-leisure-nude-suit.html]larry leisure nude suit[/URL]
nude bank checks
[URL=http://retress-accommon.ru/clip-gay-porn-star.html]clip gay porn star[/URL]
les lavigueurs nude
[URL=http://hairmarter-reichhead.ru/katie-holmes-naked-nude.html]katie holmes naked nude[/URL]
milford pa home
[URL=http://mcdonative-totallie.ru/female-free-masturbating-porn.html]female free masturbating porn[/URL]
brazil miss nude
[URL=http://wondence-borgles.ru/big-dick-daddies-grandads.html]big dick daddies grandads[/URL]
lea pic porn walker
[URL=http://surrough-releanly.ru/black-bwhite-cock-pussy.html]black bwhite cock pussy[/URL]
nude boy studs
[URL=http://mological-pagandar.ru/woman-licking-her-own-pussy.html]woman licking her own pussy[/URL]
free streetblowjobs video

== sex machine free pictures videos ==

[URL=http://cyclinto-strety.ru/bang-cream-gang-hardcore-pie.html]bang cream gang hardcore pie[/URL]
celebrity nude fakes the list
[URL=http://nietzche.ru/beach-babe-porn.html]beach babe porn[/URL]
christi shake nude photos
[URL=http://kurt-ka.ru/white-hoe-fucking-black.html]white hoe fucking black[/URL]
amanda kimmel nude photos
[URL=http://afficer-hattemport.ru/mother-daughter-fuck-aris.html]mother daughter fuck aris[/URL]
francine american dad porn
[URL=http://wondence-borgles.ru/bitch-black-lesbian.html]bitch black lesbian[/URL]
bang free gang porn
[URL=http://clusita-colled.ru/self-please-your-pussy.html]self please your pussy[/URL]
beatiful women in the nude
[URL=http://afficer-hattemport.ru/www-xnxx-com-my.html]www xnxx com my[/URL]
xtube teen pussy
[URL=http://churchment-propologic.ru/of-a-pussy-pump.html]of a pussy pump[/URL]
dita von teese dildo
[URL=http://unlawn-federable.ru/sweet-teen-black-pussy.html]sweet teen black pussy[/URL]
pride hardcore knockouts volume 1
[URL=http://occuration-pronomist.ru/scottish-sex-videos.html]scottish sex videos[/URL]
face north xxx
[URL=http://tensistic-callel.ru/lesbian-real-img.html]lesbian real img[/URL]
nude beaches wa
[URL=http://germanipa-cosmetro.ru/forced-face-fucked-entil-pucke.html]forced face fucked entil pucke[/URL]
anal gratis sex
[URL=http://althousanna-legitimater.ru/nonude-teen-picture.html]nonude teen picture[/URL]
grand blanc nude
[URL=http://liminatio-lillege.ru/pantie-fucking-movie.html]pantie fucking movie[/URL]
my stepdad masturbating
[URL=http://denversity-pontail.ru/adult-movi-clips.html]adult movi clips[/URL]
nude kendra pics
[URL=http://eitheless-octangy.ru/jenna-bush-nudes.html]jenna bush nudes[/URL]
moon bloodgood nude pic
[URL=http://goramatras.ru/shoe-fettish-porn.html]shoe fettish porn[/URL]
sexy videos of katie price
[URL=http://posterpart-princoln.ru/bound-and-gangbanged.html]bound and gangbanged[/URL]
in nude philippine public
[URL=http://denversity-pontail.ru/pornmovie-on-line.html]pornmovie on line[/URL]
leather skirt pussy
[URL=http://speculin-literatin.ru/category-sex-video.html]category sex video[/URL]
fuck lady ass
[URL=http://bendlass.ru/ariel-jasmine-porn-disney.html]ariel jasmine porn disney[/URL]
nude female babes
[URL=http://baudrille-zdened.ru/snow-white-xxx-movie.html]snow white xxx movie[/URL]
free henti sex clips
[URL=http://academan-fragedy.ru/deep-throat-xxx.html]deep throat xxx[/URL]
classic porn movie i like to watch
[URL=http://armined-ankline.ru/pussy-in-leather.html]pussy in leather[/URL]
nude arab actress

== thora birch nude pics ==

[URL=http://retress-accommon.ru/black-pornstars-in-bondage.html]black pornstars in bondage[/URL]
gina wild hardcore dvd sex shop
[URL=http://kudrostate-nucleanor.ru/good-clean-porn.html]good clean porn[/URL]
free nude scifi thumb
[URL=http://noversey-correcome.ru/big-dick-gay-stud.html]big dick gay stud[/URL]
sneak a peek xxx
[URL=http://symmets-workina.ru/twink-sex-free.html]twink sex free[/URL]
female celebritie porn
[URL=http://germarks-propolic.ru/bingham-gallery-nude-traci.html]bingham gallery nude traci[/URL]
free lesbian nude web cams
[URL=http://seconstand-boothbari.ru/inserts-nude-clips.html]inserts nude clips[/URL]
carmen electra fucked getting hard
[URL=http://arranean-holicist.ru/boob-nude-small.html]boob nude small[/URL]
pic gay porn sex
[URL=http://vetingui-potamino.ru/mia-amber-naked-nude-pics.html]mia amber naked nude pics[/URL]
m fuckng ben affleck
[URL=http://imporaries-unitivism.ru/womans-sex-drive-help.html]womans sex drive help[/URL]
leanni lei and max hardcore
[URL=http://wrestonia-areasons.ru/hanessa-vudgens-nude.html]hanessa vudgens nude[/URL]
lyrics pussycat dolls lyrics
[URL=http://homintive-wrotein.ru/backdoor-to-free-porn-clips.html]backdoor to free porn clips[/URL]
sexy free video content
[URL=http://courseshoe-forcestricted.ru/illegal-free-porn.html]illegal free porn[/URL]
free fist fucking movies
[URL=http://arameters-reindungestion.ru/dildo-hentai-huge.html]dildo hentai huge[/URL]
wet and messy chixxx
[URL=http://seconstand-boothbari.ru/bbw-massage-london.html]bbw massage london[/URL]
ebony pussy ejaculation
[URL=http://frequinter-catalian.ru/free-gay-picture-sex-story.html]free gay picture sex story[/URL]
actress indian mallika nude sexy sherawat
[URL=http://usualtic-fullet.ru/nude-black-women-pics.html]nude black women pics[/URL]
ass big fuck latina
[URL=http://resultina-diately.ru/teen-kelly-girls.html]teen kelly girls[/URL]
japanese shit porn
[URL=http://ecca-art.ru/stephie-porn-star.html]stephie porn star[/URL]
free celebs nude clips
[URL=http://cyclinto-strety.ru/history-wax-dildo.html]history wax dildo[/URL]
nude babe log
[URL=http://countary-oligate.ru/foxy-porn-links.html]foxy porn links[/URL]
fuck couple story
[URL=http://groundard-hamilitary.ru/lia-may-nude.html]lia may nude[/URL]
teen firls sex
[URL=http://sylvanishing-machiefdom.ru/courtney-devine-porn.html]courtney devine porn[/URL]
big brunette pussy
[URL=http://beckhausible-madelphing.ru/free-picture-sexy-teen.html]free picture sexy teen[/URL]
iimheretotestify fuck me
[URL=http://theobal-microphic.ru/free-national-sex-offender-regestry.html]free national sex offender regestry[/URL]
bbw escorts ohio

== tips for masturbating for guys ==

[URL=http://fdv-group.ru/black-lady-fucking-white-man.html]black lady fucking white man[/URL]
nude pictures women movies
[URL=http://explosing-lagandhra.ru/asian-lesbos-with-dildo.html]asian lesbos with dildo[/URL]
youporn com lite browse
[URL=http://vibraries-ethnicians.ru/hentai-media-tentacle-fucks-girl.html]hentai media tentacle fucks girl[/URL]
jonny test porn
[URL=http://improming-econsists.ru/teen-pink-videos-ariel.html]teen pink videos ariel[/URL]
pussycat dolls loosen up my button
[URL=http://simulting-nassic.ru/girls-of-porncraft.html]girls of porncraft[/URL]
suckig own dick
[URL=http://infraside-harbonato.ru/chocolate-female-nudes.html]chocolate female nudes[/URL]
male nude bums
[URL=http://mystrahovka.ru/girls-nudest-camp.html]girls nudest camp[/URL]
porn star bella
[URL=http://flagstantic-civilior.ru/hardcore-jennifer-lopez.html]hardcore jennifer lopez[/URL]
big fake white tits
[URL=http://tagallow-purporal.ru/young-girls-nude-video.html]young girls nude video[/URL]
dildo masturbation teen
[URL=http://fraginal-catastimately.ru/xxx-adult-dating-service.html]xxx adult dating service[/URL]
zang ziyi nude
[URL=http://arubaonline.ru/wild-porn-stars.html]wild porn stars[/URL]
no membership celebrity porn
[URL=http://mological-pagandar.ru/handjob-free-porn.html]handjob free porn[/URL]
bookmarxxx dyanna in lauren
[URL=http://faculate-baltimate.ru/index.html]amateur couple picture swinger[/URL]
tour milfslikeitbig com
[URL=http://chiatric-chaheen.ru/black-wet-pussy-girl-fuch.html]black wet pussy girl fuch[/URL]
free nude clips of tara reid
[URL=http://disambula-attributin.ru/bath-girl-taking-teen.html]bath girl taking teen[/URL]
her first porn, com
[URL=http://storiants-constrench.ru/homemade-mature-milf-porn.html]homemade mature milf porn[/URL]
video porno de noelia
[URL=http://prographro-complical.ru/amanda-ireton-nude-pics.html]amanda ireton nude pics[/URL]
13 video sex
[URL=http://imporaries-unitivism.ru/xanaduxxx-fort-wayne.html]xanaduxxx fort wayne[/URL]
asian video xnxx
[URL=http://misation-prevealed.ru/xxx-streaming-oral-video-sample.html]xxx streaming oral video sample[/URL]
free nude websites
[URL=http://courable-wheneyeats.ru/adult-desserts-sexy-sensual.html]adult desserts sexy sensual[/URL]
blue italia xxx
[URL=http://natali-calon.ru/catie-ashcraft-nude.html]catie ashcraft nude[/URL]
owl and the pussycat dvd
[URL=http://principlin-imperating.ru/effects-of-over-masturbation-in-men-zinc.html]effects of over masturbation in men zinc[/URL]
cute guy porn
[URL=http://imkos.ru/free-indiansexy-video.html]free indiansexy video[/URL]
she likes pussy
[URL=http://sacritish-factoric.ru/free-downnile-porn-for-fore.html]free downnile porn for fore[/URL]
wonderwoman nude gallery

== поиск расписаниние рейсов аэропорта кольцово ==

[URL=http://4socialism.info/raspisanie-dvizheniya-samoletov-iz-aeroporta-neryungri.html]расписание движения самолетов из аэропорта нерюнгри[/URL]
аэропорт внуково расписание рейсов домодедовских авиалиний
[URL=http://118899.info/raspisanie-samoletov-tashkent---ierusalim.html]расписание самолетов ташкент - иерусалим[/URL]
справка аэропорт мурманск расписание вылетов
[URL=http://4education.info/aviabilet-koreya.html]авиабилет корея[/URL]
регистрация на рейс трансаэро через интернет
[URL=http://4education.info/zakaz-aviabiletov-cherez-internet-iz-domodedova.html]заказ авиабилетов через интернет из домодедова[/URL]
шереметьево интерактивное табло франфурт на майне
[URL=http://911s.info/stoimost-aviabilety-barselona-kishinev.html]стоимость авиабилеты барселона-кишинев[/URL]
авиабилеты москва адлер чартер
[URL=http://118899.info/aviabilety-iz-gyuodessy-odessa-hurgada.html]авиабилеты из гюодессы одесса-хургада[/URL]
авиабилеты новосибирск иркутск
[URL=http://4education.info/zakaz-prodazha-aviabilety-kiev.html]заказ продажа авиабилеты киев[/URL]
рейс уфа шереметьево
[URL=http://4socialism.info/skidki-na-avia-bilety--akcii.html]скидки на авиа билеты. акции[/URL]
берлин страсбург авиа билеты
[URL=http://118899.info/charternye-reysy-na-ispaniyu.html]чартерные рейсы на испанию[/URL]
туроператоры египта в украине
[URL=http://118899.info/aviakassy-g--krasnodar.html]авиакассы г. краснодар[/URL]
крупнейшие туроператоры россии по итогам 2009
[URL=http://911s.info/serial-zvyozdnyy-kreyser-galaktika-onlayn.html]сериал звёздный крейсер галактика онлайн[/URL]
цены на авиабилеты благовещенск москва
[URL=http://800free.info/bilety-na-samolet-n-novgorod-adler-cena.html]билеты на самолет н новгород адлер цена[/URL]
авиабилеты гродно
[URL=http://800free.info/kupit-aviabilet-a-toronto.html]купить авиабилет а торонто[/URL]
финляндия коттедж туроператор
[URL=http://4socialism.info/cena-aviabiletov-sankt-peterburg-murmansk.html]цена авиабилетов санкт петербург мурманск[/URL]
цены на билеты в авиакассах санкт-петербурга
[URL=http://4education.info/zakaz-aviabiletov-cherez-internet-iz-domodedova.html]заказ авиабилетов через интернет из домодедова[/URL]
отзывы о тур. операторе capital
[URL=http://800free.info/aviabilety-na-charter-v-stambul.html]авиабилеты на чартер в стамбул[/URL]
узбекистанская авиакомпания хаво - юлари
[URL=http://4education.info/raspisanie-reysov-na-yakutsk-s-sevostopal.html]расписание рейсов на якутск с севостопаль[/URL]
австрия германия туроператор
[URL=http://800free.info/goryashie-putevki-aviabilety-kuba.html]горящие путевки авиабилеты куба[/URL]
расписание рейсов шереметьево в дубай
[URL=http://4education.info/raspisanie-marshrutnyh-taksi-m-domodedovo-konstantinovo.html]расписание маршрутных такси м домодедово константиново[/URL]
расписание самолетов астана шымкент
[URL=http://4socialism.info/po-bronirovaniyu-aviabiletov-v.html]по бронированию авиабилетов в[/URL]
стоимость авиабилета алматы-франкфурт
[URL=http://4education.info/deshevye-aviabilety-moskva-habarovsk.html]дешевые авиабилеты москва хабаровск[/URL]
авиакомпания аерофлот-норд
[URL=http://800free.info/ceny-na-avia-bilety-goroda-ufy.html]цены на авиа билеты города уфы[/URL]
билеты на самолет минводы-актау
[URL=http://118899.info/gde-obuchayut-na-aviakassirov-v-novosibirske.html]где обучают на авиакассиров в новосибирске[/URL]
расписание авиа рейсов минеральные воды
[URL=http://911s.info/dalavia-zakaz-biletov.html]дальавиа заказ билетов[/URL]
билеты + на самолет одесса киев
[URL=http://118899.info/raspisanie-samoletov-tashkent---ierusalim.html]расписание самолетов ташкент - иерусалим[/URL]
отзывы о туроператоре компания восточный экспресс

== рассписание авиарейса домодедово ==

[URL=http://118899.info/aviabilety-iz-gyuodessy-odessa-hurgada.html]авиабилеты из гюодессы одесса-хургада[/URL]
офис москва испанские авиакомпании
[URL=http://4socialism.info/ceny-na-aviabilety-moskva-nukus.html]цены на авиабилеты москва-нукус[/URL]
авиакомпания в севастополе аэропорт бельбек
[URL=http://4education.info/raspisanie-nalichie-aviabiletov.html]расписание наличие авиабилетов[/URL]
авиа билеты туапсе
[URL=http://911s.info/chelyabinsk-erevan-rasprodazha-avia-biletov.html]челябинск ереван распродажа авиа билетов[/URL]
авиакомпания консей пасифик
[URL=http://4education.info/deshevye-aviabilety-moskva-habarovsk.html]дешевые авиабилеты москва хабаровск[/URL]
туроператор юрта сеть роза ветров
[URL=http://800free.info/nizhnevartovsk-zakaz-aviabiletov.html]нижневартовск заказ авиабилетов[/URL]
авиабилеты москва эйлат
[URL=http://4education.info/online-tablo-vyletov-iz-domodedovo.html]online табло вылетов из домодедово[/URL]
цена авиабилеты москва-оренбург-худжанд
[URL=http://911s.info/aviakompaniya-yuzhnoy-korei-cena-bileta-moskva-bankok-moskva.html]авиакомпания южной кореи цена билета москва банкок москва[/URL]
авиабилеты волгоград-чимкент
[URL=http://118899.info/samara---vladivostok-aviabilety.html]самара - владивосток авиабилеты[/URL]
домодедово расписание прибытия
[URL=http://800free.info/aviabilet-skidki.html]авиабилет скидки[/URL]
трансаэро туры туроператор
[URL=http://800free.info/avia-bilety-kaliningrad-yuteyr.html]авиа билеты калининград ютэйр[/URL]
расписание авиасамолетов на киев
[URL=http://118899.info/kalinigrad-elizovo-petropalovsk-kamchatskiy-aviabilety-akcii.html]калиниград-елизово петропаловск камчатский авиабилеты акции[/URL]
стоимость авиабилетов мюнхен
[URL=http://911s.info/raspisanie-samolyotov-moskva-sochi-vnukovo.html]расписание самолётов москва-сочи внуково[/URL]
авиабилеты цены владивосток сеул владивосток
[URL=http://4socialism.info/pribytie-reysa-transaero-tel-aviv---moskva-25-oktyabrya-2008-goda.html]прибытие рейса трансаэро тель-авив - москва 25 октября 2008 года[/URL]
цена авиабилетов краснодар-махачкала
[URL=http://4education.info/aviabilety-ceny-pulkovo.html]авиабилеты цены пулково[/URL]
аэроэкспресс внуково-расписание
[URL=http://4socialism.info/tablo-prileta-vyleta-aeroporta-g--moskvy.html]табло прилета-вылета аэропорта г. москвы[/URL]
расписание движения самолетов г магнитогорск
[URL=http://118899.info/reysy-iz-aeroporta-tolmachevo-v-aeroport-frankfurta-na-mayne.html]рейсы из аэропорта толмачево в аэропорт франкфурта на майне[/URL]
авиарейсы пулково санкт-петербург шарм-эль-шейх
[URL=http://4socialism.info/koreyskie-serialy-onlayn-el-arna.html]корейские сериалы онлайн ел арна[/URL]
москва софия авиаперелет
[URL=http://118899.info/alitalia-mayami-italiya-kair-aviabilet.html]alitalia майами-италия-каир авиабилет[/URL]
туроператор пакс трэвел
[URL=http://4education.info/kupit-bilety-avia-zhulebino.html]купить билеты авиа жулебино[/URL]
рсаписание рейсов из перми до москвы шереметьево
[URL=http://4socialism.info/bilety-adler-aeroflot.html]билеты адлер аэрофлот[/URL]
тур оператор по доминиканской республике
[URL=http://4education.info/stoimost-avia-bileta-volgograd.html]стоимость авиа билета волгоград[/URL]
санкт петербург заказ авиа билетов
[URL=http://911s.info/samolet-yuzhno-sahalinsk-raspisanie.html]самолет южно сахалинск расписание[/URL]
авиабилет москва рио-де-женеиро
[URL=http://800free.info/raspisanie-aviareysov-kras-eyr-krasnoyarsk-baku.html]расписание авиарейсов крас эйр красноярск-баку[/URL]
когда подешевеют авиа билеты владивосток москва
[URL=http://800free.info/usloviya-vozvrata-aviabiletov-aeroflot.html]условия возврата авиабилетов аэрофлот[/URL]
септима туроператор из калининграда

User:Ilpres1971

2012-02-21T03:47:41Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxonlinepill.com, blanking

Doc:latest/relnotes

2012-02-21T03:47:40Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''Preface'''==

Welcome to ''OpenClovis Release Notes''. This document provides information about the details of the platforms on which OpenClovis SAFplus Availability/Scalability Platform (the SAFplus Platform for short) and Integrated Development Environment (IDE) have been tested and validated for SDK Release 6.0. It contains the additional features and enhancements of the product since the previous release. It also summarizes the known issues and limitations of the product and provides workaround wherever applicable.

===Key Topics===

''OpenClovis Release Notes'' covers the following topics in details:
*Tested Platforms
*What Is New
*Migration To Latest Version
*Known Issues
*Environment Related Observation
*Documentation Issues

===Audience===

''OpenClovis Release Notes'' addresses system integrators, designers, and system architects. To use SAFplus Platform, you must be aware of the fundamentals of operation, management, and configuration of telecom and networking domains. You must also be familiar with C programming, UML notations, and have basic knowledge of Linux.

===Documentation Conventions===

This guide uses different fonts and symbols to differentiate between document elements and types of information. These conventions are summarized in the following table.

{| border="0" cellpadding="3" align="center" width="680"
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Notation
!style="color:#66b154; background:#09477c"| Description
|- style="color:#ffffff; background:#549cc6"
|style="color:black" |<code><pre>Code</pre></code>
|
This font denotes the C code provided in various examples.
|- style="color:#ffffff; background:#549cc6"
|Cross reference
|
This font denotes a hyperlink. You can click on the hyperlink text to access the reference location, which can be either a section within the User Guide or a URL link. A cross reference refers to a section name and accesses the first page of that section.
|- style="color:#ffffff; background:#549cc6"
|
'''Bold Text'''
|
Menu items and button names.
|- style="color:#ffffff; background:#549cc6"
|
'''''Italic Text'''''
|
Variables for which you enter values.
|}

 [[File:OpenClovis_Note.png]]This indicates the presence of notes or annotations, related to the context of the document.
 [[File:OpenClovis_Caution.png]]This indicates that certain precautionary measures must be taken before performing a particular task.
 [[File:OpenClovis_Info.png]]This indicates that additional information is provided to you.

===Related Documents===

For additional information about OpenClovis products, refer to the following guides:
* '''SAFplus Platform SA Forum Compliance''' describes the level of compliance of OpenClovis SAFplus Platform and its Application Programming Interface (API) with the relevant Service Availability Forum Specifications.
* '''SAFplus Platform Installation Guide''' provides the system requirements, installation procedure for OpenClovis SAFplus Platform, IDE, and the Evaluation System.
* '''SAFplus Platform Sample Application Tutorial''' explains the steps to create and build a sample model using OpenClovis IDE and OpenClovis SAFplus Platform. It also provides troubleshooting information for this process. This provides the logical first step in understanding the SAFplus Platform offering.
* '''SAFplus Platform Evaluation System User Guide''' provides all the required information to configure and run the sample models packaged within the Evaluation System. This document also provides good understanding of OpenClovis SAFplus Platform's functionality. This is the natural follow on to the ''OpenClovis Sample Application Tutorial'' as it builds on the example created in that document.
* '''SAFplus Platform SDK User Guide''' provides information about SAFplus Availability/Scalability Platform architecture, various SAFplus Platform components, and their interactions. This guide helps you to configure the OpenClovis SAFplus Platform components, compile, and execute the SAFplus Platform code to build your custom application.
* '''SAFplus Platform IDE User Guide''' describes the usage of Integrated Development Environment (IDE), a graphical development environment that complements the SAFplus Platform. This guide helps you to understand how to use the various features of the IDE to build the application.
* '''SAFplus Platform Log Tool User Guide''' provides information about the usage of OpenClovis Log Tool. OpenClovis Log Tool is an interactive utility that allows you to view binary log files in a readable format and hence monitor system errors, warnings, and other log information. Log Tool allows you to format the <code>.log</code> files and filter them to view the required entries.
* '''SAFplus Platform API Reference Guide''' is provided for each component. It describes the Application Programming Interface (API), Service Model, and Management Information Model of the various OpenClovis Application Service Platform (SAFplus Platform) services. It helps the developer to understand the capabilities of the SAFplus Platform services and the APIs provided by these services.
* '''SAFplus Platform Console Reference Guide''' provides details about managing applications built on SAFplus Platform using the SAFplus Platform runtime debug console commands. SAFplus Platform Console commands can be used to manage, monitor, and test your application.

===OpenClovis Online Technical Support===

OpenClovis customers and partners can register on our Web site and receive personalized services and information. If you need any support or assistance while working on OpenClovis products, you can access the following: URL: http://www.openclovis.com. Send your queries to: support@openclovis.com. Open source community support is available at: http://www.openclovis.org/forum.

===Documentation Feedback===

We are interested in hearing from our customers on the documentation provided with the product. Let us know your comments and suggestions on improving the documentation at OpenClovis Inc. Send your comments to: support@openclovis.com. Or even better, edit (or comment in) the page on our documentation wiki located at [http://help.openclovis.com http://help.openclovis.com].

=='''Tested Platforms'''==

This chapter provides the details of the platforms on which OpenClovis SAFplus Platform have been tested and validated.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Tested Platform Configurations'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="150"| Platform
!style="color:#66b154; background:#09477c"| Configuration
|- style="color:#ffffff; background:#549cc6"
|
Hardware
|
* ATCA 5U Chassis - Schroff, ASIS
* ATCA 12U Chassis - Schroff, Sanmina, HP, Sun Netra, Radisys, Huawei Tecal Server
* Pigeon Point Systems ShMM300 and ShMM500 based Shelf Controllers
* Radisys Promentum 60x0 and its 2100 Switch/Shelf Controller blades
* CPU Blades:
** Intel Xeon based server cards
** Intel Pentium and Xeon based desktops and rack mount servers (RMS)
** Intel Itanium based RMS
** AMD Opteron based ATCA cards
** AMD Opteron and Athlon based desktops
** PowerPC based AMCs
** PowerPC based desktops
** Huawei Tecal BH23
** Sun 3020 and 3090
|- style="color:#ffffff; background:#549cc6"
|
Software
|
* Wind River PNE-LE 1.2 (2.6.10 kernel) on CPU blades
* Wind River PNE-LE 1.3 (2.6.14 kernel) on CPU blades
* Wind River PNE-LE 1.4 (2.6.14 kernel) on CPU blades
* Wind River PNE-LE 2.0 (2.6.21 kernel) on CPU blades
* MontaVista Linux Carrier Grade Edition 5.0 (2.6.21 kernel)on CPU Blades
* QNX Neutrino RTOS 6.3.2
* Pigeon Point Systems Shelf Manager version 2.2.1 on ShMM300, ShMM500
* SCM software version 1.7 on ATCA 2100 Shelf Manager
* OpenHPI 2.8.1 and 2.10.2
* Radisys HPI Client Library (HCL) version 1.1
|}

For more details on the hardware and software requirements and the steps to install OpenClovis SAFplus Platform and IDE, refer to ''OpenClovis Installation Guide''.

=='''What Is New'''==

This chapter outlines the new features and enhancements provided by OpenClovis SAFplus Platform and IDE for Release 6.0.

===New In Release 6.0===

'''SAF Message Service'''
* Optimization: The SAF message service now operates using a peer-to-peer instead of client-server model, resulting in a 400% speedup and reduced network utilization.
* Additional features: Persistent message queues are always stored off-node and will not lose messages during application or node failures. The SAF standard allows node failures to lose messages in persistent queues.

'''Availability Management Framework'''
* 1+N system controller redundancy: More then 2 system controllers are now supported.
* Custom redundancy model: Our SAF-extension "Custom" redundancy model allows the application to chose Active/Standby pairing.

'''Platform Support Package'''
* HPI event filter plugin: A facility was created to intercept, analyze and modify or squelch HPI events before they are handled by the SAFplus Platform. Since it is implemented as a plug-in to our chassis manager, this feature does not affect the latency of our fast-path event handling.
* OpenHPI 3.0 is now the default HPI package
* The HPI dynamic simulator is fully supported, with OpenClovis extensions that generate HPI events if a threshold is changed so that the simulated sensor value falls outside of the nominal range.

'''Messaging Layer'''
* The messaging subsystem used by SAFplus Platform has been converted to a plug-in, allowing the user to implement different transport mechanisms.
* UDP and TIPC plugins are now supported with the default set to TIPC as before*.

'''Leader Election'''
* Cluster leader election is now based on results from the messaging layer (i.e. from TIPC) rather then running an independent algorithm.

'''*''' Note: This feature is not yet supported by the IDE, but can be enabled by changing configuration files.

===New In Release 5.0===

====General Features====

* '''Support for Wind River PNELE 2.0''': OpenClovis SDK can seamlessly build SAFplus Platform and binaries for Wind River Platform for Network Equipment Linux Edition 2.0 on all supported SDK platforms, either using the build tool-chain of OpenClovis or of the development environment of Wind River.

====High Availability (HA)====

*'''ISSU - In Service Software Upgrade'''
Supports middleware upgrade in a rolling (in-service) or single-step mode.

'''Single-Step'''
For deployment of non-backwards compatible software, or rapid deployment of software. This method stops the relevant services on all nodes (causing an outage) and then upgrades that software and restarts. Note that services are stopped at various granularity levels depending on what is being upgraded. In other words, application A can be taken out-of-service and upgraded across the cluster without affecting application B running on the same nodes.

'''Inservice Rolling'''
This is the most commonly known telecom quality upgrade method. For deployment of backwards-compatible software across the cluster, this method stops service in one "upgrade unit" at a time, upgrades the software and restarts before stopping the next "upgrade unit". This process continues iteratively until the entire cluster is upgraded. Since the available redundant capacity takes over for the unit being upgraded service will be unaffected.

====Infrastructure and Communications====

====Group Membership Service (GMS) over TIPC====

By default GMS/openais is now compiled to run over TIPC.

====SAF Message Service====

SAF messaging data types and APIs supported by OpenClovis

*'''classes/types:'''

*SaMsgMessageT
*SaMsgHandleT
*SaMsgQueueStatusT
*SaMsgQueueHandleT
*SaMsgSenderIdT
*SaMsgQueueCreationAttributesT
*SaMsgQueueOpenFlagsT
*SaMsgQueueGroupPolicyT
*SaMsgQueueGroupNotificationBufferT
*SaMsgQueueGroupNotificationT
*SaMsgQueueUsageT
*SaMsgCallbacksT
*SaMsgMessageReceivedCallbackT

*'''APIs:'''

*saMsgMessageSend
*saMsgMessageSendAsync
*saMsgQueueOpen
*saMsgQueueClose
*saMsgQueueStatusGet
*saMsgMessageGet
*saMsgMessageDataFree
*saMsgQueueGroupCreate
*saMsgQueueGroupInsert
*saMsgQueueGroupTrack
*saMsgQueueGroupNotificationFree
*saMsgInitialize
*saMsgFinalize
*saMsgDispatch

====SAF Component cleanup script support====

5.0 introduces support to configure cleanup commands for SA-AWARE components using the Openclovis IDE. The cleanup command is invoked by AMF on component cleanup or abrupt terminations.

===System Management===

*Support of net-snmp 5.4.2.
*SNMP Traps in 64 Bit architectures.

===Platform Management===

OpenClovis SAFplus Platform provides pre-integrated support for commonly used ATCA platforms. All service affecting events reported by the shelf manager via HPI are intercepted and service on affected hardware is migrated to standby equipment, ensuring continuity of service.

This support is provided with the '''Platform Support Package (PSP)''' for Piegon Point Shelf manager 500ShMM via openHPI.

PSP is available as a separate product, please contact OpenClovis Sales for further information.

===Features of OpenClovis IDE===

* '''Running SAFplus Platform without manageability components''': IDE is having the support for enable/disable SAFplus Platform components. For more information refer to ''OpenClovis IDE User Guide''.
* '''AMF Clean-up script''': IDE is having support to specify the cleanup command in SAF Component. For more information refer to ''OpenClovis IDE User Guide''.
* '''Versioning the Configuration Files''': IDE is having support for versioning the configuration files.
* '''SAF Messaging''': IDE is having support to enable the SAF messaging. For more information refer to ''OpenClovis IDE User Guide''.

===SAFplus Platform Run-Time Director===

A new product, the SAFplus Platform Run-Time Director(ARD), provides cluster management of the SAFplus Platform via a web interface. This new product is available separately, please contact OpenClovis for demonstration and evaluation. The ARD has the following features:

* Software Distribution: Allows individual applications to be packaged in a "bundle" and be deployed to any set of nodes in the cluster.
* Inservice Software Upgrade: Supports application upgrade in a rolling (in-service) or single-step mode.
* WYSIWYG: Provides intuitive cluster management via an HTTP (web) interface.
* AJAX: Displays all SAF AMF entities and their current status -- uses asynchronous Javascript requests to dynamically update browser when changes occur.
* Dynamic AMF: Allows modification of AMF entity state and supports creation/deletion of AMF entities.
* High Availability: The ARD runs in unprotected or 2N redundancy mode.
* Python AMF API: Provides an easy-to-use CLI/programmatic API for cluster management
* Easy installation: The ARD can install itself into a running SAFplus Platform model, and therefore requires no changes to your existing model.
* Extensible: The ARD is built on top of TurboGears, a popular open source web mega-framework. Thus it provides a basis and example for your custom SaaS or EMS project.
* Integration of Platform Support Package (PSP), provides chassis configuration through OpenHPI.

===OpenClovis Documentation===

* OpenClovis Documentation is provided in two formats now, PDF and HTML. They both contain the same information.
* A new ''OpenClovis SA Forum Compliance'' document has been added
* As a courtesy, all relevant SA Forum specifications are supplied as part of our OpenClovis documentation package (only in PDF format).
* A new ''OpenClovis Sample Application Tutorial'' has been added, replacing the former Modeling Tutorial. The new document provides explanation for the various steps involved in creating and running a new application.
* The ''OpenClovis SDK User Guide'' has been extended to cover many additional topics, including:
** Communication infrastructure
** Hardware platform support
** How to debug SAFplus Platform based applications
** Build and deployment
* The ''OpenClovis API Reference Guide'' has been significantly revised:
** Numerous coding examples
** New reference pages for API error codes for easy lookup
** HTML version of API Refernce Guide is heavily cross-referenced, allowing easy navigation between the various programming construcs
* New, complete ''OpenClovis SAFplus Platform Console Reference Guide'' as a separate document

[[File:OpenClovis_Note.png]]From this release, the ''Debug CLI'' has been renamed to ''SAFplus Platform Console''.

=='''Migration To Latest Version'''==

Migration of a project or model from an earlier version of the OpenClovis IDE to the most recent version is performed automatically when the model it opened for the first time in the newer vesion. The IDE auto-detects the project's version and changes the internal files so that the information is in valid format and can be read by the current version. It also provides an option to create a backup of the project while performing the migration. For more information, refer to ''OpenClovis IDE User Guide'', Section ''Migrating Project''. IDE supports migration from R2.3 and above.

Any issues regarding migration from a previous version of the IDE are documented below.

===Change in Log File Locations===

As of release 3.0 all SAFplus Platform runtime log files are created in the <code>var/log</code> subdirectory of the SAFplus Platform install directory. It is recommended that you update existing models to also use this directory. To update an existing model edit the clLog.xml file in the model's src/config directory. Change all references of '''.:log''' in the <code><fileLocation></code> elements

<fileLocation>.:log</fileLocation>

to '''.:var/log'''

<fileLocation>.:var/log</fileLocation>

Once the model is rebuilt and deployed these new settings will take effect.

===gmsConfig.xml file===

Models of R2.3 may not contain the gmsConfig.xml file if GMS configuration is not done. If you migrate this project you will get error message saying that Migration was unable to create this file. But this is not going to affect further use of model. Model will be OK and user can make changes to it from IDE, generate source, build it, etc without any problem.

Although this error is not going to affect the functionality of the model, there is a work around for this. Before migrating your model, just open up the model in your old IDE setup. Launch "SAFplus Platform Component Configuration" dialog from the Clovis menu. Press OK. Now just migrate the model with new IDE setup, you will not get this error. Bug has been raised for this and it will be fixed in next release.

=='''Known Issues'''==

This chapter describes the known issues in the current release and provides the associated workarounds. These issues arise due to deviation from the normal functioning of the system or as a result of an unexpected behavior of a component or a service.

===Known Issues of OpenClovis SAFplus Platform===

Following are the known issues for OpenClovis SAFplus Platform:

*'''Infrastructure and Communications'''
** '''TIPC address:''' TIPC with 1.5.12 versions was found to give problems (link unstable) when you have 2 different TIPC netids configured for the same TIPC address. This issue is not seen with the 1.7.x TIPC releases, but in general we recommend you to keep the TIPC addresses unique and not collide with the same addresses on nodes configured with different TIPC netids. One of the symptoms of this is that the TIPC link between 2 machine starts going UP and DOWN continuously when there is another machine in the network, whose TIPC address is conflicting with address of one of those 2 machines. The behavior can be observed through continuous execution of command "tipc-config -l" or through "dmesg".
** In general, TIPC 1.5.XX has been found to be unstable, especially under high multicast load, and should not be used in production environments.

** '''Bug ID #7269''' A cluster having a mixture of 32bit little endian, 32bit big endian and 64 bit little endian machines/nodes may find that the GMS service in inadvertently terminates.
*** '''Workaround''' - None
** '''aspinfo known issues:''' (1) On some systems, especially systems with Python version 2.3, aspinfo can be slow to respond. (2) Some corner cases may not be properly handled and aspinfo may prematurely exit, dumping its Python stack.

* '''System Management'''
** '''Bug ID #7313''' If an Alarm Server is restarted after it published an alarm, it won't allow to clear/publish that alarm again.
*** '''Workaround''' - Currently there is no workaround.

* '''SAF Compliance'''
** '''Deviation from SAF in Event Service:''' Event Service does not yet support Event Retention as specified in SAF specification. The retention time specified in the clEventPublish() API would have no effect.
** '''Bug in SAF specificaion B11:''' The clEventDataGet() API of Event Service is in compliance with the SAF specification B11. This allows the user to either allocate memory for the event payload or obtain it from the API by passing a pointer. The latter is not possible with this API as the argument needs to be a pointer to a pointer which is not the case. As per the new specification and the recommended way the user is always required to allocate and free the memory.

===Known Issues of OpenClovis IDE===

<ul>
<li>'''Bug ID # 6543: X Error in Ubuntu Installation.''' Starting the IDE in '''Ubuntu''' installation may result some X errors in the console. This is not an IDE issue, this will not affect any of the IDE functionalities.
<ul>
<li>'''Workaround''' - See the ''Limitations'' section of the ''OpenClovis IDE User Guide''.
</ul>
<li>'''SNMP MIB Enumerated Integer Construct Limitations''': During SNMP code generation all enumerated integer labels are converted to <code>#define</code> statements. The constant names used in these statements are the enumerated integer labels converted to upper case. Because of this the all labels used within an enumerated integer construct must be unique regardless of case.

<li>'''SNMP MIB V1 TRAP-TYPE Construct Not Supported''': Due to an issue in the Net-SNMP mib2c compiler code generation for MIBs using the V1 TRAP-TYPE construct does not work properly.
<ul>
<li>'''Workaround''' - To generate trap code from an SNMP MIB use the SNMP V2 NOTIFICATION-TYPE construct.
</ul>
</ul>

===Known Issues of Install Package===

* '''Bug ID # 6749: Potential conflict with net-snmp package on local system''': In certain rare instances, building OpenHPI from the included third-party packages during SDK installation fails owing to a conflict with an already-installed version of NetSNMP on the system. In these instances, it is recommended that NetSNMP be removed from the local system before installing OpenClovis SDK, and that it be reinstalled after completing the SDK installation.

* '''Installation on Red Hat Enterprise 4''': On a Red Hat Enterprise Linux 4 system, the 'Development Tools' subset of packages must be installed to cover the requirements for installing OpenClovis SDK. In general, an installation with the default package set contains all requirements for installation.

* '''Installation on Fedora Core 6''': On a Fedora Core 6 system, installation of OpenClovis SAFplus Platform automatically builds and installs the TIPC opensource package. To build TIPC, the kernel headers must be present and so these are automatically installed (by our ./preinstall-fedora-core.sh script) using the "yum install kernel-devel" command. On rare configurations, this command does not work correctly. It is supposed to install headers so that the symbolic link located at "/lib/modules/`uname -r`/build" points to a valid directory of Linux header files. However, on some systems this symbolic link points to "/usr/src/kernels/2.6.22.14-72.fc6-i586" but the headers are actually installed in "/usr/src/kernels/2.6.22.14-72.fc6-i686" (note 'i586' vs 'i686'). To resolve this problem, change the symbolic link to point to the correct directory name, and then restart the OpenClovis SAFplus Platform installation.

* '''Configuring TIPC and assigning the SAFplus Platform node address''' to an OpenClovis SAFplus Platform is done by SAFplus Platform start up script. But if manual configuration of TIPC is allowed. Misconfiguration (such as assigning 2 nodes the same TIPC address) will result in an unstable system. When this happens the whole system (all the SAFplus Platform nodes including the ones which are already up and running properly) have to be brought down, the TIPC kernel driver unloaded (to remove its configuration) and the system restarted.

* '''Installation of SQLite using Preinstall script''': The Preinstall script installs SQLite by default as database engine. It locates SQLite - if it is already installed - without verifying version number. If its version is older than 3.3.13, then SAFplus Platform will fail to start.
** '''Workaround''' - Use SQLite 3.3.13 or newer. The source code can be downloaded from http://www.sqlite.org/download.html. The user can install the latest version of SQLite if its not present in the repository.

* '''Installation on Solaris 10/SPARC (beta)''': Installation of OpenClovis SAFplus Platform requires the following third party packages installed via either installation media or using pkgadd with packages obtained from http://www.sunfreeware.com/. Missing third-party packages may cause unpredictable behavior during installation and SDK use.
** db-4.2.52
** fileutils
** flex
** gcc-3.4.2
** gdbm-1.8.3
** glib-2.14.1
** gmake
** gtar
** libintl
** libiconv
** ncurses
** openssl
** pkgconfig
** python-2.5.1
** readline
** snprintf
** tipc-solaris-1.7.5 or SUNWtipc
** SUNWbtool
** SUNWsprot
** SUNWhea
** wget

=='''Environment Related Observation'''==

* '''Bug ID #7549''' When SAFplus Platform is running in non simulation mode, if SAFplus Platform is started from one sandbox, then it can be stopped/zapped from another sandbox.

===Enabled Firewall Can Cause SAFplus Platform to Shutdown===
The enablement of a firewall on a system running a deployed SAFplus Platform image can cause the software to shutdown. An indication that you may be running into this problem is if you see an entry similar to the following in your log file (in the log file it is one line):
<code><pre>
Wed Sep 26 15:06:54 2007 (SCNodeI0.10499 : GMS.---.---.00036 : ERROR)
[clGmsEngine.c:448] No nodes in the cluster view to run leader
electionLeader Election Aborted
</pre></code>
To resolve this problem disable all filtering in the Netfilter framework by issuing the following command.
<code><pre>
iptables -F
</pre></code>

===Reusing A Project Area With New Version of OpenClovis SDK===
Every Project Area is associated with an installation of OpenClovis SDK at a given location. If one elects to reinstall the SDK at a different location or install a newer version at a different location, the project area will stay associated with the original SDK location. This allows one to work with multiple versions of the SDK simultaneously.
In order to use an existing project area with a different or moved installation of OpenClovis SDK, remove the <code>.config</code> file from your project area directory and re-run <code>configure</code> as you normally would to work with a model.

===Running Multiple SAFplus Platform Clusters in the same Subnet===
If you are running multiple SAFplus Platform clusters within the same subnet, please ensure that the <code>TIPC network ID</code> selected for each cluster is unique.

=='''Documentation Issues'''==

This chapter describes the known issues with the OpenClovis Documentation shipped along with the product.

* Formatting issues
** Following cross-references pointing to a heading, the PDF viewer will jump to the end of the previous page if the heading is on the top of a page.
** Firefox web browsers sometimes do not correctly jump to intra-page anchors when the user clicks on a reference. This is a known issue with Firefox. The workaround is to click on Back button and then on the reference again. The browser jumps to the correct position for the 2nd time.

Doc:latest/sdkguide/manageability

2012-02-21T03:47:39Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxonlinepill.com

=='''System Management'''==

OpenClovis SAFplus Platform provides a comprehensive platform and system management and component manageablity. It delivers a high degree of redundancy, delivering access to key services through highly-resilient traffic handling and system recovery mechanisms. The SAFplus Platform manageability infrastructure provides the capability for managing the resources in the system, reporting problems happening on those resource and provides infrastructure which can take customized action based on these problems.

Manageability comprises the following components:
* [[#Clovis Object Repository (COR)|Clovis Object Repository (COR)]]
* [[#Alarm Manager (AM)|Alarm Manager (AM)]]
* [[#Fault Manager (FM)|Fault Manager (FM)]]
* [[#Transaction Manager (TM) | Transaction Manager (TM)]]
* [[#Provisioning Library|Provisioning Library]]
* [[#Mediation Library|Mediation Library]]
* [[#Simple Network Management Protocol (SNMP)|Simple Network Management Protocol (SNMP)]]

[[File:SDK_SystemMngmtinSAFplus Platform.png|frame|center| '''System Management in SAFplus''' ]]

This chapter provides information about the various components of mangeability, concepts of managed objects, and using subagents for custom MIBs.

'''Key Topics:'''
* [[#Components of Manageability | Components of Manageability]]
* [[#Working with Clovis Object Repository (COR) | Working with Clovis Object Repository (COR)]]
* [[#Attributes of Managed Objects| Attributes of Managed Objects]]
* [[#Developing SNMP Subagent for Custom MIBs | Developing SNMP Subagent for Custom MIBs]]
* [[#SAFplus Platform Manageability End to End | SAFplus Platform Manageability End to End ]]

===OpenClovis Information Model===

OpenClovis Information Model is a hierarchical, object-oriented management information model that facilitates the abstraction of all physical and logical entities in a managed environment.

'''Key Topics:'''
* [[#Introduction to the OpenClovis Information Model | Introduction to the OpenClovis Information Model]]
* [[#Building an Information Model Using the OpenClovis IDE | Building an Information Model Using the OpenClovis IDE]]

For more information on Information Modeling, please refer to Distributed Management Task Force (DMTF) Common Information Model (CIM) available at http://www.dmtf.org.

====Introduction to the OpenClovis Information Model====

The OpenClovis Information Model is built on a generic framework that provides a unified view of hardware and software elements and the services provided by them. It helps you to define the interdependencies and relationships between the managed objects. It is a mechanism to capture the application models and integrate them with OpenClovis SAFplus Platform.

To manage any hardware or software entity, it must be represented as a Resource in the Information Model. Hardware entities include chassis, blade, interface port, logical port, logical connections such as ATM VPC, VLAN, and so on. Software entities includes software processes, operating system features or application protocols such as OSPF, SS7, and so on.

The OpenClovis IDE helps you to build your Information Model using UML notation. This is accomplished through its editors, namely the Resource Editor and the Component Editor. For more information please refer to ''OpenClovis IDE User Guide''.

The Information Model allows the definition of managed objects for an OpenClovis SAFplus-based system encapsulating chassis management, devices, alarms, faults, component states, and provisioned attributes of OpenClovis SAFplus Platform components and customer applications. The model provides support for SNMP MIB import as well as Object ID (OID) to Managed Object ID (MOID) mapping.

====Building an Information Model Using the OpenClovis IDE====

The OpenClovis IDE provides a graphical development environment for defining the SAFplus Platform model. Using the OpenClovis IDE you can design the model, generate/customize the code, and build the images for your target environment. Building the information model involves the following steps:
* Create a project using the OpenClovis IDE.
* Build the resource view in the Resource Editor.
* Define the hardware and software objects of the system and model them as Resources.
* Set the attributes for the resources.
* Create components to manage the resources using the Component Editor and then associate the components with the resources.
* Set the attributes for the components.
* Configure the build-time OpenClovis SAFplus Platform components and save the data as XML files.
* Generate the code representing the defined model.
* Compile the code.
* Create the binary deployment images.

You can compile and link the code to the OpenClovis SAFplus Platform libraries to build the platform software customized for the target application. To get started using the OpenClovis IDE and build a sample model see the ''OpenClovis Sample Application Tutorial.''

===Components of Manageability===

====Clovis Object Repository (COR)====

Clovis Object Repository (COR) is an in-memory, object-oriented distributed repository service enabled with system modeling constructs. It implements data management capabilities like meta-data management as well as data management. Meta-data is expressed as class creation, deletion, and attribute definitions.

Data management capabilities include object creation, deletion, query, indexing, and distribution. COR also provides ability to implement services associated data definition using transaction, recovery, and so on. COR provides the ability for class inheritance and containment.

The Clovis Object repository is updated in the active System Controller instance and an exact replica is maintained (synchronized) in the System Controller Standby to provide high availability. In addition COR provides persistence storage of the repository to provide HA across restart scenarios. It routes the management stations requests to the user component or the object implementer for updating the component managing the hardware or the software resource. The COR supports transient attribute. An object implementer keeps track of the latest value of this attribute. Any get operation from the north bound on this attribute will be routed to the primary OI and latest value will be returned.

====Alarm Manager (AM)====

The OpenClovis Alarm Manager (AM) provides an infrastructure for configuring and handling alarms. It provides support for alarm soaking, masking, alarm hierarchies, and correlation of the alarms before publishing. It stores the information for all the alarm being published untill it is cleared. The alarm client library attached to the component which is managing the alarm resource always sends the request to the alarm manager running on the local node for the processing.

It provides the functionality of reporting the alarm from the south bound entity. It publishes events for all the alarms reported or cleared, so somebody interested in this can register for this subscription.

====Fault Manager (FM)====

The OpenClovis Fault Manager (FM) infrastructure provides a hierarchical scheme for managing faults in a system and initiating actions as configured during the design time. It can handle various user-defined run-time faults, including hardware and software faults and can prioritize faults to ensure that the critical faults are addressed before the normal or the low-priority faults.

The alarms are notified by the Fault Manager client library to the Fault Manager server located on the same node. The actions to be taken on receiving a fault are controlled by the FM policy associated with the faults.

====Transaction Manager (TM)====

The OpenClovis Transaction Manager (TM) is an infrastructure service for providing the 2-phase commit transaction semantics. Along with this it provides two libraries the client library and the agent library. The client library is used to submit the transaction jobs and also the information about all the participating components. Any component that wishes to be a part of transactions can link with the agent library and act as a resource manager.

'''Features'''

* Supports re-startable transactions. For instance, if the Transaction Manager dies, all the pending transactions will be restarted when it is coming up again.

'''How it works'''

It tracks the participants and provides ACID semantics to ensure that all the participants are updated properly, or will rollback to previous state assuring data integrity despite component failures.

====Provisioning Library====

The OpenClovis Provisioning Library manages all aspects of the various hardware and software resources on the system.

Provisioning Library:
* Is a client module that is automatically bound to every component that manages a hardware resource or a software resource.
* It keeps track of all the resources being managed which are modeled to be owned by the component. It also keep account for all the runtime creation or deletion of the resource to be managed.
* Propagates the attributes to the corresponding hardware resource, when it is set from the North bound.
* Fetches the value of the runtime attributes from the component when a get operation is done on it from the North bound.

====Mediation Library====

The OpenClovis Mediation Library acts like a gateway to the OpenClovis SAFplus Platform runtime environment on the system controller. It interacts with external management agents like SNMP, CLI, and OpenClovis SAFplus Platform components.

The Mediation Library helps in translating the service requests from the management station into requests pertaining to OpenClovis SAFplus Platform runtime environment. The extensible plug-in architecture of Mediation Library allows the external management agents to control the configuration and operation of the various managed objects within the system.

====Simple Network Management Protocol (SNMP)====

The OpenClovis Simple Network Management Protocol (SNMP) sub-agent provides the flexibility to manage both platform and non-platform hardware, OpenClovis Information Model, and the alarms present in the system. Using SNMP, you can manage the attributes of an MO that includes a get, set, or notification.

===Working with Clovis Object Repository (COR)===

This section provides information about the value addition that COR provides to an application, and outlines the concepts of managed objects, their related databases, and classes. The following topics are discussed in this section:
* [[#Terms and Definitions | Terms and Definitions]]
* [[#COR: Value-Addition to an Application | COR: Value-Addition to an Application]]
* [[#OpenClovis Information Model | OpenClovis Information Model]]
* [[#COR Architecture | COR Architecture]]
* [[#COR Functionality | COR Functionality]]

====Terms and Definitions====

'''Class''' - An individual entity with attributes.
 '''MO''' - Managed Object provides an abstraction for the manageable properties of a resource in the system. MOs have attributes, support management operations, exhibit behavior and send notifications. Operations on an MO can be Create or Delete Instances; Get or Modify attributes; Action. Notifications emitted by an MO instance are instances that are created/deleted; report attribute change; class specific notification such as alarms.
 '''MO Class''' - Specifies the containment relationship between classes. For example: chassis/gigeblade/gigeport.
 '''MO Class Tree''' - Hierarchical representation of the containment relationship between MO classes.
 '''MOId''' - Unique Identifier of an instance of MO class. It is a hierarchical containment of a resource. MOs have these unique MOIds associated with them within the system. MOIds can be used as the address for MOs. For example: Chassis 0/Gigeblade 1/ Gigeport 2.
 '''MO Instance''' - Instantiation of MO class. For example, Gigeport 3 is an instance of Gigeport class.
 '''MO Instance Tree''' - Collection of MO instances with containment relationship specified. For example, in a chassis based system, an instance of a port could be: Chassis (0)/Blade (3)/Port (2).
 '''MSO''' - Encapsulates the attributes of a Managed Object specific to the particular service they are associated with. (For example, Alarm severity is an attribute related to the alarm service; it is a part of the Alarm MSO associated with any MO desiring an alarm service).

====COR: Value-Addition to an Application====

Almost every telecommunication or data communication system has a managed object database, which captures data pertaining to the system as captured in the information model. Following are the different features provided by COR:
* '''Creation of classes -''' A class is a blueprint of an object. It defines the different attributes of an object. COR provides a capability to inherit one class from another. The inherited class inherits all the attributes of parent class.
* '''Definition of attributes in a class -''' A class when created is an empty class, meaning that it does not contain any attributes other than those defined for the parent. COR supports addition of attributes into classes through APIs.
* '''Creation of MO classes -''' The MO classes when created, defines hierarchy (invariably a physical containment hierarchy) between different classes. The MO class hierarchy is blueprint of Object Tree. This is one way by which a Telecommunication Equipment Vendor enforces a hierarchy in which object can be created by system developer.
* '''Creation and deletion of Objects -''' The Objects can be created in a hierarchical fashion as per blueprint defined by MO class tree. COR provides ability to create/delete objects.
* '''Set and Get operation support -'''The values of the attributes which were modeled as part of the managed resource class can be changed at runtime using set operation after objects of these managed object are created. The latest values of these attributes can be fetched from COR using the get operations. Both these operations support single and bulk semantics.
* '''Object Tree Walk -'''The object tree can be navigated using the features provided in the COR. This walk can be restricted to a particular subtree starting from a defined root.
* '''Distribution of COR repository''' - The COR repository are replicated on the two system controller cards. Exact replica of runtime data and metadata is maintained on both the cards. In case of failure of one card, the data can be obtained from another card.
* '''Transaction Support''' - COR provides an ability to invoke the Managed Service Providers when a data managed by the Object implementer is changed. This is done through transaction mechanism. The transaction mechanism also ensures atomicity and consistency of an operation. A transaction is started for object creation/deletion and attribute set operation started by a user.
* '''Notification Support''' - COR provides support for subscription of notification after completion of transaction. A notification is published for object creation/deletion as well as for setting an attribute of an object.

The following diagram depicts the relationship between COR classes, MO classes, and COR objects:
[[File:SDK_ClassesMOClassesObjects.png|frame|center| '''Classes, MO Classes, and Objects''' ]]

The object creation is performed in three steps. The first two steps are hidden from the user as the information model created using IDE is read by COR at the startup. All the defined classes and MO class tree will be created during this time. The object creation will start only after these two steps are done. A brief description of these three steps is as follows:
# '''Create COR class''' - The COR class is created and attributes are added to it. The class represents a resource in a system.
# '''Create MO classes''' - MO classes are nothing but COR classes arranged in hierarchy. These first two steps define model of a system. These first two steps are performed by COR as a part of Information Model development. A COR class defined in the first step above can be used for multiple MO classes, for example STS1 class can be used for Sonet STS1 as well as DS3 STS1. You need not define a separate COR class for them since attributes of both the STS1 MO classes are the same. An MO class is identified by MO class path which in a string format appears as follows: \chassisMO\SonetBladeMO\SonetPortMO for a sonet port.
# '''Create objects''' - Objects are created when the system starts running (either during boot-up or dynamically, by the System Developer using a management agent (such as SNMP/TL1 CLI). The objects can be created only according to the blueprint defined in steps 1 and 2 above. For example, the system developer can not create DS3 port under a Sonet card since it is not according to the blueprint.

====COR and OpenClovis Information Model====

This section describes the OpenClovis Information Model and how COR is used to capture the Information Model. The following section describes a two-step approach towards defining the OpenClovis information model:
# Metamodel Definition - Metamodel is a language for specifying an information model. It is the responsibility of OpenClovis SAFplus Platform to define metamodel.
# Defining System Model - Using the defined metamodel, the systems vendors define an information model.

=====Metamodel Definition=====

A metamodel defines language for specifying an information model. The following section describes OpenClovis SAFplus Platform's Metamodel and defines different metaobjects used in the metamodel. Example of different metaobjects used in metamodel are class, attributes, relationships, and so on.

The following UML diagram captures OpenClovis SAFplus Platform's metamodel:
[[File:SDK_SAFplus Platform'sMetaModel.png|frame|center| '''OpenClovis SAFplus Platform's Metamodel''' ]]

The left hand side model, as demarcated by blue line, represents the physical view or management view of the system. The right hand side of the model represents logical view. The physical view defines attributes for hardware and software resources contained in the system and the logical view defines metaclasses.

All the metaclasses below the red line are base classes. These classes will not change as we go forward. The classes above red line are specialization of the base classes defined below the red line.

Different relationships exist between metaclasses defined in both the physical view and logical view. These relationships are defined using standard UML notations.

'''Example:''' Defining System Model

Figure [[#Instance of OpenClovis SAFplus Platform's Metamodel | Instance of OpenClovis SAFplus Platform's Metamodel]] illustrates an example for OpenClovis SAFplus Platform's Metamodel.
[[File:SDK_InstanceofSAFplus Platform'sMetaModel.png|frame|center| '''Instance of OpenClovis SAFplus Platform's Metamodel''' ]]

The data present in the information model is captured in COR. The output of information model is captured as user configuration. The information model translates in the COR MO class tree. In the information model as defined above two COR MO class trees shall be generated, one for resources and other for classes. The classes can be captured in the table format. COR provides utility functions to read the table and create COR classes as well as MO classes from it.

====COR Architecture====

COR runs on two redundant system controller cards. This section talks about the network model for COR and provides details of COR subcomponents. Figure [[#COR Network Model | COR Network Model]] illustrates the COR network model:
[[File:SDK_CORNetworkModel.png|frame|center| '''COR Network Model''' ]]

Although distributed databases are complex as opposed to centralized databases, they provide some very important advantages, if implemented, such as:
* '''Performance''' - A proper distribution criterion can ensure that the data is close to the location where it is frequently accessed from.
* '''High Availability of Data''' - In distributed database, cache of an object can be maintained at multiple locations, making the data available in spite of failure of a location.

COR provides High Availability of data by means of making a replica of it on two redundant controller cards.

====COR Functionality====
COR provides the following functionalities:
# MO Class Creation.
# MO Instance Tree creation and Navigation
# Atomic Object Manipulation
# Notification Services
# Object Ownership Services

 '''MO Class Tree Navigation''': Given a class, assigns an API.
 '''Atomic Object Manipulation''': Provides APIs to create multiple objects. Either the operation suceeds or fails. Manipulation includes creation / deletion / modification. For example: In an output, multiple objects can be specified to be created. COR ensures that either all are created or deleted.
Ownership provides component to be owner of an object. An owner of an object participates in the object manipulation operation. The owner provides the three functions:
 '''Validate''': Output is validated by the object owner. If the validation fails, object manipulation on the whole fails.
 '''Rollback''': If validation fails, the object owner needs to roll back its state information.
 '''Commit''': The object owner accepts the creation only if Y is provided in the validate phase. For example: If MTU size of Gigeport is set, then the object owner of gigeport will set the MTU size in the gigeport hardware during the Commit phase.
 '''Notification''': After COR issues notification, this notification is subscribed by components.

====Node Independent Managed Objects====

In a distributed communication system, multiple applications running across multiple nodes can share MOs. Such MOs are not specifically bound to any blade or a node. They are owned by one application but the application is implemented by a pair of ACTIVE and STANDBY SUs and their software components running on different nodes. The MO can be accessed from the north-bound interface irrespective of the location of its owner application. In case of failover, the STANDBY registers the MO without affecting the north-bound interface.

OpenClovis IDE enables you to define MOs in OpenClovis MIB that are not related to any physical entity in the system. These MOs reside in a logical hierarchy tree attached directly to the root MO. For example, two gigE ports are defined in the Resource Editor of IDE with 1+1 redundancy model. These ports are associated with same OI as they collectively provide the gigE service that contains its own MO. This is a logical MO and is blade independent. The configuration of this MO is applied to both the ports.

===Attributes of Managed Objects===

Clovis Object Registry (COR) is a repository of Managed Objects representing the network element resources in a system. COR provides functions that enable read operation on the Managed Objects. These functions are used to access the values of the attributes of an object known by its MoID. Once an application discovers the object hierarchy, it can use this interface to retrieve the attribute values.

'''Definitions'''

* '''Management Station ''': This is used to view the current status of the managed entity or change its state. This can be any management process for example it can be a SNMP MIB browser, a CLI, web-based application etc.
* '''The Object Implementer (OI)''': It is a software component which owns the managed resource. There can be multiple OIs for a managed object but out of all of them there can be only one OI which will act as a primary OI. The get request from the management stations lands in the COR and then it contacts the OI(s) of a managed resource. The primary OI holds the latest value of a runtime attribute. For the configuration attribute there are corresponding attributes present at all the OIs. So when any set request is send by north bound, all the OIs are contacted to update their corresponding attribute.
* There are two types of attributes that can be part of a managed resource, one is called configuration and other is runtime or transient attribute. There are certain properties of these attributes called as attribute-flag which are as follows:
** '''Cached''' - The attribute which is stored in COR. The latest value of cached attribute is always obtained from COR.
** '''Persistent''' - This property of the attribute gives that the attribute value should be stored in a presistent Db file and should be restored in case of restart. Only a cached attribute can be persistent.
** '''Writable''' - An attribute which can be changed at runtime is called writable. This shows that it can be settable from the north bound. A initialized attribute is always non-writable.
** '''Initialized''' - A key attribute of a class has this property. This attribute is for example a index attribute which can be used to identify a row in a snmp table. The value of this attribute should be supplied while creating the object of this class. These attributes are non-writable at runtime.

====Types of Attributes====

The different types of attributes of an object are:
<ul>
<li>'''Configuration Attribute''' - A configuration attribute is used to store the configuration information about the managed resource. For example the maximum memory size can be a configuration attribute of a process resource. These attributes are always cached and persistent. These attribute are always writable to the north bound unless it is marked as initialized, as a initialized or a key attribute should not be modified at runtime.
<li>'''Runtime Attribute''' - This attribute is the property of the managed resource that keeps changing so only the primary object implementer (OI) of this resource manages its latest value. For example - If a component is managing a process running in the system, then information about the current memory used by a process is known only to the component. These attributes are not writable from management station. There is a slight variation of the runtime attribute when it is very slow changing for example - The number of days a process has run. These kind of attributes can be cached in the COR. Whenever it changes, the primary OI can set this attribute. So a runtime attribute is cached or non-cached in COR based on its nature. It can be persistent only when it is cached.
 
[[File:OpenClovis_Note.png]]The runtime cached attribute is writable only from the primary OI. It is non-writable to the north bound agent.
</ul>

A managed resource can contain both configuration attribute and runtime attribute based on the requirement. The configuration attribute will be used to store the configuration information. The runtime attribute is the transient property of the managed resource. Normally its value is maintained by the primary OI. But if it is a very slow changing one, it should be stored in COR which is updated time to time in COR by the primary OI.

====Implementation of Configuration and Runtime Attributes====

For example, COR has objects for every process running in the system. Each process has various attributes associated with it, such as name, process Id, memory usage, maximum memory size, maximum number of open files and so on. Whenever a process starts, COR creates an object of type process with specific attributes. The objects represented in COR are identified by their MoID. You must specify the MoID of an object to perform get and set operations it. When a user queries for a list of all the processes running in the system, COR returns the MoIDs for them based on the number of instances of process managed resources created. The northbound interface creates a table with the MoIDs of all the process.

Now suppose multiple processes are running on a node. Each process occupies some memory that changes during runtime. These processes are treated as managed resources in COR. The management stations can monitor these processes and send requests to know the memory usage of every process at a given time. Since the memory occupied by these processes varies at runtime, this data should not be stored in COR. This attribute is a candidate of being a runtime attribute of the process MO class.

If a transient property of the managed resource changes very slowly then that attribute can be cached in COR. For example the number of hours a process has run. If needed this attribute can also be persistent in COR. The primary OI of the managed resource has to update its value in COR whenever it changes.

The configuration attribute is the placeholder for the configuration information of the managed object. It is always cached in COR. It can be persistent in COR if required. For example, If the component wants to manage a process running in a system which has an attribute which gives the maximum number of open files it can have, then it can be made as a configuration attribute for the process managed resource.

====Importance of OI for attribute types====

A managed object can contain both configuration and runtime attributes. A managed object is managed by the object implementer. These are hidden from the management station. Whenever a request is sent from the north bound interface of a management station, the COR takes care of routing the request to the respective OI(s) of the managed object.

The Object Implementer will be involved while doing get operation on a runtime attribute or while performing a set operation on a configuration attribute.

When a read operation is done on a runtime or transient attribute, a particular OI is contacted to get the value of the attribute. The OI that provides the runtime value of an attribute is the primary OI.

For example in a 2N Redundancy model, one process acts as the ACTIVE and the other as the STANDBY. When you perform a get operation, since the ACTIVE process provides the requested value, so it is the primary OI.

For a configuration attribute of a managed resource in COR, there is a corresponding attribute present in the OI. For any set operation, all the OIs should be contacted inorder to facilitate the modification of their attribute. The request from the north bound first land in COR. It takes care of routing these requests to all the OIs where they can update the respective data bases. Also this set operation updates the value of configuration attribute in COR. So it always has the latest value of a configuration attribute.

The user can specify a particular OI to act as the Primary OI for a managed resource. Setting a OI as the Primary OI involves some restrictions. Please refer the documentation of the API clCorPrimaryOISet in the API reference guide for more information.

====Retrieving Values of Attributes====

The COR provides the mechanism to get the value of the multiple runtime and configuration attributes in one request. This can be done using the bundle get feature of COR.

You can retrieve the value of a runtime attribute of an object at a given time in order to know the value of the transient state of the managed resource. For example, to know the memory usage of a process, you must communicate with the process that implements the object (OI).

A runtime attribute can be stored at the OI if its frequency of change is high. In this case the Primary Object Implementer (OI) is a process that is responsible for providing the value of non-cached runtime attributes. When you query for memory usage of a process, COR communicates with its primary OI to retrieve the information as shown in Figure [[#Accessing MO Attributes | Accessing MO Attributes]]. Depending on the frequency of update, the information returned can contains an earlier value.

 [[File:OpenClovis_Note.png]]Only one Primary OI exists for a particular object in the system.
[[File:SDK_AccessingMOAttributes.png|frame|center|'''Accessing MO Attributes''']]

In the other case, if the frequency of change for a runtime attribute is very low, then it can be cached in COR. So COR itself can provide its latest value in the case of a get operation. The primary OI has to set the latest value of this attribute in COR whenever it is changing.

The COR always stores the latest value of the configuration attribute. So in case of a get operation on this attribute, the COR gives its value.

====Setting Values of Attributes====

You can set the values of configuration attributes from the northbound interface. SAFplus Platform provides an efficient way of performing and managing set operations on a large number of attributes. The set on the runtime attribute is not allowed from the north bound.

Similarly, you can set the values of a common attribute that is shared among multiple processes running in the system, for example the max limit of memory of all processes. A common attribute is not contained in a particular object but is centralized in one object only. Such attributes are shared by all the process running in the system.

When you modify a configuration attribute of a shared managed resource, all the OIs associated with the process are invoked where they can do the respective changes to their attribute. For example : if the configuration attribute corresponding to the maximum limit of memory in the "process" managed resource is changed and if it is being managed by multiple Object implementers, then COR will route the request to each of the OI where they can change the corresponding parameter for the process they are managing.

[[File:OpenClovis_Note.png]]When a set operation is performed on more than one process simultaneously, multiple OIs are invoked whereas in a get operation, only one OI is invoked.

====Storing Values of Attributes====

The management station that send requests from the northbound interface are unaware of the OI. It communicates with COR to retrieve any information. If the attribute is configured as cached, the information is contained within the object. If the attribute is configured as persistent, the information is stored in a file system or a permanent storage disk. The persistent attributes are always cached.

By default, the transient attributes are neither cached nor persistent, since COR does not contain its values. But it can be configured as cached if its value does not change frequently. The OI updates COR only when the value changes to reduce network traffic. If the runtime attribute is cached, the value of the attribute is saved in COR since it changes only periodically. For example, you want to know for how many hours a process is run. So, the information is updated once in every hour. If the cached runtime attribute is not persistent, COR does not save the data.

The configuration attributes are always cached in COR. These attributes are always persistent.

====Raising Alarms====

You can configure the process and get the value of runtime attributes from the northbound interface. A process can have its memory limits as high, medium and low. When the memory of a process exceeds its max limit, you can configure your application to raise alarms. An alarm is a communication medium from the OI to the northbound if an unexpected behavior is observed or a fault condition occurs. Currently, the northbound is a "pull" model as it is not informed about any value unless it sends a get request.

====Types of Process Classes====

The following are the two types of process classes:
* provClass
* alarmClass

You must specify the service Id to access a process class. You can define the service Id of a class to assign it as either a provClass or an alarmClass type. The provClass contains both configuration and runtime attributes.

A node can have multiple process classes running on it. These classes contain various attributes. The hierarchy from the node to the attribute is represented by a MO class path. A process running in a system is uniquely identified by its MoId, that is, <code><node_name>.<node_instance>/<process_name>.<process_instance></code>.

You must specify the MoID of the object from the northbound interface to communicate with COR and retrieve or modify its value. The northbound interface is exposed to different management stations such as CLI, SNMP, XML and so on. The requests from the northbound interface are passed through a Mediation Layer before it reaches COR. The Mediation Layer translates the requests sent through the MIB table from the northbound interface into COR understandable format as shown in Figure [[#Accessing MO Attributes | Accessing MO Attributes]].

To access a particular attribute, you must specify the MoId, the ServiceId and the attributeId. Generally, the configuration from the northbound interface is performed as a bulk operation. When a set operation is performed, OI communicates with the COR. You can provide a transactionId to apply all the configuration changes in bulk and save them in COR in one transaction. This reduces the frequency of communication between COR Server running on the System Controller node and COR client running on worker blades.

For example, you want to change an attribute, such as the max memory limit of all the processes running on a node. An attribute can be in the form of an array and can be updated after a certain index. If a get is performed on the transients attribute, and the primary OI is not available for a few attributes, it returns only those attributes that are associated with Primary OI.

For example, an object contains memory configuration of all the processes running on a node. When a process is started, it reads the object in COR and applies its respective configuration. So every process knows the objects that it belongs to and becomes the OI of that object.

===Provisioning OI Callbacks===

This section will describe the flow of OI callbacks which will get called whenever the managed resources are modified in COR and also during OI initialization if the resources are already present in COR.

====Flow of OI callbacks when the resource is modified in COR====

When the resource managed by a OI is modified in COR, a transaction is getting initiated and all the OIs managing that resource will be involved in the transaction. The diagrams will show the flow by which the OI's callbacks will get called.

=====Flow Diagrams=====

These diagrams will show the flow for the following cases :

*'''Case 1 :''' If the transaction contains CREATE jobs.
*'''Case 2 :''' If the transaction contains multiple SET jobs for different MOs.
*'''Case 3 :''' If the transaction contains DELETE jobs.
*'''Case 4 :''' If the transaction contains READ jobs.

'''CASE 1 :''' The Transaction contains CREATE jobs.

[[File: ProvCallbacksFig_1_1.png|frame|center|'''Transaction which contains CREATE jobs''']]

'''Txn Cycle :''' TXN START -> VALIDATE -> ROLLBACK -> TXN END

[[File: ProvCallbacksFig_1_2.png|frame|center|'''Flow of OI callbacks for ROLLBACK for CASE 1''']]

'''Txn Cycle :''' TXN START -> VALIDATE -> UPDATE -> TXN END

[[File: ProvCallbacksFig_1_3.png|frame|center|'''Flow of OI callbacks for UPDATE for CASE 1''']]

'''CASE 2 :''' Transaction contains multiple SETs for different MOs.

[[File: ProvCallbacksFig_2_1.png|frame|center|'''Transaction which contains SET jobs for different MOs''']]

'''Txn Cycle :''' TXN START -> VALIDATE -> ROLLBACK -> TXN END

[[File: ProvCallbacksFig_2_2.png|frame|center|'''Flow of OI callbacks for ROLLBACK for CASE 2''']]

'''Txn Cycle :''' TXN START -> VALIDATE -> UPDATE -> TXN END

[[File: ProvCallbacksFig_2_3.png|frame|center|'''Flow of OI callbacks for UPDATE for CASE 2''']]

'''CASE 3 :''' Transaction contains a DELETE jobs.

[[File: ProvCallbacksFig_3_1.png|frame|center|'''Transaction which contains DELETE jobs''']]

'''Txn Cycle :''' TXN START -> VALIDATE -> ROLLBACK -> TXN END

[[File: ProvCallbacksFig_3_2.png|frame|center|'''Flow of OI callbacks for ROLLBACK for CASE 3''']]

'''Txn Cycle :''' TXN START -> VALIDATE -> UPDATE -> TXN END

[[File: ProvCallbacksFig_3_3.png|frame|center|'''Flow of OI callbacks for UPDATE for CASE 3''']]

'''CASE 4 :''' Transaction contains READ jobs for a MO

[[File: ProvCallbacksFig_4_1.png|frame|center|'''Transaction which contains READ jobs for a MO''']]

'''Txn Phase :''' READ

[[File: ProvCallbacksFig_4_2.png|frame|center|'''Flow of OI callbacks for READ for CASE 4''']]

====Flow of OI callbacks when it is coming up====

Pre-provisioning is done when the application is coming up. Prov will read the MOs in COR for which the application is interested and call the application's callbacks, so that it can know the current values of the Objects in COR.

The below diagrams will show the flow by which the application's callbacks will be called during pre-provisioning.

For example if there are two objects \A:0 and \B:0 present in COR which contains the following attributes.

[[File: ProvCallbacksFig_5_1.png|frame|center|'''COR objects for which a OI is interested''']]

then the pre-provisioning will be done in the following manner.

=====Flow Diagram=====

[[File: ProvCallbacksFig_5_2.png|frame|center|'''Flow of OI callbacks during pre-provisioning''']]

===Developing SNMP Subagent for Custom MIBs===

A Management Information Base (MIB) is a type of database used to manage entities in a communications network. It comprises a collection of objects in a (virtual) database which are used to manage entities (such as routers and switches) in a network. A MIB defines the attributes/information of resources, but is only a schema of information. This schema is populated to create a custom MIB.

A SNMP subagent is a process that handles all set/get operations for the MIB. The subagent registers with the SNMP daemon to inform it that all operations for that MIB should be passed on to the subagent. Typically, a SNMP command would come from a monitoring or management station to the SNMP daemon. The daemon then passes on the command to the subagent. The subagent communicates to COR through a mediation library to set or retrieve the values in COR, and returns the result via the SNMP daemon.

With OpenClovis 3.0, the SNMP subagent can now be automatically generated. This section will walk you through the steps to configure and generate the subagent. The OpenClovis IDE is capable of fully generating an SNMP subagent from a MIB or set of MIBs.

====Importing a MIB====

From the menu, select '''Clovis -> Importing Mib Objects ...'''. Click on the '''Load''' button to browse to the location of your MIB file. Once the MIB has been loaded, click on the MIB entry in upper box, and its associated MIB objects will appear in the lower box.


[[File:SDK_SNMP_SelectMibs-fig1.png|frame|center| '''Selecting MIB Objects''']]

In the example shown in Figure [[#Selecting_MIB_Objects|Selecting MIB Objects]], DEMO-MIB has three different objects. One is a set of scalars, the other a table, and the last is a trap. Select the MIB objects you want to import into your model, and then click on the '''Import''' button.

If you are importing objects from multiple MIBs, load all the MIB files. Then for each MIB, you will need to select the MIB from the upper box, and highlight each MIB object from the lower box and import it.


[[File:SDK_SNMP_ResourceEditorWithMibObjects-fig2.png|frame|center| '''Resource Editor with MIB Objects''']]

When finished, you should see in the resource editor, something similar to Figure [[#Resource_Editor_with_MIB_Objects| Resource Editor with MIB Objects]]. You may have noted that three MIB objects were listed in the DEMO-MIB example, but only two are present in the resource editor. The third object was a trap, which gets imported as an alarm.

In the example shown, there is now an MO called demoStatusTable. In reality, this only represents one row of a table. To increase the maximum number of rows in the table, double click on the table. Under the '''Resource''' options, increase the number of '''Maximum Instances''' to match your needs. In this example shown in Figure below, there are a maximum of 10 rows.


[[File:SDK_SNMP_MaxInstances-fig3.png|frame|center| '''Select Maximum Instances''']]

====SNMP Traps====

As mentioned earlier, the trap was imported as an alarm. To adjust the type and severity of an imported alarm, from the menu select '''Clovis -> Alarm Profile ...'''. See Chapter ''Defining Alarm Profiles'' of the ''OpenClovis IDE User Guide'' for further information on the configuration of alarms.

When your alarm is appropriately configured, you can associate it with a resource. Double-click on the resource you wish to have this alarm. Under '''alarmManagement''', click on the '''Enable''' checkbox. Then under '''Associate Alarms''', highlight the alarm(s) and click on the '''Add''' button. See Figures [[#Alarm_Management|Alarm Management]] and [[#Associate_Alarms|Associate Alarms]].


[[File:SDK_SNMP_AlarmManagement-fig4.png|frame|center| '''Alarm Management''']]


[[File:SDK_SNMP_AlarmManagement-fig5.png|frame|center| '''Associate Alarms''']]

====Configuring the Subagent====

The SNMP subagent is a SA Aware Component. To configure a component to be a subagent, you need to do the following steps. First, double-click on the component to see the properties, and set '''Is SNMP Sub-Agent''' to '''true''' as shown in Figure [[#SNMP_Component_Properties|SNMP Component Properties]].


[[File:SDK_SNMP_SnmpComponentProperties-fig6.png|frame|center| '''SNMP Component Properties''']]

Next, right-click on the component and select '''Sub-Agent Properties''' from the pop up menu. Here there are two fields that need to be filled out. See Figure below.


[[File:SDK_SNMP_SubAgentProperties-fig7.png|frame|center| '''SubAgent Properties''']]

The first field will set SNMP's MIBDIRS environment variable necessary during the the subagent code generation. This is a colon ':' separated value containing all the directories to look for MIB files in. For this to work properly, you will need to make sure that net-snmp's <code>mibs</code> directory is included, which would be in your clovis installation directory. If you installed the Clovis software in the default location, it would be <code>/opt/clovis/buildtools/local/share/snmp/mibs</code>.

The second field would be the top level node name for your MIB. If you just have one MIB, this would be the MODULE-IDENTITY name in your MIB file. If you have several MIB files, it would be the MODULE-IDENTITY of the top layer in your MIB tree.

=== SAFplus Platform Manageability End to End===

The SAFplus Platform components which are used for providing the manageability infrastructure are as follows:
* Clovis Object Repository
* SNMP sub agent
* Mediation library
* Provisioning library
* Alarm Management
* Fault Management

This section describes about how these components interact to provide the resource management and fault reporting capability to the SAFplus Platform middleware.

==== North bound Requests ====
The management station requests - walk, set or get operations - are handled by the SAFplus Platform middleware using some of the above mentioned components. These operations can be done from the management station on one table or it can span multiple tables. Each table represent one managed entity in COR. The rows of the table maps to different instances of the resource. Each column of the table denotes different attributes of the resource. All this information are stored in COR. When the GET, SET or a WALK request reaches SNMP sub-agent, it is translated by the mediation library into a COR request and sent to it. This data is also cached in the sub-agent which is retrieved from COR based on the expiration of caching frequency time period.

The SET and GET operation can be done in a singular or a bulk manner. The bulk set operation is done using the transaction. The SET operation is validated with all the object implementers of the managed resource and only when all of them agrees to the change, then only it is updated otherwise the rollback is done on all of them. The Get operation can be done for configuration and transient attributes. For configuration information only COR is contacted but for transient attribute the primary OI is contacted to get its latest value.

The diagram below shows the SNMP request being processed by the SAFplus Platform. The request is first received by the SNMP sub-agent. This request is then translated into a COR based request by the mediation library and sent to it for processing. Based on the type of request, COR processes it locally or sends it to the Object implementers. If it is a SET request, COR sends the request to the Object implementers where provisioning library attached to it does the job of validating the request and then updating it on their end. If it is a GET request or WALK request on a transient attribute, it is sent to the Primary Object Implementer to get the latest value of this attribute. If it is a get request or a walk on a cached attribute, the COR will process it locally and send the response.
[[File:snmp-set-get-request.png|frame|center| '''SNMP SET/GET/WALK request processing in SAFplus''' ]]

==== Reporting failures in the system via alarms ====
The asynchronous events happening in the system are reported as alarms. These alarms can be modeled as traps in the MIB. This MIB cab be imported using IDE which will take care of configuring the alarms. So whenever these alarms occur in the system, they are reported as traps to the north bound interface.

All the alarms modeled in the system can be configured to be raised by some application using the IDE. So a component can be assigned the task of raising these alarms based on certain conditions. When these alarms are published, the mediation library along with the SNMP-subagent takes care of sending these configured alarms as traps to the north bound entity. The COR server stores the latest information about the alarm.

The diagram below shows the trap reporting feature of SAFplus Platform. A component with the alarm client library and having alarm configured through IDE, can raise the alarm. This component can run on any node. In the figure it is shown as a part of payload node. The SNMP sub-agent can be part of any node. In the diagram it is shown as part of controller node. Once the alarm is raised, the alarm server publishes the event. The mediation library attached to the SNMP sub-agent listens for this event. It verifies whether the alarm raised is configured to be raised as trap. If it is so, then it forwards the request to the SNMP sub-agent which takes care of reporting this alarm as trap to the north bound management station.

[[File:SDK_SendingTraps.png|frame|center| '''SNMP Trap reporting using SAFplus''' ]]

==== Fault reporting and repair action ====

The fault management feature of the manageability infrastructure allows the application to take customized action when the faults occur in the system. There are two kinds for fault handling supported by the Fault Manager which are described below.
*'''Fault Reporting'''
The fault reporting is done for non-service impacting alarms. The non-service impacting alarm are the one with severity less then major that is minor, warning and indeterminate. For each alarm category and severity combination, there are five escalation levels defined. For each escalation level there can be a callback associated and inside that user defined action can be taken. The fault manager calls the callback based on the category + severity + escalation level. The callback on the level one is called if the fault occur for the first time. The fault level is escalated, when the frequency of fault is more than the probation period. Both the callbacks and the probation period are configurable through IDE.
* '''Fault Repair'''
The fault repair can be done by the application which wants to trigger an action based on the service impacting problem happening on the managed resource. The managed resource on which repair action need to be done are modeled with an alarm MSO. Whenever a problem is detected on such resource, an alarm is reported to the alarm server. The alarm handle obtained after alarm raised or the alarm handle obtained in the alarm event delivery is used in the repair action. This is necessary as fault repair action is done only on the service impacting alarms. The fault manager on receiving the repair action request calls the callback assigned to the resource. This callback function is generated by the IDE for every resource having alarm MSO.

The figure shows the fault reporting and repair action feature of the SAFplus Platform. Whenever an alarm is raised in the system, the Alarm Server decides whether it should be reported as fault or not. Only the non-service impacting alarms are reported as fault. So for all these alarms, it contacts Fault Manager which takes care of calling the registered callbacks. The figure also describes the fault repair actions feature. The component doing the repair action should have the alarm handle corresponding the alarm raised. The alarm repair action should be done for service impacting alarms. So a component raising this alarm or listening for the alarm events, can trigger the repair action. In the diagram the "Fault Mgmt App" shows as alarm reporter as well alarm listener. There can be two different applications doing this job. So a component doing fault repair action can be the one which reports the alarm or the one which listens for the alarm notifications.

[[File:SDK_FaultReporting.png|frame|center| '''Fault handling using SAFplus''' ]]

Talk:High Availability (AMF) Questions

2012-02-21T03:24:23Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ order cheap xanax online - buy xanax 2mg

Doc:latest/sdkguide/highavailability

2012-02-21T03:24:23Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ purchase online generic xanax - order cheap xanax online

Talk:Doc:latest/sdkguide/cominfrastructure

2012-02-21T03:24:23Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxitem.com, blanking

Doc:latest/installguide

2012-02-21T03:24:22Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ buy xanax online wthout prescription - generic xanax

http://www.buyxanaxonlinepill.com/ order xanax cheap - xanax

=='''OpenClovis SDK Installation'''==

This chapter provides a step-by-step approach for installing OpenClovis SDK. Before proceeding with installation, ensure that all the required hardware and software are available on your system. You need not install the third-party packages, as the installation package installs the third-party packages along with OpenClovis SDK.

===Installation Procedure - Get Started===

To install Openclovis SDK on your local machine, go to the directory where you have downloaded the required installation files.

Before you install,
* Ensure you have write permissions for the current directory (directory where the installation files are downloaded) and the target directory (directory where you will install the application.)
* At least 500MB of free disk space.
* You can install the SDK either as a root user or a non root user. Installing as root user is not required for a single user host. When using the SDK for larger projects it is advisable to install as root, since multiple users can share the same SDK. Irrespective of the mode of installation, the SDK can be used to model and build code using non-root privileges.

To extract the SDK package, execute the following command:

<code><pre>
# tar -xzmf openclovis-SAFplus-*.tar.gz
</pre></code>

[[File:OpenClovis_Note.png]] The <code>m</code> option to <code>tar</code> ensures that the timestamps on the files within the SDK package are consistent with the host system. This is important, since discrepancies can adversely affect the build procedure.

Next start the SDK installation by executing the following command:
<code><pre>
# ./install
</pre></code>

After you execute the install command, the welcome screen is displayed as illustrated in Figure [[#OpenClovis Installer Welcome Screen | OpenClovis Installer Welcome Screen]]. When prompted by the installer, the user can enter the name of the directory where the SDK should be installed or accept the default provided:


[[File:OpenClovisSDKInstallation_WelcomeScreen_wPreInstall.png|frame|center| '''OpenClovis Installer Welcome Screen''' ]]

The default directory for installation is <code>/opt/clovis</code> for root installation and <code>$HOME/clovis</code> for non root users as illustrated in Figure [[#OpenClovis Installer Welcome Screen | OpenClovis Installer Welcome Screen]]. The installation progress is illustrated in Figure [[#Installation Directory and Progress | Installation Directory and Progress]].


[[File:OpenClovisSDKInstallation_InstallationDirectories.png|frame|center| '''Installation Directory and Progress''' ]]

===Third Party Packages===

The required third party packages are installed in the following steps:
* Scans the system for existing third party packages.
* Displays the list of packages that are available, along with their version numbers.
* Displays the list of packages that are not available or that have a version mismatch.

[[File:OpenClovis_Note.png]] This display may vary at the time of your installation, depending on the packages that are available on your system. Figure [[#Third Party Packages - Availability Status | Third Party Packages - Availability Status]] demonstrates a typical display.


[[File:OpenClovisSDKInstallation_ThirdPartyPackages.png|frame|center| '''Third Party Packages - Availability Status''']]

To proceed with the installation, enter <code>y</code> for the message, <code>Proceed with the installation <y/n> [y]: </code>

Figure [[#Third Party Packages Installation Progress | Third Party Packages Installation Progress]] illustrates the approximate installation time and the installation status for each package.


[[File:OpenClovisSDKInstallation_3rdPartyPackageInstallationProgress.png|frame|center| '''Third Party Packages Installation Progress''']]

After installation of third party packages, the installer displays the message, <code>All SDK dependencies are now in place.</code> as illustrated in Figure [[#OpenClovis Packages Installation - Status | OpenClovis Packages Installation - Status]].


[[File:OpenClovisSDKInstallation_InstallationStatus.png|frame|center| '''OpenClovis Packages Installation - Status''']]

After completion of the third party packages, the installer prompts the user for the installation of the crossbuild toolchains.

===Crossbuild Toolchains===

Crossbuild toolchains are required to install SAFplus Platform on a platform that is different from the development host platform. For instance if the development host is x86 Intel based and the target platform is PowerPC based the user will need a crossbuild toolchain for that particular PowerPC based architecture.

For crossbuild toolchains, you will require the following:
* A cross compiler and related binary tools for the target CPU architecture.
* All the SAFplus Platform prerequisites that are pre-compiled for the target platform, so that all library files are available.

OpenClovis SDK comes with a standard set of pre-built crossbuild toolchain packages. The names of these packages help you to identify the CPU and OS combinations for which they have been built.

The SDK installer (<code>install.sh</code>) assists you in installing one or more of these toolchains as illustrated in Figure [[#Crossbuild Toolchains | Crossbuild Toolchains]]. Enter the crossbuild toolchain that you require to be installed from the available list. After the toolchains are installed, you can select any of these cross-tools for your project build.


[[File:OpenClovisSDKInstallation_Crossbuildtoolchains.png|frame|center| '''Crossbuild Toolchains''' ]]

If you would like to install more crossbuild toolchains at a later time, please download them and re-run <code>install.sh</code>. You may skip the remaining portions of the install process past the installation of crossbuild toolchains when you are prompted to do so.

===SAFplus Platform, IDE and Utilities===

 After installation of the toolchain, the system proceeds with the installation of SAFplus Platform, IDE and Utilities as illustrated in Figure [[#Installing SAFplus Platform, IDE and Utilities | Installing SAFplus Platform, IDE and Utilities]].


[[File:OpenClovisSDKInstallation_InstallingASP_IDE_Utilities.png|frame|center| '''Installing SAFplus Platform, IDE and Utilities''' ]]

 The installer creates the required binaries and prompts you to create optional symbolic links, so that the SDK commands can be accessed on your system in a well known location, as illustrated in Figure [[#Creating Symbolic Links | Creating Symbolic Links]]. The main SDK commands of interest to the user are:
<ul>
<li><code>cl-create-project-area</code>: Command to create a new OpenClovis SDK project area. A project area is the workspace for the OpenClovis SDK. It contains the IDE models and the generated source code. The user makes modifications to the generated source within this workspace and builds runtime images here as well. A typical project area has the following directory structure:
<code><pre>
<project_area>
|ide_workspace
|+<model>
| |+build
| | |+local
| | | |-Makefile
| | |+<crossbuild>
| | | |-Makefile
| |+src
| | |+app
| | |+config
| | |+doc
| | |-target.conf
| |+target
| |-Makefile
|-Makefile
</pre></code>

<li><code>cl-ide</code>: Command to start the OpenClovis IDE. Please note that you should have already created a project area using <code>cl-create-project-area</code> before using <code>cl-ide</code> to work within this project area.
</ul>


[[File:OpenClovisSDKInstallation_CreateSymbolicLinks.png|frame|center| '''Creating Symbolic Links''' ]]

Enter <code>Y</code> to create the symbolic links. The installer then prompts the user for a location to place the links with a default option <code>/usr/local/bin</code> if you are installing as root, or <code>$HOME/bin</code> for non root user installation.

If you choose not to create symbolic links and enter <code>N</code>, then you can either:
<ul>
<li>Add the installation directory to the shell path. For example with a bash shell:
<code><pre>
export PATH=$PATH:<install_dir>/sdk-3.0/bin
</pre></code>
<li>or access the SDK commands from the <code><install_dir>/sdk-3.0/bin/</code> directory. For example to create a new project area at <code><project-area_dir></code>:
<code><pre>
<install_dir>/sdk-3.0/bin/cl-create-project-area <project-area_dir>
</pre></code>
</ul>

After creating symbolic links, the installation of OpenClovis SDK is complete. All the required packages and crossbuild toolchains are installed and the directory where you have downloaded the installation packages can be discarded.

[[File:OpenClovis_Note.png]]If your installation is not successful, or if you encounter any problems during the installation, refer to the Chapter [[#Troubleshooting | Troubleshooting]].

===Next Steps===

After completing the Installation, the OpenClovis SDK Documentation set listed in the [[#Related Documents| Related Documents]] section is available in the <code>doc</code> folder located at <code><install_dir>/sdk-3.0</code> directory.

We recommend the following steps to get familiar with our product:

*'''Read and follow the OpenClovis Sample Application Tutorial''' - The ''Sample Application Tutorial'' will step you through the process of creating a high available system. It takes you from model conception all the way through deployment and running of the sytem. After going through this guide you will understand the basics of the OpenClovis offering.

*'''Read and follow the OpenClovis Evaluation System User Guide''' - ''Evaluation System User Guide'' will introduce you to more advanced modelling topics. These topics are introduced incrementally through a series of targeted tutorials. After completing this guide you will be ready to start building your own system.

=='''Troubleshooting'''==

This chapter describes some of the probable errors that you may encounter during the installation. This chapter also provides the solution to these errors.The errors that you may encounter are:

<ul>

<li>
'''Error''': Installation Failure, during third party installation.
 
'''Solution''': You can manually fix this error by getting more information from the corresponding log file under the log directory. You can also send the <code>log.tar.gz</code> to support@openclovis.com for more help.
The installation can be resumed after the errors are fixed. The installer will detect any new updates and proceed with the missing prerequisites.
 

<li>
'''Error''': <code>gcc (pkg-config, perl, md5sum) not found in your PATH</code>.
 
'''Solution''': Ensure that the directory where the <code>gcc</code> resides is in the <code>PATH</code> variable.
 

<li>
'''Error''': Not enough space on the target installation directory.
 
'''Solution''' : Change the target installation directory to the directory with at least 500MB free disk space.
 

<li>
'''Error''': <code><WORKING_DIRECTORY></code> is read-only.
 
'''Solution''': You need to have write permission for the current working directory to extract the contents of the archive, configure, and build. Ensure that you turn ON write permission using <code>chmod +w ...</code> command.
 

<li>
'''Error''': md5 checksums are used to check if the packages are correctly downloaded. If they are not downloaded correctly, the system displays the message: <code>It is not safe to install these packages, please download them again.</code>
 
'''Solution''':The installer checks the integrity of the downloaded packages. If the download is either incomplete or corrupt, download the packages again.
 

<li>
'''Error''': SAFplus Platform fails to start, reporting the underlying SQLite database version used is not-supported.
 
'''Solution''': Use SQLite version 3.3.13 or newer. The source code can be downloaded from http://www.sqlite.org/download.html. The user can install the latest version of SQLite if the specified version is
not present in this repository.
</ul>

=='''Appendix A: Installing the Prerequisites without Internet Access'''==

Some customers do not want their evaluation system to have internet access for security purposes. If this is your situation, please consider temporarily enabling internet access while running the "preinstall-<os>" script. At this point the evaluation system should only have the base OS installed, so there is no proprietary data on the system. Also note that the "preinstall" scripts are only about a page long so you can easily review them for security purposes.

However, if you still do not want to enable internet access one strategy that can be used is to go to a system with internet access (it must use the same Linux distribution and the same version), download them there, use a USB flash drive to move them to the unconnected system, and then install them on that system. If this approach is unacceptable (it does still use the internet), then perhaps the Linux distribution you chose is not appropriate -- instead use one that contains all packages on the installation CDROMs.

===Example Using Ubuntu 7.04===

Packages can be downloaded but not installed on Ubuntu by using the "-d" flag to the "apt-get" package manager. The files are downloaded to "/var/cache/apt/archives". It is recommended to remove (or move) all files in this directory first (it is just a cache, and so it will contain any packages that you have previously installed), so that the directory contains just the packages needed for the OpenClovis SDK:

rm /var/cache/apt/archives/*

Next edit the preinstall-ubuntu.sh script, search for all instances of "apt-get" and add the flags "-d --reinstall" just after the "apt-get" program. For example:

apt-get -d --reinstall -y --force-yes install build-essential

Next run this modified script on your internet-connected machine. This script will download 6MB of files (this list will vary by Linux distribution or version):

bison_1%3a2.3.dfsg-4build1_i386.deb
libgdbm-dev_1.8.3-3_i386.deb
build-essential_11.3_i386.deb
libltdl3-dev_1.5.22-4_i386.deb
e2fslibs-dev_1.39+1.40- WIP-2006.11.14+dfsg-2ubuntu1_i386.deb
libperl-dev_5.8.8-7build1_i386.deb
e2fsprogs_1.39+1.40-WIP-2006.11.14+dfsg-2ubuntu1_i386.deb
linux-headers-2.6.20-16-generic_2.6.20-16.32_i386.deb
flex_2.5.33-10build1_i386.deb
gawk_1%3a3.1.5.dfsg-4build1_i386.deb
gettext_0.16.1-1ubuntu2_i386.deb
pkg-config_0.21-1build1_i386.deb
libdb4.5-dev_4.5.20-1ubuntu1_i386.deb
uuid-dev_1.2- 1.39+1.40-WIP-2006.11.14+dfsg-2ubuntu1_i386.deb

Now copy these files to a new directory in your unconnected machine:

On the connected machine:
root@desktop:/# cp /var/cache/apt/archives/*.deb <your flash media>

On the unconnected machine:
root@desktop:/# mkdir /root/pkgs
root@desktop:/# cp <your flash media> /root/pkgs/

Finally, install them using the standard "dpkg" package installer:

root@desktop :/# cd /root/pkgs
root@desktop:~/pkgs# dpkg -i *.deb
(Reading database ... 113653 files and directories currently installed.)
...
root@desktop:~/pkgs#

At this point, you should be done installing the prerequisites! You should now continue the installation procedure at the step after installing prequisites.

Doc:latest/safcompliance

2012-02-21T03:24:21Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ order xanax online overnight - buy xanax cheap no prescription

http://www.buyxanaxonlinepill.com/ buy xanax no prescription - order xanax no rx

=='''Compliance with Service Availability Forum AIS Architecture'''==

OpenClovis SAFplus Platform complies with the Service Availability Forum (SAF) Hardware Platform Interface (HPI) and Application Interface Specification (AIS) specifications. OpenClovis Inc. is actively participating in the SA Forum and helping to drive the emerging HPI and AIS standards based on its experience.

===Programming Model and Usage===

Section 3.1 of SAI-AIS-Overview-B.02.01 describes the SAF Application Interface programming model and the generally intended usage of the interfaces.

It introduces the area server as an abstraction that represents the server providing services for a specification area, for instance, Availability Management Framework, Group Membership Service and so on. The interface is defined as occurring between a user application that needs the services of the area server and an area implementation library.

OpenClovis SAFplus Platform adheres to the SAF area server-area implementation library abstraction and the SAF programming and usage model in providing various services.

===Availability Management Framework (AMF)===

The Availability Management Framework (AMF) is the most important software entity of the SAF AIS Specification. It provides service availability by coordinating redundant resources within a cluster to deliver a system without a single point of failure. AMF prescribes a way to model applications that needs to be highly available. In addition, AMF provides a set of APIs that must be used by these applications to be managed for high availability.

OpenClovis SAFplus Platform is implemented in complete accordance with the SAF AMF model and interfaces. This may be considered as the core of the SAF solution for high availability. The only limitation in the current release with respect to the AMF component model is that SAF defines a flexible mapping between components, processes and threads whereas OpenClovis SAFplus Platform supports only a single process per component. OpenClovis Inc. offers to support one-to-one relationship between a component and a process. However, a component can have multiple threads of execution within it.

===Application Interface Specification (AIS) Services===

The following OpenClovis SAFplus Platform components provide services that are functionally equivalent to SAF AIS specifications:
*Availability Management Framework (AMF)
*Checkpoint Service (CPS)
*Event Manager (EM)
*Group Membership Service (GMS)
*Messaging Service (MSG)

===SAFplus Platform AMF Features===
*'''HA model supported'''
** 2N
** M+N

*'''Auto Adjust'''
SAF SG auto adjust feature to adjust the SG based on the SU ranking giving preference to higher ranked ones for active assignments

*'''SI Dependency'''
SAF SI dependency across service groups

*'''CSI Dependency'''
SAF CSI dependency within the same SI for work assignments

*'''Component instantiation dependency'''
SAF component instantiation dependency for components within the same Service Unit configurable through instantiationLevel attribute.

*'''Reduction Procedure'''
SAF SG reduction procedure applied when the SG is running under reduced potential for computing and removing less optimal standby assignments to assign Service Instances.

*'''AMF NOTIFICATIONS'''
SAF HAStateChangeNotify and SIAssignmentStateChangeNotify notifications for applications to subscribe for AMF state transitions

*'''Preferred SI assignment'''
Preferred SI assignment that could be configured for SUs to control SI assignments. Coupled with the delayed SG startup configuration through restartDuration to control instantiation of all the preferred SUs, SI preference could be enforced during initial cluster startup for the Service units in the cluster.

*'''Proxy-Proxied support'''
Allow HA control of legacy application (non-SAF awared) via proxy

===SAFplus Platform Cluster/Group Membership Service (GMS) Features===
The SA-Forum CLM API is fully supported.

*'''Cluster Membership'''
CLM service manages the membership of the nodes. It manages the cluster formation during node joins and leaves.

*'''Tracking Cluster Membership'''
Any application can register for Cluster Track callback through which it can get the notification for any node joins and leaves in the cluster

*'''Getting Cluster Member information'''
API interface are available to get the information such as Address, node name etc, for any given cluster member node.

*'''Cluster node eviction/ejection'''
A cluster node can be administratively ejected from the cluster.

===SAFplus Platform Checkpointing Service (CPS) Features===
*'''Checkpoint/Section creation/deletion'''
CPS provides APIs for users to create/delete checkpoints and sections within the checkpoints.

*'''Granularity at Section level'''
CPS allows user to create a checkpoint and inside a checkpoint user can create any number of sections and read/write each sections independently.

*'''Checkpoint Status'''
CPS provides API to retrieve checkpoint status.

*'''Locking at Section level'''
CPS provides read/write locks at section level due to which multiple sections can be accessed simultaneously.

*'''Update options'''
CPS allows both Synchronous and Asynchronous update of the checkpoint replicas across the cluster

*'''Replica Management'''
CPS allows both collocated and non-collocated mode of checkpoint replicas

*'''Choosing replica at run time'''
User can use ActiveReplicaSet() APIs to set the active replica at run time.

*'''Retention time'''
CPS provides users to specify a retention time for which the checkpoint is retained even when no one is accessing the checkpoint

*'''Section Expiration Time'''
User can set an absolute expiration time for a section after which the section is deleted irrespective of its usage at that time.

*'''Section Iteration'''
Users can iterate through the sections of a checkpoint.

===SAFplus Platform Event Service features===
*'''Publish/Subscribe multipoint-to-multipoint communication mechanism'''
** Based on concept of event channels
** Publisher communicates asynchronously with one or more subscribers over an event channel
** Multiple publishers and subscribers can communicate over the same event channel; publishers can be subscribers on the same event channel
** Individual publishers and individual subscribers can communicate over multiple channels
*'''Events consist of standard header and one or more bytes of payload data'''
** i.e. Event Service does not impose any specific transfer syntax for the data
*'''Event channel management'''
** Event service provides APIs for opening, closing and deleting event channels
*'''Event operations'''
** Event service provides APIs for managing the event payload data, publishing the event, subscribing for the event etc

===Additional SAFplus Platform Services===

OpenClovis SAFplus Platform also provides various components that were implemented earlier than its implementation with SAF specifications. These components provide services that are functional equivalent to SAF AIS services as listed below:

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''SAFplus Platform Services Equivalent to SA Forum AIS Services'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| OpenClovis SAFplus Platform Components
!style="color:#66b154; background:#09477c"| Functionally Equivalent AIS Service
!style="color:#66b154; background:#09477c"| AIS Specification
|- style="color:#ffffff; background:#549cc6"
|
Clovis Object Repository (COR)
|
Information Model Management Service
|
SAI-AIS-IMM-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Alarm Manager (AM)
|
Notification Service
|
SAI-AIS-NTF-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Log Service
|
Logging Service
|
SAI-AIS-LOG-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Naming Service
|
Naming Service
|
SAI-AIS-NAM-A.01.01
|- style="color:#ffffff; background:#549cc6"
|
Platform Management Service
|
Platform Management Service
|
SAI-AIS-PLM-A.01.01
|- style="color:#ffffff; background:#549cc6"
|}

===IMM (OpenClovis Object Repository - COR) Features===
The OpenClovis Object Repository(COR) implements the IMM features. We are progressing on having API level compliance which will be available in R5.0.

The following are the IMM compliant features of COR:

*'''Object Mananger and Object Implementer'''
**COR provides a rich set of APIs to make configuration changes on a Managed Object (MO). It provides service to implement a MO by multiple Object Implementers (OI), so that the configuration changes on the MO can be validated by all the OIs. It provides APIs to make or remove an application as a OI for a MO.

*'''Runtime Attributes Management'''
**COR provides service to implement the runtime attributes of an object or all the object instances of a class. The Runtime attributes values can be cached or non-cached in COR. The cached runtime attributes values has to be updated by Primary Object Implementer (POI) periodically in COR. The value of non-cached runtime attributes will be updated by POI on request by COR. The values of cached runtime attributes can be persisted into storage devices.

*'''Configuration Attributes Management'''
**The Configuration attributes are always cached and persisted by COR. Any configuration change on these attributes by a OM will be implemented by all the OIs.

*'''Attribute Characteristics'''
**COR supports the following attribute characteristics.
***CONFIG - Indicates that the attribute is a configuration type attribute.
***RUNTIME - Indicates that the attribute is a runtime attribute.
***WRITABLE - Indicates that the configuration attribute can be modified.
***INITIALIZED - Indicates that value for the configuration attribute must be specified when the object is created.
***CACHED - Indicates that the value of the attribute is cached in COR.
***PERSISTENT - Indicates that the value of the attribute must be stored in a permanent manner by COR

*'''Object Class Management'''
**COR provides APIs to create, delete and modify the classes, and to make hierarchical relationship between the classes. It also provides service to inherit the existing class to create a new class.

*'''Tree organization of Objects'''
**COR organizes the MOs in a hierarchical manner supporting parent-child relationship, inheritance, association and containment relationships.

*'''Search Operations'''
**The search operations can be performed on a single MO, or a MO and its children, or a sub tree rooted from the given MO.
**We can either retrieve all the attributes in the MO matching the given criteria or only the matching attributes.

*'''Object Access'''
**COR bundle GET APIs can be used to retrieve the attributes values in a efficient manner by grouping the GET requests belonging different MOs into one single request to COR. The values of runtime non-cached attributes will be updated by POI on request by COR.

*'''Class Implementer'''
**COR provides APIs for the application to implement all the Object instances of a class, for both Configuration and Runtime attributes.

===SAF Notification Features===
OpenClovis SAFplus Platform is compliant with the following Notification features :

*'''Notification Types'''
**Alarm
**State Change
**Object Create/Delete
**Attribute Change

*'''Alarm Notification'''
**An alarm report is a notification of a specific event that may or may not represent an error. OpenClovis Alarm notification is fully compliant with ITU-T X.733 standard (which is recommended by SAF-NTF).

*'''State Change Notification'''
**OpenClovis AMF provides services for the following state change notifications to the Management Applications
***HA state of the SU changed
***SI partially/fully assigned
***Component arrived/departed
***Node arrived/departed

*'''Object Create/Delete and Attribute Change Notifications'''
**OpenClovis SAFplus Platform provides services for the notification of Managed Object Creation, Deletion and Attribute changes. It also supports the Management Applications to filter the attribute change notifications based on attribute identifiers.

*'''Notification Delivery Characteristics'''
**Guaranteed delivery
**At most once delivery
**Ordered delivery
**Persisted (Alarm notifications).

*'''Notification Filtering'''
**OpenClovis SAFplus Platform provides service for filtering the notifications based on one or more filter criteria which is particular to the notification type. It also provides the ability to correlate with the other notifications.

=='''Support for SAF AIS Interfaces'''==

OpenClovis SAFplus Platform complies with the SAF AIS interfaces for the following components:

===Availability Management Framework (AMF)===

OpenClovis Availability Management Framework (AMF) supports the following SAF AIS interfaces as mentioned in SAI-AIS-AMF-B.02.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of AMF'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saAmfInitialize()
* saAmfSelectionObjectGet()
* saAmfDispatch()
* saAmfFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Component Health Monitoring
|
* saAmfHealthCheckStart()
* saAmfHealthCheckStop()
* SaAmfHealthCheckCallbackT
* saAmfHealthCheckConfirm()
|- style="color:#ffffff; background:#549cc6"
|
Component Registration and Un-registration
|
* saAmfComponentRegister()
* saAmfComponentUnregister()
* saAmfComponentNameGet()
|- style="color:#ffffff; background:#549cc6"
|
Component Service Instance Management
|
* saAmfHAStateGet()
* SaAmfCSISetCallbackT
* SaAmfCSIRemoveCallbackT
* saAmfCSIQuiescingComplete()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of AMF'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Component Lifecycle Management
|
* SaAmfComponentTerminateCallbackT
* SaAmfProxiedComponentInstantiateCallbackT
* SaAmfProxiedComponentCleanupCallbackT
|- style="color:#ffffff; background:#549cc6"
|
Protection Group Management
|
* saAmfProtectionGroupTrack()
* SaAmfProtectionGroupTrackCallbackT
* saAmfProtectionGroupTrackStop()
|- style="color:#ffffff; background:#549cc6"
|
Component Error Reporting
|
* saAmfComponentErrorReport()
|- style="color:#ffffff; background:#549cc6"
|
Component Response
|
* saAmfResponse()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Unsupported API's of AMF'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Brief
!style="color:#66b154; background:#09477c"| Unsupported APIs
|- style="color:#ffffff; background:#549cc6"
|
Passive Monitoring of processes is not supported
|
* saAmfPmStart()
* saAmfPmStop()
|- style="color:#ffffff; background:#549cc6"
|
Freeing the memory allocated by the saAmfProtectionGroupTrack()
|
* saAmfProtectionGroupNotificationFree()
|- style="color:#ffffff; background:#549cc6"
|
Component Error Clear API is not supported.
|
* saAmfComponentErrorClear()
|}

===Checkpointing Service (CPS)===

OpenClovis Checkpointing Service (CPS) supports the following SAF AIS interfaces as mentioned in SAI-AIS-CKPT-B.01.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of CPS'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saCkptInitialize()
* saCkptSelectionObjectGet()
* saCkptDispatch()
* saCkptFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Checkpoint Management
|
* saCkptCheckpointOpen()
* saCkptCheckpointOpenCallabackT
* saCkptCheckpointOpenAsync()
* saCkptCheckpointClose()
* saCkptCheckpointUnlink()
* saCkptActiveReplicaSet()
* saCkptCheckpointRetentionDurationSet()
* saCkptCheckpointStatusGet()
|- style="color:#ffffff; background:#549cc6"
|
Section Management
|
* saCkptSectionIterationInitialize()
* saCkptSectionIterationNext()
* saCkptSectionIterationFinalize()
* saCkptSectionCreate()
* saCkptSectionExpirationTimeSet()
* saCkptSectionDelete()
* saCkptCheckpointWrite()
|- style="color:#ffffff; background:#549cc6"
|
Data Management
|
* saCkptSectionOverwrite()
* saCkptCheckpointRead()
* saCkptCheckpointSynchronize()
* saCkptCheckpointSynchronizeAsync()
* SaCkptCheckpointSynchronizeCallbackT
|}

===Event Manager (EM)===

OpenClovis Event Manager supports the following SAF AIS interfaces as mentioned in SAI-AIS-EVT-B.01.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of EM'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saEvtInitialize()
* saEvtFinalize()
* saEvtSelectionObjectGet()
* saEvtDispatch()
|- style="color:#ffffff; background:#549cc6"
|
Event Operations
|
* saEvtEventAllocate()
* saEvtEventFree()
* saEvtEventAttributesSet()
* saEvtEventAttributesGet()
* saEvtEventDataGet()
* saEvtEventPublish()
* saEvtEventSubscribe()
* SaEvtEventDeliverCallbackT
* saEvtEventUnsubscribe()
|- style="color:#ffffff; background:#549cc6"
|
Event Channel Operations
|
* saEvtChannelOpen()
* saEvtChannelOpenAsync()
* SaEvtChannelOpenCallbackT
* saEvtChannelUnlink()
* saEvtChannelClose()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Unsupported API's of EM'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Brief
!style="color:#66b154; background:#09477c"| Unsupported APIs
|- style="color:#ffffff; background:#549cc6"
|
Event Retention Time is not supported
|
* saEvtEventRetentionTimeClear()
|}

===Group Membership Service (GMS)===

OpenClovis Group Membership Service (GMS) supports the following SAF AIS interfaces as mentioned in AIS-CLM-B.01.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of GMS'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saClmInitialize()
* saClmSelectionObjectGet()
* saClmDispatch()
* saClmFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Group Membership Operations
|
* saClmClusterTrack()
* SaClmClusterTrackCallbackT
* saClmClusterTrackStop()
* saClmClusterNodeGet()
* saClmClusterNodeGetAsync()
* SaClmClusterNodeGetCallbackT
|}

===Messaging Service (MSG)===

OpenClovis Messaging Service (MSG) supports the following SAF AIS interfaces as mentioned in SAF-AIS-MSG-B.02.01.

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of MSG'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Library Lifecycle Management
|
* saMsgInitialize()
* saMsgSelectionObjectGet()
* saMsgDispatch()
* saMsgFinalize()
|- style="color:#ffffff; background:#549cc6"
|
Message Queue Operations
|
* saMsgQueueOpen()
* saMsgQueueOpenAsync()
* SaMsgQueueOpenCallbackT
* saMsgQueueClose()
* saMsgQueueStatusGet()
* saMsgQueueRetentionTimeSet()
* saMsgQueueUnlink()
|- style="color:#ffffff; background:#549cc6"
|
Management of Message Queue Groups
|
* saMsgQueueGroupCreate()
* saMsgQueueGroupInsert()
* saMsgQueueGroupRemove()
* saMsgQueueGroupDelete()
* saMsgQueueGroupTrack()
* SaMsgQueueGroupTrackCallbackT
* saMsgQueueGroupTrackStop()
* saMsgQueueGroupNotificationFree()
|}

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''Supported API's of MSG'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
Message Send and Receive Operations
|
* saMsgMessageSend()
* saMsgMessageSendAsync()
* SaMsgMessageDeliveredCallbackT
* saMsgMessageGet()
* saMsgMessageDataFree()
* SaMsgMessagedReceivedCallbackT
* saMsgMessageCancel()
|- style="color:#ffffff; background:#549cc6"
|
Request and Reply Operations
|
* saMsgMessageSendReceive()
* saMsgMessageReply()
* saMsgMessageReplyAsync()
|}

=='''Software Management Framework (SMF)'''==

SMF Aligned In Service Software Upgrade (ISSU.
Supports application and OpenClovis SAFplus Platform middleware upgrade in a rolling (in-service) or single-step mode.

'''Single-Step'''
For deployment of non-backwards compatible software, or rapid deployment of software. This method stops the relevant services on all nodes (causing an outage) and then upgrades that software and restarts. Note that services are stopped at various granularity levels depending on what is being upgraded. In other words, application A can be taken out-of-service and upgraded across the cluster without affecting application B running on the same nodes.

'''Inservice Rolling'''
This is the most commonly known telecom quality upgrade method. For deployment of backwards-compatible software across the cluster, this method stops service in one "upgrade unit" at a time, upgrades the software and restarts before stopping the next "upgrade unit". This process continues iteratively until the entire cluster is upgraded. Since the available redundant capacity takes over for the unit being upgraded service will be unaffected.

=='''Hardware Platform Interface (HPI)'''==

SAFplus Platform has been integrated and tested with the following implementations of HPI B.01.01 specification.
* OpenHPI 2.8.1, 2.10.2, 2.16.0
* Radisys HPI 1.4

The following sections lists out the SAF HPI APIs that are used by SAFplus Platform. Platform provider shall provide at these HPI services in order to integration with OpenClovis SAFplus Platform

{| border="0" cellpadding="3" align="center" width="680"
|+ align="bottom" | '''SAF HPI APIs used by SAFplus'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c" width="350"| Services
!style="color:#66b154; background:#09477c"| Supported APIs
|- style="color:#ffffff; background:#549cc6"
|
General APIs
|
* saHpiVersionGet()
|- style="color:#ffffff; background:#549cc6"
|
Domain APIs
|
* saHpiSessionClose()
* saHpiSessionOpen()
* saHpiDiscover()
* saHpiRptEntryGet()
* saHpiRptEntryGetByResourceId()
* saHpiSubscribe()
* saHpiUnsubscribe()
* saHpiEventGet()
|- style="color:#ffffff; background:#549cc6"
|
Resource APIs
|
* saHpiRdrGet()
* saHpiAutoExtractTimeoutSet()
* saHpiAutoInsertTimeoutSet()
* saHpiHotSwapPolicyCancel()
* saHpiResourceActiveSet()
* saHpiResourceInactiveSet()
* saHpiHotSwapStateGet()
* saHpiHotSwapActionRequest()
* saHpiHotSwapIndicatorStateGet()
* saHpiResourceResetStateSet()
* saHpiResourcePowerStateSet()
|}

In addition to the above APIs SAFplus Platform also depends on the following events generated by HPI
# Hot Swap events (SAHPI_ET_HOTSWAP)
# Sensor events (SAHPI_ET_SENSOR)
# Resource Events (SAHPI_ET_RESOURCE)

=='''Modifications to SAF AIS Header files'''==

In a few instances, OpenClovis engineers found that the standard SAF-supplied header files caused errors and warnings on certain compilers. In these cases OpenClovis modified the standard SAF header file to work with these compilers. All of these changes broaden the set of compatible compilers. None of these changes modify the SAF APIs.

For example, in saAis.h, the following constant is defined:

#define SA_TIME_ONE_MINUTE 60000000000

However, the number defined is greater than a 32-bit integer, so it is actually required to append a size suffix:

#define SA_TIME_ONE_MINUTE 60000000000LL

Doc:latest/tutorial

2012-02-21T03:24:20Z

MediaWiki spam cleanup: Reverting to last revision not containing links to www.buyxanaxitem.com

http://www.buyxanaxonlinepill.com/ buy xanax online - generic xanax online

http://www.buyxanaxonlinepill.com/ purchase online generic xanax - xanax buy online

==Creating the csa101 Model==
The first step in setting up our example is to create a model which represents the system that we will eventually deploy. This is done through the '''SAFplus Platform IDE'''. In this chapter we will step through the following tasks:
* Create a project area
* Launch the '''SAFplus Platform IDE'''
* Create the IDE project
* Specify the Resource model (the types of physical hardware in our system)
* Specify the Component model (the types of components or applications in our system)
* Specify which Components run on which Resources
* 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===
You can launch the '''SAFplus Platform IDE''' from the command line. If you chose to create symbolic links during installation you can simply enter <code>'''cl-ide'''</code> from any directory. If you did not create symbolic links during installation you can either:

<ul>
<li>Add the installation directory to the shells search path and then launch the IDE. For example with a bash shell,
<code><pre>
# export PATH=$PATH:$install_dir/sdk-5.0/bin
# cl-ide
</pre></code>
or
<li>Execute the command
<code><pre>
# <install_dir>/sdk-5.0/bin/cl-ide
</pre></code>
</ul>

The splash screen for SAFplus Platform IDE is displayed as illustrated in Figure [[#SAFplus Platform IDE Opening Screen | SAFplus Platform IDE Opening Screen]].

[[File:Tutorial_GettingStartedIDE_OpeningScreen.png|frame|center| '''SAFplus Platform IDE Opening Screen''' ]]

You will then be prompted to select a workspace in which to do your work as illustrated in Figure [[#SAFplus Platform IDE Workspace Launcher | SAFplus Platform IDE Workspace Launcher]].

[[File:Tutorial_GettingStartedIDE_WorkspaceLauncher.png|frame|center| '''SAFplus Platform IDE Workspace Launcher''' ]]

The workspace you select should correspond to the project area that you created in the previous section (in this case "/home/clovis/projectarea1"). Note that the workspace includes a subdirectory of "/ide_workspace". This is done strictly for organizational purposes. It keeps the IDE models separate from the generated SAFplus Platform models and code.
<ul>
<li>Select the workspace and click '''OK''' to launch SAFplus Platform IDE as illustrated in the Figure [[#SAFplus Platform IDE Welcome Screen | SAFplus Platform IDE Welcome Screen]].
</ul>

[[File:Tutorial_WelcomeScreen.png|frame|center| '''SAFplus Platform IDE Welcome Screen''' ]]

The '''SAFplus Platform''' IDE is launched and you are now looking at the main work area. For more information about the components of this main work area including the SAFplus Platform IDE menu and toolbar, see ''SAFplus Platform IDE User Guide''.

===Creating the Sample Project===
We will now create a project within the '''SAFplus Platform IDE'''. This project will hold both the resource model and the component model for our example system. The resource model is a physical view of the resources (the chassis, the blade types, etc.) in our system. The component model is a logical view of the components (applications, etc.) in our system.

We will be using the '''New Project Wizard''' to create our project. The wizard captures some high-level information about the system that we are building and performs a lot of the basic setup for us.

[[File:OpenClovis_Note.png]]The same model that we are building through the wizard could also be created manually through the Resource and Component Editors. For more information on the Resource and Component Editors see ''SAFplus Platform IDE User Guide''.

To launch the '''New Project Wizard''' select '''File''' > '''New''' > '''Project''' from the IDE menu bar.

The '''New Project Wizard''' is displayed and '''Clovis System Project''' is selected by default as illustrated in Figure [[#New Project Wizard | New Project Wizard]].

[[File:Tutorial_GettingStartedIDE_NewProjectWizard.png|frame|center| '''New Project Wizard''' ]]

Click '''Next'''. The '''Clovis System Project''' window is displayed as illustrated in Figure [[#Clovis System Project | Clovis System Project]].

[[File:Tutorial_NewProject.png|frame|center| '''Clovis System Project''' ]]

Enter the following information:

<ul>
<li>'''Project Name''' : Enter the name of your new project as '''SampleModel'''.
 [[File:OpenClovis_Note.png]]Do not use spaces or special characters for the project name. The project name can be alphanumeric, but cannot start with a number or have only numbers.
 Select '''Use default''' to use the same directory mentioned in the '''Directory''' field.

<li>'''SDK Location''': Enter the location where the SAFplus Platform SDK was installed. For e.g. if the SDK was installed at location /opt/clovis, then the SDK location is /opt/clovis/sdk-<version>.

<li>'''Project Area Location''': Enter the location where the generated source code for the model should be stored.
 [[File:OpenClovis_Note.png]]This can be any existing directory but is usually the project area that was created in the previous section.

<li>'''Python Location''': Enter the location where Python 2.5.0 is installed on your system. If Python 2.5.0 was installed by SAFplus Platform SDK, the directory is <code>'''<installation_directory>/buildtools/local/bin'''</code>.
</ul>

Click '''Next'''. The '''Add New Blade Type''' window is displayed. This dialog is used to define the blade types that are in our system.

[[File:Tutorial_AddBlade.png|frame|center| '''Add New Blade Type''' ]]

Remember that the system we are modelling has only one blade type...a System Controller.
<ul>
<li>Use the '''Add''' button to add a new blade type to the list. Name this blade type 'SysBlade' (for System Controller blade).
</ul>

Click '''Next'''. The '''Add New SAF Node Type''' window is displayed. This dialog is used to define the type of logical node that will be run on the corresponding blade type defined in the previous dialog.

[[File:Tutorial_AddNode.png|frame|center| '''Add New SAF Node Type''' ]]

Node types represent groups of software. They are classified as either a System Controller class or a Payload class. This distinction gives the node type certain characteristics which cause it to behave in a well-defined manner. Since we have only a System Controller in our system we will add a node type of class System Controller.

<ul>
<li>Use the '''Add''' button to add a new node type to the list. Name the node type 'SCNode' and ensure that its node class is 'System Controller (SAF Class B)'.
</ul>

Click '''Next'''. The '''Specify Program Names''' window is displayed. This dialog is used to create programs or SAF Service Types and associate them with the SAF Node Types specified in the previous dialog.

[[File:Tutorial_DefineProgramNames.png|frame|center| '''Specify Program Names''' ]]

In our system we need one SAF Service Type which represents our high availability software (csa101 that continously prints "Hello World!").

<ul>
<li>Use the '''Add''' button to add a program name to the list. Change the program name to 'csa101' and associate the program with the 'SCNode' node type.
</ul>

Click '''Finish'''. This will create the sample model using the blade type, node type, and program name information collected through the 'New Project Wizard' dialogs.

===Viewing the Model===

====The SAFplus Platform IDE Perspective====
Once the wizard pages are closed you will be returned to the main IDE view also known as the '''SAFplus Platform IDE Perspective'''. On the left hand side of this view you will see the '''Clovis Workspace''' pane which contains the new project you just created with all project related files and folders. The folders are displayed based on your filter settings. With the default filter settings, the folders shown in Figure [[#Clovis Workspace|Clovis Workspace]] is displayed in the '''Clovis Workspace''' pane. For information about filter settings, refer ''SAFplus Platform IDE User Guide''.

[[File:Tutorial_GettingStartedIDE_ClovisWorkspace.png|frame|center|Clovis Workspace]]

By default, the '''Resource''' and '''Component''' Editor views are available for the created project. To view them, click '''Clovis''' on the menu bar at the top of the screen and select '''Resource Editor''' or '''Component Editor''' from the menu. You can also click '''Resource Editor''' or '''Component Editor''' icons from the tool bar as shown in Figure [[#SAFplus Platform IDE Tool Bar | SAFplus Platform IDE Tool Bar]].

[[File:Tutorial_Toolbar.png|frame|center| '''SAFplus Platform IDE Tool Bar''' ]]

====Resource Editor View====
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.

[[File:Tutorial_ResourceEditor.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'''.

On the right hand side of the editor view you will see the '''Palette''' which can be expanded and collapsed. Expanding the '''Palette''' you will see the list of objects that can be dragged onto the editor view to add to our model. Once an object is on the editor view you can view and change its properties by right clicking on the object and selecting '''Properties...''' from the context menu.

For more information about the '''Resource Editor''' view see ''SAFplus Platform IDE User Guide''.

====Component Editor View====
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.

[[File:Tutorial_ComponentEditor.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.

On the right hand side of the editor view you will see the '''Palette''' which can be expanded and collapsed. Expanding the '''Palette''' you will see the list of objects that can be dragged onto the editor view to add to our model. Once an object is on the editor view you can view and change its properties by right clicking on the object and selecting '''Properties...''' from the context menu.

For more information about the '''Component Editor''' view see ''SAFplus Platform IDE User Guide''.

===Configuring the Components===
The '''New Project Wizard''' that we used to create our project configured the system using the most common options. We will have to make a few changes to this model in order for our example to work. We will make these changes in the '''Component Editor''' view.

In the Component Editor you will notice seven different objects that were created by the wizard. The first two of these are:
<ul>
<li>Cluster: The root object of all other objects in the Component Editor view.
<li>SCNode: This is the SAF Node Type that we specified during project creation.
</ul>

The next five objects all make up the Program or SAF Service Type that we specified on the last dialog of the New Project Wizard. These objects are:

<ul>
<li>csa101SG: This is the Service Group representing our high availability software component.
<li>csa101SU: This is the Service Unit that is logically associated with the SCNode SAF Node Type.
<li>csa101SI: This is the Service Instance
<li>csa101CSI: This is the Component Service Instance
<li>csa101: This is the SAF Component which represents our program or executable.
</ul>

We will be making changes to the Service Group (csa101SG), the Service Instance (csa101SI), and the SAF Component (csa101).

====Configuring the Service Group====
To make changes to the Service Group double-click on the box titled '''csa101SG'''. The '''Service Group Details''' dialog is displayed.

[[File:Tutorial_ServiceGroupDetails.png|frame|center| '''Service Group Details''' ]]

<ul>
<li>The first change we want to make is to the '''Redundancy Model'''. The '''Redundancy Model''' is the strategy that is used by the SAFplus Platform system to recover from a node failure. For our simple model (which only has one node) we are not going to rely on any failover recovery so change the '''Redundancy Model''' to 'No Redundancy' as shown.
 [[File:OpenClovis_Note.png]]You will notice that when you change the redundancy model some of the other fields are modified automatically and become read-only. This is to ensure integrity of the redundancy models.

<li>The second change that we want to make is to the '''Admin State'''. The '''Admin State''' defines the state of the component when the system is first brought up. In our case we want to change the '''Admin State''' to be 'Locked Initialized'. This means that when the system first starts up this '''Service Group''' (and its subcomponents) will be initialized but not yet put into a running state. So our csa101 application will not yet start printing "Hello World!".

<li>When you are finished making the changes click the '''OK''' button to commit the changes.
</ul>

====Configuring the Service Instance====
To make changes to the Service Instance double-click on the box titled '''csa101SI'''. The '''Service Instance Details''' dialog is displayed.

[[File:Tutorial_ServiceInstanceDetails.png|frame|center| '''Service Instance Details''' ]]

<ul>
<li>The only change we want to make here is to the '''Number of standby assignments'''. This value represents the number of components that will be waiting to take over during a node failure and goes hand-in-hand with the '''Redundancy Model''' that we selected for the Service Group. Since we selected 'No Redundancy' for our '''Redundancy Model''' we need to set this value to 0...since we are not supporting any failover in this model.

<li>When you are finished making the changes click the '''OK''' button to commit the changes.
</ul>

====Configuring the SAF Component====
To make changes to the SAF Component double-click on the box titled '''csa101'''. The '''SAF Component Details''' dialog is displayed.

[[File:Tutorial_SAFComponentDetails.png|frame|center| '''SAF Component Details''' ]]

The SAF Component represents our high availabilty program or executable. We need to pass a command line argument to this executable. The reason for this argument is to force the program to print the 'Hello World!' output to a special log file for our viewing. We will look at this more closely when we customize our code.

<ul>
<li>To add command line parameters click the '''Edit...''' button corresponding to the '''Command line Arguments''' label.
</ul>

The '''Command line Argument Details''' dialog is displayed.

[[File:Tutorial_CommandLineArgs.png|frame|center| '''Command line Argument Details''' ]]

<ul>
<li>Click the '''New''' button to add a new value to the list.
<li>Click on the new value in the list and it will become editable. Change the value to '''-p'''.
<li>Click the '''OK''' button to save and close the dialog.
<li>Click the '''OK''' button on the '''SAF Component Details''' dialog to commit the changes to the SAF Component and close the dialog.
<li>Save the component model using the '''File > Save''' menu item.
</ul>

===Configuring Physical Instances===
The configuration of our logical models is complete. During this process we have defined all of the 'types' of objects in our system. Now it is time to configure actual instances of those objects so that they can be built and deployed.

Object instance configuration is done through the Availability Management Framework (AMF) via the '''AMF Configuration''' dialog.

<ul>
<li>To launch this dialog go to the the '''Clovis''' menu and select '''AMF Configuration...'''
</ul>

The '''AMF Configuration''' dialog is displayed.

[[File:Tutorial_AMFConfig.png|frame|center| '''AMF Configuration Dialog''' ]]

You will note from the instructions on this page that the physical instances representing the objects in our model can be created manually or by using wizards. Using the wizards will save us both typing and time so we will use these instead of creating each instance manually.

====Creating Node Instances====
First we will create actual instances of the Node Types (in our case only one Node Type...SCNode) we created in our model.

<ul>
<li>Double-click AMF Configuration in the left hand pane. The Node Instance List appears.
<li>Click on Node Instance List. The right hand pane displays the fields we must fill out to create our node instance.
</ul>

In the right hand pane:

<ul>
<li>Select SCNode for the '''Node Type'''.
<li>Select SysBlade for the '''Blade type'''.
<li>Enter 1 for the '''Node Count'''.
</ul>

The complete form should look like the following.

[[File:Tutorial_AMFNodeWizardDetails.png|frame|center| '''Node Wizard Details''' ]]

<ul>
<li>Click the '''Create Instance Tree''' button to create our node instance.
</ul>

Expanding the '''Node Instance List''' branch of the '''AMF Configuration''' tree in the left-hand pane reveals a new node instance named SCNodeI0 (indicating SCNode Instance 0).

====Creating Service Group Instances====
Now we will create actual instances of the Service Groups that we defined in our model.

<ul>
<li>Click on Service Group List. The right hand pane displays the fields we must fill out to create our service group instance.
</ul>

In the right hand pane:

<ul>
<li>Select csa101SG (the only service group type we defined) for the '''Service Group Type'''.
*The '''Associated Node Instances''' list will be populated with all of the node instances that can be associated with the selected service group type.
<li>Select SCNodeI0 from the '''Associated Node Instances''' list.
</ul>

The completed form should look like the following.

[[File:Tutorial_AMFSGWizardDetails.png|frame|center| '''Service Group Wizard Details''' ]]

<ul>
<li>Click the '''Create Instance Tree''' button to create our service group instance.
</ul>

 
If you now completely expand the '''AMF Configuration''' branch of the tree in the left-hand pane you will see the following.

[[File:Tutorial_AMSConfigDetails.png|frame|center| '''AMF Configuration Instance Details''' ]]

Notice that not only have the wizards created the node and service group instances for you, they have also filled out the entire instance tree. This was accomplished based on two key sets of information. The first of these is the association that was made between the service group type and the node instance in the '''Service Group Wizard'''. The second set of information is the component model that we created through the New Project Wizard and the Component Editor.

 [[File:OpenClovis_Note.png]]For more information regarding the specific properties of the generated instances see [[#Appendix B: AMF Configuration Instance Details|Appendix B: AMF Configuration Instance Details]].

 
Thats it. We are done modelling the csa101 example!
<ul>
<li>Click the OK button to commit our changes and close the dialog.
</ul>
Now its time to generate the framework code.

==Generating the csa101 Code==
In this step we generate the source code for our example. The code that will be created is the framework code that handles all of the low level functionality provided by SAFplus Platform.

To generate the source code go to the '''Project''' menu and select '''Generate Source'''. Several progress dialogs will appear and after a few seconds code generation will be complete.

The source code and configuration XML files are generated and placed in subdirectories of the '''Project Area Location''' that we specified in the '''New Project Wizard'''. You can review this location by using the '''Project > Properties''' menu to get to the '''Project Properties''' dialog and then selecting '''Clovis System Project''' in the left hand pane.

You can review the generated code from within the SAFplus Platform IDE. To do this go to the '''Clovis Workspace''' pane and expand the '''SampleModel''' node. The node tree should look like the following.

[[File:Tutorial_CWCodeTree.png|frame|center| '''Clovis Workspace Code Tree''' ]]

The code of particular interest to our example is in the SampleModel/src/app/csa101 branch of the tree. This is the code for our csa101 example. The csa101 example consists of two C modules (<code>clCompAppMain.c</code> and <code>clCompCfg.c</code>) and two header files. There is also a make file that will be used for building the application. The <code>clCompAppMain.c</code> file implements our 'Hello World!' application.

 [[File:OpenClovis_Note.png]]If you run code generation a second time you will be presented with a dialog box asking if you would like to make a backup copy of the existing source code before proceeding. You can answer No to this dialog.

==Customizing the csa101 Code==
While the code that was generated in the previous section can be built and run we want to make some changes to it so that we can easily see what our example is doing. For our example we will be changing one source file (<code>clCompAppMain.c</code>) and two make files.
 [[File:OpenClovis_Note.png]]In a real production situation this is the point where you would customize the code to perform the specific tasks of your product.

You will notice in the C file that there are several places where you see the following comment block.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>

/*
---BEGIN_APPLICATION_CODE---
*/

// ...

/*
---END_APPLICATION_CODE---
*/
</pre></code>
|}

Makefiles have a similar convention but with a slightly different syntax.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|Makefile
|-
|<code><pre>

# ---BEGIN_APPLICATION_CODE---

# ---END_APPLICATION_CODE---
</pre></code>
|}

These are sections of the file where it is safe to enter custom application code without having to worry about that code being overwritten if you were to again perform '''Generate Source''' for your model. This is important since the typical development cycle is an iterative process where you will return to the IDE to make modifications to your model.

To simplify the process of building and running the csa101 example, OpenClovis, Inc. has already made the necessary code customizations and shipped this code with the SAFplus Platform SDK. At this point you can simply replace the generated source files with these customized versions to avoid typing in the changes. We will go over each customization below and explain what was done.

To replace the generated files with the customized versions shipped with the SAFplus Platform SDK follow these instructions.
 [[File:OpenClovis_Note.png]] The sample applications containing the csa101 example can be found under the installation directory at <code><install_dir>/sdk-5.0/src/examples/eval</code>. We will refer to this directory in the remaining of this section as <code><eval_dir></code>.

<ol>
<li>Exit the SAFplus Platform IDE using the '''File > Exit''' menu item. If you are prompted to save changes before exiting answer yes.
<li>Navigate to the source code work area.
<code><pre># cd /home/clovis/projectarea1/ide_workspace/SampleModel/src/app</pre></code>
<li>Using your favorite editor open the file <code>Makefile</code> that resides in this directory. This is the application make file.
<li>Add the following line to this file within the first <code>BEGIN_APPLICATION_CODE</code> and <code>END_APPLICATION_CODE</code> comment block.
<code><pre>SUBDIRS += ev</pre></code>
This will instruct the build process to build our custom output library.
<li>Save this file and exit the editor.
<li>Execute the following command to copy the output package to our working area.
<code><pre># cp -r <eval_dir>/src/app/ev .</pre></code>
<li>Navigate to the component code work area.
<code><pre># cd csa101</pre></code>
<li>Execute the following command to copy the csa101 source code.
<code><pre># cp <eval_dir>/src/app/csa101/clCompAppMain.c .</pre></code>
<li>Execute the following command to copy the component make file.
<code><pre># cp <eval_dir>/src/app/csa101/Makefile .</pre></code>
<li>Restart the SAFplus Platform IDE.
<code><pre># cl-ide</pre></code>
</ol>

===Customizing clCompAppMain.c===
The <code>clCompAppMain.c</code> file is the C module which will implement our 'Hello World!' behavior. We have to make changes in several parts of this file.
 [[File:OpenClovis_Note.png]]If you copied the files as instructed in the section above then these changes have already been made to the files. Use this section to review and understand the changes.

<ol>
<li>In the include section of this file we have added a new include for <code>ev.h</code>. This refers to a special output library that we copied to our work area in the previous section. This output library is used to redirect output from the application to a component specific log. This is purely cosmetic but it will allow us to easily monitor what is happening when we run our example. (The following code begins at line 44 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
---BEGIN_APPLICATION_CODE---
*/

#include "clCompAppMain.h"
#include "../ev/ev.h"

/*
---END_APPLICATION_CODE---
*/
</pre></code>
|}

<li>Next we define a couple of static variables that will keep track of the state of our application and a function to aid in showing when the application is running. (The following code begins at line 79 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
---BEGIN_APPLICATION_CODE---
*/

static int running = 0;
static int exiting = 0;

static char*
show_progress(void)
{
static char bar[] = " .";
static int progress = 0;

/* Show a little progress bar */
return &bar[sizeof(bar)-2-(progress++)%(sizeof(bar)-2)];
}

/*
---END_APPLICATION_CODE---
*/
</pre></code>
|}

The <code>running</code> flag will be used to indicate whether the current application is active or suspended while <code>exiting</code> is a flag that indicates that the main() function returns, causing the exit of the application.

The function <code>show_progress</code> returns a pointer to a c string with a number of spaces followed by a '.' character. The number of spaces in the string cycles from zero to an upper bound. This is used later on to provide visual indication of the progress of the application's output.

<li>Next we have added a function <code>hello_func</code> to print the output. (The following code begins at line 118 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>

void *hello_func(void *unused)
{
while (!exiting)
{
if (running)
{
clprintf(CL_LOG_SEV_INFO, "csa101: Hello World! %s\n", show_progress());
}
sleep(1);
}

return NULL;
}

</pre></code>
|}

Notice the while loop condition. This function uses the <code>exiting</code> variable that was initialized to 0. The loop will keep running until <code>exiting</code> is set to non-zero. The if condition within the while loop checks the value of the <code>running</code> variable. The work of the application: printing "Hello World!" along with the progress indicator will only be done when the <code>running</code> variable is set non-zero. Next the command <code>sleep(1)</code> simply sleeps for a second so as not to fill log files too quickly or completely swamp the CPU.

When <code>exiting</code> becomes non-zero, we return from the function.

<li>Next we have added a function to initialize the special output library mentioned earlier (which is at line 245 in the source file).

<li>Next we create a thread and call the function <code>hello_func</code> in the new thread context. (The following code begins at line 252 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/
clprintf(CL_LOG_SEV_INFO, "csa101: Instantiated as component instance %s.\n", appName.value);

clprintf(CL_LOG_SEV_INFO, "%s: Waiting for CSI assignment...\n", appName.value);

rc = clOsalTaskCreateDetached("hello_thread", CL_OSAL_SCHED_OTHER, CL_OSAL_THREAD_PRI_NOT_APPLICABLE, 0, hello_func, NULL);
CL_ASSERT(rc == CL_OK);

/*
* ---END_APPLICATION_CODE---
*/

</pre></code>
|}

<li>Next we indicate to our app when we are exiting. (The following code begins at line 284 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/

exiting = 1;
clEvalAppLogStreamClose(gEvalLogStream);

/*
* ---END_APPLICATION_CODE---
*/

</pre></code>
|}

We set the <code>exiting</code> variable to 1. This will cause the loop in our <code>hello_func</code> function to exit.

<li>Next we will put in code to manage the state of our application. (The following code begins at line 453 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
void clCompAppAMFCSISet(SaInvocationT invocation,
const SaNameT *compName,
SaAmfHAStateT haState,
SaAmfCSIDescriptorT csiDescriptor)
{
/*
* ---BEGIN_APPLICATION_CODE---
*/

// ...

/*
* ---END_APPLICATION_CODE---
*/

/*
* Print information about the CSI Set
*/

clprintf (CL_LOG_SEV_INFO, "Component [%.*s] : PID [%d]. CSI Set Received\n",
compName->length, compName->value, mypid);

clCompAppAMFPrintCSI(csiDescriptor, haState);

/*
* Take appropriate action based on state
*/

switch ( haState )
{
case SA_AMF_HA_ACTIVE:
{
/*
* AMF has requested application to take the active HA state
* for the CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/

clprintf(CL_LOG_SEV_INFO, "csa101: ACTIVE state requested; activating service\n");
running = 1;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);
break;
}

</pre></code>
|}

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>

case SA_AMF_HA_STANDBY:
{
/*
* AMF has requested application to take the standby HA state
* for this CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/

clprintf(CL_LOG_SEV_INFO, "csa101: New state is not the ACTIVE; deactivating service\n");
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);
break;
}

case SA_AMF_HA_QUIESCED:
{
/*
* AMF has requested application to quiesce the CSI currently
* assigned the active or quiescing HA state. The application
* must stop work associated with the CSI immediately.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
clprintf(CL_LOG_SEV_INFO, "csa101: Acknowledging new state\n");
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);
break;
}

</pre></code>
|}
{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
case SA_AMF_HA_QUIESCING:
{
/*
* AMF has requested application to quiesce the CSI currently
* assigned the active HA state. The application must stop work
* associated with the CSI gracefully and not accept any new
* workloads while the work is being terminated.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
clprintf(CL_LOG_SEV_INFO, "csa101: Signaling completion of QUIESCING\n");
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfCSIQuiescingComplete(amfHandle, invocation, SA_AIS_OK);
break;
}
</pre></code>
|}

We have modified the <code>clCompAppAMFCSISet</code> callback function to let our application know what to do when the state changes. In the case where the state changes to <code>SA_AMF_HA_ACTIVE</code> we set the <code>running</code> variable to 1. This will cause our application to begin printing the 'Hello World!' message. For any other state change we set the <code>running</code> variable to 0 which will cause the message to stop printing. For any state change we print out a message indicating the new state of the application.

<li>The last change that we make is to indicate to our application when the component is being disassociated with the workflow. (The following code begins at line 588 of the source file.)

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clCompAppMain.c
|-
|<code><pre>
void clCompAppAMFCSIRemove(SaInvocationT invocation,
const SaNameT *compName,
const SaNameT *csiName,
SaAmfCSIFlagsT csiFlags)
{
....

/*
* Add application specific logic for removing the work for this CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
running = 0;

/*
* ---END_APPLICATION_CODE---
*/

saAmfResponse(amfHandle, invocation, SA_AIS_OK);

return;
}
</pre></code>
|}

In the <code>clCompAppAMFCSIRemove</code> callback function we indicate to our application that we are no longer running so that the while loop in the <code>hello_func</code> function stops printing our 'Hello World!' message.
</ol>

===Customizing the Component MakeFile===
We have to make a small change to the component <code>MakeFile</code> so that it knows about our special output library during the build. To do this we add the following lines. This file is located in <code>/home/clovis/projectarea1/ide_workspace/SampleModel/src/app</code>

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|Component MakeFile
|-
|<code><pre>
# ---BEGIN_APPLICATION_CODE---

SUBDIRS += ev

# ---END_APPLICATION_CODE---
</pre></code>
|}

===Customizing the Application MakeFile===
We have to make sure that our special output library is built along with our application. To do this we change the line listing the sudirectories to make as follows. This file is located in the directory <code>/home/clovis/projectarea1/ide_workspace/SampleModel/src/app/csa101</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|Application MakeFile
|-
|<code><pre>
# ---BEGIN_APPLICATION_CODE---

...

# Library added for demo console handling for the evaluation kit
ASP_LIBS += libeval.a

# ---END_APPLICATION_CODE---
</pre></code>
|}

We are finished customizing our application code!

==Building the csa101 Code==

Now that we have finished customizing the code it is time to build it. The build process is launched using the '''Project > Build Project''' menu item. Once selected the '''Build Configuration''' dialog appears.

[[File:Tutorial_BuildConfigDetails.png|frame|center| '''Build Configuration Details''' ]]

The '''Build Configuration''' dialog is used to gather specific information about the build we are about to perform. Using this dialog you can rebuild the same model using different cross builds, or including different chassis managers. We don't have to make any changes to this dialog since the default settings make sense for our sample application.

 [[File:OpenClovis_Note.png]]If you have prebuilt the SAFplus Platform libraries then you can check the '''Use pre built SAFplus''' checkbox and include the location of the prebuilt libraries. For more information about pre-building SAFplus Platform libraries, see ''SAFplus Platform SDK User Guide''.

 [[File:OpenClovis_Note.png]]The '''Include SNMP for North Bound Access''' control is checked by default. This just means that Net SNMP will be started along with our system. If you want end-to-end connectivity you will need to supply an SNMP Sub Agent and a MIB. See the ''SAFplus Platform SDK User Guide'' for more details.

 [[File:OpenClovis_Note.png]]In the '''Project''' menu if the '''Build Project''' entry is not highlighted, then click in the right pane i.e. '''Clovis Workspace''' pane and click the '''Project''' menu again. This not highlighting of the '''Build Project''' is because the '''Clovis Workspace''' is not selected properly because of moving focus to some other pane.

 Click the '''OK''' button to begin the build. If this is the first time that the project is being built, or if you have made changes to any setting on this screen, you will initially see a progress dialog indicating that the project is being configured. The configuration step is setting up the project for building. After the configuration has completed you will see a progress dialog indicating that the code is being built.

==Creating the csa101 Images==

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.

[[File:Tutorial_MakeImagesConfigDetails.png|frame|center| '''Make Images Configuration Details''' ]]

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.
<li>Click '''OK''' to begin the make image process. A dialog box will appear and after a few seconds the the make images process will be complete.
</ul>

The images will be populated at <project_area>/target/SampleModel/images. Each node-specific image is provided as a directory containing the run-time files (binaries, libraries, prerequisites, and configuration files) as well as a tarball with the same content. e.g. For our model containing one node (<code>SCNodeI0</code>) the following files and directories are generated for deployment on the run-time system.
<code><pre>
<project_area>
|+target
|+<model>
|+images
|+SCNodeI0
| |+bin
| |+etc
| |+lib
| |+modules
| |+share
|-SCNodeI0.tgz
</pre></code>

The rest of the steps in this example are all done from the command line so we can exit the IDE. To do this use the '''File > Exit''' menu item.

==Deploying the csa101 Images==
Now that the image has been built we must deploy it so that we can run and observe our example. Since we are assuming that the example will be run on the same machine as the images were built this is a fairly trivial exercise. Use the following steps to deploy the runtime image.

<ol>
<li>First we create a directory where we will install the image. In our case we will use <code>/root/asp</code>.
<code><pre>
# cd /root
# mkdir asp
</pre></code>
<li>Next we navigate to that directory and untar the deployment package.
<code><pre>
# cd /root/asp
# tar xzvf /home/clovis/projectarea1/target/SampleModel/images/SCNodeI0.tgz
</pre></code>
</ol>

The System Controller is now installed and ready to run.

[[File:OpenClovis_Note.png]] If you were going to run the example on a machine other than the one where the images were built you would first copy the installation tarball to that machine before performing the above steps.

==Running the csa101 Example==
There are two parts to running the csa101 example. First we must start SAFplus Platform, and then we interact with the system components.

===Starting SAFplus Platform===

To start SAFplus Platform on System Controller node.
<ol>
<li>Open a shell.
<li>Run the following commands
<code><pre>
# cd /root/asp
# etc/init.d/asp start
</pre></code>
</ol>

[[File:OpenClovis_Note.png]] This assumes that you are running the SAFplus Platform example on the same PC that you are executing these commands. If you are running SAFplus Platform on a different machine then you should first ssh to that machine before executing the commands.

[[File:OpenClovis_Note.png]] If SAFplus Platform fails to start properly it could be due to the machine's firewall being enabled. SAFplus Platform will not run on a machine which has firewall enabled. See the ''Environment Related Observation'' section of the ''SAFplus Platform Release Notes'' for more information.

[[File:OpenClovis_Note.png]] By default the network interface used by the Group Membership Service is set to eth0. During the make images phase of the tutorial we also set the ethernet interface for node SCNodeI0 to be eth0. During image generation these configuration parameters are written to two files in the deployment package.
*<code>/root/asp/etc/clGmsConfig.xml</code>
*<code>/root/asp/etc/asp.conf</code>

There may be an occasion where you want to switch this interface for a machine on which you are deploying. If you would like to switch this interface on a machine without having to go through the process of rebuilding and redeploying, you can edit these two files and change the 'eth0' references to the interface you would like to use.

===Interacting with the System Components===
Once SAFplus Platform is up and running the next step is to start csa101 by informing SAFplus Platform that it should start the application. The Evaluation System's model tells SAFplus Platform that csa101 is locked for instantiation. This means that the process will not be started when SAFplus Platform comes up. This method of starting csa's is used for the Evaluation System, allowing users to interact with csa's and clearly see their output/functionality. Usually this would not be the case with applications, where they would run when SAFplus Platform begins.

At this point it would help to be familiar with the Service Availability Forum's notions of Service Unit, Service Group, and administrative state. The Service Availability Forum's Application Interface Specification (available from http://www.saforum.org/) is a good place to start.

In brief, the sample applications in the Evaluation System are part of service units which in turn are part of service groups. Service groups (and the service units that make up the service groups) can be in "administrative" states which include "LockInstantiation", "LockAssignment", and "Unlocked". There are other states, but these are the ones we care about for the purposes of this Evaluation System. If the administrative state of a service unit is "LockInstantiation" then the application that is part of that service unit will not even be started. If the administrative state is "LockAssignment" then the application will be started, but it will not be assigned any work. If the administrative state is "Unlocked" then it will not only be started, but will have a workload assigned to it, which is to say that it will start doing work (or start providing service), rather than idly sit waiting for work.

The administrative state of a service unit or service group can change from LockInstantiation to LockAssignment, from LockAssignment to Unlocked, or back to LockInstantiation, from Unlocked to LockAssignment. A picture might help here:

 [[File:eval_AdministrativeStateDiagram.png|frame|center| '''Partial Service Group Administrative State Diagram''' ]]

As the figure shows, the administrative state of a service unit (or service group) can change from "LockInstantiation" to "LockAssignment" and from there to "Unlocked", or back to "LockInstantiation". One way to change the administrative state of a service group is with the SAFplus Platform Console command line interface.

To use the SAFplus Platform Console:
<ol>
<li> Open a terminal on the Development Machine. (Or ssh into System Controller node as root, if you are running SAFplus Platform on a machine other than the development machine.)
<li> Change to image bin directory: <code><pre># cd /root/asp/bin</pre></code>

<li> Start the SAFplus Platform Console <code><pre># ./asp_console</pre></code>

<li> From within the SAFplus Platform Console: <code><pre>
cli[Test]-> setc 1
cli[Test:SCNodeI0]-> setc cpm
cli[Test:SCNodeI0:CPM]-> amsLockAssignment sg csa101SGI0
</pre></code>

The above changes the administrative state of the group csa101SGI0 from "locked-for-instantiation" to "locked-for-assignment".
 [[File:OpenClovis_Note.png]]For the command <code>cli[Test]-> setc 1</code>, the 1 represents the physical slot number of the System Controller within the Chassis. Remember that we set our System Controller to be in slot 1 in the make images dialog.

<li>Now lets tail the application log file so that we can see whats going on. In another window, as root, run:
<code><pre>
# tail -f /root/asp/var/log/csa101I0Log.latest
</pre></code>

You should see the following:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa101I0Log.latest
|-
|<code><pre>
Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00034 : INFO)
Component [csa101I0] : PID [10849]. Initializing

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00035 : INFO)
IOC Address : 0x1

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00036 : INFO)
IOC Port : 0x80

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00037 : INFO)
csa101: Instantiated as component instance csa101I0.

Tue Jul 15 21:32:06 2008 (SCNodeI0.10849 : csa101_EO.---.---.00038 : INFO)
csa101I0: Waiting for CSI assignment...
</pre></code>
|}

<li>Next change the administrative state of the csa101SGI0 service group to "unlocked" by running (in the SAFplus Platform Console) :
<code><pre>
# cli[Test:SCNodeI0:CPM]-> amsUnlock sg csa101SGI0
</pre></code>

In the window where you're running the "tail -f" you should see:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa101I0Log.latest
|-
|<code><pre>
Tue Jul 15 21:36:17 2008 (SCNodeI0.10849 : csa101_EO.---.---.00049 : INFO)
csa101: ACTIVE state requested; activating service

Tue Jul 15 21:36:18 2008 (SCNodeI0.10849 : csa101_EO.---.---.00050 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:19 2008 (SCNodeI0.10849 : csa101_EO.---.---.00051 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:20 2008 (SCNodeI0.10849 : csa101_EO.---.---.00052 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:21 2008 (SCNodeI0.10849 : csa101_EO.---.---.00053 : INFO)
csa101: Hello World! .

Tue Jul 15 21:36:22 2008 (SCNodeI0.10849 : csa101_EO.---.---.00054 : INFO)
csa101: Hello World! .
</pre></code>
|}

As you can tell from the output log our component is up and running! It is continuously printing our 'Hello World!' output.

<li>Now change the state of the csa101SGI0 service group back to "locked-for-assignment" by running (in the SAFplus Platform Console):
<code><pre>
# cli[Test:SCNodeI0:CPM]-> amsLockAssignment sg csa101SGI0
</pre></code>

In the tail -f output you should see:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa101I0Log.latest
|-
|<code><pre>
Tue Jul 15 21:39:29 2008 (SCNodeI0.10849 : csa101_EO.---.---.00241 : INFO)
csa101: Hello World! .

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00242 : INFO)
Component [csa101I0] : PID [10849]. CSI Set Received

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00243 : INFO)
CSI Flags : [Target One]

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00244 : INFO)
CSI Name : [csa101CSII0]

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00245 : INFO)
HA State : [Quiesced]

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00246 : INFO)
csa101: Acknowledging new state

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00249 : INFO)
Component [csa101I0] : PID [10849]. CSI Remove Received

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00250 : INFO)
CSI : csa101CSII0

Tue Jul 15 21:39:30 2008 (SCNodeI0.10849 : csa101_EO.---.---.00251 : INFO)
CSI Flags : 0x2
</pre></code>
|}

Our component has been put into Lock Assignment state so our 'Hello World!' output has stopped printing to the log.

<li>At this point you can either unlock the service group to change its state to "unlocked" or you can lock it for instantiation to change it to state "locked-for-instantiation". The latter will cause the csa101 process to die. From state "locked-for-assignment", it is possible to change the state to "locked-for-instantiation" by running (in the SAFplus Platform Console):
<code><pre>
cli[Test:SCNodeI0:CPM]-> amsLockInstantiation sg csa101SGI0
cli[Test:SCNodeI0:CPM] -> end
cli[Test:SCNodeI0] -> end
cli[Test] -> bye
</pre></code>
</ol>

===Stopping SAFplus Platform===

To stop SAFplus Platform on the System Controller
<ol>
<li>Open a shell.
<li>ssh into the System Controller node as root.
<li>Once logged in, run the following command
<code><pre>
# cd /root/asp
# etc/init.d/asp stop
</pre></code>
</ol>

==Summary and Next Steps==
In the csa101 example we learned the following.

<ul>
<li>How to create a system model using the '''SAFplus Platform IDE'''.
<li>How to generate the source code.
<li>How to customize this source code to fit a specific application.
<li>How to configure and build the customized source code.
<li>How to make runtime images and deploy them to target machines.
<li>How to start and stop '''SAFplus'''.
<li>How to interact with system components using the '''SAFplus Platform Console'''.
</ul>

The next logical step would be to run through the '''SAFplus Platform Evaluation System User Guide'''. This guide goes over more complex system configurations and introduces new concepts.

For more in depth information on the '''SAFplus Platform IDE''' see the '''SAFplus Platform IDE User Guide'''.

For more in depth information on the '''SAFplus Platform SDK''' see the '''SAFplus Platform SDK User Guide'''.

==Appendix A: target.conf Settings==

Below is a description of the values in the settings in the <code>target.conf</code> file.

<ol>
<li>'''TRAP_IP''' (Mandatory): Specifies where the SNMP SubAgent should send traps at runtime. If you do not have an SNMP SubAgent in your model specify '''127.0.0.1''' as the value. e.g.:
<code><pre>
TRAP_IP=127.0.0.1
</pre></code>
<li>'''CMM_IP''' (Mandatory if deployed on an ATCA chassis): Specifies the IP address of the target system's chassis management module or shelf manager. ATCA chassis Example:
<code><pre>
CMM_IP=169.254.1.2
</pre></code>
<li>'''CMM_USERNAME''' and '''CMM_PASSWORD''' (Mandatory if deployed on an ATCA chassis): Specifies the username and password required for the OpenClovis SAFplus Platform Chassis Manager to connect to the target system's chassis management module. e.g.:
<code><pre>
CMM_USERNAME=root
CMM_PASSWORD=password
</pre></code>
<li>'''INSTALL_PREREQUISITES=YES|NO''' (Mandatory): Specifies whether the target images will include 3rd party runtime prerequisites or not. Say '''YES''' if the target nodes do not meet the target host requirements specified in the Installation section of this document. e.g.:
<code><pre>
INSTALL_PREREQUISITES=YES
</pre></code>
<li>'''INSTANTIATE_IMAGES=YES|NO''' (Mandatory): Specifies whether <code>make images</code> will generate node-instance specific images instead of only generating node-type specific images. This option is a development optimization for advanced users of SAFplus Platform SDK. If unsure, say '''YES'''. e.g.:
<code><pre>
INSTANTIATE_IMAGES=YES
</pre></code>
<li>'''CREATE_TARBALLS=YES|NO''' (Mandatory): Specifies whether the node-instance specific images created will be packaged into tarballs for deployment onto the target system. If unsure, say '''YES'''. e.g.:
<code><pre>
CREATE_TARBALLS=YES
</pre></code>
<li>'''TIPC_NETID''' (Mandatory): Specifies a unique identifier used by TIPC to set up interprocess communication across the deployed OpenClovis SAFplus Platform cluster. This is an unsigned 32-bit integer, and must be unique for every model that is deployed. e.g.:
<code><pre>
TIPC_NETID=1337
</pre></code>
<li>'''Node Instance Details''': These specify the node-instance specific parameters required for deploying the model. For each node in the model there is a corresponding entry in the file:
<ol>
<li>'''SLOT_<node instance name>''' (Mandatory): Specifies which slot the node is located in. The first slot is slot 1 -- DO NOT USE SLOT NUMBER 0, it is invalid. When deployed to an ATCA chassis, the physical slot in which the blade is actually installed will override this value. When deployed to regular (non-ATCA) systems, this is a logical slot and must be unique for every node in the cluster. e.g.:
<code><pre>
SLOT_SCNodeI0=1
</pre></code>
<li>'''LINK_<node instance name>''' (Optional): Specifies the ethernet interface used by the node for OpenClovis SAFplus Platform communication with the rest of the cluster. If unspecified, this defaults to <code>eth0</code>. e.g.:
<code><pre>
LINK_SCNodeI0=eth0
</pre></code>
<li>'''ARCH_<node instance name>''' (Optional if '''ARCH''' is specified): Specifies the target architecture of the node as a combination of machine architecture (MACH) and linux kernel version. This is only required on a per-node basis if the target cluster has heterogeneous architectures across the nodes. If it is a homogeneous cluster, a single '''ARCH''' parameter (described below) will suffice. e.g.:
<code><pre>
ARCH_SCNodeI0=i386/linux-2.6.14
</pre></code>
<li>'''ARCH''' (Optional if node-specific '''ARCH_''' parameters are specified): Specifies the target architecture of all nodes in a homogeneous cluster as a combination of machine architecture (MACH) and linux kernel version. Note: The build process automatically populates this variable based on the last target the model is built for.e.g.:
<code><pre>
ARCH=i386/linux-2.6.14
</pre></code>
</ol>
For example, if we have a three-node cluster with the following details:
{| border="0" cellpadding="3" align="center" width="600"
|+ align="bottom" | '''Example Node Instance Detail'''
|- style="color:#ffffff; background:#549cc6"
!style="color:#66b154; background:#09477c"| Node Name
!style="color:#66b154; background:#09477c"| Slot Number
!style="color:#66b154; background:#09477c"| Link Interface
!style="color:#66b154; background:#09477c"| Architecture
|- style="color:#ffffff; background:#549cc6"
|SCNodeI0
|1
|eth0
|i386/linux-2.6.14
|- style="color:#ffffff; background:#549cc6"
|PayloadNodeI0
|3
|eth0
|i386/linux-2.6.14
|- style="color:#ffffff; background:#549cc6"
|PayloadNodeI1
|4
|eth1
|ppc/linux-2.6.9
|}
we would specify the node instance details as:
<code><pre>
SLOT_SCNodeI0=1
SLOT_PayloadNodeI0=3
SLOT_PayloadNodeI1=4

LINK_SCNodeI0=eth0
LINK_PayloadNodeI0=eth0
LINK_PayloadNodeI1=eth1

ARCH_SCNodeI0=i386/linux-2.6.14
ARCH_PayloadNodeI0=i386/linux-2.6.14
ARCH_PayloadNodeI1=ppc/linux-2.6.9
</pre></code>
</ol>

==Appendix B: AMF Configuration Details==
This appendix gives brief descriptions of configuration details for instances of different entities (like Node, Service Group, Service Unit etc) that are present in the '''Clovis''' -> '''AMF Configuration''' dialog box.

===Node Instance===
This screen displays the node instance that was created by the Node Instance Wizard. This node instance was created because the node type '''SCNode''' was selected on the wizard screen.

[[File:Tutorial_NodeInstanceDetails.png|frame|center| '''Node Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Node Instance Name''': This field holds the name of the node instance. This name must be unique. The name that was generated combines the node type (SCNode), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''Node Type''': This field holds the node type that was selected on the wizard screen.
<li>'''MOID''': This is the unique identifier for the node instance. It was generated by the wizard. The format of this ID is a string representing the one and only instance of the chassis (\Chassis:0) defined in the Resource Editor followed by a string representing the first and only instance of the blade type (\SysBlade:0) that was selected in the Node Instance Wizard.
 [[File:OpenClovis_Note.png]]'''MOID''' is an acronym for Managed Object Identifier. It must be unique and is used to identify which hardware chassis and blade type this instance will run on.
</ul>

===Service Unit Instance===
This screen displays the service unit instance that was created by the Service Group Instance Wizard. This service unit instance was created because the service unit type is associated with both the selected node type (SCNode) and the selected service group type (csa101SG) in our model.

[[File:Tutorial_SUInstanceDetails.png|frame|center| '''SU Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''SU Instance Name''': This field holds the name of the service unit instance. This name must be unique. The name that was generated combines the service unit type (csa101SU), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''Service Unit Type''': This field holds the type of the service unit instance.
</ul>

===Component Instance===
This screen displays the component instance that was created by the Service Group Instance Wizard. This component instance was created because the component type is associated with the created parent service unit type (csa101SU) in our model.

[[File:Tutorial_ComponentInstanceDetails.png|frame|center| '''Component Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Component Instance Name''': This field holds the name of the component instance. This name must be unique. The name that was generated combines the component type (csa101), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''Component Type''': This field holds the type of the component instance.
</ul>

===Service Group Instance===
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.

[[File:Tutorial_SGInstanceDetails.png|frame|center| '''Service Group Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''SG Instance Name''': This field holds the name of the service group instance. This name must be unique. The name that was generated combines the service group type (csa101SG), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''ServiceGroup Type''': This field holds the type of the service group instance.
<li>'''Associated Service Units''': This button is used to associate service unit instances with this service group instance. Creating this association indicates that the selected service unit(s) will run within this service group instance.
</ul>

Clicking the '''Associated Service Units''' Edit... button will display the following dialog.

[[File:Tutorial_SG_SI_Association.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.

===Service Instance Instance===
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.

[[File:Tutorial_SIInstanceDetails.png|frame|center| '''Service Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Service Instance Name''': This field holds the name of the service instance. This name must be unique. The name that was generated combines the service instance type (csa101SI), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''ServiceInstance Type''': This field holds the type of the service instance.
</ul>

===Component Service Instance Instance===
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.

[[File:Tutorial_CSIInstanceDetails.png|frame|center| '''Component Service Instance Details''' ]]

The information on this screen is described below.
<ul>
<li>'''Component Service Instance Name''': This field holds the name of the component service instance. This name must be unique. The name that was generated combines the component service instance type (csa101CSI), the letter I (for Instance), and the number 0 (since this is the first instance of this type).
<li>'''ComponentServiceInstance Type''': This field holds the type of the component service instance.
</ul>

Talk:Doc:latest/logtoolguide

2012-02-21T03:24:20Z

MediaWiki spam cleanup: All revisions contained links to www.buyxanaxitem.com, blanking