New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create jabber/irc/etc bots for Salt, and the associated documentation. #8682

Closed
gravyboat opened this Issue Nov 20, 2013 · 7 comments

Comments

Projects
None yet
6 participants
@gravyboat
Member

gravyboat commented Nov 20, 2013

@zfouts and I were discussing bots in the IRC and thought it might be nice if there was a centralized documentation page talking about the positives/negatives and security concerns of bots, as well as links to some repos that had bots for the more popular options.

@kaithar

This comment has been minimized.

Show comment
Hide comment
@kaithar

kaithar Nov 28, 2013

Contributor

This actually sounds matches up with a side-project I've been playing with ... making an improved version of the campfire/hubot model.

What are you thinking a Salt bot would do?
IM access to the salt executable modules like salt cli gives?
Notification of actions? (auditing and such... "Kaithar has just run state.highstate")
Notification of results of jobs?
Event sink?

Contributor

kaithar commented Nov 28, 2013

This actually sounds matches up with a side-project I've been playing with ... making an improved version of the campfire/hubot model.

What are you thinking a Salt bot would do?
IM access to the salt executable modules like salt cli gives?
Notification of actions? (auditing and such... "Kaithar has just run state.highstate")
Notification of results of jobs?
Event sink?

@UtahDave

This comment has been minimized.

Show comment
Hide comment
@UtahDave

UtahDave Nov 28, 2013

Member

I really like this idea.

I think it would be great to be able to "register" for various types of
alerts

  • execution failures
  • results of all executions
  • summaries of all executions
  • register to listen to various tags on the event bus, such as a new minion
    being accepted

Executing commands could be interesting if the security model was done
correctly

xt in irc did a proof of concept of this last year sometime
On Nov 28, 2013 6:36 AM, "kaithar" notifications@github.com wrote:

This actually sounds matches up with a side-project I've been playing with
... making an improved version of the campfire/hubot model.

What are you thinking a Salt bot would do?
IM access to the salt executable modules like salt cli gives?
Notification of actions? (auditing and such... "Kaithar has just run
state.highstate")
Notification of results of jobs?
Event sink?


Reply to this email directly or view it on GitHubhttps://github.com/saltstack/salt/issues/8682#issuecomment-29463858
.

Member

UtahDave commented Nov 28, 2013

I really like this idea.

I think it would be great to be able to "register" for various types of
alerts

  • execution failures
  • results of all executions
  • summaries of all executions
  • register to listen to various tags on the event bus, such as a new minion
    being accepted

Executing commands could be interesting if the security model was done
correctly

xt in irc did a proof of concept of this last year sometime
On Nov 28, 2013 6:36 AM, "kaithar" notifications@github.com wrote:

This actually sounds matches up with a side-project I've been playing with
... making an improved version of the campfire/hubot model.

What are you thinking a Salt bot would do?
IM access to the salt executable modules like salt cli gives?
Notification of actions? (auditing and such... "Kaithar has just run
state.highstate")
Notification of results of jobs?
Event sink?


Reply to this email directly or view it on GitHubhttps://github.com/saltstack/salt/issues/8682#issuecomment-29463858
.

@gravyboat

This comment has been minimized.

Show comment
Hide comment
@gravyboat

gravyboat Nov 28, 2013

Member

@kaithar The original idea was simply to use this for reporting the output of jobs and notifications of action so we could avoid diving into a security model too much. I'll have to talk with xt and see what his progress was looking like on the bot.

Member

gravyboat commented Nov 28, 2013

@kaithar The original idea was simply to use this for reporting the output of jobs and notifications of action so we could avoid diving into a security model too much. I'll have to talk with xt and see what his progress was looking like on the bot.

@zfouts

This comment has been minimized.

Show comment
Hide comment
@zfouts

zfouts Nov 28, 2013

The original idea was to give access to salt without providing shell access
to the master. The bot would have very limited ACL access to which
commands. However I really love some of the other ideas that were brought
up.

Some examples of what it could do possibly:

[!] Could not run state.highstate on app192.prod.dfw.domain.com
[*] New minion online - web913.stage.phx.domain.com
!#minions
human: Total Minions: 610 | Minions Online: 481
[!] db13slave.prod.phx.domain.com - Unresponsive to ping
[!] web17.prod.ord.domain.com - Apache was not running - restarting.
!run state.highstate
[state.highstate] web13.prod.ord.domain.com - 1 or more states failed
to run - please check the log
[state.highstate] db19slave.prod.ord.domain.com - 1 or more states
failed to run - please check the log
[state.highstate] 480 minions complete : 478 succeeded 2 failed

I will try to make some progress over this long holiday and post some proof
of concepts.

zfouts commented Nov 28, 2013

The original idea was to give access to salt without providing shell access
to the master. The bot would have very limited ACL access to which
commands. However I really love some of the other ideas that were brought
up.

Some examples of what it could do possibly:

[!] Could not run state.highstate on app192.prod.dfw.domain.com
[*] New minion online - web913.stage.phx.domain.com
!#minions
human: Total Minions: 610 | Minions Online: 481
[!] db13slave.prod.phx.domain.com - Unresponsive to ping
[!] web17.prod.ord.domain.com - Apache was not running - restarting.
!run state.highstate
[state.highstate] web13.prod.ord.domain.com - 1 or more states failed
to run - please check the log
[state.highstate] db19slave.prod.ord.domain.com - 1 or more states
failed to run - please check the log
[state.highstate] 480 minions complete : 478 succeeded 2 failed

I will try to make some progress over this long holiday and post some proof
of concepts.

@torhve

This comment has been minimized.

Show comment
Hide comment
@torhve

torhve Jul 3, 2014

Contributor

Proof of concept here:
https://github.com/torhve/saltibot

For now this is only output of events from salt. You can't control salt via IRC in this bot yet. But that's fairly easy to add.

Contributor

torhve commented Jul 3, 2014

Proof of concept here:
https://github.com/torhve/saltibot

For now this is only output of events from salt. You can't control salt via IRC in this bot yet. But that's fairly easy to add.

@jcockhren

This comment has been minimized.

Show comment
Hide comment
@jcockhren

jcockhren Jul 3, 2014

Contributor

fwiw, @kaithar's bot is a good approach to pythonic bots: https://github.com/kaithar/muhubot

Here's one that I wrote: https://github.com/sophicware/benderbot

Contributor

jcockhren commented Jul 3, 2014

fwiw, @kaithar's bot is a good approach to pythonic bots: https://github.com/kaithar/muhubot

Here's one that I wrote: https://github.com/sophicware/benderbot

@stale stale bot added the stale label Aug 12, 2017

@stale

This comment has been minimized.

Show comment
Hide comment
@stale

stale bot Aug 12, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

stale bot commented Aug 12, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot closed this Aug 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment