SmartFrog 3.12.014 is out!
Steve Loughran <[email protected]> Wed, 05 Dec 2007 18:45:13 +0000
| Newsgroups | gmane.comp.java.smartfrog.devel,gmane.comp.java.smartfrog.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------060401090806050702040103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I'm pleased to announce the release of SmartFrog 3.12.014; the artifacts
are up under
https://sourceforge.net/project/showfiles.php?group_id=87384&package_id=108447&release_id=559511
This is probably going to be the release for 2007, unless we have an
urge to do one just before christmas to keep the release schedule up.
There's no major changes, just bug fixes, better documentation for some
things, and a javadocs RPM. Javadocs go into
/usr/share/javadocs/smartfrog-${version-number} ; there may be some
changes under there in future releases.
One thing we have done is tightened the security of the RPM-installed
SmartFrog so that the logs directory is now only writeable by SmartFrog.
This would stop anyone from running SmartFrog unless they had the right
privileges, so the log to file code is enhanced to fall back gracefully
if the configured log directory is not writeable -it switches to
java.io.tmpdir in this situation. Note that locking down the log
directories does not make your system secure if your daemon is accepting
incoming calls from unauthenticated callers; it merely hides the problems.
As usual, please don't hesitate to provide feedback, bug reports, test
cases, improvements to the documentation, etc.
Early roadmap of pending changes
====================
I'm going to mention some imminent enhancements for anyone who wants to
check out the repository and get involved
-migration to OSGi. This is a merge in of a branch that is already in
the repository; we will switch to OSGi to manage classpaths. This will
improve classloading, isolation of classes, and other things, so we are
looking forward to this change.
-There is a restlet client component being put together as part of some
amazon S3/EC2 support. The client will be general purpose and let you
declare which HTTP verbs to apply during startup, pings and termination
-you can issue a list if you want for each action. I want to add some
XPath extraction of result text too. Query parameters and headers can be
set by a list. The result will be a component that can manage the
lifecycle of a remote resource (PUT on start, GET on ping, DELETE on
termination), or issue complex HTTP operations against remote resources,
and turn the result into attributes that can be picked up by other
components. Participation in features and functionality of this code is
encouraged, especially from anyone who is deploying in the S3/EC2 farm.
-steve
SmartFrog 3.12.014
======================
This is a new release of SmartFrog, the Java-based, LPGL-licensed
distributed deployment framework developed by HP Laboratories. SmartFrog
enables applications to be deployed across multiple machines,
configuring different aspects of the system so that they are all
consistently configured, and managing the life-cycle of the application
as a whole. The project's home page is http://smartfrog.org/
The release artifacts are available at
http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308
This release is 3.12.014; built from revision 5649
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:
* Core smartfrog daemon, including services to manage files, start and stop
Java and native programs.
* Example components and applications.
* Ant support: ant tasks to deploy and terminate applications from a build.
* Ant components: the ability to execute ant tasks in a deployment.
* Anubis: a partition aware tuple-space that can be used to implement fault
tolerant systems.
* Database: components to issue database commands, and deploy HSLDB and
MySQL.
* JMX: the ability to configure and manage JMX components, and to manage
SmartFrog components over JMX.
* Logging: integration with Apache commons-logging and Log4J
* Networking: email, FTP, SSH, DNS support.
* Quartz: scheduled operations using Quartz libraries.
* Scripting: support for BSF-hosted scripting languages
* Testing: Distributed JUnit and component testing with SFUnit.
* WWW: deployment of WAR and EAR files to application servers.
deploy-by-copy
is provided for all application servers that support it, and sample
templates
are provided to start and stop Tomcat and JBoss. The Jetty component can
configure and deploy individual servlets, eliminating much of the
need for WAR
files and application servers.
* XML: XML support with XOM.
* XMPP: Presence and messaging over Jabber.
Packaging
=========
This release is available as:
* RPM files inside a .tar.gz file.
* a JAR installer.
* the original core smartfrog distribution as .zip and .tar.gz (deprecated)
The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:
smartfrog: the core SmartFrog distribution.
smartfrog-daemon: the shell scripts to add the smartfrog distribution to the
path, and to run the daemon on start-up.
smartfrog-demo: example code and documentation.
All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/
to your repository list to pull SmartFrog artifacts into your Ivy- or
Maven- based build.
There are also SmartFrog components to retrieve artifacts from such a
repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.
Security warning
================
Unless SmartFrog is configured with security, a running daemon will
listen on its configured port for incoming deployment requests, and
deploy the applications with the rights of the user running the daemon.
When the smartfrog-daemon RPM is installed, that means that a process
running as root will be listening on an open port for incoming
deployment requests. Do not deploy SmartFrog this way on any untrusted
network, not without turning security on and, ideally, recreating the
RPMs with signed JAR files.
Building SmartFrog
==================
SmartFrog requires Java 1.5 and Ant 1.7 to build. The izpack and source
.zip and
.tar.gz distributions include a source tree adequate to build the
entire system. To build a later release, please follow the instructions at
http://sourceforge.net/svn/?group_id=87384
to check out smartfrog/trunk/core from our repository.
This release was built with revision 5645 of the repository, which
is available under the SVN branch
https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.12.014
We strongly encourage anyone interested in building or extending
SmartFrog to get involved in the SmartFrog developer mailing list, which
can be found from the sourceforge project page
http://sourceforge.net/projects/smartfrog/
Reporting Bugs
==============
Please file all bug reports at http://jira.smartfrog.org/
Thank you!
The SmartFrog Team http://smartfrog.org/
Changes since last release
==========================
There are no major changes in this release, only ongoing bug fixes and minor
improvements, and build process tuning.
The RPMs have been improved; the javadocs for the core JARs are
provided as their own RPM.
** Bug
* [SFOS-560] - -x bit is set in /etc/sysconfig/smartfrog
* [SFOS-561] - sfResolveHereNonlocal does not delegate to
sfResolveHere when
the attribute is not in the context and the dns component overrides
sfResolveHere to give a default value
* [SFOS-564] - regression in RunShell; list operations causing NPW
* [SFOS-572] - default for sfDump does not handle references with
repeated
names correctly
* [SFOS-574] - jjdocs target fails on CruiseControl
* [SFOS-575] - common.xml javadoc fails if there is no source
** Improvement
* [SFOS-265] - bits of smartfrog arent forwarding
SmartFrogResolutionExceptions consistently
* [SFOS-501] - Ant component needs more tests
* [SFOS-548] - Add SFNULL to schemas template
* [SFOS-551] - add Xalan and JDom to the XML component
* [SFOS-552] - review XML component source+build; add in xalan and JDOM
* [SFOS-556] - move up to httpunit 1.6.2 for testing www componentry
* [SFOS-569] - Add attribute to filter the output of positive searches.
Useful to remove the "echoExit command" from the standard output .
* [SFOS-573] - logToFile when failing to create a log file, it
should try
java temp dir before failing
** New Feature
* [SFOS-559] - Create RPMs for the other packages: ant, database, jmx,
xunit, junit, net, www, quartz
* [SFOS-568] - Add a component to test the specific OS
** Task
* [SFOS-129] - incorporate ivy published documentation into the release
artifacts
* [SFOS-357] - Move Jetty support up to Jetty6
* [SFOS-467] - Admin/Debug servlets are no longer in Jetty6; remove the
components and their tests
* [SFOS-540] - document the Ant components
** Sub-task
* [SFOS-473] - Add SSL support with an SSLSocketListener
* [SFOS-475] - Move realm/security config out of SFJetty and make
reusable
* [SFOS-476] - Remove SFJettyAdmin as the servlet is gone
--------------060401090806050702040103
Content-Type: text/html;
name="release_3.12.014.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="release_3.12.014.html"
<html>
<head>
<title>SmartFrog 3.12.014</title>
</head>
<body>
<h1>SmartFrog 3.12.014</h1>
<p>
This is a new release of SmartFrog, the Java-based, LPGL-licensed distributed
deployment framework developed by HP Laboratories. SmartFrog enables
applications to be deployed across multiple machines, configuring different
aspects of the system so that they are all consistently configured, and managing
the life-cycle of the application as a whole. The project's home page is
<a href="http://smartfrog.org/">http://smartfrog.org/</a>
</p>
<p>
The release artifacts are available at
<a
href="http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308">
http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308</a>
</p>
<p>
This release is 3.12.014; built from revision 5649
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:
</p>
<ul>
<li> Core smartfrog daemon, including services to manage files, start and stop
Java and native programs.
</li>
<li> Example components and applications.
</li>
<li> Ant support: ant tasks to deploy and terminate applications from a build.
</li>
<li> Ant components: the ability to execute ant tasks in a deployment.
</li>
<li> Anubis: a partition aware tuple-space that can be used to implement fault
tolerant systems.
</li>
<li> Database: components to issue database commands, and deploy HSLDB and MySQL.
</li>
<li> JMX: the ability to configure and manage JMX components, and to manage
SmartFrog components over JMX.
</li>
<li> Logging: integration with Apache commons-logging and Log4J
</li>
<li> Networking: email, FTP, SSH, DNS support.
</li>
<li> Quartz: scheduled operations using Quartz libraries.
</li>
<li> Scripting: support for BSF-hosted scripting languages
</li>
<li> Testing: Distributed JUnit and component testing with SFUnit.
</li>
<li> WWW: deployment of WAR and EAR files to application servers. deploy-by-copy
is provided for all application servers that support, and a tomcat-specific
component can communicate with Apache Tomcat. The Jetty component can
configure and deploy individual servlets, eliminating much of the need for WAR
files themselves.
</li>
<li> XML: XML support with XOM.
</li>
<li> XMPP: Presence and messaging over Jabber.
</li>
</ul>
<h3>Packaging</h3>
<p>
This release is available as:
</p>
<ol>
<li> RPM files inside a .tar.gz file.
</li>
<li> a JAR installer.
</li>
<li>the original core smartfrog distribution as .zip and .tar.gz (deprecated)
</li>
</ol>
<p>
The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:
</p>
<table>
<tr>
<td><code>smartfrog</code></td>
<td>The core SmartFrog distribution.</td>
</tr>
<tr>
<td><code>smartfrog-daemon</code></td>
<td>The shell scripts to add the smartfrog distribution to the
path, and to run the daemon on start-up.
</td>
</tr>
<tr>
<td><code>smartfrog-demo</code></td>
<td>Example code and documentation</td>
</tr>
<tr>
<td><code>smartfrog-anubis</code></td>
<td>Anubis partition-aware "tuple space"</td>
</tr>
<tr>
<td><code>smartfrog-logging</code></td>
<td>Enhanced logging</td>
</tr>
</table>
<p>
All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add
<a
href="http://smartfrog.sourceforge.net/repository">http://smartfrog.sourceforge.net/repository</a>
to your repository list to pull SmartFrog artifacts into your Ivy- or Maven- based build.
</p>
<p>
There are also SmartFrog components to retrieve artifacts from such a repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.
</p>
<h3>Security warning</h3>
<p>
Unless SmartFrog is configured with security, a running daemon
will listen on its configured port for incoming deployment requests, and deploy
the applications with the rights of the user running the daemon. When the
smartfrog-daemon RPM is installed, that means that a process running as root
will be listening on an open port for incoming deployment requests. Do not
deploy SmartFrog this way on any untrusted network, not without turning security
on and, ideally, recreating the RPMs with signed JAR files.
</p>
<h3>Building SmartFrog</h3>
<p>
SmartFrog requires Java 1.5 and Ant 1.7 to build.
</p>
<p>
The distribution does not include a source tree adequate to build the entire
system. Please follow the instructions at
<a href="http://sourceforge.net/svn/?group_id=87384">http://sourceforge.net/svn/?group_id=87384
</a>
and check out smartfrog/trunk/core from our repository.
</p>
<p>
This release was built with revision 5645 of the repository, which
is available under the SVN branch
<a href="https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.12.014">https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.12.014</a>
</p>
<p>
We strongly encourage anyone interested in building or extending smartfrog to
get involved in the smartfrog developer mailing list, which can be found from
the sourceforge project page
<a href="http://sourceforge.net/projects/smartfrog/">
http://sourceforge.net/projects/smartfrog/</a>
</p>
<h3>Reporting Bugs</h3>
<p>
Please file all bug reports at <a
href="http://jira.smartfrog.org/">http://jira.smartfrog.org/</a>
</p>
<p>
The SmartFrog Team
</p>
<h3>Changes since last release</h3>
<p>
There are no major changes in this release, only ongoing bug fixes and minor
improvements, and build process tuning.
</p>
<p>
The RPMs have been improved; the javadocs for the core JARs are provided as their own RPM.
<p>
<h4> Bug
</h4>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-560'>SFOS-560</a>] - -x bit is set in /etc/sysconfig/smartfrog
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-561'>SFOS-561</a>] - sfResolveHereNonlocal does not delegate to sfResolveHere when the attribute is not in the context and the dns component overrides sfResolveHere to give a default value
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-564'>SFOS-564</a>] - regression in RunShell; list operations causing NPW
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-572'>SFOS-572</a>] - default for sfDump does not handle references with repeated names correctly
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-574'>SFOS-574</a>] - jjdocs target fails on CruiseControl
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-575'>SFOS-575</a>] - common.xml javadoc fails if there is no source
</li>
</ul>
<h4> Improvement
</h4>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-265'>SFOS-265</a>] - bits of smartfrog arent forwarding SmartFrogResolutionExceptions consistently
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-501'>SFOS-501</a>] - Ant component needs more tests
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-548'>SFOS-548</a>] - Add SFNULL to schemas template
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-551'>SFOS-551</a>] - add Xalan and JDom to the XML component
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-552'>SFOS-552</a>] - review XML component source+build; add in xalan and JDOM
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-556'>SFOS-556</a>] - move up to httpunit 1.6.2 for testing www componentry
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-569'>SFOS-569</a>] - Add attribute to filter the output of positive searches. Useful to remove the "echoExit command" from the standard output .
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-573'>SFOS-573</a>] - logToFile when failing to create a log file, it should try java tem dir before failing
</li>
</ul>
<h4> New Feature
</h4>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-559'>SFOS-559</a>] - Create RPMs for the other packages: ant, database, jmx, xunit, junit, net, www, quartz
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-568'>SFOS-568</a>] - Add a component to test the specific OS
</li>
</ul>
<h4> Task
</h4>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-129'>SFOS-129</a>] - incorporate ivy published documentation into the release artifacts
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-357'>SFOS-357</a>] - Move Jetty support up to Jetty6
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-467'>SFOS-467</a>] - Admin/Debug servlets are no longer in Jetty6; remove the components and their tests
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-540'>SFOS-540</a>] - document the Ant components
</li>
</ul>
<h4> Sub-task
</h4>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-473'>SFOS-473</a>] - Add SSL support with an SSLSocketListener
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-475'>SFOS-475</a>] - Move realm/security config out of SFJetty and make reusable
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-476'>SFOS-476</a>] - Remove SFJettyAdmin as the servlet is gone
</li>
</ul>
</body>
</html>
--------------060401090806050702040103
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
--------------060401090806050702040103
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Smartfrog-developer mailing list
Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/smartfrog-developer
--------------060401090806050702040103--