You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Brian Topping (JIRA)" <ji...@apache.org> on 2011/09/23 14:50:27 UTC
[jira] [Created] (KARAF-890) "Macro Recorder" for patch
installation
"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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-890) "Macro Recorder" for patch
installation
Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-890) "Macro Recorder" for patch
installation
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116115#comment-13116115 ]
Jean-Baptiste Onofré commented on KARAF-890:
--------------------------------------------
It sounds good. On Unix, screen -L (log mode) does quite the same: it's able to generate a "script file" by recording user actions.
> "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
>
> 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
[jira] [Commented] (KARAF-890) "Macro Recorder" for patch
installation
Posted by "Andreas Pieber (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116316#comment-13116316 ]
Andreas Pieber commented on KARAF-890:
--------------------------------------
nothing to add. Really great idea. Besides of the possibility to push this into the SCM it is also quite useful during developing. I often have situations where I need a clean karaf in a very specific state and it would be really useful starting karaf, exec the script and having it in a defined state...
--> +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
>
> 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
[jira] [Updated] (KARAF-890) "Macro Recorder" for patch
installation
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-890:
---------------------------------------
Fix Version/s: 3.0.0
> "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.0
>
>
> 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
[jira] [Updated] (KARAF-890) "Macro Recorder" for patch
installation
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Pieber updated KARAF-890:
---------------------------------
Fix Version/s: (was: 3.0.1)
3.1.0
NO improvements or new features on micro release branches! I've set the target to 3.1.0.
> "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.1.0
>
>
> 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