[
https://issues.apache.org/jira/browse/SLING-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637871#comment-13637871
]
Bertrand Delacretaz commented on SLING-2822:
--------------------------------------------
I wouldn't completely remove the JUnit stuff, rather move it to a separate
bundle under testing/junit where it belongs, and maybe not include it by
default once we eventually add HC to the Sling launchpad. The optional imports
are a good sign that this needs to be a separate bundle.
Here's my current open issues list, revised to include this:
-The servlet output is not JSON
-Implement access restrictions as described above
-A Web console plugin might be useful to execute rules found under a specified
path
-Provide a simple HTML report of rules execution (in the Web console maybe?)
-Tags on rules? Can be useful to execute only subsets of them
-Need to clarify the naming conventions as per Felix's comment above
-Implement a demo rule that checks scripts for suboptimal/deprecated code and
outputs improvement suggestions (helps make sure rule output is appropriate for
such use cases)
-Add a core rule that checks OSGi configuration parameters
-Move the JUnit stuff to its own bundle under testing/junit
> Extensible Sling system health checking tool
> --------------------------------------------
>
> Key: SLING-2822
> URL: https://issues.apache.org/jira/browse/SLING-2822
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Attachments: nodes.json, nodes.json, setup.bash
>
>
> I have created a prototype at https://github.com/bdelacretaz/muppet-prototype
> that we might want to move to our contrib folder.
> Muppet (it's like a Puppet, but different (*)) allows you to check the health
> of a system by defining rules that (out of the box) verify things like the
> presence of specific OSGi bundles, JMX MBeans values, JUnit tests execution
> (including scriptable ones thanks to the Sling testing tools), correct
> disabling of default Sling credentials, etc.
> New rule types can be defined by adding RuleBuilder OSGi services, there are
> several examples in this initial code.
> I'll add a how-to for this initial version here.
> Known issues are:
> -The output does not indicate the value that causes a rule to fail
> -The servlet output is not JSON yet
> -Tags on rules would be nice to be able to run just the performance or
> security rules for example
> -A rule for checking OSGi configuration parameters would be useful.
> (*) credits to Joerg Hoh for that one, as well as inspiration in
> https://github.com/joerghoh/cq5-healthcheck
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
