Fwd: Module submission Control::CLI::AvayaData
Hi I did register this module when I first uploaded it (below). It does not however show up in PAUSE under my modules. Should I register it again ? Thanks Best regards Ludovico Stevens Forwarded Message Subject:Module submission Control::CLI::AvayaData Date: Wed, 30 Jul 2014 19:56:19 + (UTC) From: Perl Authors Upload Server Reply-To: modules@perl.org To: modules@perl.org, lstev...@cpan.org The following module was proposed for inclusion in the Module List: modid: Control::CLI::AvayaData DSLIP: RdpOp description: CLI interact with Avaya Networking products userid: LSTEVENS (Ludovico Stevens) chapterid: 5 (Networking_Devices_IPC) communities: similar: Control::CLI rationale: Sub-classes Control::CLI with focus on interacting with the CLI interface of Avaya Networking products (as well as older Nortel Enterprise switching products) over any of Telnet, SSH or Serial Port, using just Perl modules and no external binaries. enteredby: LSTEVENS (Ludovico Stevens) enteredon: Wed Jul 30 19:56:19 2014 UTC The resulting entry would be: Control::CLI:: ::AvayaData RdpOp CLI interact with Avaya Networking products LSTEVENS Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=3ee0_89a5751a7d1bf253&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=3ee0_89a5751a7d1bf253&SUBMIT_pause99_add_mod_insertit=1 Peek at the current permissions: https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Control%3A%3ACLI%3A%3AAvayaData
Module submission Control::CLI::AvayaData
The following module was proposed for inclusion in the Module List: modid: Control::CLI::AvayaData DSLIP: RdpOp description: CLI interact with Avaya Networking products userid: LSTEVENS (Ludovico Stevens) chapterid: 5 (Networking_Devices_IPC) communities: similar: Control::CLI rationale: Sub-classes Control::CLI with focus on interacting with the CLI interface of Avaya Networking products (as well as older Nortel Enterprise switching products) over any of Telnet, SSH or Serial Port, using just Perl modules and no external binaries. enteredby: LSTEVENS (Ludovico Stevens) enteredon: Wed Jul 30 19:56:19 2014 UTC The resulting entry would be: Control::CLI:: ::AvayaData RdpOp CLI interact with Avaya Networking products LSTEVENS Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=3ee0_89a5751a7d1bf253&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=3ee0_89a5751a7d1bf253&SUBMIT_pause99_add_mod_insertit=1 Peek at the current permissions: https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Control%3A%3ACLI%3A%3AAvayaData
Module submission Control::CLI
The following module was proposed for inclusion in the Module List: modid: Control::CLI DSLIP: RdpOp description: Command Line Interface via ssh/telnet/serial userid: LSTEVENS (Ludovico Stevens) chapterid: 5 (Networking_Devices_IPC) communities: similar: Net::Telnet, Net::SSH2, Win32::SerialPort, Device::SerialPort rationale: A Command Line Interface (CLI) is an interface where the user is presented with a command prompt and has to enter ASCII commands to drive or control or configure that device. That interface could be the shell on a Unix system or some other command interpreter on a device such as an ethernet switch or an IP router or some kind of security appliance. This module is useful to control/automate/script a remote device by interacting with its CLI interface remotely over any type of connection which can be used to reach the CLI interface of that remote device. Control::CLI supports any of Telnet, SSHv2 (using an interactive shell channel) and Serial Port connections. Much of the functionality of this module is in fact similar (and in some cases identical) to that offered by the popular Net::Telnet module. The real benefit of this module is that connection and basic I/O can be performed in a consistent manner regardless of the underlying connection type thus allowing CLI based scripts to be easily converted between or operate over any of Telnet, SSH or Serial port connection. To do so, Control::CLI relies on these underlying modules: Net::Telnet for Telnet access Net::SSH2 for SSH access Win32::SerialPort or Device::SerialPort for Serial port access respectively on Windows and Unix systems Since all of the above are Perl standalone modules (which do not need to rely on external binaries) scripts using Control::CLI can easily be ported to any OS platform (where either Perl is installed or by simply packaging the Perl script into an executable with PAR::Packer's pp). In particular this is a big advantage for portability to Windows platforms where using Expect scripts is usually not possible. Note that Net::SSH2 only supports SSHv2 and this class will always and only use Net::SSH2 to establish a channel over which an interactive shell is established with the remote host. This is typically the only way that SSH is implemented on ethernet switches and IP routers and other appliances. Both password and publickey authentication are supported. Each of the above modules is optional (they are not required to install Control::CLI), however if one of the modules is missing then no access of that type will be available. For instance if Win32::SerialPort is not installed (on a Windows system) but both Net::Telnet and Net::SSH2 are, then Control::CLI will be able to operate over both Telnet and SSH, but not Serial port. There has to be, however, at least one of the above modules installed, otherwise Control::CLI's constructor will throw an error. enteredby: LSTEVENS (Ludovico Stevens) enteredon: Fri Jan 4 09:40:10 2013 GMT The resulting entry would be: Control:: ::CLI RdpOp Command Line Interface via ssh/telnet/serial LSTEVENS Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=1e80_af63c268707ef089&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=1e80_af63c268707ef089&SUBMIT_pause99_add_mod_insertit=1 Peek at the current permissions: https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Control%3A%3ACLI
Re: Module submission Control::CLI
On 08/02/2011 00:40, brian d foy wrote: [[ This message was both posted and mailed: see the "To," "Cc," and "Newsgroups" headers for details. ]] In article<201102061041.p16afvio005...@pause.fiz-chemie.de>, Perl Authors Upload Server wrote: The following module was proposed for inclusion in the Module List: modid: Control::CLI DSLIP: RdpOp description: Control a device by interacting with its CLI userid: LSTEVENS (Ludovico Stevens) chapterid: 5 (Networking_Devices_IPC) communities: Mailinglists I don't think Control::* gives the right context here. Most people think of this sort of thing as "Expect". Is there something that your tool does that Expect doesn't? Maybe we can come up with a better name. :) Hi My module is the same thing as Net::Telnet but can also handle SSH and Serial connections. So it differs from Expect in the same way that Net::Telnet does. Expect is all about spawning an "external" command/binary and controlling that. Expect lacks portability as the target machine for your script needs to have that external command/binary installed. Expect also does not work on Microsoft Windows, or maybe it does with Cygwin but again that hampers portability. The scripts I write with perl (using my module, like Net::Telnet) I can bundle into a single exe file and they work on any target machine (and 99% of the time I need them to run on Win32). I emailed the module authors distribution list some 6 month ago for advice on module naming. Originally I had named it Net::CLI, but I changed it to Control::CLI based on the only advice I got: http://www.nntp.perl.org/group/perl.module-authors/2010/07/msg8681.html If you have a better suggestion it is welcome. Best regards Ludovico Stevens
Re: Module submission Control::CLI
[[ This message was both posted and mailed: see the "To," "Cc," and "Newsgroups" headers for details. ]] In article <201102061041.p16afvio005...@pause.fiz-chemie.de>, Perl Authors Upload Server wrote: > The following module was proposed for inclusion in the Module List: > > modid: Control::CLI > DSLIP: RdpOp > description: Control a device by interacting with its CLI > userid: LSTEVENS (Ludovico Stevens) > chapterid: 5 (Networking_Devices_IPC) > communities: > Mailinglists I don't think Control::* gives the right context here. Most people think of this sort of thing as "Expect". Is there something that your tool does that Expect doesn't? Maybe we can come up with a better name. :) -- brian d foy (one of many PAUSE admins), http://pause.perl.org PAUSE instructions: http://pause.perl.org/pause/query?ACTION=pause_04about Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules Please send all messages back to modules@perl.org with no CC to me.
Module submission Control::CLI
The following module was proposed for inclusion in the Module List: modid: Control::CLI DSLIP: RdpOp description: Control a device by interacting with its CLI userid: LSTEVENS (Ludovico Stevens) chapterid: 5 (Networking_Devices_IPC) communities: Mailinglists similar: Similar to Net::Telnet, but not limited to Telnet; also works over SSHv2 and Serial Port connections rationale: A Command Line Interface (CLI) is an interface where the user is presented with a command prompt and has to enter ASCII commands to drive or control or configure that device. That interface could be the shell on a unix system or some other command interpreter on a device such as an ethernet switch or an IP router or some kind of security appliance. This module is useful to control/automate/script a remote device by interacting with its CLI interface remotely over any type of connection which can be used to reach the CLI interface of that remote device. Control::CLI supports any of Telnet, SSHv2 (using an interactive shell channel) and Serial Port connections. Much of the functionality of this module is in fact similar (and in some cases identical) to that offered by the popular Net::Telnet module. The real benefit of this module is that connection and basic I/O can be performed in a consistent manner regardless of the underlying connection type thus allowing CLI based scripts to be easily converted between or operate over any of Telnet, SSH or Serial port connection. To do so, Control::CLI relies on these underlying modules: Net::Telnet for Telnet access Net::SSH2 for SSH access Win32::SerialPort or Device::SerialPort for Serial port access respectively on Windows and Unix systems enteredby: LSTEVENS (Ludovico Stevens) enteredon: Sun Feb 6 10:41:31 2011 GMT The resulting entry would be: Control:: ::CLI RdpOp Control a device by interacting with its CLI LSTEVENS Thanks for registering, -- The PAUSE PS: The following links are only valid for module list maintainers: Registration form with editing capabilities: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=1440_1f22c336228675d3&SUBMIT_pause99_add_mod_preview=1 Immediate (one click) registration: https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=1440_1f22c336228675d3&SUBMIT_pause99_add_mod_insertit=1 Peek at the current permissions: https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Control%3A%3ACLI
