On Wed, Sep 3, 2014 at 7:57 AM, Frits Hoogland <[email protected]> wrote:
> I am actually quite surprised by the lack of response. > > When using Ansible for implementing changes across systems, I can't help > to think you want to talk to network devices and alter rules? Also, when > doing operating system and hardware updates, you want to talk to the BMC, > for which the ssh port is the most reliable way! > > > I've gone through researching, and actually this seems to be a > question/feature request that pops up reasonably frequently at different > places. > > When seen as a feature request, it would be to implement a mode in the raw > module, which makes raw to just log on, and issues a command and reads the > output, instead of requesting a shell. mode=shell or plain. > I'm open to this. > > In my opinion adding a raw plain mode would open up access to a lot of > devices which are inherently unreachable by other orchestration engines > because they require an agent. The magic is in the fact that you can issue > any command to the device, instead of writing a module specifically for a > specific device. > > Cheers, > > Frits > > > On Wednesday, September 3, 2014 1:45:30 PM UTC+2, Michael DeHaan wrote: > >> I don't think it's an issue so much as a feature request - though it >> doesn't seem like there are, given lack of response to this email thread. >> >> I will say connections in ansible aren't meant to talk to non-computers, >> and in many cases, this may be something that needs to write a module to >> talk to them, similar to what we do with various load balancers. >> >> There was a recent thread about HP switches and not really having a shell >> when you login that's the same kind of thing. >> >> Most folks are using ILO's for basic power management via fence and >> haven't automated a lot more. >> >> Anyway, a module is probably appropriate, though we are probably unlikely >> to include it in core if the goal is to simulate a monitoring system. >> >> >> >> >> >> >> >> >> On Wed, Sep 3, 2014 at 7:41 AM, Frits Hoogland <[email protected]> >> wrote: >> >>> Anyone else interested in looking into this issue? >>> >>> -- >>> 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/69dc177c-f626-4af9-a90d- >>> 796354790c23%40googlegroups.com >>> <https://groups.google.com/d/msgid/ansible-project/69dc177c-f626-4af9-a90d-796354790c23%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> 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/871f0904-3bf8-4dcf-ac30-5378d6e67be6%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/871f0904-3bf8-4dcf-ac30-5378d6e67be6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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%2BnsWgyJ4590Z0tin766JP%2BO2BPkwOkhFUxW1KoSt%3D8XtwJ0nQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
