3fd6e8d500
Changes to allow starting per asic services like swss and syncd only if the platform vendor codedetects the asic is detected and notified. The systemd services ordering we want is database->database@->pmon->swss@->syncd@->teamd@->lldp@ There is also a requirement that management, telemetry, snmp dockers can start even if all asic services are not up. Why I did it For VOQ chassis, the fabric cards will have 1-N asics. Also, there could be multiple removable fabric cards. On the supervisor, swss and syncd containers need to be started only if the fabric-card is in Online state and respective asics are detected by the kernel. Using systemd, the dependent services can be in inactive state. How I did it Introduce a mechanism where all ASIC dependent service wait on its state to be published via PMON to REDIS. Once the subscription is received, the service proceeds to create respective dockers. For fixed platforms, systemd is unchanged i.e. the service bring up and docker creation happens in the start()/ExecStartPre routine of the .sh scripts. For VOQ chassis platform on supervisor, the service bringup skips docker creation in the start() routine, but does it in the wait()/ExecStart routine of the .sh scrips. Management dockers are decoupled from ASIC docker creation.
27 lines
556 B
Bash
Executable File
27 lines
556 B
Bash
Executable File
#!/bin/bash
|
|
|
|
is_chassis_supervisor() {
|
|
if [ -f /etc/sonic/chassisdb.conf ]; then
|
|
true
|
|
return
|
|
fi
|
|
false
|
|
return
|
|
}
|
|
|
|
check_asic_status() {
|
|
# Ignore services that are not started in namespace.
|
|
if [[ -z $DEV ]]; then
|
|
return 0
|
|
fi
|
|
|
|
# For chassis supervisor, wait for asic to be online
|
|
/usr/local/bin/asic_status.py $SERVICE $DEV
|
|
if [[ $? = 0 ]]; then
|
|
debug "$SERVICE successfully detected asic $DEV..."
|
|
return 0
|
|
fi
|
|
debug "$SERVICE failed to detect asic $DEV..."
|
|
return 1
|
|
}
|