IMM is probably the hardest service to live without, but in some cases
you can load a default configuration when IMM is absent. The LOG service
will probably work just fine without IMM. For AMF, as you point out,
there is no sensible default configuration except an empty one, which is
probably not very useful.
But there is also another aspect, not mentioned in this ticket: the
possibility to provide multiple implementations of a service. I can
imagine a light-weight read-only IMM service that just reads a
configuration from an XML file but doesn't allow any configuration
changes, and maybe not even admin-ops or runtime attributes. Could be
useful in some resource-constrained embedded system.
These are thoughts for the future but it can be worth keeping in mind
that it can make sense to deliver services in separate RPMs even if they
currently depend on each other.
regards,
Anders Widell
On 07/20/2017 11:52 AM, jonas arndt wrote:
And if IMM is not there? What does AMF do then😀
I can have separate packages for separate services if that is
necessary. The issue is that the current RPM spec file is not
reflecting the correct dependencies. If the AMF library is using LOG
and IMM today it needs to be reflected in the Debian control file as a
dependency. Then in the future we can change. If there are services
that need to run together even in the future I think their packages
should merge into one.
Cheers
// Jonas
On Jul 20, 2017 17:34, "Anders Widell" <[email protected]
<mailto:[email protected]>> wrote:
We actually have some ideas for how to make the services less
dependent on each other, see ticket:
https://sourceforge.net/p/opensaf/tickets/2448/
<https://sourceforge.net/p/opensaf/tickets/2448/>
For example, if the LOG service is not installed on the system
then you may choose to either not log at all, or use a fallback
solution like logging to syslog.
regards,
Anders Widell
On 07/20/2017 01:36 AM, jonas arndt wrote:
And now with a subject :-)
Hi Guys,
This is with regards to debianizing OpenSAF, i.e. ticket 2427.
As I go through the RPM dependencies in the opensaf.spec file I am
starting to think that there are some issues there.
* opensaf-lib does not depend on anything => Fine
* opensaf-amf-lib only depends on opensaf-lib => Not fine. In
reality
(checked with ldd) opensaf-amf-lib depends on IMM, LOG and so on.
I propose that we just create an opensaf-core.deb package that
covers
all core services that are mandatory anyhow. Why have AMF and IMM
separately if they are both mandatory services? Makes no sense
to me.
Then for optional services we can have separate debian packages.
Thoughts?
Cheers,
// Jonas
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
<https://lists.sourceforge.net/lists/listinfo/opensaf-devel>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
