Hi all,

As per the offline discussion had with Pradeep and Azeez few days back, I
have implemented the bootup-validator component's framework to be
extensible.

The component can be extended with new bootup validation tests by adding
new ConfigurationValidator classes with relevant parameters to validate; in
the config_recommendations.xml (the newly introduced xml in repository/conf)

A sample config_recommendations.xml:

<Configuration>
    <Validator class="org.wso2.carbon.core.bootup.validator.HWValidator">
        <Parameter name="cpu">800</Parameter>
        <Parameter name="ram">1000</Parameter>
    </Validator>
    <Validator class="org.wso2.carbon.core.bootup.validator.JVMValidator">
        <Parameter name="heapMemory">6000</Parameter>
        <Parameter name="nonHeapMemory">4000</Parameter>
        <Parameter name="totalMemory">10000</Parameter>
        <Parameter name="freeMemory">2000</Parameter>
    </Validator>
</Configuration>

The system data collection can also be extended in the same manner.
At the moment I'm having trouble with Sigar API to retrieve HW
configuration data (CPU, RAM), will update the thread with progress.

Thanks,
Dileepa

On Fri, Jan 13, 2012 at 1:01 PM, Pradeep Fernando <[email protected]> wrote:

> Hi,
>
> are we going to allow users to implement their own bootup tests, using
> somekind of extension mechanism. (we are providing all the gathered info,
> they decide on what to do with those). Is it a overkill ?
>
> are we doing any native calls within the carbon-env (Now). ?
>
> thanks,
> --Pradeep
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

Mobile : +94777-857616
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to