Clarifications

Meta Icinga Events and Community
,
1

icinga Product Support Model ?

Software Cycle for infra?

Upgrade Strategy?

Regular Release by Developers form ICINGA?

When was the Last release?

How frequently do they release updates?

Justification , why every Server need internet Connection?

What kind of Certificate used in ICINGA at the time of installation?

How the Server-Server communication happens?

do we have Container Concept in ICINGA?

User in ICINGA , are they from Application layer/OS layer? Application layer

Clarification on Replication Bi-directional/unidirectional for DB,LB,WEB?

Artifactory-

Who will support for infra? apac-infra team

would like to know about iCinga Certificate processing
.
would like to know about iCinga product support

Is Icinga a well-maintained software?

Are there regular/frequent product release & patch release plans from the original software developer(s)?

What’s its release history? Are bugs (esp. security-related) being fixed swiftly?

Icinga uses other FOSS software (e.g. PostgresQL, Apache web server). Can Icinga support newer versions of these software? Or does Icinga have very tight integration with these software and does not support discrete installations?

2

You appear to have copied an internal email request for information and posted
it to a public mailing list / forum.

You will probably get a more helpful response from this list if you can:

a) look up the obvious information yourself (for example, “when was the last
release” is public information which you can find out and don’t have to take up
someone else’s time looking for you)

b) eliminate any questiosn which are internal to yur own company, since they
are of no interest to us and we can’t answer them (for example “do we have any
plan to develop our own release cycle?”)

c) formulate your questions so that people can give you a helpful answer, and
it’s clear what you are asking (for example, what does “maintenance window?”
actually mean)

Best wishes,

Antony.

1 Like