No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Principles

Principles

This section describes the architecture and design principle of OPS.

The OPS is developed on Huawei Versatile Routing Platform (VRP). It uses open APIs to work with VRP's management plane, control plane, and data plane, allowing for function expansion on a device. Figure 3-33 shows the OPS architecture.

Figure 3-33 OPS architecture

RESTful APIs of the OPS are designed based on the Representational State Transfer (REST) structure. REST defines the following constraints and rules for a system architecture:
  • Resource identification by uniform resource identifiers (URIs): All the objects in the REST structure are abstracted as resources, and each resource is identified by a unique URI.

  • Standard methods: Operations are performed on resources using standard Hypertext Transfer Protocol (HTTP) methods, such as Get, Put, Post, and Delete.

  • Stateless communication: The session status is maintained by the client.

Following the preceding rules, web services can be designed based on system resources. Clients made by different programming languages can use standard HTTP methods to query and change resource status.
For example, you can send the following HTTP request to a device to obtain information about the startup files of the device. Here, /cfg/startupInfos/startupInfo is the URI of the startup file information. When the device receives the request, it sends a response to the client.
  • Example of an HTTP request

    GET /cfg/startupInfos/startupInfo HTTP/1.1
    
    <?xml version="1.0" encoding="UTF-8"?>
    <startupInfo>
    </startupInfo>
    
  • Example of an HTTP response

    HTTP/1.1 200 OK
    
    <?xml version="1.0" encoding="UTF-8"?>
    <rpc-reply>
      <data>
        <cfg xmlns="http://www.huawei.com/netconf/vrp" format-version="1.0" content-version="1.0">
          <startupInfos>
            <startupInfo>
              <position></position>
              <nextStartupFile>flash:/vrpcfg.cfg</nextStartupFile>
              <configedSysSoft>flash:/V100R003C00SPC100.cc</configedSysSoft>
              <curSysSoft>flash:/V100R003C00SPC100.cc</curSysSoft>
              <nextSysSoft>flash:/V100R003C00SPC100.cc</nextSysSoft>
              <curStartupFile>flash:/vrpcfg.cfg</curStartupFile>
              <curPatchFile>NULL</curPatchFile>
              <nextPatchFile>NULL</nextPatchFile>
            </startupInfo>
          </startupInfos>
        </cfg>
      </data>
    </rpc-reply>
    

RESTful APIs can be invoked in an embedded running environment (ERE) to enable third-party scripts to run in the system. Currently, the OPS integrates the Python running environment and can run Python scripts.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 58870

Downloads: 3621

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next