Skip to content
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

[dev.icinga.com #10362] Debian packaging: Separate package for CLI missing #2083

Closed
icinga-migration opened this issue Oct 14, 2015 · 8 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Oct 14, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10362

Created by tgelf on 2015-10-14 15:45:01 +00:00

Assignee: mfrosch
Status: Closed (closed on 2016-02-22 12:11:58 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-22 12:48:55 +00:00 (in Redmine)


We used to have a "common", a "web" and a "cli" package for good reasons. I never tried out the Debian packages before - until now. Wanted to install icingacli and a custom module on a monitoring node. Web frontend is neither needed nor allowed on the target system.

Seems that the cli package has gone and icingacli is now part of "icingaweb2". And there is absolutely no way to install icingaweb2 without being bombed by an undesired full-blown web server. What happened here? At first sight, all other (not Debian based) distros look fine to me.

Regards,
Thomas

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Oct 14, 2015

Updated by tgelf on 2015-10-14 15:51:08 +00:00

  • Status changed from New to Feedback
  • Assigned to set to mfrosch

lazyfrosch, I found this:

http://anonscm.debian.org/cgit/pkg-nagios/pkg-icingaweb2.git/commit/?id=6cb006135c859789c8c0b229d52f473ba198a0ff

What's been the motivation for this change? Is there any related ticket?

Thanks,
Thomas

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Oct 20, 2015

Updated by mfrosch on 2015-10-20 08:06:47 +00:00

  • Assigned to changed from mfrosch to tgelf

It currently makes no sense to ship a icingacli package, since the main application would be always required.

It would makes sense if it can be a standalone installation.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Oct 20, 2015

Updated by tgelf on 2015-10-20 18:17:55 +00:00

  • Assigned to changed from tgelf to mfrosch

lazyfrosch wrote:

It currently makes no sense to ship a icingacli package, since the main application would be always required.

It absolutely makes sense, that's why packages where designed that way.

It would makes sense if it can be a standalone installation.

It can perfectly be installed standalone. And we want to do so. You can use icingacli on webless nodes just for check execution (e.g. icingacli businessprocess check ...). You can run a full-blown Icinga Web 2 server with no Apache and no Nginx while still offering the full web application. Modules can provide CLI tools in no way related to the web frontend, that's perfectly valid and strongly encouraged.

IMHO it should be up to the project to decide what "makes sense" for a software project, that should not happen at distribution level.

@lazyfrosch: please let me know whether it is possible to restore the former state or what concrete objections would hinder us from doing so.

Thanks,
Thomas

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 16, 2016

Updated by elippmann on 2016-02-16 10:59:22 +00:00

  • Category changed from QA to Installation
  • Status changed from Feedback to Closed
  • Assigned to deleted mfrosch

I talked to Markus and he will take care that the CLI will be shipped as separate package.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 16, 2016

Updated by tgelf on 2016-02-16 11:21:56 +00:00

  • Status changed from Closed to Assigned
  • Assigned to set to mfrosch
  • Priority changed from High to Normal

Hi Eric,

I prefer to leave this open unless I see it solved ;)

Cheers,
Thomas

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 16, 2016

Updated by elippmann on 2016-02-16 11:34:17 +00:00

  • Subject changed from Debian packaging: what happened to the cli? to Debian packaging: Separate package for CLI missing
  • Target Version set to 2.2.0
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 22, 2016

Updated by mfrosch on 2016-02-22 12:11:59 +00:00

  • Status changed from Assigned to Closed
  • Target Version deleted 2.2.0

Done in > 2.1.2-2 and backports

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 22, 2016

Updated by mfrosch on 2016-02-22 12:48:55 +00:00

  • Target Version set to 2.2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.