rss
OpenSAF 4.2 Released
The OpenSAF community is pleased to announce general availability of the 4.2 release.
The source can be downloaded here.
A list of the major enhancements:
- Python wrappers for SAF AIS APIs
- IMM: Support for multiple appliers
- IMM: Improved admin operation API
- IMM: Support for CCB augmentation by Object Implementer'
- IMM: New API for out-of-band ccb error string from OI to OM-client
- DTSv completely removed
- AMF: Support for B.04 API
- AMF: Hot Standby using IMM multiple applier API
- AMF: Support for SU repair admin operation
- AMF: Support for multiple CSI dependencies
- LOG: Overload protection
- NTF: Improved reader API Execute as non root
The complete list of 4.2 enhancements can be found in this report
The complete list of 4.2 defects and enhancements can be found in this report
The complete list of all defects is shown in the mercurial change log using e.g. "hg log -b default -r 4.2.M0:4.2.GA"
The corresponding documentation can be downloaded here
Python Bindings for SAF-AIS APIs
Dear OpenSAF community,
The Python Bindings presented at the OpenSAF conference in Cambridge Massachusetts have been submitted to opensaf-staging in preparation for inclusion into release 4.2.
They can be found at opensaf-staging/osaf/tools/pyosaf/. Please see the README at this location for a brief description and example.
The package currently includes only the *.py files for the bindings themselves, and can be used immediately. More material demonstrating how to use the bindings (with additional documentation) will be included as the interfaces complete the review process. Please route all comments and suggestions through users@….
For those that could not attend the presentation in Cambridge, the presentation (slides and audio) is available at:
http://www.slideshare.net/opensaf/python-bindings-for-the-safais-apis61511
Regrettably, there is no video available of the demos conducted during the presentation.
From the conference abstract:
"Python bindings for OpenSAF APIs offer many advantages to middle-ware developers,application developers, tool developers, and testers. The bindings help to speed-up the software development life-cycle, enabling rapid development and deployment of architecture-independent components and services."
Regards, Currie Reid
autoconf requirements to build OpenSAF
For those of you using mercurial and building the default branch, you are now required to update autoconf to at least 2.61 which is known to work. 2.59 does not work!
Running OpenSAF on Fedora14
Comments:
- You can probably disable SELinux during installation (but I forgot so I describe
howto disable it afterwards).
- By default OpenSAF uses MDS/TIPC as its internal messaging protocol. Since TIPC is
not enabled in Fedora kernels nor are the user space tools available. Let's configure
and use the new feature MDS/TCP. That simplifies things on Fedora.
Steps:
1. Install FC14 on some machine (I used VirtualBox)
2. Disable SeLinux and reboot (not needed if SELinux disabled at install)
- set the value of SELINUX in /etc/selinux/config to disabled
- reboot
3. Add OpenSAF repos to yum configuration: http://devel.opensaf.org/wiki/Yum
4. Install OpenSAF (as root):
[root@FC14-1]# yum install opensaf-controller Loaded plugins: langpacks, presto, refresh-packagekit Adding en_US to language list Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package opensaf-controller.x86_64 0:4.2.M0-201103230402.fc14 set to be installed --> Processing Dependency: opensaf-libs = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-amf-nodedirector = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-log-server = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-ntf-server = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-amf-libs = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-clm-server = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-clm-nodeagent = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-amf-director = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-ntf-libs = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-log-libs = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-imm-director = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-clm-libs = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-imm-libs = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: opensaf-imm-nodedirector = 4.2.M0-201103230402.fc14 for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: libSaImmOi.so.0(OPENSAF_IMM_A.02.01)(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: libSaImmOm.so.0(OPENSAF_IMM_A.02.01)(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: libopensaf_core.so.0()(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: libSaImmOm.so.0()(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: librda.so.0()(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: libSaAmf.so.0()(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Processing Dependency: libSaImmOi.so.0()(64bit) for package: opensaf-controller-4.2.M0-201103230402.fc14.x86_64 --> Running transaction check ---> Package opensaf.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-amf-director.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-amf-libs.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-amf-nodedirector.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-clm-libs.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-clm-nodeagent.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-clm-server.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-imm-director.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-imm-libs.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-imm-nodedirector.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-libs.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-log-libs.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-log-server.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-ntf-libs.x86_64 0:4.2.M0-201103230402.fc14 set to be installed ---> Package opensaf-ntf-server.x86_64 0:4.2.M0-201103230402.fc14 set to be installed --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================================================================= Installing: opensaf-controller x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 167 k Installing for dependencies: opensaf x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 49 k opensaf-amf-director x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 276 k opensaf-amf-libs x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 113 k opensaf-amf-nodedirector x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 157 k opensaf-clm-libs x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 59 k opensaf-clm-nodeagent x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 11 k opensaf-clm-server x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 76 k opensaf-imm-director x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 214 k opensaf-imm-libs x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 344 k opensaf-imm-nodedirector x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 203 k opensaf-libs x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 565 k opensaf-log-libs x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 56 k opensaf-log-server x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 63 k opensaf-ntf-libs x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 134 k opensaf-ntf-server x86_64 4.2.M0-201103230402.fc14 opensaf-default-nightly 79 k Transaction Summary ============================================================================================================================================================================================================================================= Install 16 Package(s) Total download size: 2.5 M Installed size: 6.7 M Is this ok [y/N]: y Downloading Packages: Setting up and reading Presto delta metadata Processing delta metadata Package(s) data still to download: 2.5 M (1/16): opensaf-4.2.M0-201103230402.fc14.x86_64.rpm | 49 kB 00:00 (2/16): opensaf-amf-director-4.2.M0-201103230402.fc14.x86_64.rpm | 276 kB 00:01 (3/16): opensaf-amf-libs-4.2.M0-201103230402.fc14.x86_64.rpm | 113 kB 00:00 (4/16): opensaf-amf-nodedirector-4.2.M0-201103230402.fc14.x86_64.rpm | 157 kB 00:00 (5/16): opensaf-clm-libs-4.2.M0-201103230402.fc14.x86_64.rpm | 59 kB 00:00 (6/16): opensaf-clm-nodeagent-4.2.M0-201103230402.fc14.x86_64.rpm | 11 kB 00:00 (7/16): opensaf-clm-server-4.2.M0-201103230402.fc14.x86_64.rpm | 76 kB 00:00 (8/16): opensaf-controller-4.2.M0-201103230402.fc14.x86_64.rpm | 167 kB 00:00 (9/16): opensaf-imm-director-4.2.M0-201103230402.fc14.x86_64.rpm | 214 kB 00:01 (10/16): opensaf-imm-libs-4.2.M0-201103230402.fc14.x86_64.rpm | 344 kB 00:01 (11/16): opensaf-imm-nodedirector-4.2.M0-201103230402.fc14.x86_64.rpm | 203 kB 00:05 (12/16): opensaf-libs-4.2.M0-201103230402.fc14.x86_64.rpm | 565 kB 00:01 (13/16): opensaf-log-libs-4.2.M0-201103230402.fc14.x86_64.rpm | 56 kB 00:00 (14/16): opensaf-log-server-4.2.M0-201103230402.fc14.x86_64.rpm | 63 kB 00:00 (15/16): opensaf-ntf-libs-4.2.M0-201103230402.fc14.x86_64.rpm | 134 kB 00:00 (16/16): opensaf-ntf-server-4.2.M0-201103230402.fc14.x86_64.rpm | 79 kB 00:00 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 81 kB/s | 2.5 MB 00:31 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : opensaf-libs-4.2.M0-201103230402.fc14.x86_64 1/16 Installing : opensaf-amf-libs-4.2.M0-201103230402.fc14.x86_64 2/16 Installing : opensaf-imm-libs-4.2.M0-201103230402.fc14.x86_64 3/16 Installing : opensaf-clm-libs-4.2.M0-201103230402.fc14.x86_64 4/16 Installing : opensaf-ntf-libs-4.2.M0-201103230402.fc14.x86_64 5/16 Installing : opensaf-log-libs-4.2.M0-201103230402.fc14.x86_64 6/16 Installing : opensaf-clm-server-4.2.M0-201103230402.fc14.x86_64 7/16 Installing : opensaf-ntf-server-4.2.M0-201103230402.fc14.x86_64 8/16 Installing : opensaf-amf-director-4.2.M0-201103230402.fc14.x86_64 9/16 Installing : opensaf-amf-nodedirector-4.2.M0-201103230402.fc14.x86_64 10/16 Installing : opensaf-clm-nodeagent-4.2.M0-201103230402.fc14.x86_64 11/16 Installing : opensaf-log-server-4.2.M0-201103230402.fc14.x86_64 12/16 Installing : opensaf-imm-nodedirector-4.2.M0-201103230402.fc14.x86_64 13/16 Installing : opensaf-imm-director-4.2.M0-201103230402.fc14.x86_64 14/16 Installing : opensaf-4.2.M0-201103230402.fc14.x86_64 15/16 Installing : opensaf-controller-4.2.M0-201103230402.fc14.x86_64 16/16 For information on how to configure the initial imm.xml file check the readme file: /usr/share/opensaf/immxml/README Installed: opensaf-controller.x86_64 0:4.2.M0-201103230402.fc14 Dependency Installed: opensaf.x86_64 0:4.2.M0-201103230402.fc14 opensaf-amf-director.x86_64 0:4.2.M0-201103230402.fc14 opensaf-amf-libs.x86_64 0:4.2.M0-201103230402.fc14 opensaf-amf-nodedirector.x86_64 0:4.2.M0-201103230402.fc14 opensaf-clm-libs.x86_64 0:4.2.M0-201103230402.fc14 opensaf-clm-nodeagent.x86_64 0:4.2.M0-201103230402.fc14 opensaf-clm-server.x86_64 0:4.2.M0-201103230402.fc14 opensaf-imm-director.x86_64 0:4.2.M0-201103230402.fc14 opensaf-imm-libs.x86_64 0:4.2.M0-201103230402.fc14 opensaf-imm-nodedirector.x86_64 0:4.2.M0-201103230402.fc14 opensaf-libs.x86_64 0:4.2.M0-201103230402.fc14 opensaf-log-libs.x86_64 0:4.2.M0-201103230402.fc14 opensaf-log-server.x86_64 0:4.2.M0-201103230402.fc14 opensaf-ntf-libs.x86_64 0:4.2.M0-201103230402.fc14 opensaf-ntf-server.x86_64 0:4.2.M0-201103230402.fc14 Complete!
5. Create /etc/opensaf/imm.xml as specified in /usr/share/opensaf/immxml/README.
Make sure to edit nodes.cfg, the line with SC-1, third column to match the short
hostname of the system.
6. Configure OpenSAF to use MDS/TCP:
- Go to /etc/opensaf
- Edit nodeinit.conf.controller and remove line with nid_tipc
- Edit nid.conf and set MDS_TRANSPORT=TCP
- Edit dtmd.conf and change DTM_NODE_IP to the IP address of the local/self node
- Create a custom login file for OpenSAF:
echo "export MDS_TRANSPORT=TCP" > /etc/profile.d/opensaf.sh
7. Start OpenSAF as root (or reboot):
[root@FC14-1 opensaf]# /etc/init.d/opensafd start Starting OpenSAF Services: [ OK ]
8. Check status:
[root@FC14-1 opensaf]# /etc/init.d/opensafd status
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
9. Do some stuff:
- For example examine IMM content with the imm* commands
- Add an application (to be described later)
OpenSAF Yum testing repository is now live!
Check out the downloads section for instructions on using our, under test, Yum repository for OpenSAF 4.0.x, 4.1.x and default nightly development snapshots.
OpenSAF 4.1 now available for download
After two release candidate cycles, the OpenSAF community is happy to announce the general availability of OpenSAF 4.1. This release contains the following features:
- SMF rollback support for campaign
- SMF API to support upgrade aware user processes
- OpenSAF cluster communication over TCP (TIPC still the default), enabler for non Linux platforms
- AMF equal distribution of Service Instances over Service Units
- IMM enhanced data capacity
- IMM schema upgrade support
- AM4J/AMF Java Agent
- Improved AMF dynamic configuration support
For more details see report: http://devel.opensaf.org/report/54
To get the code, check out the download section: http://devel.opensaf.org/downloads
OpenSAF 4.1 Release Candidate 2 (RC2) available
The OpenSAF community is happy to announce the second 4.1 release candidate (RC2). This release contains critical bug fixes in the IMM Service that has been raised since RC1.
To get the code, check out the download section: http://devel.opensaf.org/downloads
You can get the revision Changelog from http://devel.opensaf.org/wiki/changelog/4.1.RC2
OpenSAF 4.1 Release candidate 1 available
The OpenSAF community is happy to announce the first 4.1 release candidate. This release contains the following features:
- SMF rollback support for campaign
- SMF API to support upgrade aware user processes
- OpenSAF cluster communication over TCP (TIPC still the default), enabler for non Linux platforms
- AMF equal distribution of Service Instances over Service Units
- IMM enhanced data capacity
- IMM schema upgrade support
- AM4J/AMF Java Agent
- Improved AMF dynamic configuration support
For more details see report: http://devel.opensaf.org/report/54
To get the code, check out the download section: http://devel.opensaf.org/downloads
OpenSAF patch release 4.0.1 is now available for download
The OpenSAF community is happy to announce the first patch release since the general availability of OpenSAF 4.0. This release contains +175 changesets.
To get the code, check out the download section: http://devel.opensaf.org/downloads
Join us for the 2011 OpenSAF Conference
Save the date for May 17-18, 2011 at the Massachusetts Institute of Technology (MIT)
The OpenSAF Foundation invites you to join us for the 2011 OpenSAF Conference, formerly named Developer Days, on May 17-18, 2011 at the Massachusetts Institute of Technology (MIT) in Cambridge, Mass.
The 2011 OpenSAF Conference is a technical conference for the open source, high availability (HA) middleware community, and this year's event has expanded beyond developers to also include users, potential OpenSAF adopters and engineering managers.
Based on attendee feedback from last year's event, this year's conference will focus more on best practices for implementing the OpenSAF Project architecture and will educate on how implementing these solutions can reduce risk and reduce your company's time to market.
Register now for this two-day event, where well-known technologists, experts and architects in the HA ecosystem will present new sessions and spur discussions about developing and implementing open source HA middleware.
The conference costs $99 per attendee and is free for the first 20 students (Student ID required).
Why You Should Attend the 2011 OpenSAF
Conference Learn about current implementations of HA middleware
OpenSAF is quickly becoming the de facto standard for HA middleware. This conference will bring you up to speed on the current implementations and trends of HA middleware for businesses today.
Hear from key players in the HA ecosystem
The OpenSAF conference will feature a variety of sessions and discussions led by industry-leading technologists, experts and architects in the High Availability ecosystem. Ericsson, GoAhead Software, HP and Wind River Systems will be among the presenting companies at this year's event.
Connect with the HA Open Source Community
Participants will have an excellent opportunity to exchange ideas and learn about current implementations of high availability middleware and share experiences and information with community experts.
2011 Conference Session Snapshot
- OpenSAF General Overview: What are the benefits and what is the current status of OpenSAF today?
- OpenSAF Technical Overview: A look at the key concepts of the OpenSAF project and the different services it addresses.
- Case Study: A real-world case study will highlight the benefits of migrating legacy applications to OpenSAF.
- OpenSAF and Alternative Solutions: How does OpenSAF complement other technologies, such as virtualization?
- Use Case Examples: Modeling real applications. This presentation will include a demo made up of a highly available video streaming component which broadcasts a movie to clients on the network. The demo will show how a cluster can be made aware of imminent hardware failures, and therefore be able to make decision based on hardware health.
Learn more about the session abstracts.
OpenSAF Release 4.1 Information
The OpenSAF 4.1 release is closing in and is now in the functional complete state. Check out this roadmap for more information about newly introduced functionality. A few issues remain to be solved before general availability.
New OpenSAF Blog Interface
The Trac FullBlogPlugin has been installed on the OpenSAF Development server, it will be used by the developer community to post news and howto's about the project.
Soon its publication mechanism will be hooked to the announce@… mailing list.
