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

Shinken 2.4 Roadmap #1451

Closed
Seb-Solon opened this Issue Jan 12, 2015 · 4 comments

Comments

Projects
None yet
4 participants
@Seb-Solon
Contributor

Seb-Solon commented Jan 12, 2015

Let's define the 2.4 Roadmap!

Release will be on 31/03/2015. See #1394

Feel free to edit this message :)

@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Jan 13, 2015

Owner

We will start with addings hosts, not service or others object. hosts are what is important,the other can wait. Will be still a nightmare to manage in a clean way hosts :)

Owner

naparuba commented Jan 13, 2015

We will start with addings hosts, not service or others object. hosts are what is important,the other can wait. Will be still a nightmare to manage in a clean way hosts :)

@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Jan 13, 2015

Owner

and i remove bug fix. It's a "of course" entry :)

Owner

naparuba commented Jan 13, 2015

and i remove bug fix. It's a "of course" entry :)

@Seb-Solon Seb-Solon added this to the 2.4 (Noteworthy Nagapie) **we will find :)** milestone Jan 14, 2015

@andyxning

This comment has been minimized.

Show comment
Hide comment
@andyxning

andyxning Jan 28, 2015

Can we just think about External Commands. I have also thought about this sometimes. I think External Commands may give us a another road to achieve this.

  • before, we do any run-time update about the configurations in Shinken, we should run shinken-arbiter to check if the update is correct. However, the existing External Commands is not enough to accomplish this job. If available, we think that we should add some more Commands.
  • If, the check is passed without error or conflict. Then, we can invoke External Commands to do this update.

andyxning commented Jan 28, 2015

Can we just think about External Commands. I have also thought about this sometimes. I think External Commands may give us a another road to achieve this.

  • before, we do any run-time update about the configurations in Shinken, we should run shinken-arbiter to check if the update is correct. However, the existing External Commands is not enough to accomplish this job. If available, we think that we should add some more Commands.
  • If, the check is passed without error or conflict. Then, we can invoke External Commands to do this update.
@gst

This comment has been minimized.

Show comment
Hide comment
@gst

gst Feb 4, 2015

Contributor

FYI:

  • "Native" plugin (plugin imported as python module once and "directly" executed in python) (@gst) (Maybe outside shinken core, in a new poller module)

=> https://github.com/shinken-monitoring/mod-native-plugins (WIP)

Contributor

gst commented Feb 4, 2015

FYI:

  • "Native" plugin (plugin imported as python module once and "directly" executed in python) (@gst) (Maybe outside shinken core, in a new poller module)

=> https://github.com/shinken-monitoring/mod-native-plugins (WIP)

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