From 824a6db3ff111f8d2427ac5adad0362bf078630a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Thu, 2 Sep 2010 15:44:33 +0200 Subject: Add test suite for xmerl --- .../xmerl_xsd_SUITE_data/sis/IntegratedSite.xsd | 5238 ++++++++++++++++++++ .../test/xmerl_xsd_SUITE_data/sis/IsTypes.xsd | 42 + .../test/xmerl_xsd_SUITE_data/sis/MainSwitch_1.xsd | 1496 ++++++ .../test/xmerl_xsd_SUITE_data/sis/MyBsModel_1.xsd | 502 ++ lib/xmerl/test/xmerl_xsd_SUITE_data/sis/bs_mim.xml | 1187 +++++ .../xmerl_xsd_SUITE_data/sis/dummy_action_mim.xml | 186 + .../test/xmerl_xsd_SUITE_data/sis/hwm_mim.xml | 631 +++ .../test/xmerl_xsd_SUITE_data/sis/instance.xml | 240 + lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim.xsd | 486 ++ lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim2.xsd | 506 ++ lib/xmerl/test/xmerl_xsd_SUITE_data/sis/nc.xsd | 14 + .../test/xmerl_xsd_SUITE_data/sis/swm_mim.xml | 881 ++++ 12 files changed, 11409 insertions(+) create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IntegratedSite.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IsTypes.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MainSwitch_1.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MyBsModel_1.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/bs_mim.xml create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/dummy_action_mim.xml create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/hwm_mim.xml create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/instance.xml create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim2.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/nc.xsd create mode 100644 lib/xmerl/test/xmerl_xsd_SUITE_data/sis/swm_mim.xml (limited to 'lib/xmerl/test/xmerl_xsd_SUITE_data/sis') diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IntegratedSite.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IntegratedSite.xsd new file mode 100644 index 0000000000..e211b313c2 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IntegratedSite.xsd @@ -0,0 +1,5238 @@ + + + + + + + + + + + + + + + + + + + Data to specify a jobs progress, status etc during its execution. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Specification of a blade when an upgrade job is ordered for a + specific blade. This data always belongs to and is included in + an upgrade job for a blade system. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Data to specify FTP server info, such as host, user, + password and path, to locate correct files or destination + for files. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Indicates status of software groups. A software group is + complete if all included load module containers have been + downloaded and unpacked correctly. A software group is inconsistent + if the checksums of the load module containers do not match the + information in the system information CXP, or if the XML + data could not be registered. + + + + + + + + + + + + + + + + + + + Datatype for an integer according to SNMPv2 definition of + unsigned32. + + + + + + + + + + + + Possible results of an action for a job. + + + + + + + + + + + + + + + + + + + Type of a load module container. + + + + + + + + + + + + Interpretation of given filename and path. + + + + + + + + + + + + Interpretation according to existing files. + + + + + + + + + + + + Indicator of job status. + A job should be started immediately, but could be postponed + if the total load on the system would become too high. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The top class - the forefather of all classes. + + Key attributes: [] + + Possible children: + Hardware + Software + NetworkConfiguration + BladeSystems + + + + + + + + Functional area Hardware Management + + Key attributes: [] + + Possible children: + BladeType + Subrack + + + + + + + + This class describes a Blade. + + Key attributes: [key] + + + + + + + + The blade type number like CNA12801 + + + + + + + + + + + + + + The name of the Blade Type. + + + + + + + + + + + + + + The width of the blade in number of slots. + + + + + + + + + + + + + + The 1G links used by the blade type , like 0,1, counted from + the leftmost backplane position. + + + + + + + + + + + + + + The 1G links used for link aggregation by the blade type , like 0-1, + counted from the leftmost backplane position. + + + + + + + + + + + + + + True if possible to read product info via the maintenance bus. + + + + + + + + + + + + + + True if this is a Main Switch blade type. + + + + + + + + + + + + + + Only valid for main switch blades. A list of slots that have 1G link. + Could be a single slot or a range or a combination thereof. + E.g. 1-24, or 1,3-13,15-24. + + + + + + + + + + + + + + Only valid for main switch blades. Specifies which slots can be used + for link aggregation. Ranges are specified in the form 1-12,13-24. + + + + + + + + + + + + + + + + + + This class describes the subrack. + + Key attributes: [id] + + Possible children: + Slot + + + + + + + + Identifies a certain subrack. + + + + + + + + + + + + + + The type of subrack. + + + + + + + + + + + + + + A user friendly Subrack name. + + + + + + + + + + + + + + The subrack position in the cabinet. + + + + + + + + + + + + + + The cabinet position in the site. + + + + + + + + + + + + + + The site location, e.g. the visiting address. + + + + + + + + + + + + + + Available slots for 1G switch links. Information taken from the type + of main switch blade that is created in the subrack. + + + + + + + + + + + + + + Available slots for 10G switch links. Information taken from the type + of main switch blade that is created in the subrack. + + + + + + + + + + + + + + Links ranges for (1G) link aggregation. Information taken from the + type of main switch blade that is created in the subrack. + + + + + + + + + + + + + + This table corresponds to slots, there is one row in the table + for each slot. The slots are grouped per subrack. A slot is + identified by subrack Id and slot number). The subrack Id for a slot + identifies in the subrackTable the subrack that the slot belongs + to. + + Key attributes: [number] + + + + + + + + The value of this object identifies the + slot position within the subrack. + + + + + + + + + + + + + + See HwmSlotStateType description. + + + + + + + The value of this object identifies the Blade System that uses this + slot. An instances of this object will only have meaning in a + conceptual row if the value of hemSlotState instance is either + usedOccupied or usedEmpty in the same conceptual row, + i.e. there is an Blade System created using this slot. (If + no Blade System is using the slot, the value will be -1.) + + + + + + + + + + + + + + + + + + + + + + + + + + Top class of structure for SWM MOM. + + Key attributes: [] + + Possible children: + Inventory + Jobs + + + + + + + + Subclass to top class Software. Parent of + Inventory classes: + SoftwareDeliveryPackage, + SoftwareGroup, + LocalBackup, + Alarm. + Inventory actions: + DownloadFile + ImportBackup + Only system created data for info and overview, + sometimes as a result of an action called by the + operator. + + Key attributes: [] + + Possible children: + Alarm + LocalBackup + SoftwareDeliveryPackage + SoftwareGroup + + + + + + + + MO of all alarms logged in the system that has not been + taken care of in a satisfactory way. + + Key attributes: [alarmId] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + All available backups locally stored. + + Key attributes: [localBackupId] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + MO for info about LoadModuleContainers, ie CXPs. + + Key attributes: [ixProdNr,ixVersion] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This class reference to multiple MOs of class + SoftwareDeliveryPackage, ie the relationship between + CXPs and CXS. + + Key attributes: [ixProdnr,ixVersion] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Subclass to top class Software. Parent of + Jobs classes: + DownloadFile, + Upgrade, + Backup. + System created data through ordered job actions. + + Key attributes: [] + + Possible children: + Backup + DownloadFile + Upgrade + + + + + + + + Subclass to class Jobs. Parent of + Jobs classes: + Create, + Restore + Import, + Export.System created data through ordered backup job actions. + + Key attributes: [] + + Possible children: + Create + Export + Import + Restore + + + + + + + + This MO handles creation of backups of the system. + + Key attributes: [backupJobId] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO handles export of locally stored backup files to + the FTP server. + + Key attributes: [exportJobId] + + + + + + + + + + + + + + + + + + + + + + + + This MO handles import of backup files from the FTP server. + The backup file is stored locally, but not loaded into the system. + + Key attributes: [importJobId] + + + + + + + + + + + + + + + + + + + + + + + This MO handles restore of backups of the system. + + Key attributes: [restoreJobId] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO contains information about requested, ongoing, + and completed software file download jobs. To start a + download job the operator calls an action Inventory class, + and a new instance of this MO is created. + For load regulating reasons a requested job may not start + immediately. + + Key attributes: [downloadFileJobId] + + + + + + + + + + + + + + + + + + + + + + + + + This MO handles upgrade jobs towards the system. The operator + may specify a specific blade to run the upgrade on, instead of + running an upgrade on the entire blade system. + + Key attributes: [upgradeJobId] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The maximum time allowed for the SW Upgrade + job to finish. After this time, the job will be interrupted. + The value 0 means that MaxTime will be given the + timer value registered with the Blade System Software Group + Version. If no such value has been registered, + MaxTime will be given a system default timer value. + + + + + + + + + + + + + + + + + + + + The MO branch where the common Network resources are configured. + + Key attributes: [] + + Possible children: + IsIpTrafficClass + IsLanTrafficClass + IsLogicalNetwork + IsVariables + IsVlan + + + + + + + + Key attributes: [name] + + + + + + + + Name if the IS IP Traffic Class. + Unique within the entire Integrated Site. + + + + + + + + + + + + + + Short description of the IS IP Traffic Class. + + + + + + + + + + + + + + DiffServ Code Point setting for this IS IP Traffic Class. + If there are two IS Ip Traffic Classes with the same DSCP, they + both must refer to an IS Lan Traffic Class with identical P-bit setting. + + + + + + + + + + + + + + Reference to a Managed Object of type ISLanTrafficClass. + + + + + + + + + + + + + + + + + + An IS Lan Traffic Class may be shared between several Blade Systems. + + Key attributes: [name] + + + + + + + + Name of the IS Lan Traffic Class. + Unique within the entire Integrated Site. + + + + + + + + + + + + + + Short description of the IS Lan Traffic Class. + + + + + + + + + + + + + + P-bit setting for this IS Lan Traffic Class. + + + + + + + + + + + + + + + + + + An IS Logical Network contains one or more IS Subnets. + It may be shared between several Blade Systems. + + Key attributes: [name] + + Possible children: + IsSubnet + + + + + + + + Name of the IS Logical Network. + Unique within the entire Integrated Site. + + + + + + + + + + + + + + Short description of the IS logical network. + + + + + + + + + + + + + + An IS Subnet contains one or more IS Subnet Segments. + It may be shared between several Blade Systems. + + Key attributes: [name] + + Possible children: + IsSubnetSegment + + + + + + + + Name of the IS Subnet. Unique within the IS Logical Network. + + + + + + + + + + + + + + Short description of the IS Subnet. + + + + + + + + + + + + + + IP network address of the IS Subnet. + + + + + + + Prefix length of the IP network address. + + + + + + + + + + + + + + Broadcast address of the IS Subnet. + + + + + + + + + + + + + + Identity of an IS VLAN. + + + + + + + + + + + + + + An IS Subnet Segment may be shared between several Blade Systems. + + Key attributes: [name] + + + + + + + + Name of the IS Subnet Segment. Unique within the IS Subnet. + + + + + + + + + + + + + + Short description of the IS Subnet Segment. + + + + + + + + + + + + + + IP network address of the IS Subnet Segment. + + + + + + + Prefix length of the IP network address. + + + + + + + + + + + + + + Router address for the IS Subnet. + + + + + + + Flag that controls wheter DHCP should be enabled or not for this + IS Subnet Segment. + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The RLSP marker generate interval in microseconds. + + + + + + + + + + + + + + Daylight savings rule in posix standard format. + Better description to be supplied later........and a regular expression + which describes the valid string format. + + + + + + + + + + + + + + The dns domain used by IS in the DNS-server. + + + + + + + + + + + + + + Number of seconds from that a new network configuration has been + published until the Blade Systems will apply the changes. + + + + + + + + + + + + + + The default DHCP Lease time in seconds. + + + + + + + + + + + + + + The lifetime of a DHCP lease in seconds. + + + + + + + + + + + + + + + + + + An IS Vlan may be shared between several Blade Systems. + + Key attributes: [identity] + + + + + + + + Identity of the IS Vlan. Unique within the entire Integrated Site. + + + + + + + + + + + + + + Short description of the IS Vlan. + + + + + + + + + + + + + + + + + + + + + + The BladeSystems mountpoint - parent of all blade systems. + + Key attributes: [] + + Possible children: + BladeSystemTemplate + Mxb + MyBsModel + Sis + + + + + + + + This class describes a Blade System. It will be cloned for each + new blade system type registered in the system. The new clone + will serve as a mountpoint for the blade system specific model. + + Key attributes: [name] + + Possible children: + Blade + BsIpTrafficClass + BsLanTrafficClass + BsLogicalNetwork + BsVlan + + + + + + + + A user friendly Blade System name, must be set at creation and can be + changed when BS is locked. + + + + + + + + + + + + + + An identifier for the BS. A new integer has to be used every time a new + BS is created. ??? Kvar ??? + + + + + + + + + + + + + + The identity of the Software Group (SWG) that the BS implements. + + + + + + + + + + + + + + The revision of the Software Group (SWG) that the BS implements. + + + + + + + + + + + + + + The administrative state of the Blade System. + + + + + + + The operational state of the Blade System. + + + + + + + The availability status of the Blade System. + + + + + + + eller sätta admState ???????????? + + + + + + + + + + + + + + Short description of the Blade System. + + + + + + + + + + + + + + IP address of the Blade System OaM Master. + + + + + + + This class describes a Blade. + A Blade is identified by the subrack and slot number. + + Key attributes: [subrackId,slotNo] + + Possible children: + LinkSap + + + + + + + + A reference to the associated subrack (i.e. the value of 'subrackId' + for the associated subrack) + + + + + + + + + + + + + + The slot number for this Blade within the subrack. + + + + + + + + + + + + + + The slot label of the blade. Will only be set at creation of table row. + This should be used in alarms related to the slot to inform the + operator of what position in the subrack the blade is located in. + E.g. for GEM subracks it will be a string like X02 for slot 0 + up to X80 for slot 25. + + + + + + + + + + + + + + An identifier for the BS to which the blade belongs. + A value of 0 means that the blade is inserted in the subrack but it + has not been configured to any BS yet. + + + + + + + + + + + + + + The type of the Blade defined by a string BladTypeIdAndRev. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + + + + + + + + + + Set to protected if blade sholud no be knocked out before the + switch blade. + + + + + + + A user friendly Blade name, always possible to set. + Default value indicates HwmBladeType and used slot. + + + + + + + + + + + + + + The administrative state of the Blade. The Blade is + unblocked by setting this object to unlocked and blocked + by setting it to locked. If the object already has the + desired value or the hwmBladeOpState has a transient OpState value + the set operation will be rejected. The set operation may be + rejected due to other reasons as well. + + + + + + + The operational state of the Blade. + + + + + + + The availability status of the Blade. + + + + + + + The type of maintenance bus on the found Blade + + + + + + + The Product Number of the found Blade + + + + + + + + + + + + + + The Product Revision of the found Blade. + + + + + + + + + + + + + + The Serial Number of the found Blade. + + + + + + + + + + + + + + The Product Name of the found Blade. + + + + + + + + + + + + + + The Vendor name of the found Blade. + + + + + + + + + + + + + + The manufacturing date of the found Blade. + + + + + + + + + + + + + + The aggregated MAC address of the found Blade. + + + + + + + The left link MAC address of the found Blade. Only used by some blades + + + + + + + The right link MAC address of the found Blade. Only used by some blades + + + + + + + The date when the blade was last changed. + + + + + + + + + + + + + + Borde kanske varfa en ändring av admstate.???? + + + + + + + + + + + + + + The name of the Blade. + + + + + + + + + + + + + + Short description of the blade. + + + + + + + + + + + + + + IP address on the ISBS subnet. + + + + + + + IP address on the ISOB subnet. + + + + + + + IP address on the ISLCT subnet. + + + + + + + A Blade may have one or more resilient interfaces to the backplane. Such + interface is called Link Service Access Point and are automatically + created and deleted along with the hosting blade. + + Key attributes: [id] + + + + + + + + The id of a LinkSap is a number from 0 to X within the slot. + + + + + + + + + + + + + + Short description of the Link Service Access Point. + + + + + + + + + + + + + + + + + + + + + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [name] + + Possible children: + BsSubnet + + + + + + + + Name of the BS logical network. Unique within the Blade System. + + + + + + + + + + + + + + Short description of the BS Logical Network. + + + + + + + + + + + + + + Flag that shows whether the BS Logical Network is private for this + Blade System or if it may be shared among several Blade Systems. + + + + + + + + + + + + + + Reference to the corresponding IS Logical Network. + + + + + + + + + + + + + + BS Subnets can either be created manually by the operator or they + can be automatically created from pre-registered network requirements + bundled with the Blade System software. + Regardless of how they are created, + each one needs to be mapped to both a BS VLan and an + IS Subnet before blades can be unlocked via the Hardware service. + Each BS Subnet contains one or more BS Subnet Segments. + + Key attributes: [name] + + Possible children: + BsSubnetSegment + + + + + + + + Name of the BS Subnet. Unique within the BS Logical Network. + + + + + + + + + + + + + + Short description of the BS Subnet. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + BS Subnet Segments can either be created manually by you or they can + be automatically created from pre-registered network requirements + bundled with the Blade System software. Regardless of how they are created, + each one needs to be mapped to an IS Subnet Segment before the blades + can be unlocked via the Hardware service. + The mapping is done with the 'isSubnetSegmentRef' attribute. + + Key attributes: [name] + + + + + + + + Name of the BS Subnet Segment. Unique within the BS Subnet. + + + + + + + + + + + + + + Short description of the BS Subnet Segment. + + + + + + + + + + + + + + Number of required IP addresses in the IS Subnet Segment. + + + + + + + + + + + + + + Flag that controls whether the corresponding IS Subnet Segment is + required to have DHCP enabled or not. + + + + + + + + + + + + + + Flag that controls whether the corresponding IS Subnet Segment is + required to have a router configured or not. + + + + + + + + + + + + + + The mapping to a corresponding IS Subnet Segment. The mapping here must + be done before the blades of the blade system can be unlocked. + + + + + + + + + + + + + + + + + + + + + + + + + + BS VLANs can either be created manually by the + operator or they can be automatically created from pre-registered + network requirements bundled with the Blade System software. + Regardless of how they are created, each one needs to be mapped to + an IS VLAN before the blades can be unlocked. + + Key attributes: [name] + + Possible children: + BsVlanSap + + + + + + + + Name of the BS Vlan. Unique within the Blade System. + + + + + + + + + + + + + + Short description of the BS Vlan. + + + + + + + + + + + + + + The mapping to a corresponding IS Vlan. This mapping must be done before + the blades of the Blade System can be unlocked. + + + + + + + + + + + + + + BS VLAN Service Access Points can either be created manually by the + operator or they can be automatically created from pre-registered + network requirements bundled with the Blade System software. + Regardless of how they are created, each one needs to be mapped to + an Link SAP before the blades can be unlocked. + + Key attributes: [name] + + + + + + + + Name of the BS VLAN SAP. Uniqie within the BS VLAN. + + + + + + + + + + + + + + Short description of the BS VLAN SAP. + + + + + + + + + + + + + + Flag which controls whether this BS VLAN SAP makes static or dynamic + use of the corresponding IS VLAN. + + + + + + + + + + + + + + Flag which controls whether this BS VLAN SAP should be + isolation protected or not. + + + + + + + + + + + + + + A mapping to the corresponding Link Service Access Point. + + + + + + + + + + + + + + + + + + + + + + + + + + This class describes a Blade System. It will be cloned for each + new blade system type registered in the system. The new clone + will serve as a mountpoint for the blade system specific model. + + Key attributes: [name] + + Possible children: + Blade + BsIpTrafficClass + BsLanTrafficClass + BsLogicalNetwork + BsVlan + + + + + + + + A user friendly Blade System name, must be set at creation and can be + changed when BS is locked. + + + + + + + + + + + + + + An identifier for the BS. A new integer has to be used every time a new + BS is created. ??? Kvar ??? + + + + + + + + + + + + + + The identity of the Software Group (SWG) that the BS implements. + + + + + + + + + + + + + + The revision of the Software Group (SWG) that the BS implements. + + + + + + + + + + + + + + The administrative state of the Blade System. + + + + + + + The operational state of the Blade System. + + + + + + + The availability status of the Blade System. + + + + + + + eller sätta admState ???????????? + + + + + + + + + + + + + + Short description of the Blade System. + + + + + + + + + + + + + + IP address of the Blade System OaM Master. + + + + + + + This class describes a Blade. + A Blade is identified by the subrack and slot number. + + Key attributes: [subrackId,slotNo] + + Possible children: + LinkSap + + + + + + + + A reference to the associated subrack (i.e. the value of 'subrackId' + for the associated subrack) + + + + + + + + + + + + + + The slot number for this Blade within the subrack. + + + + + + + + + + + + + + The slot label of the blade. Will only be set at creation of table row. + This should be used in alarms related to the slot to inform the + operator of what position in the subrack the blade is located in. + E.g. for GEM subracks it will be a string like X02 for slot 0 + up to X80 for slot 25. + + + + + + + + + + + + + + An identifier for the BS to which the blade belongs. + A value of 0 means that the blade is inserted in the subrack but it + has not been configured to any BS yet. + + + + + + + + + + + + + + The type of the Blade defined by a string BladTypeIdAndRev. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + + + + + + + + + + Set to protected if blade sholud no be knocked out before the + switch blade. + + + + + + + A user friendly Blade name, always possible to set. + Default value indicates HwmBladeType and used slot. + + + + + + + + + + + + + + The administrative state of the Blade. The Blade is + unblocked by setting this object to unlocked and blocked + by setting it to locked. If the object already has the + desired value or the hwmBladeOpState has a transient OpState value + the set operation will be rejected. The set operation may be + rejected due to other reasons as well. + + + + + + + The operational state of the Blade. + + + + + + + The availability status of the Blade. + + + + + + + The type of maintenance bus on the found Blade + + + + + + + The Product Number of the found Blade + + + + + + + + + + + + + + The Product Revision of the found Blade. + + + + + + + + + + + + + + The Serial Number of the found Blade. + + + + + + + + + + + + + + The Product Name of the found Blade. + + + + + + + + + + + + + + The Vendor name of the found Blade. + + + + + + + + + + + + + + The manufacturing date of the found Blade. + + + + + + + + + + + + + + The aggregated MAC address of the found Blade. + + + + + + + The left link MAC address of the found Blade. Only used by some blades + + + + + + + The right link MAC address of the found Blade. Only used by some blades + + + + + + + The date when the blade was last changed. + + + + + + + + + + + + + + Borde kanske varfa en ändring av admstate.???? + + + + + + + + + + + + + + The name of the Blade. + + + + + + + + + + + + + + Short description of the blade. + + + + + + + + + + + + + + IP address on the ISBS subnet. + + + + + + + IP address on the ISOB subnet. + + + + + + + IP address on the ISLCT subnet. + + + + + + + A Blade may have one or more resilient interfaces to the backplane. Such + interface is called Link Service Access Point and are automatically + created and deleted along with the hosting blade. + + Key attributes: [id] + + + + + + + + The id of a LinkSap is a number from 0 to X within the slot. + + + + + + + + + + + + + + Short description of the Link Service Access Point. + + + + + + + + + + + + + + + + + + + + + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [name] + + Possible children: + BsSubnet + + + + + + + + Name of the BS logical network. Unique within the Blade System. + + + + + + + + + + + + + + Short description of the BS Logical Network. + + + + + + + + + + + + + + Flag that shows whether the BS Logical Network is private for this + Blade System or if it may be shared among several Blade Systems. + + + + + + + + + + + + + + Reference to the corresponding IS Logical Network. + + + + + + + + + + + + + + BS Subnets can either be created manually by the operator or they + can be automatically created from pre-registered network requirements + bundled with the Blade System software. + Regardless of how they are created, + each one needs to be mapped to both a BS VLan and an + IS Subnet before blades can be unlocked via the Hardware service. + Each BS Subnet contains one or more BS Subnet Segments. + + Key attributes: [name] + + Possible children: + BsSubnetSegment + + + + + + + + Name of the BS Subnet. Unique within the BS Logical Network. + + + + + + + + + + + + + + Short description of the BS Subnet. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + BS Subnet Segments can either be created manually by you or they can + be automatically created from pre-registered network requirements + bundled with the Blade System software. Regardless of how they are created, + each one needs to be mapped to an IS Subnet Segment before the blades + can be unlocked via the Hardware service. + The mapping is done with the 'isSubnetSegmentRef' attribute. + + Key attributes: [name] + + + + + + + + Name of the BS Subnet Segment. Unique within the BS Subnet. + + + + + + + + + + + + + + Short description of the BS Subnet Segment. + + + + + + + + + + + + + + Number of required IP addresses in the IS Subnet Segment. + + + + + + + + + + + + + + Flag that controls whether the corresponding IS Subnet Segment is + required to have DHCP enabled or not. + + + + + + + + + + + + + + Flag that controls whether the corresponding IS Subnet Segment is + required to have a router configured or not. + + + + + + + + + + + + + + The mapping to a corresponding IS Subnet Segment. The mapping here must + be done before the blades of the blade system can be unlocked. + + + + + + + + + + + + + + + + + + + + + + + + + + BS VLANs can either be created manually by the + operator or they can be automatically created from pre-registered + network requirements bundled with the Blade System software. + Regardless of how they are created, each one needs to be mapped to + an IS VLAN before the blades can be unlocked. + + Key attributes: [name] + + Possible children: + BsVlanSap + + + + + + + + Name of the BS Vlan. Unique within the Blade System. + + + + + + + + + + + + + + Short description of the BS Vlan. + + + + + + + + + + + + + + The mapping to a corresponding IS Vlan. This mapping must be done before + the blades of the Blade System can be unlocked. + + + + + + + + + + + + + + BS VLAN Service Access Points can either be created manually by the + operator or they can be automatically created from pre-registered + network requirements bundled with the Blade System software. + Regardless of how they are created, each one needs to be mapped to + an Link SAP before the blades can be unlocked. + + Key attributes: [name] + + + + + + + + Name of the BS VLAN SAP. Uniqie within the BS VLAN. + + + + + + + + + + + + + + Short description of the BS VLAN SAP. + + + + + + + + + + + + + + Flag which controls whether this BS VLAN SAP makes static or dynamic + use of the corresponding IS VLAN. + + + + + + + + + + + + + + Flag which controls whether this BS VLAN SAP should be + isolation protected or not. + + + + + + + + + + + + + + A mapping to the corresponding Link Service Access Point. + + + + + + + + + + + + + + + + + + + + + + + + + + + This class describes a Blade System. It will be cloned for each + new blade system type registered in the system. The new clone + will serve as a mountpoint for the blade system specific model. + + Key attributes: [name] + + Possible children: + Blade + BsIpTrafficClass + BsLanTrafficClass + BsLogicalNetwork + BsVlan + + + + + + + + A user friendly Blade System name, must be set at creation and can be + changed when BS is locked. + + + + + + + + + + + + + + An identifier for the BS. A new integer has to be used every time a new + BS is created. ??? Kvar ??? + + + + + + + + + + + + + + The identity of the Software Group (SWG) that the BS implements. + + + + + + + + + + + + + + The revision of the Software Group (SWG) that the BS implements. + + + + + + + + + + + + + + The administrative state of the Blade System. + + + + + + + The operational state of the Blade System. + + + + + + + The availability status of the Blade System. + + + + + + + eller sätta admState ???????????? + + + + + + + + + + + + + + Short description of the Blade System. + + + + + + + + + + + + + + IP address of the Blade System OaM Master. + + + + + + + This class describes a Blade. + A Blade is identified by the subrack and slot number. + + Key attributes: [subrackId,slotNo] + + Possible children: + LinkSap + + + + + + + + A reference to the associated subrack (i.e. the value of 'subrackId' + for the associated subrack) + + + + + + + + + + + + + + The slot number for this Blade within the subrack. + + + + + + + + + + + + + + The slot label of the blade. Will only be set at creation of table row. + This should be used in alarms related to the slot to inform the + operator of what position in the subrack the blade is located in. + E.g. for GEM subracks it will be a string like X02 for slot 0 + up to X80 for slot 25. + + + + + + + + + + + + + + An identifier for the BS to which the blade belongs. + A value of 0 means that the blade is inserted in the subrack but it + has not been configured to any BS yet. + + + + + + + + + + + + + + The type of the Blade defined by a string BladTypeIdAndRev. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + The SW group of the Blade. + + + + + + + + + + + + + + + + + + + + + + + Set to protected if blade sholud no be knocked out before the + switch blade. + + + + + + + A user friendly Blade name, always possible to set. + Default value indicates HwmBladeType and used slot. + + + + + + + + + + + + + + The administrative state of the Blade. The Blade is + unblocked by setting this object to unlocked and blocked + by setting it to locked. If the object already has the + desired value or the hwmBladeOpState has a transient OpState value + the set operation will be rejected. The set operation may be + rejected due to other reasons as well. + + + + + + + The operational state of the Blade. + + + + + + + The availability status of the Blade. + + + + + + + The type of maintenance bus on the found Blade + + + + + + + The Product Number of the found Blade + + + + + + + + + + + + + + The Product Revision of the found Blade. + + + + + + + + + + + + + + The Serial Number of the found Blade. + + + + + + + + + + + + + + The Product Name of the found Blade. + + + + + + + + + + + + + + The Vendor name of the found Blade. + + + + + + + + + + + + + + The manufacturing date of the found Blade. + + + + + + + + + + + + + + The aggregated MAC address of the found Blade. + + + + + + + The left link MAC address of the found Blade. Only used by some blades + + + + + + + The right link MAC address of the found Blade. Only used by some blades + + + + + + + The date when the blade was last changed. + + + + + + + + + + + + + + Borde kanske varfa en ändring av admstate.???? + + + + + + + + + + + + + + The name of the Blade. + + + + + + + + + + + + + + Short description of the blade. + + + + + + + + + + + + + + IP address on the ISBS subnet. + + + + + + + IP address on the ISOB subnet. + + + + + + + IP address on the ISLCT subnet. + + + + + + + A Blade may have one or more resilient interfaces to the backplane. Such + interface is called Link Service Access Point and are automatically + created and deleted along with the hosting blade. + + Key attributes: [id] + + + + + + + + The id of a LinkSap is a number from 0 to X within the slot. + + + + + + + + + + + + + + Short description of the Link Service Access Point. + + + + + + + + + + + + + + + + + + + + + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Key attributes: [name] + + Possible children: + BsSubnet + + + + + + + + Name of the BS logical network. Unique within the Blade System. + + + + + + + + + + + + + + Short description of the BS Logical Network. + + + + + + + + + + + + + + Flag that shows whether the BS Logical Network is private for this + Blade System or if it may be shared among several Blade Systems. + + + + + + + + + + + + + + Reference to the corresponding IS Logical Network. + + + + + + + + + + + + + + BS Subnets can either be created manually by the operator or they + can be automatically created from pre-registered network requirements + bundled with the Blade System software. + Regardless of how they are created, + each one needs to be mapped to both a BS VLan and an + IS Subnet before blades can be unlocked via the Hardware service. + Each BS Subnet contains one or more BS Subnet Segments. + + Key attributes: [name] + + Possible children: + BsSubnetSegment + + + + + + + + Name of the BS Subnet. Unique within the BS Logical Network. + + + + + + + + + + + + + + Short description of the BS Subnet. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + BS Subnet Segments can either be created manually by you or they can + be automatically created from pre-registered network requirements + bundled with the Blade System software. Regardless of how they are created, + each one needs to be mapped to an IS Subnet Segment before the blades + can be unlocked via the Hardware service. + The mapping is done with the 'isSubnetSegmentRef' attribute. + + Key attributes: [name] + + + + + + + + Name of the BS Subnet Segment. Unique within the BS Subnet. + + + + + + + + + + + + + + Short description of the BS Subnet Segment. + + + + + + + + + + + + + + Number of required IP addresses in the IS Subnet Segment. + + + + + + + + + + + + + + Flag that controls whether the corresponding IS Subnet Segment is + required to have DHCP enabled or not. + + + + + + + + + + + + + + Flag that controls whether the corresponding IS Subnet Segment is + required to have a router configured or not. + + + + + + + + + + + + + + The mapping to a corresponding IS Subnet Segment. The mapping here must + be done before the blades of the blade system can be unlocked. + + + + + + + + + + + + + + + + + + + + + + + + + + BS VLANs can either be created manually by the + operator or they can be automatically created from pre-registered + network requirements bundled with the Blade System software. + Regardless of how they are created, each one needs to be mapped to + an IS VLAN before the blades can be unlocked. + + Key attributes: [name] + + Possible children: + BsVlanSap + + + + + + + + Name of the BS Vlan. Unique within the Blade System. + + + + + + + + + + + + + + Short description of the BS Vlan. + + + + + + + + + + + + + + The mapping to a corresponding IS Vlan. This mapping must be done before + the blades of the Blade System can be unlocked. + + + + + + + + + + + + + + BS VLAN Service Access Points can either be created manually by the + operator or they can be automatically created from pre-registered + network requirements bundled with the Blade System software. + Regardless of how they are created, each one needs to be mapped to + an Link SAP before the blades can be unlocked. + + Key attributes: [name] + + + + + + + + Name of the BS VLAN SAP. Uniqie within the BS VLAN. + + + + + + + + + + + + + + Short description of the BS VLAN SAP. + + + + + + + + + + + + + + Flag which controls whether this BS VLAN SAP makes static or dynamic + use of the corresponding IS VLAN. + + + + + + + + + + + + + + Flag which controls whether this BS VLAN SAP should be + isolation protected or not. + + + + + + + + + + + + + + A mapping to the corresponding Link Service Access Point. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IsTypes.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IsTypes.xsd new file mode 100644 index 0000000000..a9607e4253 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/IsTypes.xsd @@ -0,0 +1,42 @@ + + + + + + + + + + + + An IPv4 address + in the form v1.v2.v3.v4 where v1 ... v4 is a + decimal number in the range 0 to 255. + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MainSwitch_1.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MainSwitch_1.xsd new file mode 100644 index 0000000000..9c91d6efd6 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MainSwitch_1.xsd @@ -0,0 +1,1496 @@ + + + + + + + + + + + + + + + + + + + Description of Link Aggregation Data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Port Channel Mode + + + + + + + + + + + + + + Number of configured ports for this interface. + + + + + + + + + + + + + + Number of active ports for this interface. + + + + + + + + + + + + + + MAC Selection Policy + + + + + + + + + + + + + + Link Selection Policy + + + + + + + + + + + + + + MAC address of Aggregator + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of COS configuration data + + + + + + + + + + + + + + + + Indicates allocated buffer in percent + + + + + + + Indicates if Sceduling is Weighted Round Robin (WRR) or Strict Priority + + + + + + + + + + + + + + Indicates if Weight in case of WRR is High, Medium or Low + + + + + + + + + + + + + + + + + This struct describes Vlan data + + + + + + + Vlan Id + + + + + + + + + + + + + + Type of Vlan + + + + + + + + + + + + + + Isolation status + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of Link Aggregation Oper State Data + + + + + + + Indicates LACP activity + + + + + + + + + + + + + + Indicates if LACP timeout is long or short + + + + + + + + + + + + + + Indicates if Individual or Aggregatable + + + + + + + + + + + + + + Indicates if Syncronized or not + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of Pbit to queue mapping + + + + + + + + Interface number + + + + + + + + + + + + + + + + + + + + + + + + + + + Vlan Id + + + + + + + + + + + + + + + + + + + + Administrative and Operative Vlans + + Key attributes: [] + + Possible children: + VlanAdmin + VlanOper + + + + + + + + This class shows the Administrative configured Vlans + + Key attributes: [subrackNum] + + + + + + + + + + + + + + + + + + Information about defined Vlan Ids + + + + + + + + + + + + + + + + + This class shows the Operative Vlans + + Key attributes: [subrackNum] + + + + + + + + + + + + + + + + + + Information about operative Vlan Ids + + + + + + + + + + + + + + + + + + + + + This class describes the Class of Service function. + + Key attributes: [] + + Possible children: + Pbit + Queue + + + + + + + + Description of administrative Queue Configuration Data + to be applied for each subrack (or whole system?) + + + + + + + + + + + + + Description of administrative Pbit to Queue mapping. + + + + + + + + + + + + + Description operational Queue Configuration Data + to be applied for actual subrack and Mxb. + + + + + + + + + + + + + Description of operational Pbit to Queue mapping. + + + + + + + + + + + + + This class is used to set the Pbit to queue table. + + Key attributes: [bladeSlotLink] + + + + + + + + + + + + + + + + + + + + + This class is used to set the Queue Data table. + + Key attributes: [queueKey] + + + + + + + + Queue value 0 to 7. + + + + + + + + + + + + + + Queue Configuration Data to be applied for the whole system. + + + + + + + + + + + + + + + + + + + + + This class describes data to be read for a Mxb. + + Key attributes: [] + + Possible children: + StateBlade + StateLink + + + + + + + + This class describes data related to a specific Mxb. + + Key attributes: [subrackNum,mxbSlot] + + + + + + + + + + Description of type of Mxb. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Indicates if the other Mxb in the subrack is present or absent. + + + + + + + + + + + + + + Software version executing. + + + + + + + + + + + + + + Software version in flash memory. + + + + + + + + + + + + + + Fallback software version. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This class describes actual state data for a specific link + related to the Mxb. + + Key attributes: [] + + Possible children: + StateLa + StateVlan + + + + + + + + This class describes the state of the Blade Slot Links with + regards to Link Aggregation info. + + Key attributes: [subrackNum,bladeSlotLink,mxbSlot] + + + + + + + + + + + Description of Link Aggregation info for + actual subrack, Mxb and Blade Slot Link. + + + + + + + + + + + + + + + + + This class describes the state of the Blade Slot Links with + regards to Vlan info. + + Key attributes: [subrackNum,bladeSlotLink] + + + + + + + + + + Description of Vlans for actual subrack and Blade Slot Link + + + + + + + + + + + + + + + + + + + + + + + + + This class describes the Performance Monitoring function. + + Key attributes: [] + + Possible children: + PmBladeMeasure + PmLink + + + + + + + + Configuration of CPU upper treshold, i.e. when the CPU load + is rising and crosses this treshold then the PMON function + in ISS will raise a CPU alarm. + + + + + + + CPU lower treshold, i.e. when the CPU load + is falling and crosses this treshold then the + PM function in ISS will cease the CPU alarm. + + + + + + + The sampling period during which CPU usage is measured. + This period is given in seconds. + + + + + + + + + + + + + + Memory upper treshold, i.e. when the Memory usage + is rising and crosses this treshold then the PM + function in ISS will raise a Memory alarm. + + + + + + + + + + + + + + Memory lower treshold, i.e. when the Memory usage + is falling and crosses this treshold then the PM + function in ISS will cease the Memory alarm. + + + + + + + Bandwidth upper treshold, i.e. when the Bandwidth + usage is rising and crosses this treshold then the PM + function in ISS will raise a Bandwidth alarm. + + + + + + + Bandwidth lower treshold, i.e. when the Bandwidth usage + is falling and crosses this treshold then the PM function + in ISS will cease the Bandwidth alarm. + + + + + + + The sampling period during which Bandwidth usage is measured. + This period is given in minutes. + + + + + + + + + + + + + + Enabling monitoring of CPU and memory usage and reading + the corresponding values of utilisation in percent. + + Key attributes: [subrackNum,mxbSlot] + + + + + + + + + + Type of measurement to be performed, i.e. CPU or Memory. + + + + + + + + + + + + + + Start or stop performance measurement of a specific type + + + + + + + + + + + + + + This is the value of the usage in percent when + performing the measurement. + + + + + + + This is the value of Memory usage in bytes when + performing a Memory usage measurement. + + + + + + + + + + + + + + + + + + Performance Management Link related data. + + Key attributes: [] + + Possible children: + PmBwMeasure + PmStatistics + + + + + + + + Enabling monitoring Bandwidth usage and reading the + corresponding values of utilisation in percent. + + Key attributes: [subrackNum,bladeSlotLink,mxbSlot] + + + + + + + + + + + Start or stop measuring of bandwidth utilisation. + + + + + + + + + + + + + + This is the value of the average Bandwidth usage in percent + during the configured sampling period. + + + + + + + + + + + This class describes the Performance + Monitoring Statistics; i.e. counters + for each backplane port on the Mxb, + the actual speed used on the port and + if the port operates in full or half duplex mode. + + Key attributes: [subrackNum,bladeSlotLink,mxbSlot] + + + + + + + + + + + Performance Monitoring counter for + received octets. + + + + + + + Performance Monitoring counter for + received Unicast Packets + + + + + + + Performance Monitoring counter for + received Multicast Packets + + + + + + + Performance Monitoring counter for + received Broadcast Packets + + + + + + + Performance Monitoring counter + for number of received discarded octets. + + + + + + + Performance Monitoring counter + for number of received faulty octets. + + + + + + + Performance Monitoring counter + for number of received Unknown Protocol packets. + + + + + + + Performance Monitoring counter for + octets in send buffer. + + + + + + + Performance Monitoring counter for + Unicast Packets in send buffer. + + + + + + + Performance Monitoring counter for + Multicast Packets in send buffer. + + + + + + + Performance Monitoring counter for + Broadcast Packets in send buffer. + + + + + + + Performance Monitoring counter for + Frames with Op code Pause + + + + + + + Performance Monitoring counter for + Frames exceeding maximum frame size. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MyBsModel_1.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MyBsModel_1.xsd new file mode 100644 index 0000000000..5ec3434a65 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/MyBsModel_1.xsd @@ -0,0 +1,502 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Struct description + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A named type which is an MO Reference pointing to + * MyClass + + + + + + + + + + + + + + + + + + + + + + + + + + Enum which can be yes or no + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This is a class which can be assigned as an attribute of ChildClass. + Key attribute is 'id'. + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + My Test Class + The class hierarky looks like this: + + +==========+ + |MountPoint| + +==========+ + / \ + / \ + +=======+ +=======+ + | Blipp | |MyClass| + +=======+ +=======+ + | + | + +==========+ + |ChildClass| + +==========+ + + Key attributes: [id1,id2] + + Possible children: + ChildClass: + Definition of children under MyClass + + + + + + + + Test class identifyer - part1 + + + + + + + + + + + + + + Test class identifyer - part2 + + + + + + + + + + + + + + Date + + + + + + + + + + + + + + Date2 - named type + + + + + + + + + + + + + + + + + + + + + + + + + + Attribute description. + + + + + + + + + + + + + + + + + Child of MyClass + + Key attributes: [id] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/bs_mim.xml b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/bs_mim.xml new file mode 100644 index 0000000000..8846c05878 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/bs_mim.xml @@ -0,0 +1,1187 @@ + + + + + + + + + + + The administrative state of blades/blade systems. + Reflects what the administrator has done. + + + + + + + + + + + + + The operational state of blades/blade systems. + Reflects if the entity is on/off. + + + + + + + + + + + + The availability state of blades/blade systems. + Reflects if the entity is useable or not. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The bus type used by a blade. + + + + + + + + + + + + + + Parent of all blade systems. + + + + + + + + This class describes a Blade System. + It serves as a mountpoint for the blade system specific model. + + + + + + + A user friendly Blade System name, must be set at creation and can be + changed when BS is locked. + + + + + + + + An identifier for the BS. A new integer has to be used every time a new + BS is created. + + + + + + + + + + + + + + + + The identity of the Software Group (SWG) that the BS implements. + + + + + + + + + The revision of the Software Group (SWG) that the BS implements. + + + + + + + + + The identity of the correction package (CXR) applied to the SWG. + + + + + + + The revision of the correction package (CXR) applied to the SWG + + + + + + The administrative state of the Blade System. + + + + + + The operational state of the Blade System. + + + + + + The availability status of the Blade System. + + + + + + + The identity of the Blade System domain the Blade system belongs to. + + + + + + + + + IP address of the Blade System OaM Master. + + + + + + + + Locks the blade system. If the system already is locked the + action does nothing. + + + + + + + + + Unlocks the blade system. If the system already is unlocked the + action does nothing. This operation orders the blade system to be unlocked. + However the blade system may not be unlocked even if this order works. + See the operational state to figure out if the unlock succeded. + + + + + + + + + Shuts down the blade system. If the system already is locked the + action does nothing. + + + + + + + + + Action to create a backup file from the current + Blade System. It is stored locally on disk. + An instance of the MO class + Software/Jobs/Backup/Create is created as a log of this + action. + + + + + + + A user specified backup creation job name + + + + + + + + + Action to restore a backup into the current + Blade System. It is fetched from the local disk. + An instance of the MO class + Software/Jobs/Backup/Restore is created as a log of this + action. + + + + + + + The IS site local backup identity + + + + + + + A user specified backup restore job name + + + + + + + + + Action to upgrade the current Blade System. Files + are fetched from the local disk storage. + An instance of the MO class + Software/Jobs/Upgrade is created as a log of this + action. + + + + + + + A user specified ugrade job name + + + + + + + The Ericsson product number of blade system software group + + + + + + + The Ericsson revision of blade system software group + + + + + + + The Ericsson product number of software correction package + + + + + + + The Ericsson revision of software correction package + + + + + + + The Ericsson product number of blade software group + + + + + + + The Ericsson revision of blade software group + + + + + + + The maximum time allowed to finish the entire + software change procedure (minutes). + Default value depends on blade system software. + + + + + + + + + + + + This class describes a Blade. + A Blade is identified by the subrack and slot number. + + + + + + + A reference to the associated subrack (i.e. the value of 'subrackId' + for the associated subrack) + + + 031 + + + + + + The slot number for this Blade within the subrack. + + 025 + + + + + + + The slot label of the blade. Will only be set at creation. + This should be used in alarms related to the slot to inform the + operator of what position in the subrack the blade is located in. + E.g. for GEM subracks it will be a string like X02 for slot 0 + up to X80 for slot 25. + + + + + + + + An identifier for the BS to which the blade belongs. + A value of 0 means that the blade is inserted in the subrack but it + has not been configured to any BS yet. + + + + + + + The type of the Blade defined by a string BladeTypeId. + + + + + + + + The expectedregistered SW group id of the Blade. + + + + + + The registered SW group revision state of the Blade. + + + + + + The installed SW group id of the Blade. + + + + + + The installed SW group revision state of the Blade. + + + + + + + Indicates if this blade is a BSOM candidate. + + + + + + + Set to protected if blade sholud no be knocked out before the + switch blade. + + + + + + + A user friendly Blade name, always possible to set. + Default value indicates HwmBladeType and used slot. + + + + + + + The administrative state of the Blade. + + + + + + + The operational state of the Blade. + + + + + + The availability status of the Blade. + + + + + + The type of maintenance bus on the found Blade + + + + + + The Product Number of the found Blade + + + + + The Product Revision of the found Blade. + + + + + The Serial Number of the found Blade. + + + + + The Product Name of the found Blade. + + + + + The Vendor name of the found Blade. + + + + + The manufacturing date of the found Blade. + + + + + The aggregated MAC address of the found Blade. + + + + + + The left link MAC address of the found Blade. Only used by some blades + + + + + + + The right link MAC address of the found Blade. Only used by some blades + + + + + + The date when the blade was last changed. + + + + + + + + + IP address on the ISBS subnet. + + + + + + + + IP address on the ISOB subnet. + + + + + + + + IP address on the ISLCT subnet. + + + + + + + + Locks the blade. If the blade already is locked the + action does nothing. This operation orders the blade to be locked. + It may however take long time before it happens. + + + + + + + + + Unlocks the blade. If the blade already is unlocked the + action does nothing. This operation orders the blade to be unlocked. + However the blade may not be unlocked even if this order works. + See the operational state to figure out if the unlock succeded. + + + + + + + + + Shuts down the blade. If the blade already is locked the + action does nothing. + + + + + + + + Action to upgrade the current blade. Files + are fetched from the local disk storage. + An instance of the MO class + Software/Jobs/Upgrade is created as a log of this + action. + + + + + + + + + + + + + + + + + + + + + A Blade may have one or more resilient interfaces + to the backplane. Such an interface is called a + Link Service Access Point (LSAP), which is the + point where you access layer 2. LSAPs are + automatically created and deleted along with the + hosting blade. + + + + + The id of a LinkSap is a number from 0 to X within the slot. + + + + + + + + + The MO branch where the Blade System specific + Network resources are mapped to blade system + network requirements to common Integrated Site + resources. This activity must be performed before + a new blade or blade system successfully can be + unlocked via the Hardware service. Some blade + system designers have partly pre-registered their + network requirements, while others demand that + you read the corresponding information from + separate Operation Procedure Instructions and + manually register the blade system network + requirements. The pre-registered network + requirements automates parts of the blade + system-specific configuration activity. + + In an Integrated Site, the blade systems obtain + their actual network configuration dynamically in + runtime. When you change the network + configuration it will affect blade systems. In + order to minimize the disturbance of active blade + systems, the changes are normally applied in a + separate storage which not is visible to the + blade systems. In order to make use of the new + unpublished configuration, it must explicitly be + published by altering the updateMode. If the new + settings introduces severe problems the + configuration can be reverted to the old settings + by altering the updateMode. + + The common Network configuration including + updateMode and its publish mechanism is specified + in a separate MIM called CPD MIM. + + + + + + + + A BS VLAN is mapped to one IS VLAN. A BS VLAN is + the requirement a Blade System have of an IS + VLAN. Different instances of a Blade System type + may call their BS VLANs the same thing but in the + end the IS Site Designer can choose to map them + to the same or different IS VLAN. + + BS VLANs can either be created manually by the + operator or they can be automatically created + from pre-registered network requirements bundled + with the Blade System software. Regardless of + how they are created, each one needs to be + mapped to an IS VLAN before the blades can be + unlocked. The mapping is done with the + 'isVlanRef' attribute. + + Different instances of a Blade System type may call + their BS VLANs the same thing but in the end the IS + Site Designer can choose to map them to the same or + different IS VLAN. + + + + Name of the BS VLAN. It is unique within the Blade System. + + + + + + + Short description of the BS VLAN. + + + + + + Setting the private attribute to true, means + that the corresponding IS VLAN not can be + used by other Blade Systems. The IS VLAN is + private for this particular Blade System. + + + + + + The mapping to a corresponding IS VLAN. This + mapping must be done before the blades of the + Blade System can be unlocked. + + + + + + + + A BS Logical Network (BSLN) is associated to + one IS Logical Network. A BS Logical Network + is the requirement a Blade Systems have of an + IS Logical Network. + + BS Logical Networks can either be created + manually by the operator or they can be + automatically created from pre-registered + network requirements bundled with the Blade + System software. Regardless of how they are + created, each one needs to be mapped to an IS + Logical Network before the blades can be + unlocked. The mapping is done with the + 'isLogicalNetworkRef' attribute. + + Different instances of a Blade System type may call + their BS Logical Networks the same thing but in + the end the IS Site Designer can choose to map + them to the same or different IS Logical + Network. + + + + Name of the BS logical network. It is unique within the Blade System. + + + + + + + Short description of the BS Logical Network. + + + + + + Flag that shows whether the BS Logical Network + is private for this Blade System or if it may + be shared among several Blade Systems. + + + + + + Reference to the corresponding IS Logical Network. + + + + + + + + A BS Subnet (BSSN) is associated to one IS + Subnet. A BS Subnet Network is the requirement a + Blade Systems have of an IS Subnet. + + BS Subnets can either be created manually by the + operator or they can be automatically created + from pre-registered network requirements bundled + with the Blade System software. Regardless of + how they are created, each one needs to be + mapped to both a BS VLan and an IS Subnet before + blades can be unlocked via the Hardware service. + Each BS Subnet contains one or more BS Subnet + Segments. The mappings are done with the + 'bsVlanRef' and 'isSubnetRef' attributes. + + Different instances of a Blade System type may + call their BS Subnets the same thing but in the + end the IS Site Designer can choose to map them + to the same or different IS Subnet. + + + + Name of the BS Subnet. It is unique within the BS Logical Network. + + + + + + + Short description of the BS Subnet. + + default + + + + The mapping to a corresponding BS Vlan. This + mapping must be done before the blades of the + Blade System can be unlocked. + + + + + + The mapping to a corresponding IS Subnet. This + mapping must be done before the blades of the + Blade System can be unlocked. + + + + + + + + A BS Subnet Segment (BSSNS) is associated to one + IS Subnet Segment. A BS Subnet Segment is the + requirement a Blade Systems have of an IS Subnet + Segment. + + BS Subnet Segments can either be created manually + by you or they can be automatically created from + pre-registered network requirements bundled with + the Blade System software. Regardless of how they + are created, each one needs to be mapped to an IS + Subnet Segment before the blades can be unlocked + via the Hardware service. The mapping is done + with the 'isSubnetSegmentRef' attribute. + + Different instances of a Blade System type may + call their BS Subnet Segments the same thing but + in the end the IS Site Designer can choose to + map them to the same or different IS Subnet + Segment. + + + + Name of the BS Subnet Segment. It is unique within the BS Subnet. + + + + + + + Short description of the BS Subnet Segment. + + + + + + Number of required IP addresses in the IS Subnet Segment. + + + + + + Flag that controls whether the corresponding IS + Subnet Segment is required to have DHCP enabled + or not. + + + + + + Flag that controls whether the corresponding IS + Subnet Segment is required to have a router + configured or not. + + + + + + The mapping to a corresponding IS Subnet + Segment. The mapping here must be done before + the blades of the blade system can be unlocked. + + + + + + + + + + There is a BS VLAN Service Access Point (BSVSAP) + for each Link Service Access Point that an IS + VLAN straddles. It is per BS VLAN Service Access + Point that certain VLAN properties, such as if it + is mandatory to enable isolation protection. + + BS VLAN Service Access Points can either be + created manually by the operator or they can be + automatically created from pre-registered network + requirements bundled with the Blade System + software. Regardless of how they are created, + each one needs to be mapped to an Link SAP before + the blades can be unlocked. The mapping is done + with the 'linkSapRef' attribute. + + + + Name of the BS VLAN SAP. It is unique within the BS VLAN. + + + + + + + + + Short description of the BS VLAN SAP. + + + + + + + + Flag which controls whether this BS VLAN SAP + makes static or dynamic use of the + corresponding IS VLAN. + + + + + + + + Flag which controls whether this BS VLAN SAP should be + isolation protected or not. + + + + + + + + A mapping to the corresponding Link Service Access Point. + + + + + + + + + + A BS IP Traffic Class (BSIPTC) is the + requirement a Blade System have of an IS IP + Traffic Class. + + BS IP Traffic Classes can either be created + manually by you or they can be automatically + created from pre-registered network requirements + bundled with the Blade System software. Regardless + of how they are created, each one needs to be + mapped to an IS IP Traffic Class before the blades + can be unlocked via the Hardware service. The + mapping is done with the 'isIpTrafficClassRef' + attribute. + + Different instances of a Blade System type may + call their BS IP Traffic Classes the same thing but + in the end the IS Site Designer may choose to + map them to the same or different IS IP Traffic + Classes. + + + + The name of the BS IP Traffic Class. It is + unique within the Blade System. + + + + + + + A short description of The BS IP Traffic Class. + + + + + + The mapping to a corresponding IS IP Traffic + Class. This mapping must be done before the + blades of the Blade System can be unlocked. + + + + + + + + A BS LAN Traffic Class (BSLANTC) is the + requirement a Blade System have of an IS LAN + Traffic Class. Different instances of a Blade + System type may call their BS Traffic Classes + the same thing but in the end the IS Site + Designer may choose to map them to the same or + different IS LAN Traffic Classes. + + BS LAN Traffic Classes can either be created + manually by you or they can be automatically + created from pre-registered network requirements + bundled with the Blade System software. Regardless + of how they are created, each one needs to be + mapped to an IS LAN Traffic Class before the blades + can be unlocked via the Hardware service. The + mapping is done with the 'isLanTrafficClassRef' + attribute. + + Different instances of a Blade System type may + call their BS LAN Traffic Classes the same + thing but in the end the IS Site Designer may + choose to map them to the same or different IS + LAN Traffic Classes. + + + + Name of the BS IP Traffic Class. It is unique within the Blade System. + + + + + + + Short description of the BS IP Traffic Class. + + + + + + The mapping to a corresponding IS LAN Traffic + Class. This mapping must be done before the + blades of the Blade System can be unlocked. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1 + + + + + + + + + + 1 + + + + + + + + + + + + + + + + + 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/dummy_action_mim.xml b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/dummy_action_mim.xml new file mode 100644 index 0000000000..d691fe0b3f --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/dummy_action_mim.xml @@ -0,0 +1,186 @@ + + + + Exception description + + + + Exception parameter description + + + + + + Exception parameter description + + + + + + + + + + + + + + + + Action with no parameters + + + + Maybe strange to describe void, but here is a description anyway. + + + + + + + Action with one parameter + + + + + + + + + + + + + + + + 0 + 3 + + + + + + + + Action with many parameters, even some optional + + + + + + 0 + 100 + + + + + + + + + 0 + 3 + + + + + + + + + 0 + 3 + + + + + + + + + 0 + 3 + + + + 0 + + + + parameterdescription + + + + + + + + + Action with parameters with complex datatypes + + + + Here is a description of the return value for this action. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/hwm_mim.xml b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/hwm_mim.xml new file mode 100644 index 0000000000..a7a18b0070 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/hwm_mim.xml @@ -0,0 +1,631 @@ + + + + + + + + + + + + Information of how the slot is used. + + + + + + + + + + + + + + + + + + + + + + + + + + + The purpose of the Hardware Management function is to make it possible to maintain + the Hardware Inventory (HWI) for the Integrated Site and to present its content via ISM + or to a management system. And also to maintain the subracks usage. + + + + + + + The subrack,slot of the active om SIS. The format is "subrack.slot". + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Creates the base IS infrastructure. + This is noramlly done at factory. + + + + + + + + + Exports the Hardware Inventory via FTP. + This is an asyncrounous operation. The file exported + will have the following name format: + <node>.<timestamp>.HWI.xml.tar.gz + + + + + + + The host to which the data should be sent to + + + + + + The username on the host to be used during the FTP transfer. + + + + + + The pasword of the user + + + + + + The path were to put the file + + + + + + + + + + This class describes a Blade type. + + + + + The blade type number like CNA12801 + + + + + + The blade software group index link CSX10138 + + + + + + The blade software group revision + + + + + + The name of the Blade Type. + + + + + + The width of the blade in number of slots. + + + + + + + + + The 1G links used by the blade type , like 0,1, counted from + the leftmost backplane position. + + + + + + + + The 1G links used for link aggregation by the blade type , like 0-1, + counted from the leftmost backplane position. + + + + + + + + True if possible to read product info via the maintenance bus. + + + + + + + True if this is a Main Switch blade type. + + + + + + + Only valid for main switch blades. A list of slots that have 1G link. + Could be a single slot or a range or a combination thereof. + E.g. 1-24, or 1,3-13,15-24. + + + + + + + + Only valid for main switch blades. Specifies which slots can be used + for link aggregation. Ranges are specified in the form 1-12,13-24. + + + + + + + + + + + This class describes a Blade system domain. + + + + + The blade system domain name. + + + + + + The description of the blade system domain. + + + + + + + + + + This class describes the subrack. + + + + + + + + Identifies a certain subrack. + + 031 + + + + + + The type of subrack. + + + + + A user friendly Subrack name. + + + + + The subrack position in the cabinet. + + + + + The cabinet position in the site. + + + + + The site location, e.g. the visiting address. + + + + + + Available slots for 1G switch links. Information taken from the type + of main switch blade that is created in the subrack. + + + + + + + + Available slots for 10G switch links. Information taken from the type + of main switch blade that is created in the subrack. + + + + + + + + Links ranges for (1G) link aggregation. Information taken from the + type of main switch blade that is created in the subrack. + + + + + + + + The value of the physical plug 0. + + + + + + + + The value of the physical plug 1. + + + + + + + + The value of the physical plug 3. + + + + + + + + The BS SWG Id of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS SWG Revision of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS CXR Id (if any) of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS CXR Revision (if any) of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL SWG Id of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL SWG Revision of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL CXR Id (if any) of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL CXR Revision (if any) of the left MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS SWG Id of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS SWG Revision of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS CXR Id (if any) of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BS CXR Revision (if any) of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL SWG Id of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL SWG Revision of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL CXR Id (if any) of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + The BL CXR Revision (if any) of the right MXB in the subrack. + If not given the system will use the same as the + MXB in subrack 0. This might not be corect however. + + + + + + + + + This class corresponds to slots, there is one instance + for each slot. The slots are grouped per subrack. A slot is + identified by subrack Id and slot number). The subrack Id for a slot + identifies in the subrackTable the subrack that the slot belongs + to. + + + + + + The value of this object identifies the + slot position within the subrack. + + + 025 + + + + + + + See HwmSlotState description. + + + + + + + + The value of this object identifies the Blade System that uses this + slot. An instances of this object will only have meaning in a + conceptual row if the value of hwmSlotState instance is either + usedOccupied or usedEmpty in the same conceptual row, + i.e. there is an Blade System created using this slot. (If + no Blade System is using the slot, the value will be "-".) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/instance.xml b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/instance.xml new file mode 100644 index 0000000000..e39152cada --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/instance.xml @@ -0,0 +1,240 @@ + + + + + + + + + + + + + + + + + + + + + + + bs_localhost_101 + + + + + + + + + name1 + true + + 10.11.12.13 + + AA:BB:CC:DD:EE:FF + + /IntegratedSite:model/Is/BladeSystems/MyBsModel[name='bs_localhost_101']/MyBsModel:model/MyClass[id1='Obj'][id2='1']/ChildClass[id='Obj2'] + + + + + name2 + false + 20.21.22.23 + 01:02:03:04:5:6 + + MyClass[id1='Obj'][id2='1']/ChildClass[id='Obj3'] + + + + + + + Obj + + 1 + 2006-03-08T03:00:00.9+03:00 + 2006-03-15T22:59:58.99-01:00 + + 0 + 1 + 3 + + + + + hei + 1 + + + + + hopp + + 2 + + + + hei + hopp + + + yes + + + + + 0 + locked + + + hei + 1 + + + + hopp + 2 + + + sa + 3 + + + sa + 4 + + + + 1 + 1.0 + true + + + hei + false + + + Obj2 + /IntegratedSite:model/Is/BladeSystems/MyBsModel[name='bs_localhost_101']/MyBsModel:model/Blipp[id='name1'] + + /IntegratedSite:model/Is/BladeSystems/MyBsModel[name='bs_localhost_101']/MyBsModel:model/MyClass[id1='Obj'][id2='1'] + + + + Obj3 + ../../Blipp[id='name2'] + + Dummy/MyClass[id1='Obj'][id2='1'] + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim.xsd new file mode 100644 index 0000000000..e0534e8e14 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim.xsd @@ -0,0 +1,486 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim2.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim2.xsd new file mode 100644 index 0000000000..da6ff6bd7d --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/mim2.xsd @@ -0,0 +1,506 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/nc.xsd b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/nc.xsd new file mode 100644 index 0000000000..60a320a61e --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/nc.xsd @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + diff --git a/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/swm_mim.xml b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/swm_mim.xml new file mode 100644 index 0000000000..90afcb2b68 --- /dev/null +++ b/lib/xmerl/test/xmerl_xsd_SUITE_data/sis/swm_mim.xml @@ -0,0 +1,881 @@ + + + + + + + + + + + + + + + Interpretation of given filename and path . + + + + + + + + + + + + + + Interpretation according to existing files. + + + + + + + + + + + + + + Type of a load module container. + + + + + + + + + + + + + + + + + + Indicates status of software groups. A software group is + complete if all included load module containers have been + downloaded and unpacked correctly. A software group is inconsistent + if the checksums of the load module containers do not match the + information in the system information CXP, or if the XML + data could not be registered. + + + + + + + + + + + + + + Data to specify job progress, during its execution. + + + + + + + + Indicator of job status. + A job should be started immediately, but could be postponed + if the total load on the system would become too high. + + + + + + + + + + + + + + + Possible results of a job action. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Data to specify FTP server info, such as host, user, + password and path, to locate correct files or destination + for files. + + + + + + + + + + + + + + Absolute path including filename. + + + + + + + + + Specification of a blade when an upgrade job is ordered for a + specific blade. This data always belongs to and is included in + an upgrade job for a blade system. + + + + + + + + + + + + + + + + + + + + + + + + Container of files of data, or binary executables, needed to run the system. + + + + + + + + + + + + + + + + + + + + + + Action to delete SoftwareDeliveryPackage. + + + + + + + + + + Contains one or more SoftwareDeliveryPackage. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Action to delete Software Group. + + + + + + + + + + All available backups locally stored. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Action to export backup file to FTP server from + local disk storage. An instance of the class + Software/Jobs/Backup/Export is created as a log of this + action. + + + + + + + + + + + + + + + + + + + Absolute path including filename. + + + + + + + Action to delete backup. + + + + + + + + + + Information and cause of all currently active software configuration alarms. + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO contains information about requested, ongoing, + and completed software file download jobs. To start a + download job the operator calls an action Inventory class, + and a new instance of this MO is created. + For load regulating reasons a requested job may not start + immediately. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO handles upgrade jobs towards the system. The operator + may specify a specific blade to run the upgrade on, instead of + running an upgrade on the entire blade system. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The maximum time allowed for the SW Upgrade + job to finish. After this time, the job will be interrupted. + The value 0 means that MaxTime will be given the + timer value registered with the Blade System Software Group + Version. If no such value has been registered, + MaxTime will be given a system default timer value. + + + + + + + + + + + + + + + + + + This MO handles creation of backups of the system. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO handles restore of backups of the system. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This MO handles import of backup files from the FTP server. + The backup file is stored locally, but not loaded into the system. + + + + + + + + + + + + + + + + + + + + This MO handles export of locally stored backup files to + the FTP server. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Describes the Software management service + in the Integrated Site services management functional area (MFA). + + + + + + + System created data for information and overview. + Some data is created as a result of an action called by the + operator. + + + + + Action to download file/s from FTP server to + local disk storage. An instance of the MO class + Software/Jobs/DownloadFile is created as a log of this + action. + + + + + + + + + + + + + + + + + + + Absolute path including filename. + + + + + + + + + + + + + Action to import backup file from FTP server to + to local disk storage. An instance of the MO class + Software/Jobs/Backup/Import is created as a log of this + action. + + + + + + + + + + + + + + + + + + + Absolute path including filename. + + + + + + + + + Subclass to top class Software. Parent of + Jobs classes: + DownloadFile, + Upgrade, + Backup. + Contains system created data through ordered job actions. + + + + + + + Subclass to class Jobs. Parent of + Jobs classes: + Create, + Restore + Import, + Export. + + Contains system created data through ordered backup job actions. + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1 + 1 + + + + + + + + + + + + + + 1 + 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1 + 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- cgit v1.2.3