ONF Stratum for Cassini - Read Me

This component provides a common layer between PHAL database and the TAI interface. It
will call functions from TAI interface (the wrapper) directly to get/set information for a
specific TAI network interface.
OpticsAdapter
The optics adapter helps PHAL to access the PHAL database. It basically create a database
get or set request based on the function call from PHAL layer and returns the result.
TaiSwitchConfigurator
This component provides a default optical module and network interface configurations and
it is responsible for configuring PhalDB during the initialization.
TaiPhal
Enables PhalBackendInterface functionality for TAI. This component should manage the
gNMI event writters and TAI wrapper state. Also, it should be able to help collecting
transponder states.
Note: This component is currently not implemented.
PHAL Configuration
The PhalInitConfig was extended with the PhalOpticalModuleConfig config support.
In PhalOpticalModuleConfig , there will be one or many network interfaces in a module,
each module or network interface includes a special field called vendor_specific_id which
is used for storing a vendor specific identifier for different implementation. In this case(TAI),
this ID is repersent the object ID in TAI abstraction.
Here is an example of module config:
optical_modules {
module: 1 # the 1-based index of the module
network_interfaces {
network_interface: 1 # the 1-based index of the network interface
vendor_specific_id: 10 # the object id of the network interface
}
vendor_specific_id: 1 # the object id of the module
}
The new attributes were introduced into PhalDB . Like PHAL config, there exists multiple
optical module and each module can include several optical network interfaces.
message OpticalModule {
message NetworkInterface {
int32 id = 1;
uint64 frequency = 2; // Measured in Hz.
double input_power = 3; // Measured in dBm.
double output_power = 4; // Measured in dBm.
double target_output_power = 5; // Measured in dBm.