TermDesc
TermDesc is the description of a terminal in the most general sense.
Vendor field of tag vendor
Vendor of the provided terminal. Only accepts Kubernetes naming formats with maximum size of 63 characters. Compliant to Open RAN no restrictions are applied other than the formatting to the vendors, but currently, only oai, amr, and srs vendors are officially verified.
Stack field of tag stack
Stack of the network to be deployed. The value mappings are as the followings: 4g-sa Standalone LTE, 4G 4g-nsa Non-Standalone LTE, 4G 5g-sa 5G StandAlone, 5G-SA 5g-nsa 5G Non-StandAlone, 5G-NSA 4g-5g Simultaneous 4G and 5G cells After qualifications for 6G the stack support would be available, but no plans are provided for supporting any older generations.
Model field of tag model
Composition Model used to deploy the network. Only accepts Kubernetes naming formats with maximum size of 63 characters as used for the model names too.
Scheduling field of tag scheduling
Optional Scheduling Constraints for the Network's pods, based on Kubernetes logic.
PostConfiguration field of tag post-configuration
PostConfiguration are generic JSON-path key and value pairs that are used to customize the configuration after the Manager has decided on the final configuration. The key should start with the name of the Element, followed by a dot, then the name of the Application, followed by a dot, and finally the JSON-path of the key to be updated. For example: "oai-amf.amf.SBI.Interface[0].IPv4Addr" The configuration file for the Element has to be in one of the formats supported by Panacea.