F5OS RESTCONF path explainer
Paste an F5OS RESTCONF path and get it decoded segment by segment: the YANG module prefix, the container hierarchy, list keys such as tenant=tenant1, and the module:node prefixing convention. It also explains the port 8888 /restconf versus port 443 /api duality from F5OS 1.8. Local and offline.
网络Modules this tool can describe
A finite list. If a path uses a module that is not here, the structure is still decoded and the description is withheld rather than guessed.
- openconfig-system
- system-level configuration and state: hostname, clock, DNS, AAA, logging
- openconfig-interfaces
- physical and logical interfaces, their configuration and counters
- openconfig-vlan
- VLAN definitions and interface membership
- openconfig-platform
- hardware inventory: chassis components, slots, transceivers
- openconfig-lacp
- link aggregation control protocol groups and members
- f5-tenants
- tenants: the guest BIG-IP instances a VELOS or rSeries system hosts
- f5-system-partition
- chassis partitions on VELOS - a group of blades presented as one system
- f5-system-slot
- slot assignment: which blade belongs to which partition or tenant
- f5-tenant-images
- the tenant image inventory available to launch instances from
- f5-system-image
- F5OS platform images on the controller itself
- f5-cluster
- controller clustering and node roles
- f5-utils-file-transfer
- file import and export operations on the platform
API endpointGEThttps://ronutz.com/api/v1/f5os-restconf-path-explainerDocumented, not served. Opens the specification.
参考
- F5OS RESTCONF API
- RFC 8040 - RESTCONF Protocol
- OpenConfig - vendor-neutral YANG models
- F5 DevCentral codeshare, 2 December 2022 - automating F5OS config backup: as of F5OS 1.8, ":8888/restconf" can be replaced with ":443/api"
- F5OS-A 1.8.0 fixes and known issues, item 1572137-2 - upload and download API should work with "/api" and "/restconf"