karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-890) "Macro Recorder" for patch installation
Date Wed, 07 Mar 2012 13:30:59 GMT

     [ https://issues.apache.org/jira/browse/KARAF-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jamie goodyear updated KARAF-890:
---------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.0.1
    
> "Macro Recorder" for patch installation
> ---------------------------------------
>
>                 Key: KARAF-890
>                 URL: https://issues.apache.org/jira/browse/KARAF-890
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-shell
>            Reporter: Brian Topping
>            Priority: Trivial
>             Fix For: 3.0.1
>
>
> I had this idea so I thought I would share it.  I don't believe I have the skills to
implement it (yet), but thought I would at least get it out of my head so I don't forget it.
> When applying changes to an instance that I would like to replicate across multiple nodes
and/or otherwise notate the changes I made, it might be helpful to have something like a "macro
recorder" that can monitor my changes, record them in a replay file, allow the file to be
edited, and play the the file back.  Even in many nodes clustered in a single cluster (the
changes should propagate), any changes would likely be tested in a test cluster first and
that file committed to SCM, and the ability to apply the exact changes that were committed
to SCM could provide the immediacy of the command-line with the reproducibility of a more
structured environment.  
> From an implementation perspective, if the actions of the different commands that change
Karaf's state were firing events, it should be very simple to implement all this.  I think
it would be good that the recorder automatically kept a list of macros rather than requiring
special setup or explicit saving.  That way, macros could form "quick notes" whereby if someone
was doing something they wanted to remember, they could just start the macro recorder, and
when they stopped it, if they didn't do anything, it would still automatically persist their
work until such time they did something with it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message