You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Bill Stoddard <bi...@wstoddard.com> on 2007/09/30 16:06:00 UTC
[VOTE] Accept project Imperius into the Incubator
Greetings from North Carolina on a bright, beautiful, sunny fall day!
Thank You to all those who gave comments on the proposal. I made one small tweak; Tomcat, rather than Geronimo, should be one of the first bindings.
Please vote on accepting project Imperius into the Apache Incubator. The vote will run 1 week,
until Sunday, Oct. 7, 2007 or until all Incubator PMC members have voted.
[ ] +1 Accept Imperius project for incubation
[ ] 0 Don't care
[ ] -1 Reject for the following reason :
Thanks,
Bill
-//-
Abstract
-------------
Policy systems allow administrators to define policies that guide the
automated administration of resources. Such automation saves time and
effort by simplifying resource-management.
We proposed to develop a policy-based management infrastructure that
automates administrative tasks by executing policies written in the
"Simplified Policy Language" (SPL), a standards-based policy language.
Proposal
----------
This proposal seeks to create a project within the Apache Software
Foundation to (1) develop a policy evaluator for the SPL policy
language, and (2) develop bindings between the policy evaluator and
projects such as Apache Geronimo or Apache Tomcat.
Background
-----------
As computer systems become more complicated, they continue to become
increasingly complex and costly to manage. Various studies have shown
that the cost of managing systems often exceeds the cost of purchasing
them. The goal of the Imperius project is to reduce management burden by
allowing administrators to specify policies that replace manual
administrative actions.
Rationale
----------
Policy-based management is one approach to reducing the cost of systems
administration. Administrators define policies that express a
"management intent", and the policy-based management system executes
the policy, thereby reducing the burden on the administrator. For
example, a policy might state "backup the database daily at 1am." A
policy management system would interpret the policy, and trigger the
database to perform a backup at the assigned time, offloading that task
from the administrator.
To allow more flexible semantics, such policies are often expressed as
"If-Then" (also called "Condition-Action") rules. For example, "If
the packet comes from subnet 6.7.8.*, Then place it on the
high-priority outgoing queue" or "If the data in the database have
changed by 10%, Then perform an incremental backup." Such policies
allow for more complex automation.
To implement these kinds of rule-based policies, the policy system
must interact with the system's APIs. In the second example above,
the system relies on the ability to measure the percentage of data
that have changed since the last backup (or to compute that value from
measurable data). Similarly, to execute the "then" clause, the policy
system must be able to start an incremental backup on the database
using the database's API. Expressed generally, a policy system must
have a binding to the "instrumentation layer" or API for the system
under management.
Thus, policy systems consist of two major components: an evaluation
engine and a binding to an instrumentation environment. The
evaluation engine (1) accepts policies expressed according to a
well-defined grammar, (2) collects the data needed to evaluate the
policies, and (3) actuates the "Then" section as appropriate.
This project would build an SPL evaluation engine and bindings to
various Apache and non-Apache APIs.
The design of SPL, a Preliminary DMTF standard, is inspired by
existing policy languages and models including PDL (policy definition
language) from Bell Laboratories, the Ponder policy language from
Imperial College, and other policy languages.
The basic unit of a SPL policy is a policy rule. An SPL policy rule
consists of a condition, an action, and other fields. Multiple policy
rules can be grouped into a policy group. Policy groups can be nested
-- i.e., a policy group can contain another policy group. For the
specification of the policy condition, SPL provides a rich set of
operators that act on the following types: signed and unsigned short,
regular and long integers, float and long float, character, string,
Boolean, and calendar.
We expect the community to develop a number of bindings between the
evaluation engine and APIs. Examples include the API for Geronimo or
Tomcat, and standard interfaces such as WSDM and CIM. The community may
choose to develop a wide range of bindings, all leveraging the common
SPL engine and policy syntax.
The Imperius Policy Engine will be implemented in the form of a Java
application. The SPL application will provide the following
functionality:
1. PolicyManager - The PolicyManager acts as an orchestrator
delegating tasks to its subcomponents.
2. PolicyDataStore - The PolicyDataStore is responsible for two major
tasks: Policy Storage and the creation of Internal Policy Objects:
a. Policy Storage: This involves persisting of the policies
into a repository along with caching of the Internal Policy Objects for
use in evaluation
b. Internal Policy Object Creation: This involves syntax,
semantic analysis of the textual policy stored in the repository and the
creation of abstract syntax trees and symbol tables for use in the
evaluation of the policies.
3. Policy Evaluator - The PolicyEvaluator is responsible for the actual
evaluation of the policies. It uses the Internal Policy Object created
by the PolicyDataStore. It iterates over the list of all object
instances that satisfy the anchor object criterion (refer to the SPL
specification for more information) evaluating conditions and performing
actions.
Development will focus on features, performance, scalability, quality,
and extensibility.
Why ASF?
---------------
The developers of Imperius are interested in joining the Apache Software
Foundation because:
- we would like to encourage binding of the SPL language to
numerous product APIs, especially existing Apache projects, in an
open development environment.
- We would like development of Imperius to take place within the ASF
legal, licensing and oversight structure.
Initial Goals
-------------
The initial goals are to develop an SPL evaluation engine and bindings
to the APIs for:
1. Apache Tomcat
2. Apache HTTP server
3. WSDM (http://www.oasis-open.org/committees/wsdm/)
4. CIM
Current Status
---------------
IBM has a prototype SPL engine, and a binding to CIM APIs.
Meritocracy
------------
The Imperius project will be meritocractic. The project will follow the
guidelines
(http://apache.org/foundation/how-it-works.html#meritocracy) of the
Apache Software Foundation. We plan to proactively recruit individuals
in the Community to: (1) provide function, performance and stability
enhancements to the core engine; (2) encourage bug fixing; (3) improve
code structure; and (4) provide binding to other APIs. We believe that
open, meritocratic development will result in a stronger engine with a
broader range of binding than we could develop internally.
Community
----------
The initial community will be comprised of developers from Sun and
IBM, both of which have substantial interest in the project. The
project will be actively communicated within the ASF and to both the
DMTF and SNIA communities, encouraging growth in the Imperius community.
Core Developers
----------------
The initial core developers will come from IBM and Sun. One Sun
committer has experience with OpenPegasus and Open Solaris. Two IBM
developers have worked on OpenPegasus. Other strong developers have
expressed interest, and we expect them to earn committer status
quickly.
Alignment
----------
As noted above, Imperius can supplement the existing management of Apache
products.
In addition the code has been implemented in Java, and uses other OSS
such as ANTLR and JUNIT. ANT may be used as the code evolves.
Known Risks
------------
Orphaned products
-------------------
This proposal is not the result of an orphaned or abandoned IBM
internal project. This is a proposal we're making with a full
committment to construct an active and successful project. Initial
committers are users of this package, and have an interest in its
ongoing viability.
Inexperience with open source
-----------------------------
The initial committers have varying degrees of experience with open
source projects, as noted above. All have been involved with source
code that has been released under an open source license, but they
lack experience developing code specifically with the ASF development
process. We do not, however, expect any difficulty in executing under
normal meritocracy rules.
Homogeneous Developers
-----------------------
The project will begin with developers from both Sun and IBM, and
we expect that developers from the CIM-SPL community and from other
ASF projects to join. In addition, we have received design comments
from developers associated with the OpenGroup.
We do acknowledge the risk that the project will not garner interest
beyond IBM and Sun, though we believe that interest from communities
involved in the DMTF reduces the risk.
Reliance on salaried developers
---------------------------------
It is expected that Imperius development will occur by developers on both
salaried time and on volunteer time, after hours. While there is
currently a reliance on salaried developers (currently from IBM, but
it's expected that other company's salaried developers will also be
involved), IBM will continue to support the project in the future by
dedicating 'work time' to Imperius.
Relationships with other Apache Products
------------------------------------------
A Excessive Fascination with the Apache Brand
----------------------------------------------
The SPL language and prototype were developed to address the need for
a common policy engine that can be used by a number of others
projects, some part of the ASF. We believe that such synergy, along
with the shared philosophy, and process and licensing consideration,
make the ASF the proper community.
Scope
-------
The scope of the Imperius project at ASF would be to continue the project
development, including adding new features and bindings, and improving
overall code quality, scalability and performance.
Documentation
--------------
The CIM-SPL specification:
http://www.dmtf.org/standards/published_documents/DSP0231.pdf
Initial Source
----------------
The initial source, a prototype SPL engine, has been developed.
Source and Intellectual Property Submission Plan
--------------------------------------------------
The source comes from IBM. IBM will submit a CCLA if the incubator
proposal is accepted.
Information about DMTF policies can be found in references [1], [2] and
[3].
External Dependencies
---------------------
None
Cryptography
--------------
None implemented in the code.
Resources Required
--------------------
(3.1) mailing list(s)
- imperius-private (with moderated subscriptions)
- imperius-dev
- imperius-commits
- imperius-user
(3.2) Subversion or CVS repositories
Imperius would like to use a SVN repository.
(3.3) Jira (issue tracking)
Since Imperius would have its own release cycle, it should have its own
JIRA
project
- Project Name: Imperius
- Project Key: Imperius
Initial Committers
- Mike Nunez <Michael.Nunez at Sun.COM>
- Neeraj Joshi <jneeraj at us.ibm.com>
- Mark Carlson <Mark.Carlson at Sun.COM>
- Prashant Baliga <prabalig at in.ibm.com>
Sponsors
----------
Champion
- Bill Stoddard(stoddard@apache.org)
Nominated Mentors
- Bill Stoddard(stoddard@apache.org)
Sponsoring Entity
- Incubator PMC
References
------------
[1] http://www.dmtf.org/about/policies
[2] http://www.dmtf.org/standards/published_documents/DSP4004.pdf
[3] http://www.dmtf.org/about/policies/patent-10-18-01.pdf
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sunday 30 September 2007 22:06, Bill Stoddard wrote:
> Please vote on accepting project Imperius into the Apache Incubator. The
> vote will run 1 week, until Sunday, Oct. 7, 2007 or until all Incubator PMC
> members have voted.
[x] +1 Accept Imperius project for incubation
Cheers
--
Niclas Hedhman, Software Developer
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 11/10/07, Bill Stoddard <bi...@wstoddard.com> wrote:
>... Bertrand Delacretaz expressed concern about the number of mentors.
> Bertrand, thanks for the feedback, I believe your concern has been resolved....
Indeed, thanks and sorry for not reacting to that with a +1 in due
time - I'm glad the vote passed.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Bill,
I can set up the incubator/imperius repository if you like.
Craig
On Nov 10, 2007, at 6:22 AM, Bill Stoddard wrote:
> The Imperius Project has been accepted into Apache Incubation with
> no dissents and the following votes in favor:
>
> Yoav Shapira, Niclas Hedhman, Craig Russell, Matthieu Riou, Niall
> Pemberton, Robert Burrell Donkin
> Bertrand Delacretaz expressed concern about the number of mentors.
> Bertrand, thanks for the feedback, I believe your concern has been
> resolved.
>
> Project Mentors:
> Bill Stoddard, Filip Hanik, Craig Russell, Kevan Miller (non-
> binding)
>
> Link to Project Proposal:
> http://wiki.apache.org/incubator/ImperiusProposal
>
> -//-
>
> My biggest concern with this project is lack of community
> diversity. Projects that graduate from Incubation must have a
> diverse community, with no exceptions. I've asked David Kaminsky
> and the project members to explicitly consider, plan and document
> activities designed to promote and build the community. Project
> mentors, please reinforce this message with the Imperius Project team.
>
> Congratulations Imperius Project Members!
>
> Bill
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Posted by David L Kaminsky <dl...@us.ibm.com>.
Bill,
Neeraj and I submitted our ICLAs and we mailed the Software Grant. We
should be all set once the infra guys get us set up.
David
Bill Stoddard
<bill@wstoddard.c
om> To
David L Kaminsky/Raleigh/IBM@IBMUS,
11/10/2007 10:46 Mike Nunez <Mi...@Sun.COM>,
AM Neeraj Joshi/Durham/IBM@IBMUS, Mark
Carlson <Ma...@Sun.COM>,
Prashant Baliga
Please respond to <pr...@in.ibm.com>
bill@wstoddard.co cc
m general@incubator.apache.org
Subject
Re: [VOTE RESULT] Accept project
Imperius into the Incubator
Next Steps...
David, Mike, Neeraj, Mark and Prashant, you should:
1. Complete and return ICLAs to the ASF
http://www.apache.org/licenses/icla.txt (flat text file)
http://www.apache.org/licenses/icla.pdf (PDF)
You will not be given commit access to the Imperius source code
repository until you sign the ICLA.
2. Review material at the the following links:
http://www.apache.org/foundation/how-it-works.html
http://www.apache.org/licenses/
3. Ask questions!!
David,
Review and start working on the software grant:
http://www.apache.org/licenses/software-grant.txt
I will ask infra to setup the mailing lists.
Bill
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Posted by Bill Stoddard <bi...@wstoddard.com>.
Next Steps...
David, Mike, Neeraj, Mark and Prashant, you should:
1. Complete and return ICLAs to the ASF
http://www.apache.org/licenses/icla.txt (flat text file)
http://www.apache.org/licenses/icla.pdf (PDF)
You will not be given commit access to the Imperius source code
repository until you sign the ICLA.
2. Review material at the the following links:
http://www.apache.org/foundation/how-it-works.html
http://www.apache.org/licenses/
3. Ask questions!!
David,
Review and start working on the software grant:
http://www.apache.org/licenses/software-grant.txt
I will ask infra to setup the mailing lists.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
[VOTE RESULT] Accept project Imperius into the Incubator
Posted by Bill Stoddard <bi...@wstoddard.com>.
The Imperius Project has been accepted into Apache Incubation with no
dissents and the following votes in favor:
Yoav Shapira, Niclas Hedhman, Craig Russell, Matthieu Riou, Niall
Pemberton, Robert Burrell Donkin
Bertrand Delacretaz expressed concern about the number of mentors.
Bertrand, thanks for the feedback, I believe your concern has been resolved.
Project Mentors:
Bill Stoddard, Filip Hanik, Craig Russell, Kevan Miller (non-binding)
Link to Project Proposal:
http://wiki.apache.org/incubator/ImperiusProposal
-//-
My biggest concern with this project is lack of community diversity.
Projects that graduate from Incubation must have a diverse community,
with no exceptions. I've asked David Kaminsky and the project members to
explicitly consider, plan and document activities designed to promote
and build the community. Project mentors, please reinforce this message
with the Imperius Project team.
Congratulations Imperius Project Members!
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Bertrand Delacretaz wrote:
> On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
>
>> ...Nominated Mentors
>>
>> - Bill Stoddard(stoddard@apache.org)...
>
> Are we willing to accept a podling with just one mentor?
>
> Although [1] doesn't set a minimum number, we usually (always?) have
> more than one.
The recent tradition is to try to obtain and hold three active mentors
per podling, as best we can. I'd love to see two more folks to step up
and help co-mentor.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: [VOTE] Accept project Imperius into the Incubator
Posted by "Noel J. Bergman" <no...@devtech.com>.
Craig Russell wrote:
> > having only one mentor is likely to cause process issues for the
> > podling: there will be no binding quorum
> Not necessarily. The initial committers plus the Mentor would form
> the PPMC, and in this case five members should be able to muster
> three votes.
Unless they are members of the Incubator PMC, their votes are not binding.
--- Noel
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Craig L Russell <Cr...@Sun.COM>.
On Oct 2, 2007, at 9:50 AM, Robert Burrell Donkin wrote:
> On 10/1/07, Bertrand Delacretaz <bd...@apache.org> wrote:
>> On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
>>
>>> ...Nominated Mentors
>>>
>>> - Bill Stoddard(stoddard@apache.org)...
>>
>> Are we willing to accept a podling with just one mentor?
>>
>> Although [1] doesn't set a minimum number, we usually (always?) have
>> more than one.
>
> having only one mentor is likely to cause process issues for the
> podling: there will be no binding quorum
Not necessarily. The initial committers plus the Mentor would form
the PPMC, and in this case five members should be able to muster
three votes.
But I agree that it would be good to find two more volunteer Mentors.
For many reasons we've discussed in the past.
Craig
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On 10/1/07, Bertrand Delacretaz <bd...@apache.org> wrote:
> On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
>
> > ...Nominated Mentors
> >
> > - Bill Stoddard(stoddard@apache.org)...
>
> Are we willing to accept a podling with just one mentor?
>
> Although [1] doesn't set a minimum number, we usually (always?) have
> more than one.
having only one mentor is likely to cause process issues for the
podling: there will be no binding quorum
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
> ...Nominated Mentors
>
> - Bill Stoddard(stoddard@apache.org)...
Are we willing to accept a podling with just one mentor?
Although [1] doesn't set a minimum number, we usually (always?) have
more than one.
(sorry, missed that in the discussion that lead to this vote)
-Bertrand
[1] http://incubator.apache.org/guides/proposal.html#template-mentors
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
> Greetings from North Carolina on a bright, beautiful, sunny fall day!
>
> Thank You to all those who gave comments on the proposal. I made one small tweak; Tomcat, rather than Geronimo, should be one of the first bindings.
>
> Please vote on accepting project Imperius into the Apache Incubator. The vote will run 1 week,
> until Sunday, Oct. 7, 2007 or until all Incubator PMC members have voted.
>
>
> [X] +1 Accept Imperius project for incubation
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/12/07, Bill Stoddard <bi...@wstoddard.com> wrote:
> ...We've not forgotten about this vote.... in a holding pattern while the
> IBM team works out some unanticipated wrinkles ...
Could you update us on the current mentors list?
I think more mentors signed up, it'd be good to have the list here
(and/or add the updated proposal to
http://wiki.apache.org/incubator/).
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Bill Stoddard <bi...@wstoddard.com>.
Incubator PMC members,
We've not forgotten about this vote.... in a holding pattern while the
IBM team works out some unanticipated wrinkles ... too many cooks in the
kitchen :-). I expect to wrap this up late next week. Stay tuned.
Thanks,
Bill
Bill Stoddard wrote:
> Greetings from North Carolina on a bright, beautiful, sunny fall day!
>
> Thank You to all those who gave comments on the proposal. I made one
> small tweak; Tomcat, rather than Geronimo, should be one of the first
> bindings.
>
> Please vote on accepting project Imperius into the Apache Incubator.
> The vote will run 1 week,
> until Sunday, Oct. 7, 2007 or until all Incubator PMC members have voted.
>
>
> [ ] +1 Accept Imperius project for incubation
>
> [ ] 0 Don't care
>
> [ ] -1 Reject for the following reason :
>
>
> Thanks,
> Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
Hi,
> -//-
>
> My biggest concern with this project is lack of community diversity.
> Projects that graduate from Incubation must have a diverse community,
> with no exceptions. I've asked David Kaminsky and the project members to
> explicitly consider, plan and document activities designed to promote
> and build the community. Project mentors, please reinforce this message
> with the Imperius Project team.
>
I was just reading the Imperius proposal and the CIM-SPL spec. If I am
not completely getting it wrong CIM-SPL may be used on a firewall/router
system no?
I am asking this question because I recently submitted the Bennu project
proposal [1] to the incubator ML and I think a CIM-SPL implementation
may be re used to abstract for example firewall rules such as iptables
or OpenBSD pf rule systems.
References:
-----------
[1] Bennu proposal: http://wiki.apache.org/incubator/BennuProposal
Cheers
Daniel S. Haischt
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Matthieu Riou <ma...@offthelip.org>.
On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
>
> Please vote on accepting project Imperius into the Apache Incubator. The
> vote will run 1 week,
> until Sunday, Oct. 7, 2007 or until all Incubator PMC members have voted.
>
[X] +1 Accept Imperius project for incubation
Matthieu
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Niall Pemberton <ni...@gmail.com>.
On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
>
> Please vote on accepting project Imperius into the Apache Incubator. The vote will run 1 week,
> until Sunday, Oct. 7, 2007 or until all Incubator PMC members have voted.
>
>
> [X] +1 Accept Imperius project for incubation
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Craig L Russell <Cr...@Sun.COM>.
+1
Craig
On Sep 30, 2007, at 7:06 AM, Bill Stoddard wrote:
> Greetings from North Carolina on a bright, beautiful, sunny fall day!
>
> Thank You to all those who gave comments on the proposal. I made
> one small tweak; Tomcat, rather than Geronimo, should be one of the
> first bindings.
>
> Please vote on accepting project Imperius into the Apache
> Incubator. The vote will run 1 week,
> until Sunday, Oct. 7, 2007 or until all Incubator PMC members have
> voted.
>
>
> [ ] +1 Accept Imperius project for incubation
>
> [ ] 0 Don't care
>
> [ ] -1 Reject for the following reason :
>
>
> Thanks,
> Bill
>
> -//-
>
> Abstract
> -------------
>
> Policy systems allow administrators to define policies that guide the
> automated administration of resources. Such automation saves time and
> effort by simplifying resource-management.
>
>
> We proposed to develop a policy-based management infrastructure that
> automates administrative tasks by executing policies written in the
> "Simplified Policy Language" (SPL), a standards-based policy language.
>
>
>
> Proposal
> ----------
>
> This proposal seeks to create a project within the Apache Software
> Foundation to (1) develop a policy evaluator for the SPL policy
> language, and (2) develop bindings between the policy evaluator and
> projects such as Apache Geronimo or Apache Tomcat.
>
>
>
> Background
> -----------
>
> As computer systems become more complicated, they continue to become
> increasingly complex and costly to manage. Various studies have shown
> that the cost of managing systems often exceeds the cost of purchasing
> them. The goal of the Imperius project is to reduce management
> burden by
> allowing administrators to specify policies that replace manual
> administrative actions.
>
>
> Rationale
> ----------
>
> Policy-based management is one approach to reducing the cost of
> systems
> administration. Administrators define policies that express a
> "management intent", and the policy-based management system executes
> the policy, thereby reducing the burden on the administrator. For
> example, a policy might state "backup the database daily at 1am." A
> policy management system would interpret the policy, and trigger the
> database to perform a backup at the assigned time, offloading that
> task
> from the administrator.
>
> To allow more flexible semantics, such policies are often expressed as
> "If-Then" (also called "Condition-Action") rules. For example, "If
> the packet comes from subnet 6.7.8.*, Then place it on the
> high-priority outgoing queue" or "If the data in the database have
> changed by 10%, Then perform an incremental backup." Such policies
> allow for more complex automation.
>
> To implement these kinds of rule-based policies, the policy system
> must interact with the system's APIs. In the second example above,
> the system relies on the ability to measure the percentage of data
> that have changed since the last backup (or to compute that value from
> measurable data). Similarly, to execute the "then" clause, the policy
> system must be able to start an incremental backup on the database
> using the database's API. Expressed generally, a policy system must
> have a binding to the "instrumentation layer" or API for the system
> under management.
>
> Thus, policy systems consist of two major components: an evaluation
> engine and a binding to an instrumentation environment. The
> evaluation engine (1) accepts policies expressed according to a
> well-defined grammar, (2) collects the data needed to evaluate the
> policies, and (3) actuates the "Then" section as appropriate.
>
> This project would build an SPL evaluation engine and bindings to
> various Apache and non-Apache APIs.
>
> The design of SPL, a Preliminary DMTF standard, is inspired by
> existing policy languages and models including PDL (policy definition
> language) from Bell Laboratories, the Ponder policy language from
> Imperial College, and other policy languages.
>
> The basic unit of a SPL policy is a policy rule. An SPL policy rule
> consists of a condition, an action, and other fields. Multiple policy
> rules can be grouped into a policy group. Policy groups can be nested
> -- i.e., a policy group can contain another policy group. For the
> specification of the policy condition, SPL provides a rich set of
> operators that act on the following types: signed and unsigned short,
> regular and long integers, float and long float, character, string,
> Boolean, and calendar.
>
> We expect the community to develop a number of bindings between the
> evaluation engine and APIs. Examples include the API for Geronimo
> or Tomcat, and standard interfaces such as WSDM and CIM. The
> community may
> choose to develop a wide range of bindings, all leveraging the common
> SPL engine and policy syntax.
>
> The Imperius Policy Engine will be implemented in the form of a Java
> application. The SPL application will provide the following
> functionality:
>
> 1. PolicyManager - The PolicyManager acts as an orchestrator
> delegating tasks to its subcomponents.
>
> 2. PolicyDataStore - The PolicyDataStore is responsible for two
> major
> tasks: Policy Storage and the creation of Internal Policy Objects:
>
> a. Policy Storage: This involves persisting of the policies
> into a repository along with caching of the Internal Policy Objects
> for
> use in evaluation
> b. Internal Policy Object Creation: This involves syntax,
> semantic analysis of the textual policy stored in the repository
> and the
> creation of abstract syntax trees and symbol tables for use in the
> evaluation of the policies.
>
> 3. Policy Evaluator - The PolicyEvaluator is responsible for the
> actual
> evaluation of the policies. It uses the Internal Policy Object created
> by the PolicyDataStore. It iterates over the list of all object
> instances that satisfy the anchor object criterion (refer to the SPL
> specification for more information) evaluating conditions and
> performing
> actions.
>
> Development will focus on features, performance, scalability, quality,
> and extensibility.
>
>
>
> Why ASF?
> ---------------
> The developers of Imperius are interested in joining the Apache
> Software
> Foundation because:
>
> - we would like to encourage binding of the SPL language to
> numerous product APIs, especially existing Apache projects, in an
> open development environment.
>
> - We would like development of Imperius to take place within the ASF
> legal, licensing and oversight structure.
>
>
> Initial Goals
> -------------
>
> The initial goals are to develop an SPL evaluation engine and bindings
> to the APIs for:
>
> 1. Apache Tomcat
>
> 2. Apache HTTP server
>
> 3. WSDM (http://www.oasis-open.org/committees/wsdm/)
>
> 4. CIM
>
>
> Current Status
> ---------------
>
> IBM has a prototype SPL engine, and a binding to CIM APIs.
>
>
> Meritocracy
> ------------
>
> The Imperius project will be meritocractic. The project will
> follow the
> guidelines
> (http://apache.org/foundation/how-it-works.html#meritocracy) of the
> Apache Software Foundation. We plan to proactively recruit individuals
> in the Community to: (1) provide function, performance and stability
> enhancements to the core engine; (2) encourage bug fixing; (3) improve
> code structure; and (4) provide binding to other APIs. We believe that
> open, meritocratic development will result in a stronger engine with a
> broader range of binding than we could develop internally.
>
>
>
> Community
> ----------
>
> The initial community will be comprised of developers from Sun and
> IBM, both of which have substantial interest in the project. The
> project will be actively communicated within the ASF and to both the
> DMTF and SNIA communities, encouraging growth in the Imperius
> community.
>
>
> Core Developers
> ----------------
>
> The initial core developers will come from IBM and Sun. One Sun
> committer has experience with OpenPegasus and Open Solaris. Two IBM
> developers have worked on OpenPegasus. Other strong developers have
> expressed interest, and we expect them to earn committer status
> quickly.
>
>
>
> Alignment
> ----------
>
> As noted above, Imperius can supplement the existing management of
> Apache
> products.
>
> In addition the code has been implemented in Java, and uses other OSS
> such as ANTLR and JUNIT. ANT may be used as the code evolves.
>
>
>
> Known Risks
> ------------
>
> Orphaned products
> -------------------
>
> This proposal is not the result of an orphaned or abandoned IBM
> internal project. This is a proposal we're making with a full
> committment to construct an active and successful project. Initial
> committers are users of this package, and have an interest in its
> ongoing viability.
>
>
> Inexperience with open source
> -----------------------------
>
> The initial committers have varying degrees of experience with open
> source projects, as noted above. All have been involved with source
> code that has been released under an open source license, but they
> lack experience developing code specifically with the ASF development
> process. We do not, however, expect any difficulty in executing under
> normal meritocracy rules.
>
>
> Homogeneous Developers
> -----------------------
>
> The project will begin with developers from both Sun and IBM, and
> we expect that developers from the CIM-SPL community and from other
> ASF projects to join. In addition, we have received design comments
> from developers associated with the OpenGroup.
>
> We do acknowledge the risk that the project will not garner interest
> beyond IBM and Sun, though we believe that interest from communities
> involved in the DMTF reduces the risk.
>
>
>
> Reliance on salaried developers
> ---------------------------------
>
> It is expected that Imperius development will occur by developers
> on both
> salaried time and on volunteer time, after hours. While there is
> currently a reliance on salaried developers (currently from IBM, but
> it's expected that other company's salaried developers will also be
> involved), IBM will continue to support the project in the future by
> dedicating 'work time' to Imperius.
>
>
> Relationships with other Apache Products
> ------------------------------------------
>
> A Excessive Fascination with the Apache Brand
> ----------------------------------------------
>
> The SPL language and prototype were developed to address the need for
> a common policy engine that can be used by a number of others
> projects, some part of the ASF. We believe that such synergy, along
> with the shared philosophy, and process and licensing consideration,
> make the ASF the proper community.
>
>
> Scope
> -------
>
> The scope of the Imperius project at ASF would be to continue the
> project
> development, including adding new features and bindings, and improving
> overall code quality, scalability and performance.
>
>
> Documentation
> --------------
>
> The CIM-SPL specification:
> http://www.dmtf.org/standards/published_documents/DSP0231.pdf
>
>
> Initial Source
> ----------------
>
> The initial source, a prototype SPL engine, has been developed.
>
>
> Source and Intellectual Property Submission Plan
> --------------------------------------------------
>
> The source comes from IBM. IBM will submit a CCLA if the incubator
> proposal is accepted.
>
> Information about DMTF policies can be found in references [1], [2]
> and
> [3].
>
>
> External Dependencies
> ---------------------
>
> None
>
>
> Cryptography
> --------------
>
> None implemented in the code.
>
>
> Resources Required
> --------------------
>
> (3.1) mailing list(s)
>
> - imperius-private (with moderated subscriptions)
>
> - imperius-dev
>
> - imperius-commits
>
> - imperius-user
>
> (3.2) Subversion or CVS repositories
>
> Imperius would like to use a SVN repository.
>
> (3.3) Jira (issue tracking)
>
> Since Imperius would have its own release cycle, it should have its
> own
> JIRA
> project
>
> - Project Name: Imperius
>
> - Project Key: Imperius
>
>
> Initial Committers
>
> - Mike Nunez <Michael.Nunez at Sun.COM>
>
> - Neeraj Joshi <jneeraj at us.ibm.com>
>
> - Mark Carlson <Mark.Carlson at Sun.COM>
>
> - Prashant Baliga <prabalig at in.ibm.com>
>
>
>
> Sponsors
> ----------
>
> Champion
>
> - Bill Stoddard(stoddard@apache.org)
>
> Nominated Mentors
>
> - Bill Stoddard(stoddard@apache.org)
>
> Sponsoring Entity
>
> - Incubator PMC
>
>
> References
> ------------
> [1] http://www.dmtf.org/about/policies
> [2] http://www.dmtf.org/standards/published_documents/DSP4004.pdf
> [3] http://www.dmtf.org/about/policies/patent-10-18-01.pdf
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Accept project Imperius into the Incubator
Posted by Yoav Shapira <yo...@apache.org>.
Yo,
On 9/30/07, Bill Stoddard <bi...@wstoddard.com> wrote:
> Please vote on accepting project Imperius into the Apache Incubator. The vote will run 1 week,
> until Sunday, Oct. 7, 2007 or until all Incubator PMC members have voted.
>
>
> [ X ] +1 Accept Imperius project for incubation
Yoav
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org