karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Commented: (KARAF-216) Create an admin:clone command
Date Tue, 08 Feb 2011 07:25:57 GMT

    [ https://issues.apache.org/jira/browse/KARAF-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991823#comment-12991823
] 

Jean-Baptiste Onofré commented on KARAF-216:
--------------------------------------------

More than the features URLs, all configuration file should be cloned. For instance, if the
source instance contains a "tuned" org.ops4j.pax.logging.cfg file, the "cloned" instance should
contain the same thing.

> Create an admin:clone command
> -----------------------------
>
>                 Key: KARAF-216
>                 URL: https://issues.apache.org/jira/browse/KARAF-216
>             Project: Karaf
>          Issue Type: Improvement
>          Components: runtime
>    Affects Versions: 2.0.0
>         Environment: All
>            Reporter: Adrian Trenaman
>            Assignee: Jean-Baptiste Onofré
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Create an 'admin:clone' command. This command would allow you to create a new instance
of the current broker, with the same list of features and featureURLs. 
> Options to the command would be: 
> -l <location>: the file location.
> -p <port>: the port for SSH
> -jmxPort <port>: the JMX port to listen on
> -f <feature>: if specified, this flag will override the current instances list
of boot features with the specified features.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message