FLYNC Model¶
Hint
The main entry point for any FLYNC Model is this class.
- class FLYNCModel¶
Bases:
FLYNCBaseModelRepresents the top-level FLYNC configuration model for a system.
This model aggregates all ECUs, system topology, metadata, and general configuration settings for the entire system.
Parameters¶
- ecuslist of
ECU List of ECU definitions included in the system.
- topology
FLYNCTopology The system-wide topology including external ECU connections and optional multicast paths.
- metadata
SystemMetadata System-level metadata including OEM, platform, and hardware/software information.
- general
FLYNCGeneralConfig , optional Optional general configuration settings applicable system-wide.
- model_post_init(context)¶
Perform post-initialization processing after the model is created.
Following steps are performed:
Populate the solicited-node RX multicast group memberships for each IPv6 address configured in any ECU.
Populate the solicited-node TX multicast group memberships for each ECU based on the RX entries for the same multicast group and VLAN.
- validate_unique_ips()¶
Validate all IPs are unique system wide
- get_all_ecus()¶
Return a list of all ECU names.
- get_ecu_by_name(ecu_name: str)¶
Retrieve an ECU by name.
- get_all_controllers()¶
Return a list of all controllers in all ECUs.
- get_all_interfaces_names()¶
Return all the controller interface names
- get_interfaces_for_ecu(ecu_name: str)¶
Return a list of all interfaces for a given ECU.
- get_system_topology_info()¶
Return system topology details.
- model_config = {'extra': 'forbid'}¶
Configuration for the model, should be a dictionary conforming to [ConfigDict][pydantic.config.ConfigDict].
- ecuslist of
Multicasting¶
See also
Multicast Group Memberships are dynamically collected per-ECU. Go to ECU Multicast Group Memberships to understand how they are populated.
On system-level these Multicast Groups are then validated:
For a multicast group, at least one TX node is expected.
A tx node must reach all rx nodes of the group.
Hint
After successful validation of the Multicast Groups,
the switch config is automatically updated with the relevant group entries in the respective VLANEntry.