NetworkDesc
NetworkDesc is the description of a network in the most general sense, either AccessNetwork, CoreNetwork, or EdgeNetwork.
Name field of tag name
Name of the network section. Only accepts Kubernetes naming formats with maximum size of 63 characters.
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.
Scopes field of tag scopes
Scopes are optional logical separators. The Workloads in the different scopes would not recognize each other and the Operator would not populate their link information to each other.
Profiles field of tag profiles
Profiles are arbitrary, vendor-defined options that could be disabled or enabled to add or remove features from a particular Workload. The enabled profiles are the ones that are explicitly listed in the Network's profile list.
Scheduling field of tag scheduling
Optional Scheduling Constraints for the Network's pods, based on Kubernetes logic.
Labels field of tag labels
Optional Labels to be associated with all the resources of this Network, useful for multi-x dimension selection, customized scheduling, or other labeling needs. Several default labels, in compliance with the Kubernetes best practices are applied automatically, but could be overridden by providing custom labels. The labels should respect the Kubernetes label formats, otherwise would cause undefined behavior.
Annotations field of tag annotations
Optional Annotations to be associated with the pods of this network, useful for scoping, custom variable updates, and environment editing. Several default annotations, in compliance with the Kubernetes best practices are applied automatically, but could be overridden by providing custom annotations. If both the Network and Composition Model provide the same annotation, the one from the Network will be used.
Filters field of tag filters
Filters used to pick the slices assigned to this network and by default to all of its network functions. CompositionModels define how the mapping from a Network to an Element object should be done.
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.