This one 'telnet' module could be used in many cases. Abstracting by implementing this in a generic way, like uri, get_url, wait_for, would add more power to the core modules.
<IMHO> Implementing adapter modules for each and every API looks like a maintenance burden. When I first looked at the list of api modules, it looked haphazard. On Apr 16, 2014, at 13:42, Michael DeHaan <[email protected]> wrote: > So in that case, what I would probably do is write a module for managing the > OSGI modules, and this module could be deployed via the regular SSH mechanism > and then could connect to 127.0.0.1:port to send commands from that module. > > We have some other modules that speak "API" once deployed, many rely on > various libraries versus low-level socket bits, for which you may have some > in Python available to you, if not, telnet protocol isn't too atrocious :) > > > > > On Wed, Apr 16, 2014 at 2:54 AM, Bas Meijer <[email protected]> wrote: > Obviously I am not running a telnet server, hence the quotes in my question. > Tomcat Virgo is an OSGi Java server that allows management with a localhost > telnet-like interface for managing OSGi modules. Allowing a query 'ss' and > commands like 'refresh 140', 'stop 123', 'start 54'. > > $ telnet localhost 2501 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > osgi> ss > "Framework is launched." > > > id State Bundle > 0 ACTIVE org.eclipse.osgi_3.8.1.v20120830-144521 > Fragments=1 > 35 ACTIVE org.eclipse.virgo.kernel.userregionfactory_3.6.2.RELEASE > 64 ACTIVE org.eclipse.equinox.cm_1.0.400.v20120319-2029 > 65 ACTIVE org.eclipse.virgo.kernel.userregion_3.6.2.RELEASE > 66 ACTIVE org.eclipse.virgo.shell.command_3.6.2.RELEASE > 67 ACTIVE org.eclipse.osgi.services_3.3.0.v20120307-2102 > ... > > Lot's of other protocols print a header with their version on connect, have a > debug port, or allow a shutdown string. A generic 'telnet' module would be a > nice addition to the ansible toolbox. If it is as simple as you said, just do > it please. > > > > On Apr 15, 2014, at 23:49, Michael DeHaan <[email protected]> wrote: > >> There isn't, and quite intentionally. >> >> Telnet is a obviously a very insecure protocol, completely insecure in fact, >> and we strongly want to discourage usage. >> >> Yet, it would be quite trivial to write a connection plugin to support it, >> though, as connection plugins just need to support the ability to put a >> file, get a file, and execute a module (assume ftp would also be used rather >> than netcat?). >> >> To be honest, I considered it as an April fools joke at one point -- to >> actually implement it -- but I didn't do it. >> >> Most networking equipment -- though a lot of the ways people attempt to >> configure networking equipment with Ansible can be hacky -- can usually be >> coerced into enabling SSH. >> >> We would likely refuse the pull request, to be honest -- it is just asking >> for a world of hurt should MITM possibilities arise. >> >> --Michael >> >> >> >> >> >> On Tue, Apr 15, 2014 at 5:33 PM, Bas Meijer <[email protected]> wrote: >> Is there by any chance a 'telnet' module? I would like to connect to a >> certain port on localhost and enter text and look for strings in the output. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/91124DEF-F2F0-40D1-94B1-A673D7119008%40iwelcome.com. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgzSaHKkcctOF%2BcL3N9sSq8oiytyp6ZrdPqr%3Dit229gc9A%40mail.gmail.com. >> >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/0AEE7140-9784-49C7-82AC-4A798306A396%40iwelcome.com. > > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgw%3Da8sOvXWRZnJoh9k8Audj6Lnn5GZ2J%3DOSesNd2g0i-A%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/B3446F6F-30E2-4C8A-A766-0E884D3F2EAC%40iwelcome.com. For more options, visit https://groups.google.com/d/optout.
