Technical FAQs

Answers to Frequently Asked Questions covering the technical aspects of Opsview can be found at the documentation website:
http://docs.opsview.org/doku.php?id=opsview3:faq

Product FAQs: Community vs Enterprise Editions of Opsview

How does the Enterprise edition differ from Community Edition?

Both editions are derived from the same code base. Opsview Enterprise contains mature features, has a predictable release schedule and published road map. Opsview Community edition contains the latest features and has a frequent release cycle. Opsview Community is ideal for anyone evaluating Opsview, monitoring small networks or wanting to develop new functionality.

Will all bug fixes find their way into Community edition?

Yes. Bugs will be fixed in the most current Community release and supported Enterprise releases.

Is the Community edition effectively a beta version of Opsview?

No, Community releases will be issued when the code is stable. We do not envisage the Community edition of Opsview to be a 'beta' release or any less stable than the previous Opsview releases.

Will the Community edition have less features than Enterprise?

No, both editions are derived from the same code base and will have the same features. New features will arrive later in the Enterprise release, following community review process.

How long will features take to arrive in the Enterprise edition?

We expect to have 3 Enterprise releases a year. The longest delay we would expect is 6 months with most features appearing within 3-4 months.

Will you be introducing new monitoring features as Modules for Opsview Enterprise?

'Core' functionality will be introduced into Opsview Community. We expect Modules to extend Opsview functionality beyond what is 'monitoring' and to provide integration with other software. Opsview Modules will only be available to Opsview Enterprise users.

Is Opsview Enterprise still Open Source?

Yes. Opsview Enterprise is released under the same license (GPL v2) as Opsview Community edition.

Will there be any limitations imposed on Opsview Community edition? Eg: Number of host, service, or contacts that may be configured?

No, we will not impose any limitations in Opsview Community edition.

How do I differentiate between Community and Enterprise editions?

Opsview Community edition releases will have a '3' to denote the major software revision, followed by an odd number. E.g: 3.1, 3.3, 3.5, etc.
Opsview Enterprise edition releases will have a '3' to denote the major software revision, followed by an even number: E.g: 3.2, 3.4, 3.6, etc.

Opsview releases before 3.1.0 are considered equivalent to the Community Edition.

How do I differentiate between feature and maintenance releases for Opsview Enterprise?

New functionality will only be introduced during a 'feature release' designated by an increase in the number to the right of the decimal (3.2, 3.4, etc). Maintenance releases are designated by the digit following the second decimal (3.2.1, 3.2.2, etc).

How do I upgrade from Opsview Community to Opsview Enterprise?

Both Opsview software editions are derived from the same code base. One of the reasons for this is to ensure a smooth transition between Opsview editions.
You can always upgrade to a more recent version of Opsview across editions. For example:

Opsview 3.1.x (Community) -> Opsview 3.2.x (Enterprise)
Opsview 3.3.x (Community) -> Opsview 3.4.x (Enterprise)

and even

Opsview 3.0.x -> Opsview 3.4.x (Enterprise)

It is also possible to 'upgrade' from an Enterprise Edition to a more recent Community Edition, so you are not locked-in once you've made the transition. For example:

Opsview 3.4.x (Enterprise) -> Opsview 3.5.x (Community)

This may have an impact on your support provision however, so we recommend that you speak with someone at Opsera first.