Hi,
Looking at another example, where Snort provided for the opensource
version (aka as all other examples) and a paid version, pre installed on
a box. So far, at least on this end of the pond, that has not been very
successful.There is a risk Opsview in two flavors will end up on a
similar way.
Personally, I would go for an Opsview-stable release and an
Opsview-unstable. Stable as in rock solid, dummy-proof version, where
the unstable provides for the added/modified features. These features
would then gradually move into the stable release.
Any added enhancement like the ones below, can be developed and once
bought as an add-in. This way, you allow for companies to select what
added enhancements they would like - and pay for it. The maintenance
then comes as a must - you will need to ensure the bought enhancement
keeps working while opsview is upgraded. Alternatively, an upgrade-fee
to enable migration for the release selected.
In my company, I can imagine we run a stable version, perhaps buy added
features and the upgrade those once a year - to a cost.
My 0.02$
Thanks
paul
James Peel wrote:
I have to say that I don't like the idea.
I can't think of many features (or modules) that would only benefit
Enterprise (paying) customers.
I understand. Some specific examples of Opsview modules, on the basis
we already provide these to some customers:
- SMS gateway
- Log file processing / analysis
- Service desk integration
Sure, these are potentially useful to everyone. The choice is:
- Pay us for a pre-rolled, fully supported module
- Integrate another tool yourselves or roll your own
There are costs and benefits associated with each option.
We have no intention to move 'core' monitoring functionality out into
modules. Modules essentially provide functionality beyond the current
scope of Opsview, such as integration with other systems.
To me, it sounds like a contradiction. It either means that not too
many modules will be available to Enterprise customers and therefore
it won't make sense to pay for it -OR- that there will be a lot of
wanted modules in the Enterprise version and everyone using Opsview
will have to pay to get them.
If this approach is going to work for Opsera, it will be at the cost
of the open source users. That's the way I see it.
It will be important for us to strike a balance.
Opsview Enterprise and Opsview Community will have a shared feature
set, and most customers start off as community users. So it would not
benefit us to push too much functionality out into modules.
--
James
------------------------------------------------------------------------
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/listinfo/opsview-users
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/listinfo/opsview-users
