Fprtool Backend Development
Following decommissioning current flight tools (ft) announcement, here are some main points for new flight tools (fprtool) development:
- The only difference from code side is the top-level component module. Meanwhile, other modules (flight-tools-api, flight-tools-impl, etc) are the same.
- fprtool:
fpr-tools-service
- ft:
flight-tools-service
- Deployment in flight staging (flighttest03, flighttest04, flighttest05) will be supported until decommission of Ansible Tower. For Jenkins pipeline, you can use https://jenkins.noc.tvlk.cloud/job/flight-fprtool-release/. When deploying on Ansible Tower, enter
fprtool as service_name in the prompt instead of ft . After deployed, make sure to stop ft service in flight staging by connecting to it via ssh and run supervisorctl stop ft-embbeded because fprtool and ft listen to the same port, 29080.
- For debugging, fprtool will use port number 8766 instead of 8799 (ft debug port number) to equalize with other fpr services.
If there's any suggestion or inquiries, feel free to reach me. Thank you.