Ok, replying directly to a review request message does not work... Retrying the send of this.
________________________________ From: Anders Björnerstedt Sent: den 18 juli 2013 16:32 To: '[opensaf:tickets] ' Subject: RE: [tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB) One early review comment I have is about terminology. The terms "transaction mode" and "non-transaction mode" are used in a way that makes me a little uneasy. All ccbs are transactions, even single operation ccbs are transactions in the sense of having all the ACID properties over the cluster. Command exlpanations like: "--ccb-apply will commit a transaction. In non-transaction mode, --ccb-apply doesn't do anything and always return 0" could be missundersdtood. I would prefer a term like: "auto-apply-mode" vs "explicit-apply-mode", or equivalently "auto-commit-mode" vs "explicit-commit-mode". And "--ccb-apply will apply/commit the current ccb. In auto-apply mode, an explicit --ccb-apply has no effect." /AndersBj ________________________________ From: Zoran Milinkovic [mailto:[email protected]] Sent: den 18 juli 2013 15:49 To: [opensaf:tickets] Subject: [tickets] [opensaf:tickets] #20 IMMTOOLS: immcfg support for mixed changes in a transaction (CCB) Features in immcfg: * If libreadline is supported by the system, readline and history will be used in command line mode, otherwise stdin without history is used * --ccb-apply will commit a transaction. In non-transaction mode, --ccb-apply doesn't do anything and always return 0 * --ccb-abort will abort a transaction. In non-transaction mode, --ccb-abort doesn't do anything, and always return 0 * On error, if immcfg uses input from a pipe or a file, immcfg aborts a transaction and exit. In command line mode, immcfg aborts a transaction and continue to work * Ctrl+D commit a transaction and exit * Ctrl+C abort a transaction and exit ________________________________ [tickets:#20]<http://sourceforge.net/p/opensaf/tickets/20/> IMMTOOLS: immcfg support for mixed changes in a transaction (CCB) Status: review Created: Tue May 07, 2013 08:47 AM UTC by Zoran Milinkovic Last Updated: Thu Jul 18, 2013 01:35 PM UTC Owner: Zoran Milinkovic Today immcfg only support one type of change at a time (create, delete, modify). This makes more complicated changes fragile since they are not protected by an IMM CCB. A rather easy fix would be to have the immcfg read from stdin and add each line to the same CCB, and at end of file commit the CCB. Is is suggested that each line of input is of exactly the same syntax as the current command line. The change will be backwards compatible and just extend immcfg. Any comments on this idea? Migrated from: http://devel.opensaf.org/ticket/2437 ________________________________ Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
