datastores
此内容尚不支持你的语言。
AsterNOS datastore operations
copy-config
Section titled “copy-config”| Path | Access |
|---|---|
| /copy-config/input | Read-Write |
| /copy-config/input/source | Read-Write |
| /copy-config/input/target | Read-Write |
/copy-config/input
Section titled “/copy-config/input”Path
/copy-config/input
Node Type
container
Access
Read-Write
/copy-config/input/source
Section titled “/copy-config/input/source”Path
/copy-config/input/source
Node Type
leaf
Access
Read-Write
Data Type
Constraints
Multiple constraints:
- The uri type represents a Uniform Resource Identifier (URI) as defined by the rule ‘URI’ in RFC 3986.
Objects using the uri type MUST be in US-ASCII encoding, and MUST be normalized as described by RFC 3986 Sections 6.2.1, 6.2.2.1, and 6.2.2.2. Characters that can be represented without using percent-encoding are represented as characters (without percent-encoding), and all case-insensitive characters are set to lowercase except for hexadecimal digits within a percent-encoded triplet, which are normalized to uppercase as described in
Section 6.2.2.1 of RFC 3986.
The purpose of this normalization is to help provide unique URIs. Note that this normalization is not sufficient to provide uniqueness. Two URIs that are textually distinct after this normalization may still be equivalent.
Objects using the uri type may restrict the schemes that they permit. For example, ‘data:’ and ‘urn:’ schemes might not be appropriate.
A zero-length URI is not a valid URI. This can be used to express ‘URI absent’ where required.
In the value set and its semantics, this type is equivalent to the Uri SMIv2 textual convention defined in RFC 5017.
- Enumeration with options:
- startup
- running
Mandatory
Yes
/copy-config/input/target
Section titled “/copy-config/input/target”Path
/copy-config/input/target
Node Type
leaf
Access
Read-Write
Data Type
Constraints
Multiple constraints:
- Enumeration with options:
- startup
- The uri type represents a Uniform Resource Identifier (URI) as defined by the rule ‘URI’ in RFC 3986.
Objects using the uri type MUST be in US-ASCII encoding, and MUST be normalized as described by RFC 3986 Sections 6.2.1, 6.2.2.1, and 6.2.2.2. Characters that can be represented without using percent-encoding are represented as characters (without percent-encoding), and all case-insensitive characters are set to lowercase except for hexadecimal digits within a percent-encoded triplet, which are normalized to uppercase as described in
Section 6.2.2.1 of RFC 3986.
The purpose of this normalization is to help provide unique URIs. Note that this normalization is not sufficient to provide uniqueness. Two URIs that are textually distinct after this normalization may still be equivalent.
Objects using the uri type may restrict the schemes that they permit. For example, ‘data:’ and ‘urn:’ schemes might not be appropriate.
A zero-length URI is not a valid URI. This can be used to express ‘URI absent’ where required.
In the value set and its semantics, this type is equivalent to the Uri SMIv2 textual convention defined in RFC 5017.
Mandatory
Yes