This ticket effectively requires that systems running an older OpenSAF
version must be capable of loading an imm.xml file created using an
imm.xml-schema developed for a later OpenSAF version.
This is quite a tall order.
I think we can support that requirement only for some simpler types
of change, such as new attribute flags for class descriptions.
But we then need to counter with a requirement towards the user that if
they intend to load a cluster using an OpenSAF system version that is older
than the imm-xml-schema version for the imm-xml file to load, then they must
also provide that new imm-xml-schema file in the imm loading directory.
Before the immloader tries to start loading, it could check the header
of the imm.xml file to be loaded. That header contains information about
the schema version for the imm.xml file. If that schema version is *later*
than the known schema version bound to the release, then the immloader
will report that as a warning to the syslog. The immloder will then also
look for the newer schema file in the imm-loading directory.
If the new schema file is *not* found, then this is also reported by the
immloader as a warning to the syslog. The immloader will still proceed
and try to load the provided new imm-xml file, since there is a chance
that loading could succeed. But there is no guarantee and if loading fails
then at least the cause and possible action should be clear from the syslog.
If the new schema file is found, then the loader will read that new schema
file and may obtain information to allow forwards compatibility, at least
for new attribute description flags.
In the above description, 'immloader' could also be 'immcfg -f'
---
** [tickets:#116] IMMTOOLS: IMM is not forwards compatible with changes in the
XML dump format**
**Status:** accepted
**Created:** Mon May 13, 2013 07:57 AM UTC by Zoran Milinkovic
**Last Updated:** Mon Nov 04, 2013 01:26 PM UTC
**Owner:** Zoran Milinkovic
In order to provide compatibility with future changes in the IMM XML format,
the IMM tools should ignore things like unknown attribute flags when loading an
XML file.
It would also be a good idea to check if the XML file uses a known version of
the XML schema, and log a warning message (but still try to load it) if the
version is unknown.
Migrated from:
http://devel.opensaf.org/ticket/3121
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
